So we need to paralyze 30% of the economy, that would have gone to bankruptcy within months if not for massive money creation, just to get a -10% in CO2 emissions. Easy. Then, where do you get the next -10%? And the next one? And...
Maybe there is a way to get -10% without paralyzing the economy. But nobody is looking. Or they’ve devices that it’s “too expensive” to invest in tech that will save 10% later.
If we continue to do nothing effective, the economy will be paralyzed by 100%.
We could get to net negative, just with carbon capture, for less than Iran is costing us. (Atmospheric carbon capture, if scaled, would cost ~ $1-2 to capture a gallon of gasoline's CO2 emissions).
Of course, that's one of the dumbest ways to get to carbon neutral. Solar and wind + batteries cost less than internal combustion engines, yet they're somehow "too expensive" and would cripple the economy.
There are entire categories of scams that exist only thanks to cryptocurrencies. Do you think random people in Western countries would wire money to human traffickers running pig butchering farms in Cambodia without stablecoins? Or to ransomware gangs in Russia without Bitcoin?
Not only they aren't remotely comparable, but there's obviously a huge difference when fraud goes through accounts linked to real identities, since banks and payments systems are legally mandated to deal with KYC and AML regulations.
Where coins are held is completely irrelevant. There are cryptocurrencies on real blockchains, and while the technology is dumb and mostly useless, nobody denies that PoW and properly implemented PoS are decentralized.
And then there are centrally issued and controlled coins on private, permissioned ledgers a.k.a. databases. But most cryptobros never cared about the technology nor the political goal, so anything can be called a cryptocurrency as long as it's a medium for gambling and speculation outside the regulated financial framework.
Native images shouldn't be too messy anymore, Oracle put a lot of effort into DX improvements and all major web frameworks are now aware it's an important and growing use case.
Struggling to build native images should be a sign you're reliant on libraries that are dangerously outdated and abandoned.
They can definitely be pretty messy in some ways; even the standard library doesn't work out of the box perfectly. I have certainly struggled to get image manipulation with java.awt (e.g. thumbnail generation for a fairly standard web use case) to work in a native image.
So it is an antipattern nowadays to manipulate the classpath after building? Iirc native image require static classpath, but it is quite common to inject e.g. environment specific data via the classpath. Should one just read from the filesystem instead, or what’s the strat there?
With the AOT cache, you can actually modify the classpath (or module path as is now used for modern applications) after it has started up. The names and classes for the APIs are different, but you can still load jars at runtime even with the AOT cache enabled and functional.
The AOT cache compatibility issues come when your boot module path differs between training and actual run. As long as that is not the case, you can use it without problem and load additional modules at runtime after it has started up.
With GraalVM, that is not possible. It still has the closed-world assumption.
Most of that monster ecosystem is exactly that: monstrous code in one-off throwaway libraries written by people who don't care about software, as it's not their job.
If you set a bar, any bar, there's really not much offered by Python that you cannot find in a more reasonable language. Especially if you're gluing together C++ and Rust libraries for data processing or ML workloads. Python is still disproportionately popular there but I'm also convinced its days are counted. C++ will be tremendously harder to get rid of, in comparison, if that's even possible.
reply