Call me pessimistic , but I can't imagine the appeal of a closed source proprietary language when so many good open source ones are free.
It just seems like really nasty Vendor lock in.
Call me pessimistic , but I can't imagine the appeal of a closed source proprietary language when so many good open source ones are free.
It just seems like really nasty Vendor lock in.
The base concept is cool, I was more caught off guard by having to learn a new language here
The core systems stuff was all Java enterprise inter-operating with off the shelf Oracle and TIBCO stuff. Building those small once off apps into the main infrastructure would have required involving the bigger suppliers who were more expensive and would be stonewalling you with change requests before long.
If you weighed the risk and determined that you were happy with these non-revenue path applications being subject to that risk, I think it might be ok. That said using something like Heroku is close enough and at least your application code is mostly portable.
I really feel like you're focusing on the wrong thing.
To me, the pitch is that Dark is FaaS-native (meaning you don't have to bend over backwards or use complex tooling to get a good write/debug/deploy experience).
The language itself being new and proprietary is actually a drawback. They can make it very friendly and productive, of course, but the other features are what should really sell someone on using Dark.
I mentioned Python as Dark appears to be heavily influenced by it. Python is meant to be dirty and fast to code in.
To be honest, I've never used a functional programing language. What Unity does is essentially allow you to call various apis , with C#, in the game engine, which is C++ base.
But it's real C# and I can hop over to my day job and utilize it. Dark isn't a portable skill set.