As long as the content is great, this doesn‘t matter at all. It helps especially non-native speakers a lot to clearly communicate their ideas. And it saves time for the important work. We should get used to it as fast as we can.
Even if you’ve already learned distributed system design, it makes things much more complicated, is easier to break and harder to maintain. Getting new developers to the project is harder as most lack the experience working with distributed systems.
And most of the projects started by small companies will never have the need for scaling. Should they once need scaling, the project is typically so successful they can easily pay for experts to help them.
I love the idea, but at least on my iPad it’s hard to discover what I could do on this site. That some menu options are written with Cyrillic letters doesn’t help either. It would be great if you could make the onboarding smoother.
Yes, I see the reasoning, but it really is a tiny fraction of mankind dealing with this issues. And, as you said, there’s tech for that.
One design flaw of your solution is the complicated math to go from classic time to GPTS. Time zones may be annoying, but in most cases, we just have to add full hours. New York is six hours behind the time of central Europe. That is easy math.
Another aspect, perhaps I missed it: How does GPTS handle daylight savings, especially when some regions switch on different days? The conversion from GPTS to classic time and vice versa has always to be dependent on the current location.
And finally, what about frequent travelers? Any time zone they visit will have vastly different opening times of shops or bars. They’d be forced to do the math everytime.
Just a clarification as the headline could imply a wrong understanding: It’s not the EU that banned it. Meta itself forbid its use by entities within the EU to not have to comply with EU laws.
Interesting ideas, but I‘d say no chance for adaption. Mainly because most people have no need for global scheduling. They would have to adapt to a completely unfamiliar system, without any advantages for them.
For similar reasons, the French Republican calendar or the Soviet Revolution calendar weren’t successful. Interesting though that the French Republican calendar already tried to use a decimal system for timing with ten hours a day and hundred minutes an hour.
Isn’t what you call a "sharp name" just a brand-able name? These kind of domain names aren’t parked that often as they are typically some kind of fantasy names or combinations of two or even more words. So no, I don’t think they’re undervalued.
Assuming numbers are just a construct of our minds, we could even argue that unicorns have more existence than numbers. We can’t proof a unicorn doesn’t exist. So there is a probability of its existence greater than zero. As numbers are only constructed, we’re sure they don’t exist and this shows that unicorns have more existence than numbers.
I really like the aesthetic of the site and how the principles are shown. IMHO everyone building things, even the nerdiest tool, should know about these laws. One addition I'd like to see on that site: Show more examples of well-done interfaces that highlight the respective principle. There are some (I found two Google screenshots), but I'd like to see it for every law. That would be great.