5 ms·
cant wait for react.js to be archived
by dym_sh 4y ago
cant wait for react.js to be archived
- satvikpendem 4y agoWhy? And what's better?
- nelsonic 4y agohttps://kit.svelte.dev/ https://kit.svelte.dev/
- satvikpendem 4y agoI don't like any framework that uses templates. I already know JS, let me use that. Also they usually work poorly with editors and TypeScript since they require custom syntax to be supported. I'll stick with JSX.
- no_way 4y agoI like JSX too, it allows multiple composable components in the same file, but Sveltekit support for typescript has been amazing so far, the whole framework has been written with typescript in mind and it shows.
- satvikpendem 4y agoThat's good to hear. I also used to use Vue before switching to React, which has a similar layout, ie HTML, styles, and script tags in a single file component. It was alright but it had some weird rules, like registering plugins, two way data binding, etc. Biggest thing though is the package support for Vue and other non-React libraries was miserable compared to React, so I switched and I definitely prefer it over any template-based framework.
- mrweasel 4y agoI scrolled down and still saw and npm command. I just check out whenever I see NPM. I really should learn how to use that thing.
- dym_sh 4y agoVirtualDOM is why. vanilla.js is better
- satvikpendem 4y agoHave fun rewriting your own ad hoc, informally-specified, bug-ridden, slow implementation of half of ̶C̶o̶m̶m̶o̶n̶ ̶L̶i̶s̶p̶ React.
- dym_sh 4y agothat's the "problem" tho — i dont need that level of abstraction, i already know how to assign event listeners and toggle css classes, which covers 99% or real-life needs
- satvikpendem 4y agoFor small projects, sure. But it breaks down in larger ones, ask me how I know. The reality is React and other tools solve problems at scale, plus they're genuinely nice to develop in, while vanilla JS simply is not.