I don't disagree with the core point that long-horizon, FOSS communities should think twice before operating atop services like Google Groups. Also the particular quality atrophy and feature degradation sucks.
Perhaps it's better framed to say that Groups is not prioritizing the particular users that the author is speaking on behalf of (ack, the monospace thing is a serious bug beyond FOSS communities). Google Groups and the shared infrastructure underneath is a critical piece of GSuite and GCP in many places, and I'd be very surprised if it ended up on the Killed By Google list.
In Seoul in the late 90s I paid some $50K equivalent jeonse for a ~1000 sqft apt, with no further monthly rent. From what I understood, the landlord can make back something equivalent to rent via common interest rates. I was young and frankly didn't understand the exposure or workings at play in this article.
Historically, in Korean culture it was very common for the extended family to live together. When a child married they often continued to reside with the parents/in-laws until they had saved enough money to move out on their own. Jeonse is far less than the amount required to buy a place, and because they get the full amount back when they move out to a bigger/nicer place (more jeonse), they can build up their savings until they have enough to buy a place.
Back then mortgages were rather rare and even monthly rents weren't that common. Things are far different now of course.
> Jeonse is far less than the amount required to buy a place
That depends on interest rates. I lived in Korea between 2010 and 2015 and in the end jeonse really didn't make sense anymore. I had a German coworker who went straight from company paid housing to buying his own place after two years, which is not easy as a foreigner. I regret not doing the same. Of course if you look at the higher end of the market, the relative difference can still be fairly substantial. But I lived in an area where you could buy an apartment for say 200M KRW while the jeonse would be 190.
actually, the reason to live with the parents had nothing to do with money. traditionally, the oldest son would take over the household of his parents when he gets married.
this is still very common in china and it is seen in many other cultures, so i expect korea to be similar.
I recommend you read books 2 and 3 in the REP series. TBP is comparatively really slow (IMO necessarily), but the series really picks up in 2 and 3 in a way that makes you appreciate the foundation that book 1 laid.
For those looking for a more automated approach for doing things like blue/green, take a look at Spinnaker (http://spinnaker.io). Here's a quick video for App Engine - https://youtu.be/pOPgTHz_nYw
Disclaimer, I work on the project.
We don't have a deployment strategy named "blue/green" for the App Engine provider for various reasons, but do provide stages such as "deploy", "disable", "enable", "destroy", as well as setting traffic split percentages that you can string together in a pipeline.
Due to the cross collaboration with Google and Netflix, and the role Spinnaker can play in infrastructure and deployment pipelines of containers, do you think it will eventually go under a collaborative project like the Cloud Native Computing Foundation?
Spinnaker is a part of [NetflixOSS](https://netflix.github.io/), no current intention I know of to submit it to CNCF. Spinnaker certainly does align with some of the core principles behind CNCF (e.g. containers, microservices), and our Kubernetes support is pretty strong (we'll continue aggressively improving it).
In any situation, we certainly run into member projects of CNCF with design considerations, and expect to continue working closely.
We're going to start a POC of Spinnaker soon and look forward to checking it out. The project looks amazing and really aligns with our goals and initiatives.
