markdown guide

Yes, you can! I've actually considered trying out sometime how performant it is(n't) to use jsdom to output HTML on a "real" server :D


They funny thing is that jQuery is a Bootstrap dependency.


I think that the real definitive backend framework is Mozilla ๐Ÿ˜†


Vanilla js is great they have an awesome website too. Go and download a copy!


Haha been using js for 15 years, and today is the first time I've looked for js.com ๐Ÿคทโ€โ™‚๏ธ


The best JavaScript framework is always the one you havenโ€™t used.


LoL. This answer should be printed in Christmas greetings cards


I was thinking fortune cookie ๐Ÿฅ  but Iโ€™ll take it!


Angular? No Google or bust.
Vue? It's basically one guy, come on.
React? Boo, Facebook evil! And also pretty much one guy.
Preact? Get the FUCK OUT OF HERE.
Backbone? Stupid name, no way.
Ember? Come on now you're just making up names.
WebComponents? That's not.. has nothing to do wit.. just forget it.
Meteor? Yes take the spaghetti to the server, too no?

I don't know man, they all suck. Just throw a coin or something.


With an aversion to JavaScript, I'll just comment that while learning Python/Django, I've been lead towards reading the docs of backbone.js. It's tolerable; the two map pretty nicely to each other. I also like the look/docs of riot.js.

Otherwise, yes; 100%, your comment.


It depends

For a simple portfolio => VanillaJS
For a cool project to show=> React
For a complex app => Vue
For an enterprise-level app => Angular

That's all IMO ๐Ÿ‘ป


For enterprise apps, angular is a devil considering they made so many incompatible version upgrades and it is such an opinionated framework. Something stable like jquery and/or backbone is more suitable for enterprise apps.


I think the enterprise appeal with Ng is its opinionated project structure. There's not much wiggle-room, so onboarding a new Ng dev to a 3-year-old Ng project is almost nil. ... compared to something else, this hire may take weeks to hit velocity.

And by "enterprise", we mean somewhere large enough that employee churn is part of the game, and devs are disposable.


I never expected I would agree with anyone in this kind of thread ..yes ๐Ÿ‘


What? Angular for Enterprise-level app? Angular's inconsistency can't make it. LOL.


Honestly? I've never had a better developer experience than in the late 2000s with backend-rendered templates with a sprinkling of jQuery for dynamic bits.

It was fast, accessible, worked in every browser, and if you did things right (caching, streaming the header before the body is ready, etc.), navigations felt seamless. We've still got some of these running that haven't been touched in a decade (other than updating dependencies and changing company themes).

clip from The Simpsons: old man dancing, singing "gimme that old-time fun"

But, when I really need the interactivity of a JS framework, my go-to is Vue, though I am very, very interested in the approach used by Svelte. I also really like Web Components with lit-element, but I feel there's still a bit of work to be done by the community to reduce the amount of plumbing needed to build a full app with them.


Now, to get really controversial: nothing's better than an page with just the standard header and an iframe containing the body.

Except maybe <frameset>...

Animated: old man breaks a plate and says "come on, grease monkey, let's tangle!"


Wondering if anyone here has heard about thing called backbone.js. Though its an old framework, a large part of enterprise world still prefers it instead of modern ones like angular/vue.js.

On the backend or node side, express probably wins hands down.


I'm curious about the "popular" frameworks' popularity, so I've started a twitter poll myself. Do vote and let me know your choice!


Backbone... now there's a name I haven't heard in a long time...


It was the first framework I used , old is gold :D


We had this in production 11 years ago.

Zombie Views, Zombie Views everywhere.



Pending its completion.

import * as m from 'mithril'
import { Component } from 'monster'

import JourneyChapter from 'components/journey_chapter'

export default class Journey extends Component
      presence: true
      array: true
    target: true
    user: true
    console.log 'chapters', @chapters
    m 'section.journey',
      m '.wrap',
        m '.section_title'
          m 'h3', 'Your Journey'
          m '.clear'
        m '.body',
          m '.chapters_wrap'
            m '.chapters',
              for chapter in @chapters
                m JourneyChapter,
                  chapter: chapter
                  target: target
                  user: user

It's used to power ExamPro and I've been working on an end-to-end tutorial on how to use it:

I organized the code into star trek-like departments

The CLI is also star trek inspired. So when you want to create a new app you type:

computer begin program <name-of-web-app>

Why create a new Javascript framework?
Modern framework feels over-engineered. I want to have the productivity that I used to have but I need a framework that is:

  • isomorphic,
  • solves all common use cases
  • has a strong dsl
  • with great documentation.

So far nobodyโ€™s falling for my bait ๐Ÿ˜„


As far as I know, vanilla is always the best flavor.

(Donโ€™t trust me yet Iโ€™m not experienced enough to have a proper informed opinion)


None of them. As in a tool in mechanics or construction, there is the right tool for the job, it's just a matter of knowing enough to pick the right one. Sometimes all you need is a hammer and a crowbar, other times you might need that volt meter, pressure gauge, and torque wrench... It just depends.

I use React, I think it's great but I've looked into others, like Vue, Angular, Svelte, and see their usefulness and benefits. Personally, I would love to master all the things but I chose to focus on React ecosystem and JavaScript I plan on getting into TypeScript.


You always need duct tape around. I leave it to you to decide your analogical tech equal to duct tape lol ๐Ÿ˜†


Are you serious? You want to have orange website thread here?


Iโ€™m banking on some self-awareness here.


Ah yes, Ask dev.to posts, one of my favorites...


Fake News LOL. More like whatโ€™s the best JavaScript practices in regards to frameworks is a better question. I hate with a passion when a student builds their entire portfolio with React when building it static and building one component that handles something that actually needs to be React ( using real time data, like an auto completing search bar ) will do.


It is very common to use a god damned 2 ton truck to move the contents of your night stand drawer.

But, i do get the need to show you actually know react, or whatever flashy thing facebook did.


The best javascript framework is all the friends we made along the way.


I'm a backend dev so all I just started to get into learning React and personally I find it makes it is pretty straightforward. My personal reasons for landing on React were because I looked at job applications at companies I admire and saw React as a requirement more than others. Anyone see Svelte and Vue used by really interesting companies?


Next.js + React + Typescript for me.

I was leaning toward Vue for quite some time but I've found typescript to be super helpful on really large apps. Last time I checked typescript cannot validate the template code the way it can for React jsx. Also Next.js 9 is really an absolutely wonderful platform and super flexible for the smallest to the largest apps. Nuxt for vue is great as well but Next 9 polished off the rough edges in my mind. React hooks have also grown on me considerably.

I do think Vue handles a few things better. The transition component baked in, computed values and watchers, truly reactive style, and event emitters are quite nice and intuitive in this framework.

That being said, I'm watching Svelte intently because I like the compiled approach to a front end framework, however their app framework Sapper is a little green for me to commit to on client projects just yet.

I think it's interesting that as of now, the combo of the front end library with typescript and the node framework is swaying my opinion as well. Typescript is a really nice, low-calorie safeguard for even small projects.



imo the next big iteration since react

Big Idea

All the work to make the state change reactive is done in compile time and not runtime thus speeding up things up alot.

Major Drawback

Still an early framework, so it will need some time to be a truly competitive alternative to something like react and vue, but it will in my mind surpass them eventually


I've tried a bit of react.js wasn't that much into it, and later devoted more time in learning Vue.js which was more interesting to me personally.
Later on, will surely come back to react to study it better.


I want people to keep making frameworks so we have good ideas to steal for the next "best" framework.

Svelte 3 made me feel like when I saw Angular the first time. Keep 'em coming.


Thats some mighty fine bait you've got there.

For real though, I'm slowly becoming partial to Svelte. I love the idea behind it, and its fun to play with. But, as with a good amount of other devs have posted in the thread, "best" depends on the situation.


Hahaha as the disclaimer goes it depends

But for MYSELF

FW to get paid bank: React
FW to build a start-up from scratch: Vue
FW to build app's FAST: Vue
FW to land freelance clients: React
FW to stick to one language: Node/Express
FW to work with an ML environment via API: Python Flask API

FW to get paid today?: Whatever you're currently good at


React isn't a framework guys... Frameworks are evil, juste use react with plain old vanilla es6, eventually redux, lodash, typescript if you like having a complicated life and you're on for writing any webapp ๐Ÿ˜

For pure website, PHP or JEE are fine, excepts if you want to deal with ssr shit (and a lot if technical debt).

Maybe there is a start of a troll but I guess it's pretty fair, right ?


Guess it depends what is your background, how big the team for project is, what the project is about and how much you want to earn. I used to do a lot of projects with jQuery, did some stuff with VUE, did also some small project with Svelte (could replace jQuery..) but decided to dig deep into React. Why? Because after joined a new project the team already used React so had to learn it. Understood that there is a HIGH demand of React devs I decided to follow this path even if my heart goes to VUE/Svelte.


Oh boy the can of worms have been opened...๐Ÿ›๐Ÿ›๐Ÿ› ๐Ÿ˜œ


The problem here is in the title: javascript.

Anyway, frameworks can't be best at anything, they only provide structure to your work, they are the idea on how things should be, how things can be made easier.

The "best" is the one that is most compatible with your own vision, which is subjective, hence, no winner can rise from that.



(Ohhhhhh i just made some people mad ๐Ÿ˜ˆ)


Angular - large projects
VanillaJs/TypeScript - rest projects


svelte, just an opinion, but i really like it


I've recently started playing with Svelte and I think I'm in love. For my work stuff, I still go Angular because of its opinionated nature, but that may change in the future


Just my two cents.

Svelte for Front-end hands down. It really deserves more attention as it really does helps when developers don't have to fight with the framework they are using and just use it with as little mental boilerplate as possible.

Fastify seems to be one of the fastest back end framework out there. Structure of Fastify is really appealing too.

TailwindCSS is one of my personal favorite CSS tool / framework out there.


It depends ๐Ÿ˜‚

Honestly, whatever your team decides on as a whole ๐Ÿš€

Or what your ORG uses ๐ŸŽ‰

Classic DEV Post from May 3 '19

Are you a multi-passionate developer?

When I started on the path towards being a developer, I did not realize how many ...

Ben Halpern profile image
A Canadian software developer who thinks heโ€™s funny. He/Him.

Make better choices about your code and your career

Create Your Account