0rzech

Same in Poland. You pay tax on printers, printer paper, disc burners, writable discs and so on, and in return you may legally make backup copies of the copyrighted works and share them with your close relatives. IANAL, though.

The best part is that this year they've added smartphones, tablets and laptops to the list of taxed devices, which is ridiculous and pure greed. And the minister argued that the manufacturers will bear the increased cost themselves, which just adds insult to injury. She also said that other countries do that already (Germany was the example AFAIR, hehe), but she just conveniently left out the fact that Poland already has one of the highest VAT rates in the EU, so our devices will be even more expensive relative to their base price, than they already are.

You're right, AFAIK.

> Obviously, they are still a corporate, but, until now they've respected me as a consumer unlike many other corporations. I value that.

I concur. Great prices, great products, great customer support.

Sometimes it is, sometimes it isn't. But it wasn't OP's argument, was it?

There are more differences.

Packages can release updates arbitrarily, while standard libraries tend to have longer release cadences.

It's also more difficult to put arbitrary code into an stdlib, because stdlibs are scrutinized better.

Also, it's harder for some random anonymous developer to gain push access to stdlib repository.

One of the reasons so much Rust code is in libraries is not because there are no people to write it (duh), but because putting these in std commits maintainers to keeping backwards compatibility and slows down included package's release cycle.

They won't, but the less attack vectors, the better.

Is Rust ecosystem really that much better, if at all? This is a genuine question.

You can't disable build.rs, Rust Analyzer executes proc macros as soon as you open the project (and it needs to execute them in order assist the developer), minimum days since release has not yet made it into stable (though luckily it is planned for 1.100), and the number of project dependencies goes easily into several hundreds (still better than npm's few thousands, though, and I know that some deps are from Cargo workspaces), and on top of that, lots of packages stick to 0.x version for years.

Personally I see Rust community's packaging and security culture more akin to that of JS than to Java et al.

It absolutely is a culture thing. I've seen many threads asking about backend frameworks in Go, and every time there were lots of answers akin to "screw framework dependencies, stdlib is more than enough".

This is not true on many levels:

  * Most of the team stayed at the company.
  * The layoffs hit mostly DevOps and infra people in Flutter team.
  * At least part of the laid off roles were moved offshore to Germany, India etc.