Hey React, why won't you die?

Seriously, you are cumbersome to use, heavy as shit, awful syntax and do only the most basic reactive operations possible.

Why do you have to re-render un-changed components?

You were good when you came out, but please, get the fuck out of job requirements everywhere.

no

@theabbie reported as offensive content. useState should not exist

@sinisimattia are you the vanilla web developer?

@sinisimattia So, what do you think is better? Or better yet, build your own framework.

@theabbie No, i simply prefer other frameworks and hate that most people immediately use react without thinking if that is the right use case

@atheist Don't need another framework to add to the pile. Vue & Svelte are much, much better syntax/performance-wise.

Abandon React. It is only good for super specific and small-scale stuff

@sinisimattia

People might hate me for this, but fuck frontend.

I dislike the existence of JS as a web-developer, and as a web-consumer.

What's wrong with JUST having a lightweight HTML doc?

Once you start adding logic to the frontend, the site ends up slower, less compatible between devices, acting in unexpected or even abusive ways.

Maybe I'm just old, but I liked platforms like YouTube, Reddit and Wikipedia better before they started doing all kinds of SPA shit.

Just load a fucking HTML document. Shave that HTML document down, to the single-digit-kilobyte range. If you feel like you need AJAX, that means your pages are too fat, they contain too much bullshit.

What have we actually gained on the web, since the gif-ridden HTML4-era? Just a bit of visual fidelity? Scrolling animations? I actually LIKED it when a website didn't poll or connect unless I AS A USER clicked a submit button. 🤷‍♀️

*old grumpy guy rant*

@bittersweet I agree. Looks like we’re in the same age bracket. I learned HTML in half an afternoon and was building sites for clients within a week. Sites were small and very quick to load. CSS (for all its frustrations) did help in terms of applying sitewide style changes but it has been abused out of scope of the original intent for it for a long time now.

@stackodev Indeed.

I'm not a language designer or web infra expert, but I feel like how HTML5 replaced Flash video, we might need some kind of HTML6 to simplify all the JS-vdom-reconciliation-acrobatics every framework is choosing to reinvent over and over again these days.

@bittersweet yeah, totally agree.... HOWEVER I still believe that the web is the best app delivery system out there.

So, if what you are building is an APPLICATION (with lots of user input etc.) then HTML doesn't cut it.

Non sites like blogs and shit like that it's just too heavy

the real root problem with react is that it is TOO flexible and most people end up with a mess ;)

gotta know what you are doing.

also, please inform me of those 'faster' frameworks - i like angular as well, but that 'Generating ES5 bundles for differential loading...' that takes 5 minutes plus for larger apps? not into that.

@bittersweet It seems to me that front end scripting is used for 2 things. Highly dynamic pages with videos and ads popping up everywhere, and abusive tech designed to track to steal data from users.

@sinisimattia Is the web really so ideal for building apps though, or is it because of familiarity?

I guess HTML+CSS is pretty nice for building GUIs. But if you could do it from scratch, would you pick XML as the basis for layouts? Isn't the CSS syntax kind of weird? And why is is exactly that people keep trying to fix the dialects (sass, less, stylus, haml, twig, blade, coffeescript, typescript, etc), and the organizational paradigms (serving templated HTML from backend, SPA with frontend frameworks, templated two-way-bound components)?

For some reason, there's some uncomfortable tension with web technologies.

I'm not sure what the ideal picture would be. Just that frontend-heavy-SPA apps make me throw up.

I just tabbed to devRant from Asana. Which showed me a modal, informing me that Asana ran into a syncing error and needs to be reloaded, throwing away any changes. That, right there... that's not what I fought for during two World Wars (oh wait... I'm not THAT old).

@sinisimattia I uhhh, sense you may have missed the sarcasm...

@bittersweet people just love to make their own syntax of templates, new programming language for no reason. PERL creator loves playing with a syntax too much.

@bittersweet Totally true, and yes, I do mean in terms of familiarity and cross-platform support.

For everything else (especially in regards to CSS) I agree.

I totally hated how web pages were built using stupid template like Jinja. Developing components using Storybook and react is actually nice. Managing normalized states in redux and Apollo totally sucks. Trying to hydrate store while using SSR is even worse. The whole project becomes dumpster fire when you have to use react with last century JS API like Google map.