I think you may be right. I'll look into it and report back here.
Given I was recently involved in minimising the impact of Lightbend's similar move earlier this year, AFAIU it means their products will be conditionally open source. They'll be free to use for non-commercial use but you'd need to pay for anything else.
This is the 2nd of such moves this year to my knowledge; first there was #Lightbend and #Akka and now this. What a year for #FOSS 😕
I know for a fact that so many organisations use #hashicorp products for commercial purposes w/o ever contributing back. And I understand how this may feel for hashicorp in these harsh economic times. Though this still is, IMHO, a cheap move: they used an OSS license for a very long time which resulted in a massive user base and a "soft" vendor lock-in, and now they decided to milk that user base.
Looking forwards to solid community-driven forks of their products 💪
Did anyone actually take action?
I'm not sure how to, or if I'm supposed to, since I'm based in Canada.
I wonder what would be the advantage of this over a secondary PG instance?
I can think of Lower infra costs to set a service up w/ minimal upfront investment. However, that depends on how far SQLite can be scaled as the DB size grows.
Interesting idea nonetheless!
The fix was just published to the main repository 🎉
I see your point. Though the main thing, as I mentioned in the question, is that I'm using features from 4.4 so that strategy wouldn't work for me.
Hopefully they pull it off for real and it will not get bogged down by bureaucracy and red tapes.
That's pretty much what I ended up doing. Install Gnu Make 4.4 as part of the pipeline. I then added a check to warn the user if the Make version they use is not supported.
Does it collect/transmit the keystrokes to their server?