The point is that you can enable each separate extension you want running on your code editor or uninstall them if you're unsatisfied. This makes it as light as you want it to be - or as heavy as you need it to.
I was doing fine with just vim and tmux
VSCode is like vim without vim controls and in a browser. Seen that way, it makes more sense. With Vim, you have to hunt for obscure Github repositories and follow arcane installation instructions for hidden extensions that you may or may not need and you have to learn a whole-ass keyboard-shortcut-based programming language just to use any of it.
With VSCode, you click on Extensions, search what you want and it'll probably be there unless it's a toxic ecosystem like PHP/C# or some niche ecosystem that no one heard about.
Your "minimum wage" link states multiple times that it is only for federal employees, not for the general population. There are still states where you can get less than 10$/h.
You can't have content addressing because it's mutable. On the other hand, UUIDs are made for that. There's even multiple types of UUIDs made for distributed computing with namespaces and such.
Well, that reminds me that Mastodon has huge, unresolved problems, such as tags being part of the post's body like Twitter rather than being a separate field like Tumblr.
Reading tweets with a hundred hashtags at the bottom seem really thirsty for attention, which is bad because Mastodon wants to fundamentally work with these, yet doesn't have good in-post integration for them. It makes interactions less genuine, more performative.
The issue with gaming on laptops is that you'll need to spend at least 1200$ at the bare minimum to play anything and 1600$ to have a good experience. And even then, the laptop is pretty much disposable and will be severely outdated in 5 years.
The best option for a laptop would be the Framework Laptop, but these can go for 3000$. The big advantage is that they're worth every penny as they are upgradable. You can literally swap every part, including the motherboard. The aftermarket value for these laptops is going to be amazing.
It's still like that with programming languages like Go and Rust. Job offers are exclusively for senior staff engineers with 5 years of language-specific experience.
Yep. And clients would be able to participate to the seeding.
Servers software developers would still have a massive amount of work to do to implement IPFS integration, but it's doable. IPFS also has work to do here to make IPFS work natively with cloud storage protocols (like Amazon S3), but it already exists.
One issue with open source software is that you often have to pick the least-effort solution to avoid burning out your free labour. Free time is limited, and if IPFS takes slightly too much work to add, then it's off the table.
There's also lots of people who made an account in multiple instances before realizing that you don't have to do that