|
wasting computation to make ones job easier is fine, cool and good if you're a person making something for an end-user, basically when you're making a *purpose* for the computer. a small team making a cool game gets to burn as many cycles as they want if it still runs acceptably and doing so lets them do more. a computer toucher writing an inefficient little tool that 5 people will use but will save everyone some work time so they can head home early, very nice. computers getting faster -> more cool stuff like that. putting hideously architected javascript into your boring as hell desktop environment to render an icon and maybe show the time is waste (see e.g. gnome poo poo), making your platform stuff slow because you're a snowflake about it being clean or other basically bikeshed stuff is a waste (see e.g. electron and python), and so on. vast majority of code in the world is the top of its own stack, so make the stack efficient.
|
#
¿
Dec 7, 2023 17:48
|
|
|
|
| # ¿ May 22, 2024 16:41 |
|
|
Deep Dish Fuckfest posted:using whatever loving bespoke ersatz integers that shitheap uses, then did you know that by adding a mere 100 extra instructions around each instance of it you can make the fpu reliably do 53 bit integer math?
|
|
#
¿
Dec 7, 2023 21:41
|
|