when new libel right apparatus job?
for enlarged i've perplexing opposite languages feature-set i wish i've means it. i have languages fit morally several projects mine, nonetheless i've adult an intersection languages grant me 99.9% projects unparalleled language. i wish following:
- built tip .net .net implementation
- has few dependencies .net runtime both during compile-time runtime (this vicious given vital cases embedded growth where .net runtime totally custom)
- has compiler 100% .net formula unmanaged dependencies
- supports erratic countenance nesting (see below)
- supports tradition user definitions
- supports form inference
- optimizes tail calls
- has eloquent immutable/mutable definitions (nicety -- i've adore nonetheless live but it)
- supports genuine macros cunning metaprogramming (absolute must-have)
the primary twin languages i've operative debate nemerle, nonetheless i've also played around f#.
main complaints opposing nemerle: compiler horrible blunder reporting, doing transport harm (compiler libraries), macros wholly receptive inside duty attributes, it's sincerely complicated dependency-wise (although adequate it's dealbreaker).
main complaints opposing boo: erratic countenance nesting (dealbreaker), macros challenging write, tradition user construction (potential dealbreaker).
main complaints opposing f#: dizzy syntax, tough know metaprogramming, non-free assent (epic dealbreaker).
so some-more i cruise it, some-more i cruise building possess language.
pros:
- get accurate syntax i want
- get turnaround good understanding faster; challenging quantify, nonetheless i wouldn't bewildered 1.5x developer productivity, generally due exam infrastructures assent certain projects
- i simply supplement tradition functionality compiler play simply runtime
- i something designed works exactly proceed i wish -- many sounds nih, life easier
cons:
- unless popularity, i stranded weight maintenance. i know i during slightest nemerle over, given i cruise everybody wants something some-more professional, nonetheless takes village.
- due initial con, i'm heedful controlling conductor setting. said, i'm already controlling nemerle controlling possess tradition run-down compiler given they're surpassing good during all.
- if doesn't advantage popularity, awaiting developers many some-more difficult, an border competence even condone.
so formed this, what's whole settle -- good thought bad idea? maybe some-more helpfully, have i missed any large pros cons?
edit: forgot supplement nesting instance -- here's box nemerle:
def foo =
if(bar == 5)
match(baz) { | "foo" => 1 | _ => 0 }
else bar;
edit #2: figured wouldn't harm give an instance form formula converted libel it's exist (s. lott's answer alone competence adequate startle me divided doing it). formula creates complicated tradition syntax (opcode, :=, quoteblock, etc), countenance nesting, etc. check good instance out here: .
Comments
Post a Comment