@jalefkowit "Developers have poured out sweat over the last couple of decades to get you working in ways that make it hard to scale like crazy."
What do you think has been the driver for that?
@jalefkowit "Developers have poured out sweat over the last couple of decades to get you working in ways that make it hard to scale like crazy."
What do you think has been the driver for that?
@tokyo_0 we all tend to fall into the "yeah, but I can't use the old stuff, because MY PROBLEMS ARE COMPLICATED!" hole.
so we reinvent the wheel and overcomplicate solutions
sometimes we're somewhat correct in that, but most of the times it's just in error
and then the solutions not only have to support YOUR complex stuff, but everone elses complex stuff too. The simple use-case tends to get ignored, because that's solved already.
You don't become a hero by solving how to butter bread.
@tokyo_0 @jalefkowit As I remember the driving force was a few particularly bad giant corporations not devs, and the motivations were to optimize for being able to hire low pay frontend devs without collective bargaining power for everything, and each building their own pet frameworks devs would get accustomed to, to reduce mobility between their big competitors.
@dalias @tokyo_0 @jalefkowit
In my experience, this gets closer to the truth. Same explanation for "Why cloud?" - namely, that the OPEX-aligned management won in their fight against the CAPEX peeps. Most big tech currents are really buisiness currents, when you peek under the hood.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.