The times just before social media. Internet was just modern enough to serve memes to thousands of users, yet it wasn't treated as serious as now. It was literally wild west of digital world.
No, any documentation >>> GUI. GUI relies on your previous experience with similar environments. Just jump into a GUI of Visual Studio (not code) project configuration and see for yourself.
As a 1998 who had access to the internet during its wildest peak with no parental control at all (had internet since I was 10 years old), I do not agree with ANY parental control. Your kid is going to stumble upon these topics anyway, sooner or later, internet or real life.
Instead of preventing it - monitor it, and make sure you discuss it with them. Some years from now on, you will lose whole control over them, and then they won't be easily persuaded.
Censorship creates people that are easily manipulated - no matter what your intentions are.
Thanos was right. Some greater-being should just snap some part of humanity out of existence. Just not the random half, but those who actively try to ruin it for the others.
The thing is, they look like too much for a simple app with near none interactive elements.
But once app starts growing, concepts like reusable components, reactivity and state management become such an important tool.
Imagine tracking shopping cart's total value. With these frameworks it's just one store containing total value, exposing the value as reactive state. Once the value changes, all components using directly or indirectly that value update immediately. In vanilla you would have to keep track of every instance where that value is used manually.
Additionally, if you decide keeping total value of cart in frontend is stupid (because it is), you just modify your store to provide only readonly value, and create setters that require you to pass item or item id. Then that setter would hit up backend keeping your cart's total value, add an item, and backend would return new total, which would now be set as that store's new total value.
These frameworks are kind of SOLID principles applied to chaotic world of user interfaces.
I tried to learn React, but it was unnatural for me, but then senior front dev at my workplace suggested Vue. I remember Vue's options api being too weird to even try it.
Then I discovered there's composition api and fell in love with it. React's flow without its weird quirks.
I think Svelte is next step towards feeling as natural as possible.
Dafuq are you talking about? I've downloaded many random shit from Github on Windows to restore some basic UX functionality on W11, while I have never downloaded any software from Github repo on Linux, because everything I need is either on Ubuntu repo or some ppa or - shockingly - is built-in DE. And I'm a programmer and Linux is my daily driver.
It is better than in most languages with exceptions, except from languages like Java, that require you to declare that certain method throws certain error.
It's more tedious in Go, but at the end of the day it's the same thing.
When I use someone else's code I want to be sure if that thing can throw an error so I can decide what to do with it.
I have Logitech G535. And I play osu!. I'm pretty sure there is latency but I couldn't feel any difference between them and headphones connected to DAC. So if there's any latency there, it is definitely less than 5ms.
Have you even made a production grade front end project?
You can't use "pure" HTML solutions because every browser can display these differently. You have to use CSS to make a website look and behave modern. "Pure" center tag is clunky and doesn't work everywhere and that's "by design" (That behavior is defined in specification, and we can't change specification to meet today's standards because that would make it non backwards compatible). Additionaly you need to make your website scale to wide range of devices. And sometimes you need to even add JS to fix some of the issues if you don't want the developer to implement a non-maintainable solution taking him 5 hours, if he could do that in JS in 5 minutes.
Look CSS is not perfect. It's hacky solution to a problem, but news flash: most software engineering is. And it's proved to be working.
"But what if in the future..." - address future problems in the future. As soon as they appear - not before or after that.
That's the stupidest thing I've read today. I hope you're not any kind of engineer. There are some situations where it might not be worth it to future-proof something, but if you apply that to everything you end up needing a full rewrite instead of just adding a feature.
The times just before social media. Internet was just modern enough to serve memes to thousands of users, yet it wasn't treated as serious as now. It was literally wild west of digital world.