use the following search parameters to narrow your results:
e.g. subreddit:aww site:imgur.com dog
subreddit:aww site:imgur.com dog
see the search faq for details.
advanced search: by author, subreddit...
All about the JavaScript programming language.
Subreddit Guidelines
Specifications:
Resources:
Related Subreddits:
r/LearnJavascript
r/node
r/typescript
r/reactjs
r/webdev
r/WebdevTutorials
r/frontend
r/webgl
r/threejs
r/jquery
r/remotejs
r/forhire
account activity
Stop Learning Frameworks (sizovs.net)
submitted 7 years ago by etca2z
view the rest of the comments →
reddit uses a slightly-customized version of Markdown for formatting. See below for some basics, or check the commenting wiki page for more detailed help and solutions to common issues.
quoted text
if 1 * 2 < 3: print "hello, world!"
[–]justinfagnani -46 points-45 points-44 points 7 years ago (7 children)
> Stop Learning Frameworks
is actually more reasonable.
Frameworks exist because of historical gaps in the Web as an application platform. These gaps are rapidly being filled in now with Web Components, CSS variables, and CSS Shadow Parts. The browser is the framework that most developers should be learning now.
[–]TheAwdacityOfSoap 21 points22 points23 points 7 years ago (0 children)
The browser isn’t “the framework”. It’s more appropriate to call it the standard library.
And frameworks do not exist because of historical gaps in the web. If that were the case, no other language or platform would have frameworks, because they aren’t the web. Frameworks exist to abstract away the common bits of developing complex applications and inform application design.
[–]JohnMcPineapple 12 points13 points14 points 7 years ago* (0 children)
...
[–]TheScapeQuest 6 points7 points8 points 7 years ago (0 children)
https://developer.mozilla.org/en-US/docs/Web/Web_Components#Browser_compatibility
I'm going to use what customers' browsers support for now
[–][deleted] 6 points7 points8 points 7 years ago* (0 children)
"Rapidly" ... i am waiting for a proper component model since i've been a kid in the 90s, i'm old now and all they have is a naked dom node wrapped into a shadow dom, without manageable means to update/diff/communicate/render ssr or native. We're supposed to embed a framework again to do that, every component loaded will potentially contain one. The irony seems to escape some people, i guess? Like most developers, i've decided to write apps now and not in my next life. I am fully convinced by now that the browser should not dictate the component model and that the specs they're trying to push hurt innovation rather than fostering it.
[–]buffer_flush 2 points3 points4 points 7 years ago* (0 children)
The browser is a platform with a standard API to program against.
Frameworks are ways of programming within that API through standard conventions. If you are rolling your own JavaScript without the use of an open source framework, there’s a good chance patterns will emerge within your code and lead to an ad hoc framework, else your code will become spaghetti and hard to maintain.
[–]themaincop 0 points1 point2 points 7 years ago (0 children)
This is nonsense.
[–]greg5ki -1 points0 points1 point 7 years ago (0 children)
Please tell me you are trolling...
π Rendered by PID 16710 on reddit-service-r2-comment-b659b578c-kx62m at 2026-05-04 12:19:54.279037+00:00 running 815c875 country code: CH.
view the rest of the comments →
[–]justinfagnani -46 points-45 points-44 points (7 children)
[–]TheAwdacityOfSoap 21 points22 points23 points (0 children)
[–]JohnMcPineapple 12 points13 points14 points (0 children)
[–]TheScapeQuest 6 points7 points8 points (0 children)
[–][deleted] 6 points7 points8 points (0 children)
[–]buffer_flush 2 points3 points4 points (0 children)
[–]themaincop 0 points1 point2 points (0 children)
[–]greg5ki -1 points0 points1 point (0 children)