4 ms·
Guys, when you do a new language, syntax is nearly completely uninteresting, because it's exchangeable. Please answer some of these questions, instead: 1. memo
by choeger 5y ago
Guys, when you do a new language, syntax is nearly completely uninteresting, because it's exchangeable. Please answer some of these questions, instead:
1. memory management strategy [x]
2. target platform [?]
3. evaluation semantics (lazy/eager) [?]
4. argument passing strategy [?]
5. if type-safe: overloading [?]
6. if type-safe: parametric polymorphism [?]
7. if type-safe: (nominal/structural) subtyping [?]
8. if type-safe: module system/language [?]
9. if compiled to machine code: separate compilation [?]
10. if compiled to machine code: ABI [?]
11. if interpreted: multi-threading capability (Ok, this one's a hit on python) [?]
12. ... I probably missed a couple of data points
edit: I should have seen sooner that it is a parody, but my point still stands.
- FeepingCreature 5y agoUsually, the process of exchanging syntax is equivalent to "doing a new language" though.
- bluetomcat 5y ago13. Demonstrate pieces of code and classes of tasks where your shiny new language excels over idiomatic code in languages A/B/C, in terms of safety, readability, performance, brevity or whatever else category you consider important
- mirekrusin 5y ago...unless it's a joke, like in this case where reader should guess it's just c# and 2nd mentioned dialect is f#. They forgot to mention it's open source and backed by (M).
- DeathArrow 5y agoBut you do realize this is just a parody making fun of new languages?
- gvx 5y agoIt was too subtle for me too. It didn't help that I've seen new languages on here that were completely serious and much more absurd than this.
- smitty1e 5y agoI thought something a bit off when this purported language sprang forth fully-featured from its author's brow with all of the library support for F(M)ANG adventures.