Why do people create something and explicitly license it under an open source license and are then surprised when it's used as the license permits? I can see a few possible reasons:
1. Culture: GitHub seems to have the culture of people using and putting out their code as open source just because everyone else is doing it, or they just don't know or care to do enough research about software licenses.
2. Promotion: open source seems to be used as a way to promote your product and you simply hope that no one will "screw you over" by using the license as it permits, even by big companies. They'll use open source to build their product but will cry foul when corporations do the same exact thing the open source creators were doing in the first place!
These two factors seem to account for a significant portion of the open source license based posts on Hacker News in the past several years.
What will happen in the future? It seems that people will create more proprietary software in the form of ostensibly "open source" licenses such as the SSPL by MongoDB or others. People will say that they're not truly open source, just another variation on proprietary source available licenses, which is true but the problem isn't a moral one, it's a practical one. GPL was started because the end user freedoms were eroded, and these licenses also fall into that, where people will soon discover that a proprietary license isn't great when they want to expand the original software but are encumbered by the license, such as if they work for a large company or other such restriction. Having no restrictions is always better than having even small ones.
But how will open source creators make money, one may ask. The simple answer is, they don't, and they shouldn't expect to. The more complex answer is, open source is not a business model, it is merely a licensing and distribution model. You must compete not on the code but the problems your code solves. Your product must also include marketing, sales, branding, and other business skills. Treat your product as a startup.
Amazon could open source all of its code and infrastructure and it would still be the dominant player in cloud computing as well as buying stuff online. Why? They are not in the business of selling code, they are in the business of selling convenience (as every business is actually, you don't hunt your own meat, a grocery store sells you the convenience of buying food, with money rather than time and effort; business is just commoditized convenience). Moreover, people know and trust Amazon, they don't know your other site, even if you took their source code and made your own website.
At the end of the day, people need to understand that a product is not a business. If you want to make money, you probably shouldn't make a free product. There are ways to leverage a free product into a business, as seen with TailwindCSS (free, open source) to Tailwind UI (paid, proprietary) or Laravel to Laravel Spark and Forge, but don't expect people to spontaneously pay you when they could use your product for free, unless, again, you have the business skills to make your product stand out via marketing and having product-market fit.
Promoting yourself on Github hasn't had much in the way of features thus far. The profile's Readme.md being a tiny step in that direction. Unsure if future steps will include "social-networky" stuff, as a way of enhancing the GH Culture as you put it. Other sites have forums where people with different skills organize to collaborate (GFX, Audio, Coding, Promotion)
1. Culture: GitHub seems to have the culture of people using and putting out their code as open source just because everyone else is doing it, or they just don't know or care to do enough research about software licenses.
2. Promotion: open source seems to be used as a way to promote your product and you simply hope that no one will "screw you over" by using the license as it permits, even by big companies. They'll use open source to build their product but will cry foul when corporations do the same exact thing the open source creators were doing in the first place!
These two factors seem to account for a significant portion of the open source license based posts on Hacker News in the past several years.
What will happen in the future? It seems that people will create more proprietary software in the form of ostensibly "open source" licenses such as the SSPL by MongoDB or others. People will say that they're not truly open source, just another variation on proprietary source available licenses, which is true but the problem isn't a moral one, it's a practical one. GPL was started because the end user freedoms were eroded, and these licenses also fall into that, where people will soon discover that a proprietary license isn't great when they want to expand the original software but are encumbered by the license, such as if they work for a large company or other such restriction. Having no restrictions is always better than having even small ones.
But how will open source creators make money, one may ask. The simple answer is, they don't, and they shouldn't expect to. The more complex answer is, open source is not a business model, it is merely a licensing and distribution model. You must compete not on the code but the problems your code solves. Your product must also include marketing, sales, branding, and other business skills. Treat your product as a startup.
Amazon could open source all of its code and infrastructure and it would still be the dominant player in cloud computing as well as buying stuff online. Why? They are not in the business of selling code, they are in the business of selling convenience (as every business is actually, you don't hunt your own meat, a grocery store sells you the convenience of buying food, with money rather than time and effort; business is just commoditized convenience). Moreover, people know and trust Amazon, they don't know your other site, even if you took their source code and made your own website.
At the end of the day, people need to understand that a product is not a business. If you want to make money, you probably shouldn't make a free product. There are ways to leverage a free product into a business, as seen with TailwindCSS (free, open source) to Tailwind UI (paid, proprietary) or Laravel to Laravel Spark and Forge, but don't expect people to spontaneously pay you when they could use your product for free, unless, again, you have the business skills to make your product stand out via marketing and having product-market fit.