3 ms·
> 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" an
by smt88 6y ago
> 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.
- beojan 6y agoProprietary doesn't mean it's anyone's full time job.
- NOGDP 6y ago> 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.
- Snitch-Thursday 6y ago> 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 https://github.com/fsharp/fsharp). (The historical Visual F# compiler was developed by Microsoft per http://research.microsoft.com/en-us/um/cambridge/projects/fsharp/ack.aspx 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.
- thrower123 6y agoIf 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.
- pjmlp 6y agoApparently 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?
- fhrowaway201010 6y agoGuido Van Rossum also works there, so what's your point?
- Deimorz 6y agoNo he doesn't. He worked at Dropbox starting in 2013, but retired last year.