years ago in Japan daylight and nighttime were each given 12 hours and clocks were made to adhere to this ... throughout the year as summer days grew longer and nighttime shorter their clocks adjusted to make an hour longer or shorter self adjusting

TIL - this is very cool. It looks like somebody actually put together a wari-koma (temporal) watch in 2011 as well.

https://www.masahirokikuno.jp/watches/temporal-hour-watch/

The non-fixed type system per https://ja.wikipedia.org/wiki/%E5%92%8C%E6%99%82%E8%A8%88 was called "futei jihou" (non-fixed time system), same with other sites https://museum.seiko.co.jp/knowledge/relation_16/ . "Temporal hour system" seems like the correct translation.

My guess is that "wari koma" here means basically "separated panels" (wari: broken, koma: panel). Wadokei means (traditional) Japanese timepiece.

If you want to look at some old ones the Seiko museum in Tokyo has a few. Entry is free and I can only recommend it.

Thanks for the tip! The wadokei clocks on the museum's site look incredible.

https://museum.seiko.co.jp/en/collections/traditional_Japane...

Just double checking, but the day and night were each given 6 hours, not 12.

spacex has cost advantage due to rocket lands back on launch pad not getting destroyed like all others

take your abandon laptop which still runs and install Ubuntu on it ... you will see how easy linux is today ... there is no justification for microsoft windows in 2026

I've had haggis in the UK and it's absolutely delicious. interesting thing is if you go to an Arab butcher shop in Brussels they have essentially the same thing. they don't call it haggis but it's the same ingredients so the plot thickens as to the history, I think it's a universal treat

after+30 years writing code in a dozen languages building systems from scratch I love vibe coding ... it's drinking from a fire hose ... in two months I vibe coded a container orchestration system which I call my kubernetes replacement project all in go with a controller deciding which VM to deploy containers onto, agents on each host polling etcd for requests created by the controller ... it's simple understandable maintainable extendable ... also vibe coded go cdk to deploy AWS RDS clusters, API gateway, handful of golang lambda functions, valkey elasticache and a full feature data service library which handles transactions and save points, cache ... I love building systems ... sure I could write all this from scratch by hand and I have but vibe coding quickly exposes me to the broad architecture decisions earlier giving me options to experiment on various alternatives ... google gemini in antigravity rocks and yes I've tried them all ... new devs should not be vibe coding for the first 5 years or more but I lucked into having decades of doing it by hand

https://m.youtube.com/watch?v=KFvhpt8FN18 clear detailed explanation of the AWS outage and how properly designed systems should have shielded the issue with zero client impact

Sounds like a replacement for slack is needed

harbor is great ... simple to install ... it's the only container registry I ever use

And in my experience is the only one that has RBAC and can be deployed on premise and that actually works, I’ve tried everything at this point

I am currently looking into zot, what were your blockers/hiccups with it?

When we looked at modernizing our image hosting, it came down to Zot vs Harbor, and we preferred Zot as it looked easier to deploy. Just a go binary with a few environment variables connecting to our minio, what could be easier?

However, when getting the config prod-ready, we started to trip over one thing after the other. First, my colleague was struggling to get the scale-out clustering to work in our container management. Right, use the other deployment way for HA. Then we found that apparently, if you enable OIDC, all other authentication methods get deactivated, so suddenly container hosts would have to login with tokens... somehow? And better hope your OIDC provider never goes down. And then we found a bug on top that Zot possibly doesn't remove blobs from minio during GC.

At that point we reconsidered and went with Harbor.

? GitLab?

It doesn't make any sense to deploy a full gitlab just to get a docker registry. RBAC is also associated with repositories and users in a way that is unconventional to manage

for simple use cases, the official registry is good enough too

If you use paid S3 as the storage layer, then you want to control size.

With the self hosted official registry, the stop-GC-restart process is a PITA.

The one thing rants like yours completely ignore is that he’s not just “revealing”. But he’s taking action outside the authority of the executive branch and you people seem all too happy to cast aside rule of law for your own personal agendas.

Trump was President of the United States for four fucking years and he's in his second term now. You don't get to play the "not a politician" card with him anymore.