Re: A modern programming language for FreeBSD: Swift

--------
Konstantin Belousov writes:


> IMO Jamie deserves the gratefulness and encouragement for the work done,
> and not the naive sarcasm due to some missed wording.

The wording is not a problem.

But the Silverbulletism™ the wording signals is a warning sign
that mandatory homework has not been completed.

(Not handing in homework is known to cause sarcasm.)

As a reminder, the homework is this:

A) Does the imagined benefits derive from the proposed language
   itself or from other software in the ecosystem around the language ?

B) Does upstream even want FreeBSD to import/integrate ?

C) Can the proposed language's compiler and runtime be sensibly
   imported and maintained in FreeBSD's source tree and bmake
   build technology ?

D) What /new/ things will the proposed language allow us to do ?

E) What is the FreeBSD killer-feature/application of the proposed language ?

F) Quantify the risks.


Notes:

A: FreeBSD cannot import ecosystems, only compilers and (sensible sized) runtimes.

D: Pointing to rewrites of trivial existing programs will be scored negatively.

F: Risk = probability times consequence.
   Amongst the risks for the FreeBSD projects are things like "nobody
   can maintain this", "nobody wants to maintain this", "nobody
   knows how to maintain this" and "upstream changed their mind in
   a way which is incompatible with FreeBSD's inclusion", "upstream
   fizzled out", "upstream split into multiple different directions" etc.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.