10 Jun
2013
10 Jun
'13
6:37 p.m.
On 10/06/13 9:22 PM, Jason McBrien wrote:
We develop our vertical client/server app on powerful
development machines,
then use load testing software to see how it scales on multiple user loads
and slower client machines.
Using one machine is a non-starter, as we have different hardware
requirements depending on what the user is doing. If you're doing basic
accounting, you don't need a lot of machine. If you are doing statistical
analysis on millions of data points, you do.
Right, every situation is different. For code that runs on client
machines, bringing the developer face to face with older spec is
probably a good idea. For back-end code, it doesn't necessarily apply.
--Toby
On Mon, Jun 10, 2013 at 9:12 PM, Toby Thain<toby at telegraphics.com.au>wrote:
On 10/06/13 1:18 PM, Tothwolf wrote:
...
I'm slowing coming to the opinion that a first year C developer should
be /forced/ to develop on a CPU and memory constrained platform, such as
Agree 100%. It wouldn't help if they *continued* to develop on machines a
few years behind the curve, as well.
--T
a 386 with 4-8MB of memory vs a modern multi-core CPU with multiple
gigabytes of memory, so that they will learn
first hand how to write
more efficient C code. I wonder how many of the current userspace
developers and package maintainers have ever even touched a 386 based
machine, let alone something even more resource limited?