aidos

What? There’s no way that’s correct. I use PIL exactly like that and don’t have matplotlib in my codebase.

I feel similarly and again.

We actually have this pattern in our codebase and, while we don’t have all the features on top, it’s a succinct enough thing to understand that also gives lots of opportunity for discussion.

> “Our technical team is currently working diligently to address the issues you raised”

Oh now you’re going to be diligent. Why do I doubt that?

More crucially, when did we lose the ability to click and hold on the first checkbox and then drag down the list to set them all the same way!

> 1982: Dragging through a field of check-boxes flips the state of the first and assigns the new state to all other boxes dragged through.

At 100s of millions I’m assuming you have something closer to a static site than an application?

I love bad kerning more than most, but a lot of those feel like someone just put a space in the wrong place.

That’s a shame, I like my kerning to sit in that sweet spot where people don’t notice it but once you point it out it gives them an unsettling feeling wherever they see it.

Why is that? Whenever I’m giving examples I almost always use 7, something ending in a 7 or something in the 70s

That’s how 1Password used to work. Not sure how much of that is still left in the system these days.

Originally it was an app with no remote component. The vault was yours to look after. Most people kept it in Dropbox to make it accessible anywhere. The vault itself actually had an html file in it that you could open in a pinch that was able to decrypt secrets (only for reading, from memory).

1Password as a service came later.

This is amazing!

I was speaking to a friend the other day who works in a team that influences government policy. One of the younger members of the team had been tasked with generating a report on a specific subject. They came back with a document filled with “facts”, including specific numbers they’d pulled from a LLM. Obviously it was inaccurate and unreliable.

As someone who uses LLMs on a daily basis to help me build software, I was blown away that someone would misuse them like this. It’s easy to forget that devs have a much better understanding of how these things work, can review and fix the inaccuracies in the output and tend to be a sceptical bunch in general.

We’re headed into a time where a lot of people are going to implicitly trust the output from these devices and the world is going to be swamped with a huge quantity of subtly inaccurate content.

Not wrong, but since you’re mentioning vim in the context of git, might be worth adding :cq as a way to exit with a non-zero status to prevent git from finishing the commit / operation.

Not 100% sure of the details but I think it’s more like a digital pwm system.

I had dimmers installed when we rewired our house and I thought they were rubbish. Replaced those with Varilight v-pro and they were noisy. Discovered that I could switch between leading edge and trailing edge modes (or something like that) and the sound went away. Love them now.

I’ve always worked around that by having a requirements.base.txt and a requirements.txt for the locked versions. Obviously pip doesn’t do that for you but it’s not hard to manage yourself.

Having said that, I’m going to give uv a shot because I hear so many good things about it.

You don’t need to ditch vim to have these features! Mostly they’re using lsp in a client (editor) / server relationship. You can run the same tooling happily from vim (I use neovim, but I believe it’s all implemented in vim too).

Mobx has similar patterns with the computeds. They allow you to have a little more control over their lifecycle. The general rule is that they’re kept alive until they’re no longer observed but you can pass a flag to keep them around even when they’re not needed.

I pushed my Amstrad to the limits but, God, wasn’t the Amiga something else?

Disagree. That seems like it would just slow down progress.

Astral are winning mindshare because the tooling is so much better than the previous generations. That’s the action that’s required here - to be the compelling choice, rather than another choice that’s pretty much like the others and differs only a little.

What a beautiful bit of work. Are they actually commercially available and how are you going to handle production? Did you set out to sell them from the start or was it a personal project that has spiralled? How long have you been working on it?

In any case, congratulations!

Did not know that! The pulsing baseline on Sheep is awesome. Not as awesome as the way the vocals tail off into hypnotic synth at the end of each line. It’s such a well crafted album.

Interesting! Thanks.

Ah thanks! I was going to ask in here to see if anyone knew because the explanation about overwriting the same vector seemed pretty off base.

Never worked in Rust though so wondered if the iterator api had some weird optional notion of size that could be utilised throughout the chain.

Mine is simple but relies on a few cheap tricks (like generating uuids in the frontend and manually linking relationships in an order where replaying on the db is going to work). Happy to walk you through it if you want to message me.

Hadn’t seen that one. Thanks for the heads up. It’s the sort of thing that I could see being useful in a bunch of places. We have a number of hand rolled things to deal with similar issues.

Might not be a perfect fit here because some of the views are session context dependent (but could maybe still be workable).

We hit on exactly the same pattern for our product and it works really well.

We use Hasura as the read engine. That updates a graph of mobx objects that drive the ui. We apply updates directly to those objects so the ui updates immediately. The mutations are posted back to a Python api that applies them to the db.

I’ve looked at Electric because we’ve had to recreate some of what they do to interface with Hasura. At the moment it’s a non-starter because we use pg views to shape the data for the frontend.

I’ve not tried it but this popped up on here a while back and sound like it might fit the bill.

https://taskfile.dev/

It’s 2. We’re just running a js function here with nothing magical going on.

It might seem that there’s a chance that people will be confused about what bar is, but in practice all the changes are happening in handlers and bar will be a const anyway so you have no plans to mutate it directly.

The react team have done an incredible job maintaining backwards compatibility across versions over the years. They’ve even fought for bug parity when doing major internal rewrites.

A lifetime of dirty browser hacks is suddenly flooding back. Kids these days will never appreciate what we had to go through to make a page render anywhere near consistently in different browsers.

Tricks like crafting css that only some browsers could parse.

    height/**/: 300px;

Or the insane sliding doors technique we used to get rounded corners.

https://alistapart.com/article/slidingdoors/

The mystery script we included to get alpha support in images.

https://git.twinhelix.com/cgit/iepngfix/tree/iepngfix.htc

The fact that select inputs were rendered by the OS so you had to find them all and hide them when you opened a modal so they didn’t sit on top of your content.

The desire to support custom files that drive us into swapping all the text for blocks of Flash after the page loaded.

It was almost better than the 20 level deep nested table layouts full of shims we had to do.

Oh interesting! So you map exactly to the structure in s3? It’s like fuse backed by s3 with good performance?

Super interesting product. I have a couple of questions:

In terms of storing in s3 - is that in your buckets? Sound like the plan is to run the caching on your infrastructure, are there plans to allow customers to run those instances themselves?

Presumably the format within s3 is your own bespoke format? What does the migration strategy look like for people looking to move into or out of your infrastructure? They effectively pull everything down from their s3 to the local “filesystem”?

As a general rule, yes they are compressed. As you point out, they compress really well.