Hacker News new | ask | show | jobs
by Zenst 4560 days ago
If they are working on a language that makes distributed computing with all the arror handerling done for you as it reads, then I can see it has uses. At least that would obviscate one or two layers of framework you end up having to add.

Now the question not being asked and one area which would certainly open this up would be built in handerling and offloading onto GPU's. Certainly for what they appear to be designing then it would be something to factor in as the main drives for a distibuted system design would be for resiliance against loads or performance putting it crudely and on the performance front GPU's start factoring in earlier and earlier into designs. Though idealy you should be able to code away and have the compiler or some resource-profile file handle those aspects for you without adding another consideration/limit into your design.

Whilst many seem supprised that started with the C# base are maybe forgiting C# is Microsofts baby (they have more control over it) and whilst F# is also there remit the use of C# at the time and even now still points to a better user base more likely to embrace a upgrade so to speak. Also around the time they started this we were just embracing the ceailing of the monolyth CPU and GPU's were just around the corner. So a move towards making multi system and with that CPU's on a larger scale makes perfect sense and direction. Now given the length of time and the resources they have this was either a small pet project that matured or one that has gone thru many changes over its internal development. Maybe a bit of both, maybe that added in some GPU love, maybe not. But still, it does sound like an interesting language and if it has a level of Message Queue robust design for distributed computing built in then that alone would make this a nice robust off the shelf base language. Not that you cant add a framework or third party libary and code to get the same effect, just be nice to have that thinking and worry obviscated away from you as it just works. Heck if you do full error handerling for every aspect of fail in your code and its enviroment the simplest of Hello World programs tend to become much bigger (did the display work, did the user see the message, what if the program aborts mid message, how to restart on failure from aborts or power cuts....). Murphy has many avenues of saying hello to your nice program, removing some at any level is always welcome so will be interesting to see what they come up with.