4 ms·
Ideally all languages would be quick to program in but the reality is that some languages have really long compile times and are unsuitable for quick prototypin
by bobajeff 2y ago
Ideally all languages would be quick to program in but the reality is that some languages have really long compile times and are unsuitable for quick prototyping, experimenting, creating proof of concepts, or small programs. That's where scripting languages come in handy.
- imtringued 2y agoNothing prevents anyone from building an ABI compatible interpreter where only parts of the program are compiled.
- deleted 2y ago[deleted]
- idle_zealot 2y agoI think the bigger problem is a language design one. Scripting languages are often easier to use than more performant ones because they make a lot of choices for the developer (automatic allocation and garbage collection, doesn't expose reference versus value, no pointers, everything is a table/object/whatever). A runtime can try to make inferences about how language features are being used in order to speed up execution or reduce memory use, but usually even then things end up being less efficient than if the programmer had to actually make choices about memory allocation, if/when to free things, etc.
- bobajeff 2y agoNothing save for time, skill and enough financial support. Sure. While we're at it why not make a Web Browser too? Technically, nothing stops us.