justinsaccount

Looks like a cell phone recording of a monitor. It's also slightly askew, you can tell the horizontal lines are not quite horizontal. The bright explosion likely confused the autofocus, or maybe the person holding the camera jumped.

Maybe it's outputting https://en.wikipedia.org/wiki/Whitespace_(programming_langua... :-)

> Microsoft recommending STS be turned off when the server receives reliable timekeeping through the Network Time Protocol.

Why then are the first lines of the STS code not something like

    // server receives reliable timekeeping through the Network Time Protocol.
    if (ntp_enabled() && ntp_working())
        return 0;

Can they do Lenovo next?

  ThinkPad P1 Gen 4 Intel (16") - Mobile Workstation
  Save $3,800.00 65% off (Est Value $5,789.00) $1,989.00

For faces that might be true. I've had issues with different tools when sharing a full desktop session on a 4k monitor.

That's usually how I go about things too. It's annoying that a lot of the new crop of youtube programming videos skip these steps. I've seen a few "How to write X using Y" videos that basically write the whole thing from top to bottom one line at a time.

https://www.youtube.com/@JustForFunc and https://www.youtube.com/@fasterthanlime are good exceptions to this. I want to see the process of building out something complicated one bit at a time, including all the mistakes and dead ends.

Before LE almost no one automated SSL cert refresh. Depending on your SSL cert vendor you couldn't automate things even if you wanted to. It's not that the automation ran fine for five years, it's that you'd be lucky if the manual process last done 5 years ago was even documented.

SSLMate is about as old as LE, they both started around the same time.

Python does not include a structure d logging package as part of the stdlib as far as I know. What package are you thinking does what slog does?

The biggest difference is in rust you have to handle the error case, but in go you can accidentally ignore it.

> To be fair, Carmack had been pushing for an all-out device but got sidelined by Zuck's push towards cheap and scale.

You have that completely backwards.

> "I've always been clear that I'm all about the cost-effective mass-market headsets being the most important thing for us and for the adoption of VR," Carmack said. "And Quest Pro is definitely not that..."

https://arstechnica.com/gaming/2022/10/carmack-wants-a-250-v...

What if valve released a standalone VR headset? For me that would be the no-brainer.. a (most likely) open platform + large library.

20+ years ago I used distcc + jpegtran to rotate a few thousand jpegs. From what I remember I just had to write the Makefile as you would normally.

I think the end result was that the transfer time at 10mbps speeds made it take longer than it would have just transforming locally, but it was neat to see it work!

Sounds like Bluesky screwed up by not implementing the https://publicsuffix.org/ list

> it may even be harmful

It definitely is, I tried to make the same point a week ago :-)

https://news.ycombinator.com/item?id=35707786

What purpose does predicting the outcome of an election serve in a democracy?

> who possibly can win

huh, who told you that, the people forecasting the election?

It's simple: Election forecasting is often used as a form of voter manipulation, if not outright suppression.

People should vote for the candidate that they want to win, not the candidate that the tv says has a better chance of winning.

The very idea of election forecasting is harmful to democracy and should be shunned wherever it appears.

Also you can benefit from being able to use all of SQL to manage the queue.

I built a system ages ago that had modest queue needs.. maybe 100 jobs a day. It involved syncing changes in the local database with external devices. Many changes would ultimately update the same device, and making the fewest number of updates was important.

The system used an extremely simple schema: A table with something like [job_id, device, start_after, time_started, time_finished]

When queueing a job for $device, do an upsert to either insert a new record, or bump up the start_after of a not yet started job to now+5 minutes. When looking for a job to run, ignore anything with a start_after in the future.

As edits were made, it would create a single job for each device that would run 5 minutes after the last change was made.

I know a lot of queueing systems have the concept of a delayed job, but I haven't come across any that had the concept of delayed jobs+dedup/coalescence.

Have you ever read https://medium.com/@gtrevorjay/you-could-have-invented-conta... ?

You were halfway there :-)

USB-C to HDMI adapters are not the same as display link.

DisplayLink is a janky proprietary virtual framebuffer thing that is pretty similar to the linked project.

See my above comment, there's a reason why all of your examples work:

Java package managers tend to install packages written in java

Go installs packages written in go, and maybe C using cgo

Cargo installs packages written in rust

php package managers install packages written in PHP, extra extensions are rare

etc

People having trouble with python are NOT having trouble with python. They are having trouble because they are trying to use packages that are just python bindings to absolutely massively complex c++ and Fortran libraries.

Often people using python don't even have a C compiler installed (let alone a fortran one for the scientific stuff), so pip blows up the first time they try to install a package that hasn't been pre-built for their system+python version.

Things like pandas and numpy are not python packages. Yes, they are packages FOR python, but they are not python.

https://hpc.guix.info/blog/2021/09/whats-in-a-package/ does a good job of explaining why installing packages like that is a complete shitshow.

upstart: a broken design and abandoned by its author and canonical https://lwn.net/Articles/581548/

openrc: I don't believe openrc had a process supervision story 8-9 years ago. from what I recall at the time openrc was just a slightly better sysvinit.

runit: I have a lot of experience with runit, and while it works, it has many footguns and is hard to use correctly.

s6: a better runit with better footguns

A great thing that more people should read, is https://lwn.net/Articles/578210/ from one of the Debian developers who voted to switch to systemd. It touches on things like the lack of adoption of upstart, and openrc not solving the problems they had.

FWIW, you can easily install tailscale (and probably other things too) on the chromecast.

I saw this on our site that used next.js once. Looks like they use Gatsby which I guess is similar.

Cache headers weren't being set properly, new pages would or wouldn't load depending how you reached the page (direct link vs. javascript loading the content via an internal cache or via a fragment fetch)

This is not "zero-downtime", this is "zero-downtime, maybe, as long as nothing goes wrong and the new container comes up immediately".

You would be much better off using something like dokku, which handles zero-downtime deploys properly and supports using a CHECKS file to verify that the new container is working properly before routing requests to it.

Most people actively avoid having rust anywhere near their cars.

Zero downtime deployments are just a side effect of doing any kind of A/B deployment.

The same features can help you avoid longer downtime. I use dokku at home to run a little web portal. I have a CHECKS file in the repo that has

  WAIT=1
  TIMEOUT=1
  ATTEMPTS=10
  / Portal
  ...

If I try to update to a new version and the site doesn't come up at all (or a GET for / doesn't have "Portal" in the response), the update is aborted and requests never fail.

Neat.

More things should be links. Like if I'm on

https://www.knifegeek.io/blades/pro-tech-malibu

Most all the words on the page should be links. "Pro Tech", "Wharncliffe", "Damascus", "Malibu" etc should all be clickable to view similar things.

Oh, and you should add a metadata field for locking mechanism.. fixed, friction, lockback, liner, frame, button, axis, butterfly, etc.