5 ms·
So proprietary is bad? I have no issues with things being owned by a single entity, especially when they're financially backed by that (massive) entity. What i
by movedx 7y ago
So proprietary is bad? I have no issues with things being owned by a single entity, especially when they're financially backed by that (massive) entity.
What is being proposed as the alternative here?
- oaiey 7y agoI even think that for language and base class library design a strong ownership is key to success. They make the language consistent and the library easy to learn. In both aspects, just compare .NET/C# with PHP.
- movedx 7y agoExactly. I want my language to be crazy good and have an amazing library to tap into. In fact, it was Go's great standard library (JSON parsing, hardened prod' ready HTTPS server, SSH, crypto, etc) that formed a large part of why I love the language. And yeah, I'd rather go with .NET/C# over PHP any day (although I understand PHP is getting better and better, which is good to hear.)
- oaiey 7y agoWell PHP and .NET do not play in the same league. But it is about consistent language and library design. Great failure in PHP and great success in .NET/C#. I developed PHP till 2007, then as a hobby project in 2013. Massive improvement. And I heard very good things about performance the last years. Swoole even can compete with the top tear languages