Readit NewsThis highlights my experience with these controls pretty well... I have no idea what is n-finger touchable or holdable anymore and I just stumble into features accidentally.
Of course they have merits. But, so what? I didn't dedicate my life to this field to build things that "have merit", but to build great things. And we have great things. It's just that neither Oracle nor JavaScript are among them.
Nobody is telling you to build things that just "have merit". Just because you don't like them, it doesn't mean that great things weren't built off the back of Oracle and in JavaScript.
If some Oracle product is the best pick for the task, or JavaScript is the best pick for the task... will you pick it? Or will you whine about what you dedicated your life to?
If you can't see that other people might feel different about this, or be able to build great products with these, maybe you're the one without the imagination and ambition...
And accept that both have merit. You may not like it but there's a reason languages, tools, companies, products, whatever become popular. And it isn't just because "people are idiots" or evil companies. Console wars are for teenagers.
In my experience React is rarely the best solution and adds a huge amount of complexity which is often completely unnecessary because React is rarely needed.
In the early days my very controversial view was that frontend developers tend to be fairly mediocre developers, and this is why a lot of frontend frameworks suck and frontend developers just mindlessly adopt whatever the hot new technology is with seemingly no concern for performance, maintainability, security, etc.
But honestly I'm not sure this explains it anymore... There are a lot of really talented frontend development teams out there working for companies with plenty of cash to try something different. I don't really understand why there's no serious competitor frameworks in terms of market share out there.
As far as I'm aware there's no analogies to this in other areas of the web tech stack. There's plenty of backend frameworks to pick from depending on the product. There's also plenty of competitive DBMSs, cloud providers, package managers, code editors, etc, etc. I don't understand why frontend development is so static in comparison because it's certainly not that React is the perfect solution for everything.
I can't speak to the complexity you've encountered, but for me it's pretty much zero. A button component is just a function. React-Router is good enough and code splitting is pretty much just changing how to import something. Component state is dead-easy to write by just adding a useState hook. Bundlers pretty much handle everything these days so not to much concern about size.
Your view on front-end developers having been mediocre in the past isn't far off though, at least in my experience. I noticed a big difference between the people who wanted to build nice looking pages and the ones that wanted to build applications myself. Even today it amazes me how many people have never unit tested their code, have no idea about layering an application and have poor JS/TS fundamentals. It's gotten a lot better though.
Ultimately it isn't perfect for everything, but for a lot of people it's an easy choice. And for me personally, the tons of other JS frameworks do very little in that area that I'd pick them. I'd rather spend my time working on the product. Lol, maybe its just the default because its the default at this point.
Honestly between React, Angular and Vue, there's enough jobs if you do want to specialise, but the mental model between the three isn't that different that a good engineer wouldn't be able to adapt.
React is boring old tech to me at this point and I'm happy with that. Like choosing Java, C# or Python for the back-end. I'd rather focus on innovating my clients products until something earth shattering comes along.
That too says something about our times. Maybe a few things. From being unable to trust things without verifying, to people’s willingness to alter the truth to make a point, to how people fear discussing race and gender loud even in passing.
Here a counter that increases and decreases with mouse movement would take less space and be more intuitive.
And a much much better design because it would provide a numerical readout of the value directly at the point of interaction.
But in fairness, most design is bad because designers tend toward satisfying themselves rather than users...ok, I will stop ranting now.
Most software I use does still show some numeric value somewhere, either around the element when changing it, or in some other panel. This way you get some more information than in the hardware equivalent if you need more granular control. Its particularly nice if they allow you to click/double-click for editing values.
From my perspective as a user, knobs convey exactly what I need. Mostly I don't care about the exact number, just about what position something is in. Knobs behaving like sliders is fine. I'm not physically moving a knob, I might be moving it with a mouse or touchpad. You can't stray with a physical control the way you can with a digital one. And they allow interface designers to put a lot more information on screen where space is at a premium.
Honestly, just go download a trial version of something like Reaper or Reason and go make some music. You'll get a better feel.