and why you should never trust cloud providers with your only copy of anything
well, yeah. Even the old 3-2-1 backup policy is against that.
Wow, prejudiced much. The JS ecosystem evolved a lot over the year, and polyfills for most environment are next to non existant. The worst environment to me (react-native) do heavily use them, but they’re built-in anyway.
Also, about stuff being slow when made in JS… people that make slow clusterfuck in JS would also make slow clusterfuck in other languages. React is guilty of that too, trying to re-implement core language features OVER the language itself, and that is stupid. Still, as with every language, it is possible to use it decently. You’ll never get to the point of raw optimized assembly performance, but even higher level scripting language can leverage JIT compilation and work well on any modern (<10 years) computer. Taking as an example the worst developers out there using the worst way to do things is not exactly a good benchmark.
Backward compatibility and not seeing the future. Some decisions are taken at one point in time, then a new use case show up, then a new paradigm evolve, then… etc etc.
It’s really the same thing that holds back a lot of languages and libraries. And even when replacement shows up, old habits from devs and old projects maintenance keep all these things well alive too.
It was explicitly said to not use this outside of VSCode, so, I’m not sure where the surprise comes from.
The problem is that they’re killing competition.
So, they pay to develop a product, for themselves, explicitly says “it’s only for us, shoo shoo”, and when they decide that their product, that they pay for, and provide for free to their user, should not be used by other, it kills the competition that did not do anything except take the product for free despite being told not to?
I’m not on the side of Microsoft for most things. But if doing nothing but taking someone else’s free product qualifies to be competition that should be protected, we’re having problems.
There were tons of options with multiple HTML elements with a sequence of CSS properties to reliably provide vertical centering (and also use vertical space at the same time) back in the days.
Now, between flex and grid (mainly flex for me, I find them more convenient) all the HTML scaffolding we used to make this work can be removed to get the same result. That’s what I mean with “no trick”.
Well, we’ve been vertically centring content with no-trick pure CSS for years now, so, good I guess?
No kidding. I started to receive messages from reddit mods (not the user, but actually coming as “from /r/subname mods”, with phishing/scam links.
So they have access to your crypto keys right? Not necessarily, no. I won’t even bother reading the stuff, but it is perfectly possible to have systems where user’s cryptographic keys are kept under the sole control of the user, being using client-only known secrets for encryption, wallet-like software, or even more basically keeping the key only in local storage and telling the user the seed so he can “recover” it if the local storage gets wiped/lost.
Bottom point is, it is very possible to do so, and it can be done in a safe-enough manner for most people without much hassle. Of course, that’s theoretical; weither or not corporations care about actual privacy, control, and are willing to work toward these is another matter entirely. But the technology have been there for years.
That would require a bit of work to implement and might be hard on the server.
Too much salespeople see complaints like “your application is bad” and answer with “we’re going to force it on you even more then”.
Self-hosted gitea. Free, runs on a potato, built-in actions support, optional wiki and package hosting, etc.