@seldo economics indeed but the changing storyline is also well documented (yes that's grifting!)
And also ppl need to know how HTML/etc work in order to use React not the other way around.
@brianleroux @seldo I can too attest to said gaslighting. And Iβm a heavy SPA user because for the longest time that was the only way to build fully offline capable applications on the web.
Letβs hope for a better future here. π
@janl @seldo yes, and the only way to build hybrid apps too. Well, only good way. But got mobbed for suggesting backend rendered was a better default. The webpack guy, employees of said company, called me "irrelevant old guard" while the coworkers all dog piled likes.
Respect is a two way street and they lost mine a long time ago. When ppl show you who they are I believe them.
@brianleroux @janl don't you think it's a bit on the nose what you're saying about SPA devs & "using the platform", when you yourself had a reasonably big moment in tech not using the platform (Native Apps vs PhoneGap), or is that history you'd like to forget about?
Everyone makes trade-offs, and you are not above them.
@brianleroux my point is more: you made a name for yourself encouraging folks not to writing native apps (iOS, Android, and Windows), often leading to developers creating applications that were great or performant on any platform.
So it's a bit on the nose for you to be saying developers are unprofessional because they opted for a SPA framework & didn't prioritise making the back button work (which iirc, was actually a common gripe about phonegap apps)
Everyone makes trade-offs
@thisismissem I read what you said and it's not true.
We always stated the point was write web standards and focus on web technology. It was a "stop gap". We definitely had poor experiences and occasional good ones like Instagram for example.
Unprofessional work is possible with any technology. I'm not saying all spas are bad but I am saying there are better default ways of building web apps.
@brianleroux right, and you can build good SPAs with React (Remix is a case-in-point), just like it was possible to make good apps with PhoneGap.
If majority of developers are making a trade-off though to use these tools in ways that give bad user experiences, I'm gonna go with either naivety (didn't know) or trade-off (didn't prioritise), that doesn't necessarily make them unprofessional or the tools they use bad.
@brianleroux we can judge code to the cows come home, but judging it in isolation is not useful β there's just different compromises to make, and some of them get made with very little thought, which is actually okay: you can't do everything.
A certain set of decisions doesn't make work unprofessional, or those who did it unprofessional or stupid.
@thisismissem yeah I'm not taking issue w all devs or even any individual devs. Context is important.
I will stand by the opinion that working links, forms and good performance by default are hallmarks of professional work.