I get your point about react but I dont like it at all. I dont want a web app 100% made out of a JS framework. In fact, I despise all of the JS, honestly. The "appification" of the web is a horrible thing in my opinion, mate. browsers were meant to read web documents not to run full blown web applications that consume a lot of your RAM. And much of this blame we can put on bad devs.
"And sadly, there are a lot of coders out there that use a ton of tools but don't understand what these tools are actually doing.
If you blindly follow a tutorial to build your app but you don't know what your commands are installing into your project, you are not a real developer. A lot of people are not real developers."
Well made point. Yeah. I agree.
I for the same reason you prefer React, I prefer to learn SwiftUI to work with the Apple environment only, I never had a good experience with Android, so yea I get your point and reason, but I dont want to try again, hence why at work I am the only one who doesnt test or develop anything on Android. And that's OK because they acknowledge that I have a stunning eye for design and UI interactions, as well as finding solutions that use much less JS for squeezing a bit more performance. Sometimes I have to teach a bit of CSS to the devs (I am now a UI/UX Designer, been a frontend web dev for almost two decades).
I am also learning SwiftUI because I no longer want to work with the web. The web 2.0 and now 3.0 with the rise of JS frameworks and web apps takes away a lot of my interest in web design. So developing apps for macs and iOS have been a lot more interesting for me these days, and building native apps is bringing me back to the excitement levels I had when I was developing websites for the web 1.0. Always learning and improving. That's a good feeling, I haven't had that in years since web became the convoluted mess it is now.
SwiftUI is really easy to get going on and I am learning really a lot. You know, when I was a kid I wanted to be a programmer like my dad (he worked a lot more on things like Fortran, Cobol, C... in his era, and very little in this web era), but as I grew up, my interest was more on the design side of the things and less on programming, so I became a web designer, then frontend web dev, and now a UI/UX designer. I learned HTML, CSS, then struggled through JS and jQuery and so on in an adventure that started around 1998 when I was a young man. When Web 2.0 came up, a lot of my interest on it vanished.
I was working on "semi-automatic mode", with literally no joy in coding web pages and designing them with tools and frameworks I never wanted to work with and ultimately ended being a hot mess (I had to work with other developers, was never a solo flight, and most of them don't actually care about the right way to do it; as long as it works and they're being paid at the end of the day, they don't care). I had one LMS product we developed, where it could clean its cache, when it was fully native with no modifications before we begin developing it, cache was cleaned almost instantaneously. After throwing a lot of mods on it, guess what it now takes eternal minutes to clean it up. Depressing to see it and not being able to do anything to change it, because it doesnt depend entirely of me to do something about.
Now after the work shift, I spend a few hours learning SwiftUI and having a lot of fun with it. Maybe one day I can leave my current work and find another where I could work doing native apps (well, I can also learn to code for Windows and even Linux, I am not entirely tied to one platform to develop, even though Apple is my primary target, but I dont want to work with the cross-plaform garbage - like Electron, for example - that does have disadvantages in one or another platform; I'd rather use native solutions for each one). And maybe one day, I can dream of the day when JS is killed like Flash was, and the web becomes great again to work with it, then I could go back to it with the same joy and excitement I had when I began my career.
Meanwhile, the web as it is now - full of web apps, JS frameworks all over the place, React, Vue, Angular... Is not where I want to be or work with. You can call me old fashioned if you want, I won't deny the fact that I do love the simple, basic, HTML and CSS duo. Afterall, I am a designer, not exactly a programmer; but JS is one of the requirements for a web dev, unfortunately. After 2 decades in this career, I can't even properly code something in JS yet alone jQuery. But if you ask me something about HTML, design, or even CSS, I'll come up with a swiss-army knife of solutions for you, collected through 20 years of experience doing web sites for all types of business.
As for React, its nice to see the final product working and looking shiny, but if I look under the hood, I'll be terrified to see the hot mess it is; so I prefer not to look... or look on Activity Monitor (or Task Manager for the Windows ppl) the RAM usage...
