Saying you want to actively geoengineer your way out of a problem isn't "the same thing" as having passively geoengineered your way into a problem.
The way I see it, if we want to inhabit this planet for the next several hundred thousand years, eventually natural variations will arrive that swamp anything we've done in our usual passive, uncoordinated fashion. So if we want to keep living here, we're going to need to figure out how to set the world's thermostat. Might as well start working the problem now.
Yes, that's the point. The point is that humans should own the influence they have over the world, and put that influence to use.
As opposed to trying to flinch away from it and pretend it doesn't exist. And then acting surprised when that doesn't make their influence go away - and merely makes it unguided, purposeless and often harmful.
I imagine they are referring to the cognitive overhead of learning to work with it.
Whether that is “something natural to you”, “something you learn and adapt to” or “something you fight with forever” seems to vary per-person, with I suspect, most people falling into the forest 2 categories.
I was talking about coding effort - reasoning about borrowing, lifetime annotations, and the fact that this can make refactoring more involved because lifting arbitrary blocks of code, especially when closures are involved, can require extra work.
Someone who's saying "the rest of the language sucks" may be thinking of something like that, hence my question above.
But when it comes to performance overhead, programming around the constraints of the borrow checker can introduce runtime costs that wouldn't otherwise be necessary - e.g. when cloning is used to handle borrowing conflicts.
Even if, in theory, it's possible to restructure a program to avoid performance impacts, in practice people don't always do that, not least because more efficient solutions may not always be obvious. This comes back to my point about coding effort.
I spent a bunch of time, pre-LLM, to try to replace a bunch of unsafe blocks scattered throughout an ML inference codebase, that someone had used to achieve maximum performance. I wasn't able to get a version that performed as well.
This kind of thing may not matter if you're writing e.g. ordinary web services, but for more performance-critical code, it can be an issue. Of course, `unsafe` is always an option to deal with that, but that undermines Rust's guarantees.
you should be reasoning about spatial memory safety ANYWAYS, so this is not imo extra overhead. Arguably with a checker in place (if the checker is sound and if you have good intuition about how to design code), you have to reason about it LESS, because you keep barreling on and only need to stop to think about it less. I suspect that people who complain about the borrow checker are just miring themselves into lazy choices that pile on top of each other, especially if you add more and more kludges, and then when one thing changes they need to do a ton of painful refactoring, that can break things too, if you're depending on a mutation that suddenly turns into a clone for example.
Fun fact, Russian soldiers ride on top of their tanks and APCs because its safer than being inside of one during an assault. Doesn't mean you are wrong, but there will always be trade-offs. There is no such thing as perfectly secure.
Tank desant is practiced because there isn’t room in the tank to fit extra people. It’s very much not safer outside of a tank than inside! It’s actually the worst of both worlds, because you don’t have the armor protection but are highly visible. The only advantage it gives over infantry assault on foot is mobility. Which is why it’s generally only practiced when there aren’t sufficient APCs/IFVs available
Not exactly true. BMPs are death traps, sure, and sitting on top of those instead of in them is rational given the risk of burning to death inside of one or being obliterated by a mine splitting the hull in half.
But the only reason to sit outside a tank rather than in one is because riding on a vehicle is safer than walking through an open field. Tank crews are not sitting outside of their tanks, and they don't have seats inside for passengers.
That stopped being true for at least 3-4 years (with APCs maybe still used until two or so years ago, tanks are still used but as "turtles" or/and "porcupines" [1], no way to have soldiers riding them). Drones have conquered (almost) everything.
That depends a lot on how the cow is raised. Cows raised on overgrazed/undermanaged land with feed trucked in from elsewhere and then sending the cows to feedlots for finishing on more trucked in feed. Yeah, definitely bad CO2 and methane emissions.
Cows raised in pasture that is properly managed and rotationally grazed - these can end up carbon negative.
* the pasture being well managed sinks CO2 long term.
* methane emissions from the manure decomposition is minimal
* the feed isn't trucked around
* if slaughtering and butchering are done on-site the only trucking needed is sending the beef product offsite.
Perhaps too an extent... In New Zealand (where I live) we have many cows, who are primarily grass-fed and pasture raised. However, agriculture is the source of 53% of our gross GHG emissions, with enteric fermentation (mostly from cattle but also sheep) making up over 40% of our country's gross GHG emissions alone.
I work in solar farm development, and as we already have a very renewable grid adding more solar does not greatly reduce our emissions due to avoiding fossil fuels, however the removal of cows from the land we use is arguably the some of the best environmental outcome of our work.
You're not accounting for most of the methane or the fact that the CO2 sink is temporary. That said, I agree that there are better and worse ways of doing it.
A very large amount of the methane comes from the manure pits in feed lots and fermenting grain feed in the animal's gut. The more time in pasture eating grasses and not grain the lower the methane emissions. It's not 100% but its a very significant reduction.
The CO2 sing being temporary is a true statement, but incomplete. For instance, coal turns out to be a merely temporary sequestration of CO2 also. The more healthy plants and soil (micro)organisms, the more carbon is locked up in those life forms. Further a lot of that carbon in healthy soil stays for quite a long time - it gets locked up in peats and other products of anerobic zones deeper down - some gets washed into river/lake/ocean bottom sediment for even longer periods of sequestration. Yes decomposition keeps the largest portion of it in a short term cycle, on the order of a few years, but claiming that having more life doesn't help CO2 because its "temporary" is a bit of overly-reductive misdirection sold to justify the status quo.
The other problem is once you've sunk that carbon the pasture is full and you need to find a new one. You will run out of carbon-thirsty pastures pretty quick assuming you find one in the first place.
Company builds datacenter that needs 2GW and a solar/wind/battery farm that produces a steady 2+GW then wires them together
And
Company builds datacenter that needs 2GW and a solar/wind/battery famr that produces a steady 2+GW and wires both datacenter and generation into the grid?
The later is what the wall of text is demonstrating.
* farmer wants supplemental income - if X fewer sheep means you can have > Xprice_of_sheep dollars from solar. Not to mention diversifying income streams.
Transmission losses are real.
* not everywhere has access to a desert.
* A lot of places are barren "deserts" due to overgrazing, and the overgrazing causes a lack of shade that is a positive feedback on desert conditions. Solar panels can provide just enough shade to bring back plants and grazing area.
I don't really agree with the person you responded to, but there is a lot of agriculture that is dependent on mined input, having long depleted the soil of whatever nutrients were there when we started. There are many places that are abandoned and barren because we did agriculture there. Land is still being dramatically degraded by many types of agricultural practices.
Meanwhile there are forests that were forest (and other ecosystems as well) 10s of thousands of years ago and just as lush and fertile (if not moreso) than they were to begin with.
Sustainable generally means we can maintain the fertility of the land indefinitely without mined inputs. Whether or not it's a completely achievable goal, it makes good sense to strive for it... Mines will become spent, theres only so much land to degrade, etc.
Often when people talk about sustainable agriculture they are talking about systems that mimic biological systems that keep those forests lush for millennia. These types of agricultural systems frequently look similar to agricultural systems of the past with more human labor involved, but less damaging waste products and fewer externalities. (Reducing pollution of the water downstream and minimizing ecosystem impact).
> There are many places that are abandoned and barren because we did agriculture there.
Totally but I'd argue nowadays it's not because we are missing the knowledge but rather ignorance and short-term economic gains.
Imo sustainability goes hand in hand with population (and lifestyle). We want a diverse ecosyaystem, this simply doesn't work if there are 10 billion people wanting to eat meat or produce tons of plastic. Our problem is not knowledge in agriculture that prevents us from sustainable living.
Absolutely not. First of all color, race, gender and age are not functions of personal choice. MBA degree is the result of making choices. One can assume many things from the choices a person makes.
Further, choice is influenced by training and experience, and the point of MBA programs is to teach people how to make certain types of business choices in a certain way. Of course their motivations and behaviors are influenced by their degree to some extend.
reply