News for hackers. Stuff that matters.
Re:Dark’s new backend will be in F# by throwaway284534 on Tuesday November 03, 2020 @10:41AM (#24980612)
Does anyone else see the irony here? The Dark engineers switched their core language with another because the open source ecosystem wasn't broad enough to cover their needs. And yet they're asking their customers to make the same bet on their proprietary language and platform. I mean just look at this FAQ[1]. There isn't a clear path out of vendor-lock in, a terms of service, or even a guarantee that the platform won't disappear without notice.

- [1] https://darklang.com/language

Re:Dark’s new backend will be in F# by pimterry on Tuesday November 03, 2020 @11:07AM (#24980862)
It's interesting to contrast with Docker, who similarly pitched an exciting new development model & ecosystem. In Docker's case, it was indeed non-proprietary, built on existing standards, and has now got to the stage where you can now swap Docker out for competing alternatives to avoid lock-in entirely.

On the other hand, while that model went great for Docker the technology, it has not gone well for Docker the business. I imagine Dark might see Docker as a cautionary tale of why _not_ to go down that road.

Re:Dark’s new backend will be in F# by raiyu on Tuesday November 03, 2020 @12:18PM (#24981633)
The problem for Docker wasn't that per say, Docker itself was the free part that got everyone interested it's just that their paid for tier went head to head with Kubernetes and lost.

Had Kubernetes not existed they would be doing just fine economically as they would be the dominant platform.

They got beat by competition.

Re:Dark’s new backend will be in F# by freedomben on Tuesday November 03, 2020 @12:44PM (#24981941)
Disclaimer: I work for Red Hat on OpenShift so I'm biased, but this is just my opinion.

Yep I agree. I recently helped a customer to move from Docker EE to OpenShift. They were frank about the pain points they experienced and why they were moving. It really came down to competition. K8s solves the problems they were having in a better way. Now with so much momentum behind K8s, nearly everybody is re-platforming their offerings on top of K8s.

Re:Dark’s new backend will be in F# by edjrage on Tuesday November 03, 2020 @12:22PM (#24981677)
Honest question as an outsider: What did Docker introduce that wasn't better addressed by other technologies? E.g. wasn't reproducibility the main point and already properly solved by nix?

By the way, it's "per se"

Re:Dark’s new backend will be in F# by isogon on Tuesday November 03, 2020 @12:32PM (#24981801)
Dockerfiles are far simpler than the Nix language. Likewise, sure, FreeBSD had jails first (and for a long time!), but they are more difficult to set up.

Docker allowed reproducibility to be accomplished by a person who likes the idea of it, but will shelve it if it doesn't work within an evening. This describes me, for example. I think it took off for that reason.

Re:Dark’s new backend will be in F# by nendroid on Tuesday November 03, 2020 @12:59PM (#24982116)
Nix has a multitude of drawbacks the biggest being learnability.
Re:Dark’s new backend will be in F# by pbronez on Tuesday November 03, 2020 @03:56PM (#24983888)
god yes. Friggin' Nix is such a great idea, but such a pain to start using...
Re:Dark’s new backend will be in F# by b0afc375b5 on Tuesday November 03, 2020 @07:16PM (#24985525)
I mean you could say the same for vim, but I still learned it and am now reaping the benefits.
Re:Dark’s new backend will be in F# by dwaltrip on Wednesday November 04, 2020 @12:45PM (#24991244)
Yes, but most people don’t bother.
Re:Dark’s new backend will be in F# by freedomben on Tuesday November 03, 2020 @12:42PM (#24981907)
IMHO, it was the whole package: One tool that could configure and wrangle all the various kernel namespaces in order to make containers work.

They also benefited significantly from the splash they made and the tech excitement factor. I still run into people in my consulting work that are fairly new to containers, but brand recognition on Docker is through the roof. Everybody has heard of them even if they don't know what it can do for them.

Re:Dark’s new backend will be in F# by rodgerd on Tuesday November 03, 2020 @04:19PM (#24984118)
As Apple have spent the 21st century demonstrating time and time again, a more usable form of a well-established idea is better.
Re:Dark’s new backend will be in F# by SSLy on Tuesday November 03, 2020 @12:27PM (#24981731)
You don't have to use the nix lang, Dockerfiles are much easier to get started working with.
Re:Dark’s new backend will be in F# by rodgerd on Tuesday November 03, 2020 @04:15PM (#24984069)
Even prior to k8s, Red Hat and Cloud Foundry (amongst others) were pitching better container orchestration tooling that Docker offered (e.g. OpenShift 1 wasn't based on k8s).
Re:Dark’s new backend will be in F# by OutsmartDan on Tuesday November 03, 2020 @12:53PM (#24982040)
At this point, Darklang just seems like an over glorified side project. I cannot see any real business creating an entire backend system out of darklang- the learning curve, vendor lock-in, and volatility of the project is not worth the risk.
Re:Dark’s new backend will be in F# by smt88 on Tuesday November 03, 2020 @12:56PM (#24982086)
> because the open source ecosystem wasn't broad enough to cover their needs

I don't really think this matters. Dark is intending to be "batteries included" and relieve developers of the need for a huge ecosystem with multiple libraries for everything.

> And yet they're asking their customers to make the same bet on their proprietary language and platform.

I always use very popular open-source stacks.

That said, if given the choice between a tiny FOSS language and a tiny proprietary one (that might be profitable), I'll always choose the latter.

Small languages are extremely vulnerable to extinction regardless of who maintains them. But if at least one person's full-time job is to maintain a language, I feel much more confident than if 1-5 people are maintaining it part-time.

Re:Dark’s new backend will be in F# by Snitch-Thursday on Tuesday November 03, 2020 @02:04PM (#24982801)
> That said, if given the choice between a tiny FOSS language and a tiny proprietary one (that might be profitable), I'll always choose the latter.

(Not to put words in parent poster's mouth, just for reader clarity)

F# is no more proprietary than Rust. F# was started by Microsoft Research but is now an open source language 'owned' by the F# Foundation and licensed under the MIT license (https://github.com/fsharp/fsharp).

(The historical Visual F# compiler was developed by Microsoft per http://research.microsoft.com/en-us/um/cambridge/projects/fs...) but AFAIK today Microsoft's small full-time F# devtools team work on contributions to the open-source compiler in addition to their work on VS tooling.

Re:Dark’s new backend will be in F# by thrower123 on Tuesday November 03, 2020 @02:58PM (#24983357)
If we're going to be frank, the Venn-Diagram of people who build F# tooling and libraries and the people who work for Microsoft in some capacity on F# are nearly a circle. No one would ever use F# divorced from .NET, and it's kind of a red-haired stepchild there.

It's a fun language to work in, with some neat features, but C# is gobbling up every compelling advantage inexorably.

Re:Dark’s new backend will be in F# by pjmlp on Tuesday November 03, 2020 @03:03PM (#24983394)
Apparently many don't have an issue with some key Haskell developers also being on Microsoft pay check.

Also Microsoft alongside Facebook is looking for ex-Mozillans to join their Rust teams, then what?

Re:Dark’s new backend will be in F# by fhrowaway201010 on Tuesday November 03, 2020 @04:44PM (#24984355)
Guido Van Rossum also works there, so what's your point?
Re:Dark’s new backend will be in F# by Deimorz on Tuesday November 03, 2020 @05:36PM (#24984831)
No he doesn't. He worked at Dropbox starting in 2013, but retired last year.
Re:Dark’s new backend will be in F# by fhrowaway201010 on Tuesday November 03, 2020 @05:43PM (#24984887)
Yes he does, as a Distinguished Engineer.
Re:Dark’s new backend will be in F# by nickpeterson on Tuesday November 03, 2020 @07:09PM (#24985481)
I think C# is becoming F# a lot faster than F# is becoming C#. I think people who really learn F# are setting themselves up to be productive for a long time.
Re:Dark’s new backend will be in F# by NOGDP on Tuesday November 03, 2020 @01:27PM (#24982433)
> Dark is intending to be "batteries included" and relieve developers of the need for a huge ecosystem with multiple libraries for everything.

If it's actually going to be 'batteries included' in any meaningful way, then it will have to piggy-back off of one or more of these 'huge ecosystems', which invariably leads to the ability to integrate external pieces of these systems when needed. Which just makes it a wrapper around existing 'huge ecosystems'.

There's a reason why established languages such as Java, C#, C++, JavaScript, etc. have multiple libraries for the same problem - these libraries have different features, tradeoffs, designs etc. Same reason why existing projects get forked and new projects get started. Same reason these 'huge ecosystems' have frameworks, design patterns, idioms, best practices, etc. Competition, innovation, new designs, new ways of solving existing problems is a good thing.

I don't see dark as anything more than a very new framework, with lofty promises and zero evidence towards the idea that it will be better than existing systems in any way.

> Small languages are extremely vulnerable to extinction regardless of who maintains them. But if at least one person's full-time job is to maintain a language, I feel much more confident than if 1-5 people are maintaining it part-time.

A tiny FOSS language at least has a chance of getting some maintenance/bug fixes from the community. What happens when your proprietary language dies for lack of traction? Also, nothing prevents a person working full-time on a FOSS language.

Re:Dark’s new backend will be in F# by beojan on Tuesday November 03, 2020 @01:18PM (#24982331)
Proprietary doesn't mean it's anyone's full time job.
Re:Dark’s new backend will be in F# by mumblemumble on Tuesday November 03, 2020 @11:54AM (#24981364)
Is lock-in that big of a concern for people who are using serverless? I have no direct experience here, but my understanding was that all the major serverless platforms are built on proprietary APIs.

That said, this item from the FAQ is nice to see; I'd love to see more vendors not just making promises along these lines, but making them binding:

> if the worst should happen, we will open-source Dark ... We're committed to codifying the specifics in a legal framework

Re:Dark’s new backend will be in F# by imglorp on Tuesday November 03, 2020 @12:20PM (#24981653)
Yeah lockin is a problem in general for serverless if you need all the cloud vendor's extras. For example, lambda doesn't make sense without IAM, VPC, etc and you often want things to hook to it like SQS, API Gateway, database, cognito, etc.

Instead of lockin, you can run serverless in your own framework though, such as Kubeless or Knative, which could be deployed on prem or in a more generic cloud deployment.

Re:Dark’s new backend will be in F# by yellowapple on Tuesday November 03, 2020 @01:17PM (#24982327)
Doesn't that kind of defeat the point of "serverless", though? I mean, I guess if that's how you like to structure your code then go for it, but the primary marketing pitch I've ever heard was around it, you know, absolving developers of the need to worry about servers.

I guess if you've got a large enough environment that you have dedicated devs pushing things to Kubeless/Knative instances maintained by dedicated ops/sysdmins, then maybe that's the niche there?

Re:Dark’s new backend will be in F# by jacques_chester on Tuesday November 03, 2020 @02:07PM (#24982820)
It depends on what you think "serverless" means.

Is it solely about the developer experience? Or is it about the economic ownership of hardware? Or both?

Re:Dark’s new backend will be in F# by imglorp on Tuesday November 03, 2020 @02:54PM (#24983320)
I was referring specifically to lambda-style "functions as a managed service", which might be a better term than serverless. Managed instance would be serverless by the economic definition.
Re:Dark’s new backend will be in F# by throwaway894345 on Tuesday November 03, 2020 @11:00AM (#24980787)
I agree with this criticism, but I wonder how they could monetize without locking in users. I suppose they could open source their toolchain so anyone could stand up their own Dark framework on-premise and maybe they sell support and/or a managed service and/or "enterprise features" (whatever those are in this context)? Maybe these things will come sometime after the private-beta (perhaps they're just getting a better feel for their product's value proposition before committing to opening any particular piece of it up)?
Re:Dark’s new backend will be in F# by goldenshale on Tuesday November 03, 2020 @12:28PM (#24981748)
Or maybe this is why Dark is a bad business endeavor in the first place. I would never bet my company's future on something like this, and the toolchain doesn't seem sufficiently powerful to warrant the risk.

Sorry, but this is no Clojure. Instead of a proper comment syntax you define a dummy variable to a string? Ghetto.

Re:Dark’s new backend will be in F# by siwatanejo on Tuesday November 03, 2020 @11:04AM (#24980830)
I think it's easy to monetize: make the BCL dual license AGPL+proprietary
Re:Dark’s new backend will be in F# by nine_k on Tuesday November 03, 2020 @11:56AM (#24981391)
This is not about being open-source, but about being popular.

OCaml is a fine language, but it's not a wildly popular one. Should the authors have started with, say, Python or JS, they won't have the problem with support from third parties. Please note how their choice was between open-source Rust and proprietary (CORRECTION: also open-source already) F#, both descendants of the ML family.

When you pick a language and start to feel you're overgrowing its ecosystem, you either migrate off of it (as in the post), or start developing it to help it move in the direction you want. In the case of OCaml, Jane Street and Facebook chose the latter route.

UPDATE: Thanks for reminding that F# has been open-sourced: https://github.com/dotnet/fsharp/

Re:Dark’s new backend will be in F# by lostmsu on Tuesday November 03, 2020 @11:59AM (#24981429)
Re:Dark’s new backend will be in F# by marta_morena_28 on Tuesday November 03, 2020 @01:45PM (#24982628)
> The Dark engineers

What do you mean. The whole page talks about "I" and "me". That's going to go well...

Re:Dark’s new backend will be in F# by freehunter on Tuesday November 03, 2020 @01:49PM (#24982663)
There used to be a company and a team of engineers. Recently they laid off everyone and it’s down to just a one-person show now.
Re:Dark’s new backend will be in F# by perrygeo on Tuesday November 03, 2020 @02:53PM (#24983309)
Sounds like a great time for a backend rewrite!
Re:Dark’s new backend will be in F# by nullsense on Tuesday November 03, 2020 @02:26PM (#24983026)
So, heading in a positive direction then?