3 ms·

On the other hand, if software makers kept using the same software, we'd still be programming in assembly, and play games in DOS :)

grishka 6y ago
I meant more like using tools appropriate for the job. Hint: JavaScript and friends isn't anywhere near an appropriate technology choice for a desktop app. Assembly is inconvenient, unforgiving, and tied to a particular CPU architecture. Object-oriented paradigm is well-suited and stood the test of time for making GUIs for example. And I don't mean stop inventing new things — I mean stop using stuff without understanding how it works under the hood. Stop embracing that kind of thinking and lowering the barrier to entry by wrapping everything into layers upon layers of "simple" abstractions and making it obscenely inefficient in the process. Stop "moving fast and breaking things". Stop making everyone think that software sucks, that that's its default state. I hate this "developer time is more expensive than machine time" saying. And there's no "premature optimization". Performance isn't a feature you can add at a later date whenever you feel like it — it's a function of the overall design of your product. Also, I can't help but feel like most of programming these days happens for the sake of the process itself, and the resulting product is more of an unintended side effect. > and play games in DOS Not necessarily a bad thing tbh.
- rhn_mk1 6y ago
  The other extreme to "move fast and break things" is "get extremely attached to your old ways". I don't think either is healthy. I'm sure that limiting software to only perfect diamonds of speed and security would raise barrier to entry enough that we would have missed out on some brilliant but inefficient ideas. Where the healthy middle point lies is something I don't know.

3 ms·

On the other hand, if software makers kept using the same software, we'd still be programming in assembly, and play games in DOS :)

by rhn_mk1 6y ago

grishka 6y ago
I meant more like using tools appropriate for the job. Hint: JavaScript and friends isn't anywhere near an appropriate technology choice for a desktop app. Assembly is inconvenient, unforgiving, and tied to a particular CPU architecture. Object-oriented paradigm is well-suited and stood the test of time for making GUIs for example. And I don't mean stop inventing new things — I mean stop using stuff without understanding how it works under the hood. Stop embracing that kind of thinking and lowering the barrier to entry by wrapping everything into layers upon layers of "simple" abstractions and making it obscenely inefficient in the process. Stop "moving fast and breaking things". Stop making everyone think that software sucks, that that's its default state. I hate this "developer time is more expensive than machine time" saying. And there's no "premature optimization". Performance isn't a feature you can add at a later date whenever you feel like it — it's a function of the overall design of your product. Also, I can't help but feel like most of programming these days happens for the sake of the process itself, and the resulting product is more of an unintended side effect. > and play games in DOS Not necessarily a bad thing tbh.
- rhn_mk1 6y ago
  The other extreme to "move fast and break things" is "get extremely attached to your old ways". I don't think either is healthy. I'm sure that limiting software to only perfect diamonds of speed and security would raise barrier to entry enough that we would have missed out on some brilliant but inefficient ideas. Where the healthy middle point lies is something I don't know.