0rzech
Turris [1] has already been updating their routers for years and they continue doing it.
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.
I concur. Great prices, great products, great customer support.
By the way, many people think that Polish alphabet is just English with diacritics, but in reality neither q, nor v, nor x are part of it.
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.
You can't disable build.rs, Rust Analyzer executes proc macros as soon as you open the project, 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.
* 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.I love working with Dart (which IMO is _not_ "worst parts of Java and Javascript (...) turned (...) into a language", "Terrible to write, terrible to read, terrible to use" - quite the opposite, actually) and its toolchain, including Flutter.
I find the architecture simple to follow, no need for "either print apps as fast as possible or to emulate some Clean Code like behavior", though I do think some people use overcomplicated state management solutions. But nobody forces anybody to do that.
My experience with Web has been fine so far and I've seen fully cross platform Flutter apps working absolutely fine on mobile, desktop and web.
This is not to gaslight your experience, YMMV after all.
And React Native, with its dependency hell, project rot, npm ecosystem under the hood, and transpilation with lax runtime leaking into TS, is a total no-go for me. Though I base this opinion partially on my experience with NodeJS, and partially on that of my friends who use RN.
Btw. Does your platform support bundling UI in addition to streaming it from the server? How large is the bundled runtime?
PS. Clicking on "see all supported platforms →" on your project's homepage gives 404 for https://docs.hypen.space/docs/adapters .
The language, like any other, does have some weaker parts, but in general is _very_ nice to write in - thanks to both the language itself and the toolchain built around it.
The apps compile to native binaries for production and are run in Dart VM during development. The SDK is multi purpose. You can write "scripts", you can write CLI apps, servers and with Flutter - the rest of them.
No, it does not. I create an account only when I'm forced to, e.g. on Google-certified Android phones, where I keep all synchronization off.
I'm eagerly waiting for official GrapheneOS phones. Pixels are a no-go for me because of the price-to-perf/quality ratio.
PS. It takes about 50 minutes to hunt down and turn off hopefully all the data grabbing features on a Samsung Android phone. Madness!
This is also one of the reasons I migrated away.
Perhaps https://radicle.dev or https://tangled.org would be fine for you?
Amongst other unwanted activities, their blog post mentions "Projects written and maintained with heavy use of LLMs". If you often chat with LLM, or ask the agent to review your changes, it's writing and maintaining the project with heavy use of LLMs too.
IMHO, this is even more restrictive and ambiguous than "projects that mostly consist of code written by "generative AI"-tools".
And what if a project is hand-written, but the tests are LLM-generated and then refactored by a human? Well, tests are part of a project, so it's bad too.
Also, while reading their blog post, I couldn't shake the feeling that they disdain niche single-person projects. Apparently they never intended to be a "dumping ground", as many people from their community now claim. But it's insulting to assume that when you share your small single-person project, you just "dump" something, as if it is some kind of trash by definition.
What I look for in a theme is:
1. Being easy on the eyes.
2. Easy distinction between different keywords etc.
3. Good contrast.
The best light theme I've seen so far is Selenized for VSCodium [1] and for VS Code [2]. There's a Selenized light for JetBrains IDEs too. [3]
[1] https://open-vsx.org/extension/santoso-wijaya/helios-selene
[2] https://marketplace.visualstudio.com/items?itemName=santoso-...
[3] https://plugins.jetbrains.com/plugin/23800-selenized-theme