3 ms·
I receive $0 compensation for working on the D compiler. It's Boost licensed. Everyone is free to use it for whatever they want, and the source code is free to
by WalterBright 2y ago
I receive $0 compensation for working on the D compiler. It's Boost licensed. Everyone is free to use it for whatever they want, and the source code is free to use, too.
I'm fully aware of what I'm doing :-)
The D Language Foundation is a non-profit, has expenses, and is funded by donations. None of it goes to me.
- lionkor 2y agoI assume, then, that you do it because it's fun :) That's why I do open source.
- WalterBright 2y agoYes, it's fun, and I like design work making things better. It's fun seeing other languages adopting D design innovations.
- movedx 2y agoDo you think making important, widely used open-source software is a good idea when it's being done, for fun? What happens when it's no longer fun, but 150,000 people depend on it for their job? Imagine Linus Tarvolds stopped working on Linux before there was a foundation to take over because he did it just for fun and no one else wanted to take up the mantle? It's hard to say what the outcome from that would have been... maybe Google would have claimed it entirely and slowly shifted the license to something else? I appreciate that people can create things for fun, and those things can be open-source, but if someone creates something because it's the right thing to do and not just about fun... well where do we stand now? Should they make it open-source but demand money? Should it be closed-source if the fun-factor is less than 80%? 50%? Unless a small, dedicated team of capable people agree that your open-source project is worth preserving, allowing it to survive you as the founder, I question the validity of open-sourcing anything for fun unless you design the licence, and more, to enable you to walk away and/or get bored. Would love to hear your thoughts.
- satvikpendem 2y ago> THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. - MIT license When using open source, you take that risk. I've used a lot of libraries that have been abandoned over the years where I either had to switch to a fork, another library entirely, or just write the functionality myself. I know the risk inherent in OSS. For large projects like Linux, since it's so large, someone else would pick it up, but again, there's always a risk that someone doesn't.
- Qem 2y agoMost proprietary software has similar scary warnings in their licenses/EULAs.
- satvikpendem 2y agoSure but SLAs generally exist if you're buying proprietary software as B2B, not necessarily so for OSS, unless you buy support contracts as well, which some companies like RedHat provide.
- Digit-Al 2y agoThe difference is this: No EULA can override an organisation's legal obligations. Most countries have fairly robust "fit for use" laws, so if you sell something and it is not fit for use you can be taken to court. If there is no sale then there is no "fit for use" protection. I do not mean this to imply I think commercial software is superior to free software, I am a great believer in FOSS, I just wnat to show a reason why a "scary" warning in commercial software is not equivalent to the same warning in FOSS.
- matrss 2y ago> What happens when it's no longer fun, but 150,000 people depend on it for their job? Then someone else can take over, or not, depending on how important it really is to those 150000. From the perspective of a business, using open source is strictly safer than closed source. With closed source, if the entity owning the code goes bankrupt, increases licensing fees substantially, just axes the project (incidentally what Google is also known for) or looses interest in some other way, you are out of luck. Go find something similar and hope there is a migration path. With open source, the equivalent is the maintainer walking away because they are bored, and you have the code right there to take over, or pay someone else to do so. > I question the validity of open-sourcing anything for fun unless you design the licence, and more, to enable you to walk away and/or get bored. Every open source license is already designed so that you can just walk away for whatever reason, e.g. when you are bored.
- corysama 2y agoI made a toy implementation of D’s ranges in C++ and it was very fun and educational :)
- WalterBright 2y agoC++'s ranges came from D, but C++ decided to construct ranges from a (begin, end) pair, which is not as good as D's design. D's ranges are constructed from a (pointer,length) pair.
- AndyMcConachie 2y agoThank you for your contributions. I believe the world would be a better place if you were paid for them.
- WalterBright 2y agoThe problem with being paid is then the payer gets to call the shots. By not being paid, then D has a chance at a consistent, coherent design. I sometimes say "hell no" to features popular in other languages (like version algebra, and macros). How do you say "hell no" to your employer?
- megatron2009 2y agoYes, but the article is not talking about your scenario. It is talking about commercial software, where people would need to be paid to ensure that the software is supported on the platforms they like. You have the privilege of being able to develop open-source but that's hardly a sustainable model.
- ValentinA23 2y agoThank you! I needed a robust algo to enumerate loops in directed multigraphs, and found an implementation of Hawick's algorithm in D. Instead of writing my own implementation in the language I use, I decided to just compile the code I found and call the binary. Went super-smoothly, even though I had never used D. Great work!
- WalterBright 2y agoGood to hear!