Lady in Love @Lady@cat.family

@wallhackio why do you have a C programming language book from 1988

@coriander feed them to goats 🐐

@akjcv better to make complex things impossible than to make them difficult

@aescling @wallhackio https://www.petmd.com/cat/poisoning/can-cats-drink-coffee

@coriander and let’s be real no tesla has ever lasted 9 years

@coriander i’m not sure if i was an elon musk hater in 2015 but i definitely was by the end of 2016

@coriander *does some math* damn im old

@wallhackio @aescling i’m ideologically opposed to languages which aren’t developed by a standards organization but swift is good

@wallhackio @aescling javascript has pretty much always operated under the pretense of “we will present a (comparatively) simple and understandable mental model to programmers and simply invest a lot of time and resources developing compilers that can optimize that to be fast”. the problem is that javascript gives its compilers very little information, and the fact that the runtime environment is a browser where anyone can open up devtools at any time and muck around places real limitations on how many optimizations they can do.

swift follows the same principle of “present a simple and understandable mental model, then rely on the compiler to make it fast”, but it is designed in such a way as to give the compiler a vast trove of information to work from, and when run as a static binary the possibility space is a lot more known.

(also javascript takes a stance of “you can change anything unless you explicitly prohibit it” while swift takes a stance of “everything is immutable unless you explicitly enable changing it”, which sure does make optimizations easier)