Sure It Is: The Time Dilation Of NPM Install

The JavaScript framework naming convention has officially reached peak confusion. First you're excited about Next.js, thinking you're cutting edge. Then suddenly everyone's talking about Nest.js and you have to pretend you knew the difference all along. By the time you figure that out, Nuxt.js appears and you're completely lost... wait, is it pronounced "nuxt" or "nuked"? And just when you thought you understood, you realize there's ANOTHER framework with practically the same name. At this point, I'm convinced framework creators are just hitting random keys near 'n' on the keyboard and adding ".js" to whatever comes out.

Content I don't get why Javascript gets such a bad rap: You take a whatever and put that as an argument into a function that could also be an object, and then you transform that whatever into a whatever that another function, or whatever, will be able to render to the user. Easy peasy.

Content Dhanush N DhanushXen HTML - for structure CSS - for style Javascript - for fun React - for work C - for dinosaurs C-for college Swift - for UI Ruby - for rails Query - for legacy Python - for science Typescript - for safety Java - for 3 billion devices 8:29 AM 02 Jul 21 ZIappo.com 603 Retweets 58 Quote Tweets 3,062 Likes 17 ProdrammerHumor.io

Content U W NAME

Content Andrew Trask iamtrask 18h If you were dropped 2000 years back in time with nothing but the knowledge you have now - what would you do? 3,170 174,175 2,722 1 Sunil Pai sunilkpai Replying to iamtrask warn them about javascript 18:36 26072020 Iwitter Web App 5 Retweets 277 Likes v

Content Javascript first appeared in 1995. Programmers in 1994: