This week's notable links

[ Martin SFP Bryant at The New Stack ]

"How do you get started if you want to integrate your own software with ActivityPub? [Evan] Prodromou has written a new book on this very topic, and we caught up with him to explore the practicalities of linking up with the fediverse."

I'm convinced that ActivityPub is the underlying standard that all future social software will be built on. Evan is one of the founding parents of the fediverse, and this article is a great overview. His new book will be an invaluable resource for everyone who wants to embark upon this journey.

#Fediverse

[ Link ]

[ George Hammond at the Financial Times ]

"Y Combinator, the San Francisco start-up incubator that launched Airbnb, Reddit, Stripe and Coinbase, is backing a weapons company for the first time, entering a sector it has previously shunned."

Specifically, its a low-cost cruise missile startup, which the Financial Times reports would be suitable for use in a potential war between the US and China. The cruise missiles are 10x smaller and 10x cheaper than today's alternatives, but presumably still murder people.

Also from the article:

"There is “a very interesting situation where geopolitical heat and the end of zero-interest rate policies have made people become more pragmatic,” said the founder of one start-up that was in the same group of YC-funded companies as Ares. [...] “People support builders doing cool, hard stuff.”"

Very interesting indeed. Certainly, you can make money by selling weapons of war. But should you? And in what world is killing people "cool stuff"?

Silicon Valley's origins are in large part military , of course, so this shouldn't be too much of a surprise. But for a while there, in the wake of the this-is-for-everyone radical inclusion of the web (which was not a military creation), it seemed like tech was heading in a different direction. It's disappointing to see that this was ephemeral at best.

#Technology

[ Link ]

[ Tara Tarakiyee ]

"I want to talk about three examples I see of cracks that are starting to form which signal big challenges in the future of OSS."

I had a knee-jerk initial reaction to this post - what open source bubble?! - but Tara Tarakiyee makes some important points here about our dependence on open source code and how that might change over time.

The through line to all of them is about money. The OSI's new "open source AI" definition is loose because AI vendors likely couldn't make money otherwise (although whether they can make money anyway is still up for debate); source-available licenses have become prevalent because it's easier to sell commercial licenses and therefore make a living building software; much open source software was precariously funded through European Commission Next Generation Internet grants, which are now evaporating .

While we can stand for pure open source values all we like, the people who build open source software need to make a living: food must go on the table and they need a roof over their heads. Ideally their compensation would extend beyond those basic necessities.

This has been the perennial problem for open source: how can it be sustainable for the people who build it? We're not launching into a post-monetary Star Trek future any time soon. In the meantime, people need to be paid for their work, or open source runs the risk of being a hobbyist-only endeavor.

People won't pay for software that they don't need to pay for. I suspect open-core, which opens the core of a software platform while monetizing high-value extensions , is the best answer we can hope for. But even that might not be realistic.

#Technology

[ Link ]

[ Andy Jassy on LinkedIn ]

Andy Jassy on using Amazon Q, the company's generative AI assistant for software development, internally:

"The average time to upgrade an application to Java 17 plummeted from what’s typically 50 developer-days to just a few hours. We estimate this has saved us the equivalent of 4,500 developer-years of work (yes, that number is crazy but, real)."

"The benefits go beyond how much effort we’ve saved developers. The upgrades have enhanced security and reduced infrastructure costs, providing an estimated $260M in annualized efficiency gains."

Of course, Amazon is enormous, and any smaller business will need to scale down those numbers and account for efficiencies that may have occurred between engineers there.

Nevertheless, these are incredible figures. The savings are obviously real, allowing engineers to focus on actual work rather than the drudgery of upgrading Java (which is something that absolutely nobody wants to spend their time doing).

We'll see more of this - and we'll begin to see more services which allow for these efficiency gains between engineers across smaller companies, startups, non-profits, and so on. The dumb companies will use this as an excuse for reductions in force; the smart ones will use it as an opportunity to accelerate their team's productivity and build stuff that really matters.

#AI

[ Link ]