What next

[eternaloptimist]

hey all,
Just curious what most front-enders are using these days. React, (Google/Angular) Material-Design, Polymer 1.0, Vue, Angular, Gulp etc? Been learning most of this myself but it's getting out of control lol. Many things doing the same thing. What do you guys use?

 

[Turgon]

DOM.

I prefer to stay away from the ever-changing catwalk of framework fashion.

 

[^^vampire^^]

Frameworks are useful but like Turgon said if it can be done well with just DOM then go for it. It was fine when just AJAX and JQuery were on the board but now there are 10's, if not 100's of frameworks available. They're flooding the development world and a lot of these will stop development after a few years which will mean huge rewrites of your code in the future.

 

[semaphore]

Frameworks are useful but like Turgon said if it can be done well with just DOM then go for it. It was fine when just AJAX and JQuery were on the board but now there are 10's, if not 100's of frameworks available. They're flooding the development world and a lot of these will stop development after a few years which will mean huge rewrites of your code in the future.

Um. All that awesome dom code you are writing is basically doing what the frameworks already do (far better). Also there are frameworks that have been around for a very long time and due to the massive investment and support they are not going to disappear anytime soon (angularjs, reactjs, ember).

 

[shauntir]

Um. All that awesome dom code you are writing is basically doing what the frameworks already do (far better). Also there are frameworks that have been around for a very long time and due to the massive investment and support they are not going to disappear anytime soon (angularjs, reactjs, ember).

^ Listen to this guy.

<sarcasm>OP, don't learn angular and node. Why, because then you can't apply for a job that actually uses these technologies and be on cutting edge. Rather, dev using your own built libraries that is way more tested and feature rich than angular, jquery, node etc. Since you never know, open source libraries like these will be dead in a few years.</sarcasm>

 

[^^vampire^^]

Um. All that awesome dom code you are writing is basically doing what the frameworks already do (far better). Also there are frameworks that have been around for a very long time and due to the massive investment and support they are not going to disappear anytime soon (angularjs, reactjs, ember).

Yeah I'm quite aware of what the frameworks are and what they do thanks. What I'm saying is that everyone is jumping on the bandwagon and so every job you see has a requirement for some obscure framework. Yes the likes of JQuery etc aren't going anywhere but why put yourself in the position of having to do a major rewrite by using a framework that might be dropped in a year or two. Obviously making use of a javascript framework doesn't mean you will automatically be in this position but it can happen with the less popular ones.

 

[Turgon]

...Yes the likes of JQuery etc aren't going anywhere...

Even jQuery is going to change massively (if it wants to remain relevant), because it has been targeting a development approach that is losing ground in relation to all the newfangled 'data-binding' methodologies of newer frameworks. jQuery is (mostly) a DOM manipulation wrapper, and no-one wants to manipulate the DOM 'directly' anymore, so no-one will want jQuery as it currently stands.

On top of all that, see this Ouroboros of silliness:
The newer DOM spec has had to compromise certain forward-thinking API designs because jQuery 'reserved' some namespace it "shouldn't have" in it's early days: From DOM4:

5.2.2 Interface NonElementParentNode

The getElementById() method is not on elements for compatibility with older versions of jQuery. If a time comes where that version of jQuery has disappeared, we might be able to support it.

Ugh!

POSIX C for the Win!