An important white paper which probably went unnoticed. It gives a nice overview of the strategies one can build around Open Source components.

Good mulling for thought. It's always a bit challenging to nicely explain the tie between engineering metrics and how they impact the business. This is a nice starting point.

Very good piece explaining why the Ferdiverse is currently our only option for a decentralized social media platform. Maybe Bluesky will become another option... maybe... but so far it's only empty promises with a real risk of capture.

Can you see this kind of models getting abused quickly? Clearly it says something about the tech industry wanting to reduce costs.

Excellent post showing reasons to be skeptical about Bluesky's future. Despite all their likely sincere claims I don't see how they'll escape enclosure and enshittification when their sketchy VCs will want to see money back.

Indeed, we should stop listening to such people who are basically pushing fantasies in order to raise more money.

The arm race is still on-going at a furious pace. Still wondering how messy it will be when this bubble bursts.

This is a very harsh and bleak view on the current generative AI craze. Clearly it survives on some sort of weird faith that things will magically improve. Some decision makers clearly run fully on said faith and lost all kind of realistic view of the situation. They are just very disconnected from the user's needs.

There's even a funny quote in there: "Generative AI must seem kind of magical when your entire life is either being in a meeting or reading an email".

When this bubble bursts, it's hard to predict what the fallout will be on the tech industry... for sure it won't be pretty. It also begs the question: what is this industry going to do next? There's clearly no plan after generative AI.

There is a sane conversation going on around uv in the Python community. Here is a good summary.

Definitely something architects should do more. Understanding the business needs should be the input to the technical decisions. Otherwise you might just happily build the wrong thing.

I wish more product companies would pick this license. Going for AGPL with a support and/or double license offering is a strong model in my opinion.

It's bloody hard to build a strategy. This article is full of good wisdom to make one. This won't make it really easier, but at least you won't start in the wrong direction and will be able to know if what you produce is any good.

Definitely this. Managing expectations is a big part of management. It's also important for customer relationship. In both cases, clear communication and finding misunderstandings early are key.

Unsurprising trend... this was a market where there was no chance to have a single dominant platform due to the existing studio behemoths. So now we're in the streaming wars, people can't afford to pay for every silos... and they turn to piracy again. Could have been all avoided if we went the "global license" route instead of dumping money on platforms.

Unsurprising move, they claim it's for the betterment of mankind but in practice it's mostly about capturing as much market share as possible.

This is a stupid move on Unity's part... they're built on LGPL but ban others in their store to have LGPL dependencies. Shame on them. Good move from Videolabs though, wish them lots of success.

That's a very good question. What will be left once all the hype is gone? Not all bubbles leaving something behind... we can hope this one will.

Good point on why you don't want to drive your organization simply on RFCs. Yet another fad of "this worked for them, let's do it as well"... per usual this fails to take into account the specificity of the context where it worked.

Interesting food for thought. The later point about the tension between business and users lately is also a good one and should be kept in mind. That's an ethical concern you find most in companies publishing Free Software though. It's not the full packaged solution but a good starting point.

There will always be some design and some testing. The intensity of both activities needs to be properly managed over time though.