3 ms·

> And since most managers care only about getting the project done on time and within the budget, this is what most developers concentrate on. I think that is

> And since most managers care only about getting the project done on time and within the budget, this is what most developers concentrate on. I think that is the crux of the issue succinctly put.

w_t_payne 9y ago
Yeah. This is a business and management problem, not a programming problem. If the business wanted to impose memory and compute budgets for different parts of the program, they could. This is what happens in aerospace and automotive when you have more than one program sharing a processor.
- agentultra 9y ago
  It happens in game development when you're targeting resource-constrained hardware consoles. It can happen in web development as well if you're working on a disciplined backend team that cares about designing for request latency and concurrency. But often scrappy startups don't have the time or money to care about those things. It's more about product fit and keeping customers happy to keep the money coming in. I personally don't use that excuse and design everything I can with a budget in mind. It's a nice constraint to have an upper bound on response time. Forces you to pick your battles.
  - noir_lord 9y ago
    My targets depend on context but I like client side stuff to be done in under 100ms since that was the limit for a human to feel like the interface is 'instant' I learnt at college. There a bunch of tricks you can pull to give that impression even when you have to go over that limit. These days I'm lucky, I only work on an internal web app that is almost entirely served over gig ethernet.
amiga-workbench 9y ago
Commercial software is very rarely of a sufficient quality. Software that comes out of nonprofits or the free software movement is arguably better built and treats the user better.
- sacado2 9y ago
  [citation needed] Lots of people stopped using firefox in favor of chrome precisely because firefox was incredibly greedy memory-wise.
  - noir_lord 9y ago
    I stopped using Chrome on Linux (except for development and testing) because it absolutely batters the CPU, enough that it powers on the fans on my laptops where FF rarely does. I've never really understand why either and it's been on two totally different laptops.
  - FridgeSeal 9y ago
    In their defence, Mozilla has done a lot of work to fix these issues, and Chrome really isn't that much better. I'm on FF 57 at the moment (nightly) and it's stupid fast. Like, really fast.

> And since most managers care only about getting the project done on time and within the budget, this is what most developers concentrate on. I think that is the crux of the issue succinctly put.

w_t_payne 9y ago

Yeah. This is a business and management problem, not a programming problem. If the business wanted to impose memory and compute budgets for different parts of the program, they could. This is what happens in aerospace and automotive when you have more than one program sharing a processor.

agentultra 9y ago
It happens in game development when you're targeting resource-constrained hardware consoles. It can happen in web development as well if you're working on a disciplined backend team that cares about designing for request latency and concurrency. But often scrappy startups don't have the time or money to care about those things. It's more about product fit and keeping customers happy to keep the money coming in. I personally don't use that excuse and design everything I can with a budget in mind. It's a nice constraint to have an upper bound on response time. Forces you to pick your battles.
- noir_lord 9y ago
  My targets depend on context but I like client side stuff to be done in under 100ms since that was the limit for a human to feel like the interface is 'instant' I learnt at college. There a bunch of tricks you can pull to give that impression even when you have to go over that limit. These days I'm lucky, I only work on an internal web app that is almost entirely served over gig ethernet.

amiga-workbench 9y ago

Commercial software is very rarely of a sufficient quality. Software that comes out of nonprofits or the free software movement is arguably better built and treats the user better.

sacado2 9y ago
[citation needed] Lots of people stopped using firefox in favor of chrome precisely because firefox was incredibly greedy memory-wise.
- noir_lord 9y ago
  I stopped using Chrome on Linux (except for development and testing) because it absolutely batters the CPU, enough that it powers on the fans on my laptops where FF rarely does. I've never really understand why either and it's been on two totally different laptops.
- FridgeSeal 9y ago
  In their defence, Mozilla has done a lot of work to fix these issues, and Chrome really isn't that much better. I'm on FF 57 at the moment (nightly) and it's stupid fast. Like, really fast.