Re:Janet: a lightweight, expressive and modern Lisp
by moron4hire on Wednesday May 13, 2020 @08:17AM
(#23166067)
Microsoft doesn't make breaking changes. I have code that has survived three or four of your supposed cycles that still runs completely fine.
Re:Janet: a lightweight, expressive and modern Lisp
by orthoxerox on Wednesday May 13, 2020 @09:39AM
(#23166768)
Microsoft did kill off or sunset some parts of the Framework. WCF, WWF, AppDomain, expression trees, dynamic, VB.
People who wrote WCF services in VB for a living are probably extremely disappointed.
Re:Janet: a lightweight, expressive and modern Lisp
by mr_custard on Wednesday May 13, 2020 @10:41AM
(#23167316)
Disappointed? Not at all! I worked with it many years ago.
Whilst WCF made some notable improvements over what existed within the ecosystem before it, it was still a sprawling, complex PITA and full of developer friction. Killing it off in this case was definitely the right thing to do :-)
Re:Janet: a lightweight, expressive and modern Lisp
by jbeam on Wednesday May 13, 2020 @11:56AM
(#23168195)
Do you have anything to support that expression trees are being sunset? I haven't seen anything of the sort, unless you are talking about a deprecated library that has been replaced. But System.Linq.Expressions is still around.
Re:Janet: a lightweight, expressive and modern Lisp
by moron4hire on Wednesday May 13, 2020 @12:08PM
(#23168336)
I've also seen nothing about DLR being removed
Re:Janet: a lightweight, expressive and modern Lisp
by ohitsdom on Wednesday May 13, 2020 @09:41AM
(#23166785)
.NET Core's cross-platform tools and ecosystem is wonderful. I'm working on a small team and the devs are using Windows, Mac, and Linux. CI builds are a mix of Windows and Linux, deploying to Linux.
I think their biggest weakness now is branding (.NET vs .NET Core). This will be fixed with .NET 5, which merges the two and will make all flavors of .NET cross-platform.
[1]: A different philosophy that gives more control to the user in exchange for explicitness puts it ahead in some areas (structs) and behind in others (compilation quality, GC), but as a runtime engineer it's "technologically" behind (I work on OpenJDK so I'm biased, but I came to work on OpenJDK because that's where most interesting innovation in runtimes happens).