4 ms·

> Today's JavaScript developer is acting like they have a 100 GHz CPU with terabytes of memory. And being lazy and uninspired as a result. Not sure how I feel

> Today's JavaScript developer is acting like they have a 100 GHz CPU with terabytes of memory. And being lazy and uninspired as a result. Not sure how I feel about a statement this broad. I work mostly with front end code and I try neat things and tricks to reduce resource use all the time. I also always push for the lightest way of doing things in PRs. I’m certain I’m not the only engineer who thinks like this.

kstrauser 8y ago
I agree. I don't do frontend stuff, but I sit next to the team that does. They take a lot of pride in making fast-loading pages that render quickly and respond instantly. That's not compatible with writing giant, bloated, inefficient code.
- vezycash 8y ago
  >They take a lot of pride in making fast-loading pages that render quickly and respond instantly. Maybe in your company. My experience browsing modern front-end SPA design however begs to differ. They pride themselves in loading megabytes of uncompressed images, layers of invisible background images, frameworks to load frameworks, auto-download/auto-playing 4k videos...
  - seattle_spring 8y ago
    No one prides themselves on any of those things.
    - chris_wot 8y ago
      And yet they still do it.
- choochootrain 8y ago
  i agree with you but you have to keep in mind that pages which load fast on a fiber connection and render and respond quickly on the latest macbook don't guarantee the same for the average user. giving devs 4 year old laptops would help but when shiny startup is offering new macbooks how can you compete?
  - pbhjpbhj 8y ago
    Giving devs 4yo laptops when they only need then for testing seems, erm, strange, limiting. Just have them test under processing and bandwidth limits?
shados 8y ago
Definitely can't generalize, but the average macbook pro sporting web dev often forgets what their users deal with. I had conversations at work where I pointed out the data we had on our users (and how they weren't even close to having that kind of hardware and internet connection), and no one would believe me until they saw the data themselves.

kstrauser 8y ago

I agree. I don't do frontend stuff, but I sit next to the team that does. They take a lot of pride in making fast-loading pages that render quickly and respond instantly. That's not compatible with writing giant, bloated, inefficient code.

vezycash 8y ago
>They take a lot of pride in making fast-loading pages that render quickly and respond instantly. Maybe in your company. My experience browsing modern front-end SPA design however begs to differ. They pride themselves in loading megabytes of uncompressed images, layers of invisible background images, frameworks to load frameworks, auto-download/auto-playing 4k videos...
- seattle_spring 8y ago
  No one prides themselves on any of those things.
  - chris_wot 8y ago
    And yet they still do it.
choochootrain 8y ago
i agree with you but you have to keep in mind that pages which load fast on a fiber connection and render and respond quickly on the latest macbook don't guarantee the same for the average user. giving devs 4 year old laptops would help but when shiny startup is offering new macbooks how can you compete?
- pbhjpbhj 8y ago
  Giving devs 4yo laptops when they only need then for testing seems, erm, strange, limiting. Just have them test under processing and bandwidth limits?

shados 8y ago

Definitely can't generalize, but the average macbook pro sporting web dev often forgets what their users deal with. I had conversations at work where I pointed out the data we had on our users (and how they weren't even close to having that kind of hardware and internet connection), and no one would believe me until they saw the data themselves.