Reader was dropped in the run up to G+. I believe there was a strategic decision to try and get people to move to G+ and move both personal news and organisational news together.
The leadership was never completely honest about why Reader was shutdown, and the stated reasons didn't pass some basic sniff checks. But it was easy to read between the lines: the executives' attention was on other things, and Reader was a threat to their growth. But also it was a passion project that a company like Google would struggle to keep updating since it brought in little revenue (even though there were hordes of people volunteering to maintain it for free in their 20% time).
The decline of RSS among a certain audience was only peripherally related to the elimination of Reader; it's not like there aren't other RSS readers out there even if Google makes a convenient villain. But Google did whiff on social in general and certainly indexing the world's information became a very secondary goal especially after failing with some efforts on the copyright front.
This discussion is crazy. Google is a business that sells advertising. They build a free browser so that it is easier for the end user to use their product. Chrome does tricky things to help google like, automatically searching if you don't type a URL into the address bar. You as a user, you have typed midjourney instead of midjourney.com using google search as your dns lookup.
Google is a business that has correctly identified that users are most likely unable to type the full URL into a browser and uses this opportunity to display some advertising. As my retirement investment holds a small amount of ETFs that would own google shares, yay for me. Thank you for not typing .com
This is so true and unfortunate because golang has an inbuilt example function that closely follows the test functions. It means that all that really needs to change is how godoc promotes or badges libraries with examples.
I run a two service cluster in the home lab for fun. I use PVC mapped to a NFS share for the actual data so you could always run a local postgres binary against it. In a production environment I would map these to local disk partitions like you would normally do for a db.
The upgrade process is actually quite nice when it works but it is "another" thing to learn and troubleshoot.
I think of CRDs as a troubleshooting flowchart that someone with more experience than me has put together. When it's right it's great and when it's wrong it makes trouble shooting harder. That is until you remember that the whole point of k8s is ephemeral containers. When one breaks just delete it and let pgcluster CRD resync the data.
The main rationale is definitely the license. The existing bindings for Qt Widgets (therecipe/qt and kitech/qt.go) are LGPL. That's just really difficult to use in Go where static linking is the default behaviour.
The other bindings have some strange behaviours when I checked them closely.
- therecipe/qt: The design of the "qtbox" runtime for therecipe/qt, introduced before the maintainer went MIA. Now that we know the Jia Tan xz story, it's my hope that MIQT can be a "nothing up my sleeve" binding with a clear source code supply chain, with no prebuilt binaries.
- kitech/qt.go: The rationale for their version was to focus on compilation speed, but with GOCACHE this is no longer really a problem. It also seems to be unmaintained.
You can have the LGPL'ed code but the price to pay is that your users give your objects files (i.e. pre-link stuff; but not the source code) so that your users can modify the LGPL code and rebuild your project with the modifications.
There are many parts to government but the French are actually sponsors of matrix. So one would have believed that they agreed with secure communications.
