An idea you can steal: turn common generated/lockfile diffs into something readable (a la https://www.npmjs.com/package/diff-package-lock)

https://github.com/ivankovic/omnidiff/issues/61 feel free to subscribe to the issue to see when it is done.

What I'd really like to see is a spoiler-free mode.

I can watch a race on catch-up, but if I'm doing that then I can't open PCS to check profiles or standings/time-gaps until I'm fully caught up

Exactly this.

On top of that, when catching up it's great to have an indication of _when_ to start watching a race. For that I've been using the info provided on the HowFarOut[1] Twitter account.

[1] https://nitter.click/HowFarOut

We are looking at ways to indicate ahead of time when you should start watching (and sign up for push notifications) as well as ways to do this based on what is happening in the race (crosswinds alarm!)

We have that! It is not perfect but is improving. By next season we will have catch-up mode too so you can tune in when you can and get caught up on the major events that got the race to where it is

I grew up in Idaho, so I know well the pains of trying to follow the sport from another timezone

I've given the app a go, but one thing I'm wary of is how much bluesky stuff is in - and that's likely to have race spoilers too

It's a shame Lucas' cycling blog isn't on that platform, that's a great source for news and updates

We will be labeling spoilers from bluesky as well before next season starts so they stay hidden. Work in progress but it should be getting better at a pretty quick pace!

Hillel Wayne did a series of interviews with people who are considered "proper" engineers, which you can read here:

https://www.hillelwayne.com/tags/crossover-project/

the tl;dr is that for the most part, modern software development is very similar to engineering

pgrust sounds very interesting, but with the deep changes there’s no viable path to upstream it - is the end goal to be robust enough that it’ll get wide adoption?

Is it really interesting though? It's essentially just vibe-coded by people who are unqualified for this kind of work. One of the authors claimed that what qualified them was having worked on a large-scale postgres cluster; they never actually worked on databases or compilers.

They are going to lose their coding driver's license.

Weirdly Apple seems to have something like this built-in for finding an apple TV remote - but the same flow doesn't appear to be launchable for any other device

It works for newer AirTags as well, this isn't BLE based but Ultra Wideband.

That's an entirely different technology, and if you look at it from an RF lens, a highly impressive one.

UWB is interesting.

If you use your phone as a key for your Tesla, you can turn on "nearby interactions" on the phone and the car can very accurately know your position.

Then with the accurate positioning, you can stand still in front of your trunk, and have it open. (it is a setting, hands free trunk/frunk)

Upthread the implication seems to be that smolmachines would be in some way a replacement for orbstack to run docker containers

But it seems more like a completely different way to run isolated workloads?

smol machines is a virtual machine, akin to firecracker but designed to run locally as well

It also has container-inages support built-in with crun so you can create a VM with a container running by default.

You can also just... run docker inside of it.

on the rare occasions where I need to loudly indicate my presence to a motor vehicle I wouldn't really want to be moving my hands - if I have time to move a hand to a horn I probably have time to brake/manouvre instead.

Generally in those situations I shout really loudly at the driver, and in general they seem to hear me

The way AWS keep their pricing section completely separate from their system and architecture docs, despite architecture being the primary driver of cost, is a major contributor to this

A bitmap index scan allows the database to narrow down which pages could include the data, but then still has to recheck the condition on the contents of those pages - so will still not be as performant as an proper index scan

With postgres indexes not containing liveness data for tuples you'll have to hit quite a lot of those pages anyway, unless they are frozen.

This pitch seems ok to people using simple log aggregation tools or metric tools that have to be wary of tag cardinality

But how does it compare to an actual modern observability stack built on a columnar datastore like Honeycomb?