Nightmare for beginners

So true, srsly fuck front end development in 2018. JS hipsters fucked it up so bad it's became a motherfucking nightmare.

@vsg24 don't worry, next week we'll have a new framework that fixes everything ....

@Alice

Good to see dinosaurs alive and kicking.

Sorry, Just a joke... :)

@Alice

If you have not given webpack a look, please do.

https://survivejs.com/webpack/

@ajit555 webpack is the core of the problem.
The only reason to use node for front end is to use fucking es6 or newer shit, then webpackit so it is no longer fancy new JS so it can fucking run in a browser.

This all enormous ecosystem just blows.

Way too much of an overstatement. No one uses node in front end. Front end just shares it's package manager with node. Just because npm has n in it doesn't mean you gotta learn node to use it.

@hashris But you got have it on your PC, which is strange it‘s like having to install Java to compile Python.

In my day job there is a mesh of front end nightmare. Basically all of the above. And stuff is built in react etc.

In my side project / freelance stuff I just use html and css with the odd sprinkling of ..... jQuery!

Honestly you wouldn’t know the difference when using my personal apps versus day job apps.

@hashris how does the packages work without node? Its all javascript to be executed end during development.

But in my opinion thats something what is a part of an interpreted language especially one which is executed on a machine outside of your control.

With PHP you know what version you run, with javascript you cant know what the interpreter supports. Webpack and the like help unifying it in a way older interpreters also understand the newer syntax

Just learn Vue and webpack, then you got everything you need

@mundo03

The problem you are solving should drive the technology, not the other way round.

If you are just creating websites, with external libraries, or creating web application where server side generation of pages is done, perhaps you do not need webpack.

Do one thing. Create a simple Web application having a single HTML page, and 3 js files, A.js, B.js referencing A.js and C.js referencing both A.js and B.js. HTML page is referencing regular JS libraries like jQuery etc. Try calling logic from C.js in your HTML page.

Then the other week a framework that compiles the fix to another fix that's .5x father than the fix@ItsNotMyFault

@mundo03 I don't see webpack as the problem, on the contrary. For most projects it would be a nightmare to use es6 features without it. If there's one thing that screws everything up is the speed which things change and turn obsolete, but on the other hand that's a consequence of a rapidly evolving environment.

All these react, vue, webpack and whatnot is giving me fucking head aches

Too fucking complicated to know em all

Solution: Don't use JS.

Platform I work on used to have a tiny bit of JS — basically just an ajax call wrapper for some forms, so it could sync a checkbox click without the need for a submit button and page reload.

Now we use a pretty heavy crapload of Vue.

So now we have nice animated stuff, swiping tiles, fading texts, meh. Nothing has changed, functionally. We also have quadrupled the amount of bugs, and have much more device/browser related problems.

In my opinion, good modern design can be achieved with just html & css, and when you really need two-way binding and insertion of data in components because reloading the whole page is too much work... your page is probably too bloated and won't work on mobile anyway.

This is kinda taken out of context from this well written article: https://medium.com/the-node-js-coll...

@bittersweet using less JS is just the best thing devs could do now. I see so many websites and apps that would actually be better without a crapload of JavaScript.

People are spamming js when things can be done with simple html and css

Life is so sad

Lol and here I've spent the last year porting over a huge flash web app client to Vue.js, and the main html page is basically just an empty page with script includes and the rest of the page dynamically loads in sub pages as needed, honestly I don't think this type of project would have been possible without a framework. (Not to say I like JS or frontend for that matter)

And here I am writing my beloved vanilla js, using gulp only to minify and uglify and make it work without the hellish overload.

@ajit555 all that worls with out node, what is the point?

@FilipeRamalho I believe that's what the term overstatement refers to. It's just there on the system. No one has to earn it. You literally just install it and use the package manager.