3,283 karma · joined July 3, 2014
Yes, you're just not clever enough to understand all of the jargon I just invented and refuse to explain, audit every line of code, audit the organization that actually controls the project, spend a month brainstorming all of the possible failure modes and get a PhD in multiple disciplines to discover if any of my claims are deceptive.
For users: the widespread deployment of NAT has eliminated global end-to-end connectivity of the internet. That drives further centralization of the internet, as offering services requires expensive purchases of IPv4 space, big central NAT gateways and makes p2p applications difficult to impossible.
For infrastructure maintainers: the increased address space makes it possible again to allocate addresses as you wish. There's no need to architect your network around IP address scarcity. You can allocate pretty much as many networks as you want, for whatever you want, without worrying it's going to be too small.
Of course the World Bank and IMF will be happy to help you out of you drop them again though.
That is to say, very few countries actually have a choice on agreeing to "free trade" policies, local laws aren't really enough to resist that.
It's true that Heroku has a better experience, but that doesn't matter if the NRE for making it work on a cheaper platform is recouped after barely a month. I think the fact that these services are able to be successful despite having a worse experience shows how uncompetitive Heroku's pricing is.
One is that a large fraction of these security issues are not real, potentially exploitable vulnerabilities, but merely the fact that it is possible to abuse an API to subvert Rust's safety guarantees. These are things would, by the standards of other programming languages, not be worth even reporting and be considered user error.
The other is that a surprisingly large fraction of these are not from regular unsafe Rust code, but from misunderstanding the guarantees a C library makes when creating bindings for it. This is to be expected, as fully understanding those as a library is pretty difficult.
A total of one memory safety issue reported for an entire ecosystem this year so far also seems pretty good.
All in all, I think these are both pretty promising signs that the safety guarantees Rust provides working as intended.
Or perhaps the bust is a great time to generate some credulous positive news coverage.
That's not completely true. The amount of resources wasted per hour are proportional to the value of the coin. Lacking any genuine uses for for cryptocurrencies, people determine coin value by things like transaction volume, market capitalization, influencer endorsements and active wallets instead. Thus every additional user, transaction and especially the common million-dollar wash trades designed to pump their respective projects, contribute significantly to the waste that is generated.
They know this makes independent repair uncompetitive, which is why they do it.
Yes, which is the point. They are offering a compromise for a tiny market (self-repair) in hopes of this distracting from and preventing laws that would benefit the market that actually matters (independent repair).
It's like throwing your underpaid demoralized employees a pizza party so they don't quit, nothing but a damage control gesture that deliberarely doesn't actually help.