5 ms·

2.) looking things up. Well, shit. Is this even possible in web development these days? With the exception of jQuery, there hasn't been a single JS or backend

2.) looking things up. Well, shit. Is this even possible in web development these days? With the exception of jQuery, there hasn't been a single JS or backend framework that I've used from one year to the next.

nostrademons 11y ago
So don't use them. Virtually all my work at Google was with vanilla JS and I had the DOM APIs memorized in my head.
- S4M 11y ago
  So how do you know you're not missing out, or more precisely, that you're not missing out and what you are missing out is so great that the productivity you gain from restricting yourself to the subset of tools you fully master does not compensate for what you are missing out - I am thinking of frameworks like Angular or React? I am asking that as someone who doesn't use the frameworks I mentioned and sticks with vanilla JS and DOM APIs. If you were at Google I suppose that you had lots of technical conversations with colleagues so you more or less knew about the latest trends and their benefits, but it's harder at a smaller company or working on your own.
  - PopeOfNope 11y ago
    Anybody who adopted Angular right out of the gate is kicking themselves now because everything they wrote in the last year is now obsolete. Hopping on the latest thing might be fun and you might learn a few things, but I'd prefer to wait for things to be fully battle tested and have a good history of support before I put it into production. Another good reason is speed. It's rare for a framework to be faster than native DOM api's. And the app loads faster!
  - nostrademons 11y ago
    That's the question everyone asks, right? People tend to be really insecure about the possibility that someone else might be doing better than they are. The short answer is that you don't - there is always the possibility that someone has invented something that lets someone else do your job way more effectively. But you accept the risk that you're missing out for the certainty that you're getting features done and code written quickly. And periodically, maybe look around and try some of the new inventions that seem to be getting traction to see if they really do make your job better. The key point is to rely on your own data and observations rather than the opinions of others.
- PopeOfNope 11y ago
  I'd love nothing more than to just use the latest DOM APIs, but every company I've spoken to in the last 5 years wants a framework. They feel more comfortable working with an app structure that everybody else is using to supposedly great effect.

nostrademons 11y ago

So don't use them. Virtually all my work at Google was with vanilla JS and I had the DOM APIs memorized in my head.

S4M 11y ago
So how do you know you're not missing out, or more precisely, that you're not missing out and what you are missing out is so great that the productivity you gain from restricting yourself to the subset of tools you fully master does not compensate for what you are missing out - I am thinking of frameworks like Angular or React? I am asking that as someone who doesn't use the frameworks I mentioned and sticks with vanilla JS and DOM APIs. If you were at Google I suppose that you had lots of technical conversations with colleagues so you more or less knew about the latest trends and their benefits, but it's harder at a smaller company or working on your own.
- PopeOfNope 11y ago
  Anybody who adopted Angular right out of the gate is kicking themselves now because everything they wrote in the last year is now obsolete. Hopping on the latest thing might be fun and you might learn a few things, but I'd prefer to wait for things to be fully battle tested and have a good history of support before I put it into production. Another good reason is speed. It's rare for a framework to be faster than native DOM api's. And the app loads faster!
- nostrademons 11y ago
  That's the question everyone asks, right? People tend to be really insecure about the possibility that someone else might be doing better than they are. The short answer is that you don't - there is always the possibility that someone has invented something that lets someone else do your job way more effectively. But you accept the risk that you're missing out for the certainty that you're getting features done and code written quickly. And periodically, maybe look around and try some of the new inventions that seem to be getting traction to see if they really do make your job better. The key point is to rely on your own data and observations rather than the opinions of others.
PopeOfNope 11y ago
I'd love nothing more than to just use the latest DOM APIs, but every company I've spoken to in the last 5 years wants a framework. They feel more comfortable working with an app structure that everybody else is using to supposedly great effect.