HN user
That's assuming you're using dynamically linked libraries/shared libraries. They're talking about "vendoring" the library into a statically linked binary or its own app-specific DLL.
Logseq to a local directory that I synchronize with my phone using SyncThing. It works great, and the fact that it's like a personal wiki feels right to me.
That said, if I were self hosting on a server, I'd probably host a personal MediaWiki instance.
Thank you. Now I have loads more videos to watch. "Mandelbrot's Evil Twin" is kind of crazy trying to visualize a 6-dimensional space in my head.
My understanding is that CloudKit runs on it.
License changes - BSL or closing the source
If there's no money in it for them - reduction of staff or funding leading to slower releases and bugfixes
Moving some features like Spring Cloud / Spring Integration, or new development behind a paywall (think RHEL)
Big users (like Netflix, Walmart, JPMorgan, LinkedIn/Microsoft, etc) would likely be able to pay for it (until they moved off), but smaller companies and individual developers not so much
Grafana's Tanka is a very underappreciated tool if you have to do something similar to Helm.
I could see the writing on the wall with this.
On that note, I'm already looking at migrating my codebase off of Spring. Just testing the waters with Quarkus, Helidon, Micronaut, Pekko, Vert.x, and plain Jakarta EE right now.
What advantage would this offer over a durable, transactional queue, like, say Pulsar? I don't see much of an advantage, and depending on how much you're pushing through your queue, I could see the outbox table causing issues with your production system if you're using that DB to hold the data.
Plus the increase in toilet paper usage and loss of productive time with all the additional fiber that everyone's getting.
Although the majority of what I do is in Python, I've taken to using Flyway for DB migrations.
A lot of what I do is using some of the more esoteric features of PG (think domains, custom aggregate functions, etc), so the ability to run migrations as direct SQL is great.
Another bonus - depending on your DB/driver, it may set this up as a prepared statement, so executions after the first one happen much quicker.
With regards to replication and remastering - that was fixed in 9.3 - https://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_...