Quite interesting and nice. A bit delves into a "mass surveillance" like theme though.

Would be great to have some sort of local-only RF synchronization between the devices to "confirm" these events and issue alerts without requiring any connection at all...

P.S: Local-only RF synchronization, as in accelerometer and gyroscope data encoded directly (analog) 2.4ghz signal.

to accommodate $MSFT shareholders downvotes, have my upvote :)

nevertheless, even NFS is better than sharepoint. At least, NFS works...

I think it highly depends on your architecture and the scale you are pushing.

The other far-edge is the S3, where appending has just been possible within the last a few years as far as I can tell. Meanwhile editing a file requiring a full download/upload, not great either.

For the NFS case, I cannot say it's my favorite, but certainly easy to setup and run on your own. Obviously a rebooting server may cause certain issues during the unavailability, but the NFS server should be in highly-available. with NFSv4.1, you may use UDP as the primary transport, which allows you to swap/switch servers pretty quickly. (Given you connect to a DNS/FQDN rather than the IP address)

Another case is the plug and play, with NFS, UNIX permissions, ownership/group details, execute bit, etc are all preserved nicely...

Besides, you could always have a "cache" server locally. Similar to GDrive or OneDrive clients, constantly syncing back and forth, caching the data locally, using file-handles to determine locks. Works pretty well _at scale_ (ie. many concurrent users in the case of GDrive or OneDrive).

> I have no idea what lsd is doing. I haven’t read the source code, but from viewing it’s strace, it is calling clock_gettime around 5 times per file. Why? I don’t know. Maybe it’s doing internal timing of steps along the way?

Maybe calculating "X minutes/hours/days/weeks ago" thing for each timestamp? (access, create, modify, ...). Could just be an old artifact of another library function...

This shouldn't be an actual syscall these days; it should be handled by vDSO (`man 7 vDSO`). Maybe zig doesn't use that, though.

Call this unpopular opinion (probably gonna get downvoted anyway), but the amount Oracle gets paid because lazy-devs are well, too lazy to read which JVM arguments should they put to their deployment, requiring hand-holding by the Oracle-support team.

I understand in the olden times there were javax.* and JavaEE, but nowadays, especially in the newer JDKs, these are completely gone. Whoever maintains Java 1.6 in their core infrastructure already doomed, regardless of Oracle asking them $$$ or not.

edit: I know various Java-devs which are "runs on my machine" mindset. As a DevOps engineer, most of the production outages I took care of were avoidable by removing this mindset and actually testing the code in a sandbox environment...

I've had an ongoing debate with a guy who is supposedly senior java dev of 20+ years that doesn't understand the most basic aspects of concurrency, and codes "worked on my local" style and engages in obnoxious blame games with DevOps and infra teams about how his application works totally fine spinning up 10,000 threads on his 16 core macbook, but for "some reason" craps out in production running on a 1 vcpu allocated container. At least a year of back and forth on this and he doesn't understand why. Wish I was making it up.

I am not sure if it's ironic or not, but this post itself is also AI related :). An it's getting quite a lot of votes & comments...

Meanwhile, I really liked the blog theme/design. (reading on an iPad) Simple, yet powerful, with a nice touch of the blinking underline at the end of the title. (It's a simple trick via CSS, but nice to see!)

Besides the hard-coded cache, shouldn't DNS infrastructure already help with the caching just by the TTL value itself? Given quite many & large public DNS resolvers out there, like Cloudflare's 1.1.1.1 and Google's 8.8.8.8

I overall like the DNS, it is a global database with eventual consistency. Possible to store transient data. Usually not blocked by firewalls just by the sheer innocent nature. (Although gets intercepted quite a lot...)

It's a networking event, not an interview loop.

In the same lines, don't ask anything. Everything is a bias. ie, What do they do? - Also a bias as they are engineer, or product, or sales, or whatever.

I am not sure if the _Swarm_ is still alive, but it can definitely do blue/green rolling deployments...

I fought really hard at one of the startups I previously worked. For the CV/Resume polishing, engineers pushed for K8s. It was outrageous for me since there were total of 3 applications running. 1 Python monolith and 2 other smaller Go apps.

Just before that, I was able to reduce AWS costs from 5k+/eur/month to sub 2k/eur/month. Having 3 parallel environments running at the time. (Dev/Staging/Prod).

To me, the `inetd` _is_ the CGI. Which made internet waay more fun. I, myself hosted various shell scripts through inetd, even an HTTP one which was written completely in Bash.

Although the VPS is long gone, and I did not use any version control at the time. The laptop I wrote the stuff are gone too :'(. But it was certainly quite fun. Deployment was as easy as Makefile + scp and testing was the another Bash script with bunch of `netcat`s and greps.

What a time to be alive :)