Angular will be much more useful in 5 years than it is today. Because sure you get some nice performance improvements with all the scoping and stuff, but only if your client has the memory capacity to load 12,000 lines of bullshit. So basically, this shit only works good on phones built after 2014.
And then you want to add another library to the page? Something with cool touch effects and complex geometry? Maybe even Google maps? Forgetaboutit! You already used up all your available memory to load 12,000 lines of code you never deploy just so you don't have to attach event listeners to your sign up form because you're a lazy piece of shit who couldn't write actual JavaScript if your life depended on it.
Also, once you go Angular, you can never go back. You ain't never gonna unpack all those inline attributes and event listeners. In fact, you can never interact with the DOM again, you've just surrendered your right to manipulate elements directly, forever.
And the last thing that sucks about Angular is the event dispatch loop thing which cals 8,234,793 functions every time you update a form input. I know it's not that taxing because they're mostly small functions being called simultaneously, but still it's totally unnecessary.
It is hard to construct a JavaScript software design pattern that fits every use case because JS is such a unique and flexible language.
Excellent synopsis. Every time I think about starting an angular project I get about two seconds in and realize jquery/plain ol' js is so much better and extendable
I just started using ReactJS for work, it's a lot less rigid, a little more light weight. It works for forms I guess.
If you want to have a rich touch interface that works on 3rd world smartphones, you gotta code most of it from scratch, scope the shit out of everything, manage your memory very carefully.
3 comments
0 u/pray_the_gay_away 21 Mar 2016 13:00
Angular will be much more useful in 5 years than it is today. Because sure you get some nice performance improvements with all the scoping and stuff, but only if your client has the memory capacity to load 12,000 lines of bullshit. So basically, this shit only works good on phones built after 2014.
And then you want to add another library to the page? Something with cool touch effects and complex geometry? Maybe even Google maps? Forgetaboutit! You already used up all your available memory to load 12,000 lines of code you never deploy just so you don't have to attach event listeners to your sign up form because you're a lazy piece of shit who couldn't write actual JavaScript if your life depended on it.
Also, once you go Angular, you can never go back. You ain't never gonna unpack all those inline attributes and event listeners. In fact, you can never interact with the DOM again, you've just surrendered your right to manipulate elements directly, forever.
And the last thing that sucks about Angular is the event dispatch loop thing which cals 8,234,793 functions every time you update a form input. I know it's not that taxing because they're mostly small functions being called simultaneously, but still it's totally unnecessary.
It is hard to construct a JavaScript software design pattern that fits every use case because JS is such a unique and flexible language.
0 u/iamjanesleftnipple 22 Mar 2016 03:40
Excellent synopsis. Every time I think about starting an angular project I get about two seconds in and realize jquery/plain ol' js is so much better and extendable
0 u/pray_the_gay_away 22 Mar 2016 04:40
I just started using ReactJS for work, it's a lot less rigid, a little more light weight. It works for forms I guess.
If you want to have a rich touch interface that works on 3rd world smartphones, you gotta code most of it from scratch, scope the shit out of everything, manage your memory very carefully.