I think his letters should always be taken with a grain of salt. He was probably just building his own myth, the article discusses that:
> As with most Zodiac writings, it sounds more like myth-building than sincerely held beliefs. Zodiac plagiarized often from pop culture, stealing ideas and lines from movies, operas and short stories. His letters, even more than his actual murders, were carefully constructed to present himself as the ultimate supervillain.
Mafia coming to you for protection money since "bad things happen" is not extortion. They just ask nicely. The fact that your building burned down after you didn't pay is totally unrelated.
> So, you are rejecting the premise that a lot of misinformation is spread and it has much wider reach than in the past?
No, but how do we jump to conclusion that government, government-controlled or government-aligned entity should be allowed to control the information we receive?
> How is it that Google create/rebrand/close so many music and chat services over the years.
It's not a rebrand. It's a rewrite. People need them promos.
In many cases, however, rewrites are actually warranted. As underlying infra gets replaced it becomes very expensive to run and maintain legacy services.
Rewrites are warranted, but rebranded every time you rewrite is not. Being able to replace core components while keeping the same brand and feature set is what takes real effort. Throwing everything out and making a completely different app with is imo a bit lazy and bad for the user.
If you truly must change things, gradual piece by piece changes is far prefered than complete 100% replacements like GPM -> YTM.
If they had slowly migrated GPM behind the scene to use Youtube over the years, and then after 2-3 years, just changed the name, I'm sure users would've been far less alienated.
I don’t think Google set up a predictable product iteration unveiling structure. One day I expect to see the PlayStation 6 for example, and one day I expect to see an update to the MacBook, and so on.
One day, do I expect to see an unveiling of a new Gmail UI? None of it is predictable because it feels like they do some serious a/b tests and just silently roll stuff out. They lack a structured presentation timeline. Currently users have no predictable expectations.
When that’s the case, just rename stuff, rebrand stuff, get rid of stuff, who the fuck cares. We didn’t promise the user updates, or even iterations, we simply promised them a one time product.
That’s the only thing that I can think of behind all of this. The simpler answer could just be their product team is not the best of the best for a company that works pretty hard at getting the best.
Your two examples at the top are both hardware, those work very differently. Websites used to do massive updates, but many have learned that it just leads to a lot of angry users. Slowly updating one component at a time works much better in my experience, and it's far less change for the user to adapt to at once.
To be fair, it seems Memorystore instance is not the same gb-for-gb as Elasticache, since Memorystore gives you extra memory overhead, and on aws you have to manage it yourself. Memorystore also has free network egress/ingress. There is also a RedisLabs offering on Google Cloud with integrated billing.
if you run Redis you need at least 25% of extra RAM on top the instance memorysize if you want to avoid a lot of nasty OOM scenarios. Memorystore gives this memory by default and in aws you need to tweak the reserved-memory. https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/...
"Air Moorea didn’t know it had both types in its fleet, it replaced all its control cables on the interval specified for carbon steel cables — about once a year."
Did they just ordered the replacement parts per catalog without looking at what exactly is being installed? I mean, they would have noticed that one plane has a different part number.
If I'm reading the report correctly, it's not clear they ever replaced the cables. The plane was new to the fleet (and was the only plane with stainless steel cables), and "Air Moorea specified on the parts follow-up documentation that the life of the rudder and elevator cables was
limited to one year (operations in saline atmosphere) from 2 October 2006" (the cables had been checked and re-installed prior to handover). The accident occured 9 August 2007.
Furthermore, even if they had known, it's not clear it would have made a difference:
> Twin Otter cables can be made of carbon steel or stainless steel. These two types of cables are interchangeable on the airplane. Their inspection and replacement programmes are the same although their behaviour is different: carbon steel cables are more sensitive to corrosion, stainless steel to wear.
> The checks required by the manufacturer are based on the number of flying hours performed or on the calendar and not on a number of cycles. This inspection rhythm is well adapted for the phenomenon of corrosion but not for that of wear.
Absent their own experience with the cables ("Several operators had adopted special inspection intervals closer together than those mandated by the manufacturer"), would they have changed anything?
In this case, the author goes on to say the manufacturer had the same recommendation for both cables. Airlines that knew of the issue didn’t communicate with the manufacturer, and Air Moorea hadn’t identified the problem with the relatively new aircraft added to their fleet. The damage in the cable wasn’t visible in their regular inspections.
With it's pros being the ability to know how close the points are just having the 2 coordinates and arbitrary precision.
Who knows how far away epic.region.music and epic.global.music are from just the names? While 18SUJ2163104440 and 12SVC0452723150 are 6 grid zones apart east to west.
That's a handy property for the 3 people on Earth who have the algorithm behind it memorized, but the rest of the world would prefer to be able to easily read, write and share the codes.
It's actually quite pleasant to use and allows you to just truncate to the level of precision you want. S/He just posted the 1m resolution string when 18-SU-J-216-044 would get you to 100m.
All this said, I think the real issue is that we refuse to PICK a standard and so every device with a GPS and ever map has one or two of
-MGRS
-UTM (almost identical to MGRS)
-LL DD MM' SS.ss"
-LL DD.dddd...
-LL DD MM.mmmm...'
etc.
If you make a device that can output or accept a location string, make sure it can handle all LL cases and UTM/MGRS.
Most people can tell proximity in lat/lon coordinates based on the algorithm they learned in first grade: the number line. Perhaps they could use a similarly ubiquitous system, like the alphabet. There’s even a song to help you memorize it!
