I don't disagree, but it is perfectly acceptable per the MIT license, which is an OSI approved license. MIT doesn't require source distribution with the binary (which is why from the developer perspective, it's a more "permissive" license)
The license describes what users are allowed to do with the source code, it doesn’t (and shouldn’t) define what a creator has to do to make the source code open.
Then it sounds like you're philosophically opposed to copyleft license like GPL. That's ok, we can agree to (in my case vehemently) disagree, but your philosophy is inconsistent with the commonly accepted definition of "open source" such as OSI's OSD[1][2]
I think you completely misunderstand me. I don’t have any opinion on GPL, but in the links you shared, even OSI considers the license to be separate from the definition of open source “Open source licenses are licenses that comply with the Open Source Definition”. You can use a license that open source projects use (ie MIT), and still keep the source closed, or you can write one that puts obligations on you if you want. In fact, you can use or write pretty much any license you want if you own the copyright.
I don't know, I could envision a situation where investing enough capital in hardware to be able to generate "infinite" tokens for free (or close to that) might open up possibilities not economically practical otherwise. Especially once the incumbents run out of hype / investor money to burn and start raising their prices to push revenue in line with their enormous expenditures.
Also, presumably at some point far in the future we'll reach a technological asymptote and factors like latency may start to play a bigger role, at least for some applications.
I grant that training data is crucial distinguishing factor that may never become competitive in-house.
If it were, they wouldn’t be asking. And you haven’t answered it either. Your parent comment is asking why the grandparent commenter thinks it makes sense to restrict third-party stores to the EU instead of having them everywhere.
I 100% agree with you but also sad fact is that it’s easy to understand why people don’t want to take this role. You can make enemies easily, you need to deliver “bad news” and convince people to put more effort or prove that effort they did was not enough. Why bother when you probably won’t be the one that have to clean it up
I'm not sure what exactly you're trying to say with this. That we need marketing to succeed? Or that the product has too much marketing (where?) and low quality?
Name one "writing app" that doesn't apply to? Still feel like you're being needlessly harsh, don't you remember writing your first text editor too? Most of us do it at one point or another.
The reasons are always the same. 20% because some changes are actually improvements, and 80% cargo cultism where if you just build the right containers and chant the correct YAML incantations, you too will become a Google… followed by the phase where everybody just keeps doing these things because they organizationally don’t know any other way anymore, until the next big trendy thing, which does revert some of the issues of the previous trendy thing, but introduced a new set of already solved problems because this profession is incredibly myopic when it comes to history.
“In this article, I’m going to be making an argument for gatekeeping. Not people, but culture, which is always worth defending. I’m not advocating for elitism, credentialism, or hostility towards beginners.
Instead, I say we should band together and defend the norms, values, quality standards, and our shared understanding of what open–source is for.”
I think this is very important distinction that should be understood broader.
reply