4 ms·
The post refers to an existing team -- "we" used for everything -- so he's presumably convinced other people to work on it as well. Unless they're all on the s
by setr 6y ago
The post refers to an existing team -- "we" used for everything -- so he's presumably convinced other people to work on it as well.
Unless they're all on the same page (because why not?), there must be something compelling about it.
- hackerbrother 6y agoI always wonder if "we" spend too much time on new languages and not enough on good libraries in existing popular languages.
- setr 6y agoThey’re really not that different — a language is essentially a library, but at a lower level of the stack (the hierarchy being OS > language > framework > library > application) From that perspective, it makes about as much sense designing a framework versus a language, relative to a library. The question then to justify a new language is to justify whether it could have been done with about as much benefit, but on a higher tier (thus, lower effort, for both the developer and the user)