4 ms·
That stuff isn't readable. It's mostly garbage. If you don't need to make 20,000 devs work together in a chain gang, why even bother? Here's the platforms you
by _3u10 5y ago
That stuff isn't readable. It's mostly garbage. If you don't need to make 20,000 devs work together in a chain gang, why even bother?
Here's the platforms you need if you're not 20,000 strong:
https://motherfuckingwebsite.com/ https://motherfuckingwebsite.com/
http://programming-motherfucker.com/ http://programming-motherfucker.com/
https://github.com/brandonhilkert/fucking_shell_scripts https://github.com/brandonhilkert/fucking_shell_scripts
http://vanilla-js.com/ http://vanilla-js.com/
- codethief 5y agoYou're missing one link: https://bettermotherfuckingwebsite.com https://bettermotherfuckingwebsite.com :)
- onion2k 5y agoThat stuff isn't readable. It's mostly garbage. Arguments like this do you no favors. There are hundreds of thousands of developers using React today. They aren't all wrong. There are legitimate reasons to use it, it works very well, and code written with it is not 'garbage'. It certainly has its flaws too of course. However, while any website that's using React appropriately could be written in vanilla JS instead, after a while the code would start to look like a poor quality React implementation. This is obvious, because what React is doing - abstracting the process of inter-component communication, and giving developers tools to solve common problems within components - is actually very common in app development. Leveraging React rather than reinventing that particular wheel is a good idea.
- codethief 5y ago> Arguments like this do you no favors. […] There are legitimate reasons to use it, it works very well, and code written with it is not 'garbage'. Did you take a look at the links OP posted? I interpret their comment very much tongue-in-cheek.