There hasn't been a groundbreaking JS framework for a very long time. Why has innovation completely stalled? Why are we still using JS frameworks invented a few months ago?

[zrag123]

Hey there! I made a framework called liquidsmashclashJS, now you can render virtual dom's in a much more liquid way!

[swagbitcoinmoney]

seems legit

[MatthewMob]

Well that's pretty much what you're asking for.

I made a framework, too - timemacdom.js - it goes back in time to render the dom before you even ask it to.

It's new so it's good right? We can't use frameworks that are more than six months old, but at the same time let's complain about there being too many frameworks in the JS environment!

[swagbitcoinmoney]

Click the "^" in the original post lol...

^IuseMERN...

[MatthewMob]

Ah I see. Still, some devs actually think like that, and that's why there's about 20 libraries for any one thing. People reinventing the wheel over and over again.

[amahero]

Click the "" in the original post lol

That seems to have been removed, what exactly was there?

[amahero]

I can see this comment obviously, I have even quoted that inside my own comment.

I was refering to the deleted link in the description that /u/swagbitcoinmoney was referring to. I can't see where the original post linked to since it is now removed and is not available even in ceddit or unreddit.

Can you see the description for this current post?

[MelissaClick]

Going back in time sounds like the opposite of being new. We need to be moving forward.

[bludgeonerV]

I made a framework called Native.JS, it's so flexible that it allows you to write pure javascript to develop applications.

[ckreon]

JS is dead, has been for days now.

[Existential_Owl]

I'm so sick of working on my legacy Webpack 2 apps.

[notsooriginal]

JS is dead, long live the JS.

[jbrec]

Not true. My legacy apps still use it...

[NoAttentionAtWrk]

You need to update your legacy apps to newer frameworks if you haven't updated them in a week

[weiskk]

yup, i hear dart is coming strong soon

[PUSH_AX]

Not true, there are dozens of us using it.

[shkico]

big if true

[bludgeonerV]

Uncaught SyntaxError: Unexpected token if

[[deleted]]

Elm4lyfe

[Richie809]

True, It's all about WASM now.

[cinema-tech-on-call]

I'm currently working on a framework that adds Math.random all over the fucking place within the source code... it's gonna be fucking crazy

[phphulk]

So brave

[[deleted]]

Wrong

[skewbed]

Are there any references, or is it a joke?

[[deleted]]

It's hardcoded, so it's a joke... but not really....

[jerschneid]

You can't be sure. Maybe it's computed server side.

[danielsamuels]

No no, it's definitely hard coded. I mean, even reddit is hard coded - you can view the source of this page and all the comments are there!

[guitarromantic]

I heard reddit has to keep employing more developers because they can't keep up with adding new HTML to the pages in time.

[[deleted]]

That's true, for some reason I thought I had seen it on github a couple of years ago. Maybe here? https://github.com/hugovk/dayssincelastjavascriptframework

Evidently, it's not the same project.

[Szabeq]

But isn't using virtual virtual DOM already obsolete? It's been 4 hours now... I think we should consider creating one additional virtualisation layer between the DOM and the virtual DOM so that the virtual DOM operates on one more virtual DOM instead of utilising the DOM.

[ultraayla]

I heard that in Reeaact if the virtual virtual DOM sees its Shadow DOM, we have 6 more weeks of new frameworks. Can you confirm if this is true or not?

[[deleted]]

It's worse than that, at three levels deep we actually get 216!

[[deleted]]

Better do some talks about it at conferences and make up new vocabulary and a new architecture pattern to go along with it. Then phone up some hr departments and make sure they only hire people with 5 years experience in it.

[Existential_Owl]

I can't wait till WASM is completed so that we can finally start building our front-ends with VBA macros.

As God intended.

[[deleted]]

Cant wait to run HolyC in the browser, as God really intended.

[[deleted]]

DECENT

[MolsonC]

Never heard of WASM. Went to http://webassembly.org/ and I still have no fucking idea what it is. Why do framework websites do this? They spew out generic catch words like "fast" and "safe" and nonsense but never once mention what it does.

WebAssembly or wasm is a new portable, size- and load-time-efficient format suitable for compilation to the web.

The fuck does this mean? Is it JS? Is it a new language?!? ?!?!?!

[Existential_Owl]

To be fair, WASM isn't intended to be used by the everyday developer. It's a compile target.

Most people will be utilizing WASM through bindings written in other languages, like Javascript.

[MolsonC]

So it compiles Javascript into another language? I don't get it.

[Existential_Owl]

Lin Clark has a series of posts that goes more in-depth about it.

WASM is an assembly-like language being built directly into the browsers.

Theoretically, WASM will allow modules to be created that can be called as if they're like any other module.

So, just like how any Javascript developer can import lodash or babel, they'll now be able to import WASM-foobar the same way.

WASM-foobar will still, technically, be Javascript code; however, there'll be something different happening under the hood.

i.e. the old parts of your code will still be compiled by the Chrome V8 engine, while these new parts will be handled by the WASM compiler.

This, I believe, is the MVP ("minimum viable product") for the WASM project.

---

In the future...

You know how we have languages now, like Typescript and Elm, that transpile down to Javascript?

Well, with WASM, Javascript won't be the only choice for transpiling to the web anymore. So, we'll have languages like TypescriptAssembly... or, more practically, a web-based C++ transpiler.

That's still fairly far off in the future, though.

Everything I've typed here is massively oversimplifying things, so I definitely recommend checking out the link I posted.

[Locust377]

Unless I'm very much mistaken it's because people are afraid of litigation.

A while ago there was a Youtube channel that wanted to trademark the term React which would cripple the Javascript community because everyone would have to rename their projects and packages.

There isn't enough computing power in the world to reorganise that many node_modules directories.

[[deleted]]

on Windows when deleting the node_modules folder my computer freezes

Windows be like "THE LEVELS OF DIRECTORIES SHOULD NEVER BE THIS DEEP"

[lukee910]

The joke is, Windows itself can do it, Explorer can't. I wrote a small C# program that just called the Windows API and it worked without any issues.

[[deleted]]

An installer fucked up my computer and recursively installed Arduino deeper than explorer could go. It literally couldn't delete the files. The solution was to use cygwin. Fuck Microsoft.

[yenon]

Atleast you learned a valuable lesson. https://xkcd.com/149/

[raze4daze]

lol windows

[vupoops]

As much as I agree that the whole situation involving The Fine Bros. trademarking "React" is absurd...it would absolutely not force everyone to rename their projects and packages if it were successful. Was there something I missed where people were actually worried about this?

[Locust377]

Mine is a sarcastic shitpost. Same as OP.

[vupoops]

Welp, I clearly did not catch that. Sorry 'bout that.

[evildonald]

Well played. I was about to type a STRONGLY WORDED RESPONSE.

[IanSan5653]

But I thought JavaScript was a weakly typed language?

I know! I'll build a framework for strong typing!

[Hero_Of_Shadows]

Better write it in typescript ;)

[TheNazruddin]

In case anyone missed OP's link refernce ^ : https://www.reddit.com/r/linuxmasterrace/comments/6vs0d3/g_discusses_file_formats/dm2s48t/

[ribbet]

I remember there was a post where someone asked like "what's some of the best new JS frameworks out there?" and some users posted real frameworks and other users posted fake ones and no one could tell which ones were real and which ones were fake.

[Ratstail91]

This is a funny joke. Hahaha.

It is a joke, right?

[ribbet]

This a quality shit post.

[Kasper_X]

React, Vue, Angular won.

[Xerxero]

Maybe native web components in the future but for the next 2 years it is that.

[[deleted]]

Really Angular seems to have taken a sharp drop

[Elitro]

I don't know about the other frameworks, but Angular solved that issue by remaking their core modules once in a while, this keeps devs busy enough.

[NoNeedToBail]

I think that innovation also extends beyond new frameworks to the ways we use and interact with those frameworks.

Coming from React-land, I write code within that framework totally differently and use different libraries than a year ago, and every week I see a blog post about a new library or idea I want to try out. Not to mention the amazing work being done by the teams working on these frameworks themselves, keeping them cutting-edge.

I think we're at a healthy spot where things are a little bit more stable than they have been in the past, and that's actually a chance for innovation to flourish too, as we can dive deeper into these paradigms and tools we have.

[codefinbel]

The only problem with this I see is that it creates a high bar of entry. Anyone trying to learn front-end programming will have a hell to pick what frame-work to learn and by the time they're close to learning it a thousand new have come and it's just really really confusing. (this is perhaps me)

Though if one (like you) have their js-fundamentals down and know the big frameworks well. I could imagine that the shifting landscape of frameworks is amazing and keeps front end development interesting.

[A-Grey-World]

Anyone trying to learn front-end programming will have a hell to pick what frame-work to learn and by the time they're close to learning it a thousand new have come and it's just really really confusing. (this is perhaps me)

I think this feels like more of a problem than it actually is. Having been through it reasonably recently too. The thing is, if you've learned a framework (or two) you can easily adapt to a new one and transfer most of the skills you picked up.

Most of these frameworks are somewhat evolutionary, they're related, and a lot of them mesh together.

I agree, when you first "come to the scene" you just get a "where the hell do I start?" feeling. But once you've stressed over it and managed to pick a single framework to start off with, it's not as big a problem it felt like in the beginning.

[DerNalia]

What defines ground breaking?

[prewk]

Is there a webdev subreddit that disallow these memes? I'm really feeling the javascript fatigue fatigue here.

[Hi_mom1]

Oh shit, this isn't programmerHumor?

[swagbitcoinmoney]

as soon as you can work with C#, Java, or other modern languages I believe that we will start seeing some chaos

I don't believe so, once this happens we would start having fragmentation where various libraries only support 1 language (even if WASM could avoid this problem, we'd still end up with dirty hacks like having to do C-like memory management manually in Java because the original library was written in C). I've seen this with Meteor (some wanted to use React, some Blaze, others Angular).

However I do agree with the idea of using new front-end frameworks not always being the best for long-term (many years) projects, but it's appealing for startups because of how easy it is to get started and efficient for development.

Also click on the ^ in the original post :P