5 ms·

3rd-Age: People will finally learn to effectively use vanilla JS, DOM API, HTML5, and CSS3 and will stop relying on transient abstraction tooling. They will act

3rd-Age: People will finally learn to effectively use vanilla JS, DOM API, HTML5, and CSS3 and will stop relying on transient abstraction tooling. They will actually learn the standards rather than rely on a Tech team's rendition of the next new thing. Roast me

ng12 6y ago
Roast you? How about this: a version of this comment is posted on just about every JavaScript post for the last five years and it hasn't changed much.
- yc12340 6y ago
  > a version of this comment is posted... for the last five years Sounds like he is right and you are too old and averse to change to admit it!
JSavageOne 6y ago
Given that we've gone in the opposite direction towards greater abstraction from jQuery -> React/Angular/Vuejs and more tooling, doesn't seem likely.
- RyanGoosling 6y ago
  I've* (not we've)
  - JSavageOne 6y ago
    No, we've. If you're a professional JS developer in 2020 coding everything in vanilla JS with no framework or tooling, you are in the minority.
    - RyanGoosling 6y ago
      I'm just going to link this with no other context: https://www.youtube.com/watch?v=Yx6k6WR8GRs https://www.youtube.com/watch?v=Yx6k6WR8GRs
      - deleted 6y ago
        [deleted]
  - SketchySeaBeast 6y ago
    Is this a debate one that's based upon what you think is actually happening, or what you hope is actually happening? I admit I don't have a perfect vision of the industry, but frameworks seem very popular.
discreteevent 6y ago
I started off programming Windows 3.1 in C. So that argument just holds no attraction for me. As far as I'm concerned the browser is a bloated and extremely poor abstraction for building a UI (although it's a good document viewer). Any framework on top of it is peanuts in comparison.
rk06 6y ago
Web Components are the future! /s
- RyanGoosling 6y ago
  https://developer.mozilla.org/en-US/docs/Web/Web_Components https://developer.mozilla.org/en-US/docs/Web/Web_Components Yes! Component design and rendering state changes does not require Vue/React/Angular, wake up people!

ng12 6y ago

Roast you? How about this: a version of this comment is posted on just about every JavaScript post for the last five years and it hasn't changed much.

yc12340 6y ago
> a version of this comment is posted... for the last five years Sounds like he is right and you are too old and averse to change to admit it!

JSavageOne 6y ago

Given that we've gone in the opposite direction towards greater abstraction from jQuery -> React/Angular/Vuejs and more tooling, doesn't seem likely.

RyanGoosling 6y ago
I've* (not we've)
- JSavageOne 6y ago
  No, we've. If you're a professional JS developer in 2020 coding everything in vanilla JS with no framework or tooling, you are in the minority.
  - RyanGoosling 6y ago
    I'm just going to link this with no other context: https://www.youtube.com/watch?v=Yx6k6WR8GRs https://www.youtube.com/watch?v=Yx6k6WR8GRs
    - deleted 6y ago
      [deleted]
- SketchySeaBeast 6y ago
  Is this a debate one that's based upon what you think is actually happening, or what you hope is actually happening? I admit I don't have a perfect vision of the industry, but frameworks seem very popular.

discreteevent 6y ago

I started off programming Windows 3.1 in C. So that argument just holds no attraction for me. As far as I'm concerned the browser is a bloated and extremely poor abstraction for building a UI (although it's a good document viewer). Any framework on top of it is peanuts in comparison.

rk06 6y ago

Web Components are the future! /s

RyanGoosling 6y ago
https://developer.mozilla.org/en-US/docs/Web/Web_Components https://developer.mozilla.org/en-US/docs/Web/Web_Components Yes! Component design and rendering state changes does not require Vue/React/Angular, wake up people!