Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I got tired of relearning JavaScript frameworks and instead tried to escape their clutches.
Most of my developer life I've spent relearning how to do the same thing in a different framework.
And every three or four years its the same story, figure out templating, figure out building, complain on github bugs etc.
I am trying to reduce framework fatigue by allowing you to think "can I make my application with just vanilla JavaScript". The advantage of vanilla JavaScript is it write once - do not need to rewrite.
Do YOU think I will abandon ship and end up having to use a framework again?19 -
Does any other front-end developer have the fear that we'll run out of handy words or phrases for JS frameworks and have to import massively long sentences to use what we need?6
-
When you find you should use `$("#id").html(response)` instead of `$("#id").innerHTML = response` and it works just fine out of a sudden.
So, how was your day?
4 -
All the articles about javascript fatigue lately. Omg just shut the fuck up already. Being a developer is hard, deal with it2
-
I prefer drugs. I’m learning JavaScript as my first programming language and just getting the basics and the syntax down is fucking killing me.
13 -
I don't consider myself a guru in JavaScript (hell I studied theoretical chemistry), but I do hate much of the rationalization behind building a Jenga stack of libraries, frameworks, dependencies... for building everything web related.
Many of the problems I see people solving with these giant stacks could be easily solved understanding how websites work (html, css, js and how interact with each other) with no dependencies giving smaller (for end users at least) and more maintainable code (in the sense it would not require updating dependencies that may be discontinued...)
I do imagine situations where these are ideal... Since there are not absolutes and developing is very context sensitive, but man if I have js article fatigue for ridiculous scenarios.2 -
It's official. I've hit javascript ~fatigue~. *Burnout*. STAAAAHP with all the frameworks and libraries and weirdly named stuff. To quote Abe Simpson: "I used to be with it, but then they changed what *it* was. Now what I'm with isn't *it*, and what's *it* seems weird and scary to me. It'll happen to you...".
I need to switch gears.1 -
I just learned vue.Js, its very easy to learn, and it introduced me to node js, now i can build node apps with express and i can even use modules and build my proper ones.
#javascript #VueJS2 -
All this talk of javascript fatigue, and yet when tools like parceljs come out people still regress to webpack... I don't get it9
-
Javascript fatigue. Because the node scene is so new it doesn't have the established isms and methods of best practices so every few months the next best framework or library comes out promising to fix the problems we all face
-
Webpack, requirejs, AMD, browserify all are wonderful tools but they don't play nice with node(client side) .
I LITERALLY switched between all, because the hacks worked but not quite. (Using node and electron, go figure!)
You know what they say fifth times the charm.
1
Top Tags
Weekly Rant
View