Re:Self-Contained Development Environments (2018) [pdf]
by AnIdiotOnTheNet on Friday August 07, 2020 @12:00PM
(#24083343)
> Certainly some developers have been targeting performance (particularly compiler devs. Arguably UI devs)
Difficult to believe with how unresponsive modern UIs are.
Re:Self-Contained Development Environments (2018) [pdf]
by nitwit005 on Friday August 07, 2020 @05:10PM
(#24086491)
We make the UIs responsive, and then we come up with a new way to make them slow.
Re:Self-Contained Development Environments (2018) [pdf]
by user5994461 on Friday August 07, 2020 @12:43PM
(#24083898)
Performance was critical to all projects 25 years ago when software had to run on a 100 MHz CPU with 16 MB of memory.
Re:Self-Contained Development Environments (2018) [pdf]
by zeveb on Friday August 07, 2020 @01:43PM
(#24084574)
FWIW, Apple's Power Macintosh 8500, released 25 years ago tomorrow, started at 120MHz & 16MB RAM, but went up to 200MHz & 512MB RAM.
As I recall, it was pretty snappy! I think it would still have been sufficiently snappy had its OS been written in Smalltalk or Lisp …
Re:Self-Contained Development Environments (2018) [pdf]
by spanhandler on Friday August 07, 2020 @03:52PM
(#24085830)
BeOS on a 166Mhz Pentium with 128MB of RAM (luxury!) felt positively spacious. Like you were lavishing it with far more resources than it needed and so rarely risked even approaching its limits, so far as maintaining UI responsiveness while multitasking, at least.
I'm not sure I agree with this assessment. Certainly some developers have been targeting performance (particularly compiler devs. Arguably UI devs). However, in corporate development, performance has ALWAYS come second to development time. The only time performance matters is.. well, when it does :). That is to say, it only matters when slow things are causing unhappy clients or missed deadlines.