HN user

silvester23

505 karma
Posts0
Comments145
View on HN
No posts found.

The thing about the anti-piracy is true, at least in the original version (I don't know about re-releases).

The way it worked was you had to offer at least a few pizzas that were reasonably close to recipes from the booklet in order to get any customers. Once you had that, you could get creative with custom recipes but if you only did custom recipes, you were bound to fail.

For us, the DX of uv for dependency management is much better than just using pip and requirements.txt.

To be clear though, we only use uv in the builder stage of our docker builds, there is no uv in the final image.

Boring Go! 6 months ago

Kind of off topic but I don't understand the reading time. It says "7.8h 48m". What does that even mean?

This is actually covered by the --locked option that uv sync provides.

If you do `uv sync --locked` it will not succeed if the lock file does not exist or is out of date.

Edit: I slightly misread your comment. I strongly agree that having no lock file or a lockfile that does not match your specified dependencies is a case where a human should intervene. That's why I suggest you should always use the --locked option in your build.

Was there any particular reason you stopped making music?

I'm listening to one of your mixes right now and I'm wondering if you were influenced by Klangkarussell at all (or maybe the other way around?) or if that was just the general 2014 vibe.

I would also say absolutely. We've been using pipenv for ~6 years and have managed to build a pretty good workflow around it. But uv is just _so much faster_. So we've started moving everything over to uv and I don't think we'll ever look back.

Migrating is not super hard, we wrote a small script that moves all the information from a Pipfile to a pyproject.toml and it works like a charm.

What they mean is that in Java, for example, a method has to explicitly state which exceptions it might throw as part of its signature. Note that they said "throws", not "throw".

Python does not have that.

You might enjoy the podcast "372 pages we'll never get back". It's basically a bad book club. The title is a reference to the first book they cover which is Ready Player One.

They are on Book 23 or so at the moment, more or less alternating between books by "big" authors like Dan Brown or Sean Penn and super obscure stuff like Harry Potter-Twilight-crossover fan fiction.

A full circle is 360° and a curved piece makes a turn of 30°, so you need 360° / 30° = 12 pieces turning in the same direction to make a full circle.

Every time you use a piece turning the other way, you need to add an extra piece turning the way you want to complete the circle, so the difference between the directions has to be 12.

Note, however, that not every track with exactly 12 more pieces turning one way than the other necessarily makes a complete circle, straight pieces can cause the ends not to match up.

If you are into this kind of in-depth look into fantasy worlds, you might enjoy the blog A Collection of Unmitigated Pedantry (https://acoup.blog).

For a related article see, e.g. this one: https://acoup.blog/2019/06/14/collections-the-siege-of-gondo...

It has a bit of a different angle in that it critiques works of fantasy in terms of realism, feasibility and consistency in a pretty nitpicky way (the hint's in the name, really). Still I find it mostly good-humoured.

The Outer Wilds (not worlds) is another one that I think rivals Obra Dinn, and is more accessible. It might be the best narrative-focused puzzle game ever made.

If only I could play it again for the first time. There's really nothing quite like it.

By the way, it's just Outer Wilds, no "The". Still easily confused with The Outer Worlds, though.

I only read the first two sections of that article but they already contain such strange assertions that I don't think it's worth it to bother with the rest:

I think “a culture where social norms are enforced with repeated and vociferous public shaming” is the most useful way to define the term.

That might be the most useful way for the author to make their point, but as far as I am aware, for most people being cancelled definitely entails some sort of deplatforming, e.g. some BigCo not wanting to be associated with your name. If you keep doing what you're doing while being insulted on Twitter, that's not being cancelled, that's just ... well, Twitter.

What I find more interesting is that this argument requires the very thing that it laments. That is, in order to make this argument, you need to have figures like Louis CK who escape/survive the consequences of public shaming, but simultaneously to assert that this is a bad thing.

In no way does the tweet embedded at the top of the article imply that it's a bad thing that Louis CK is playing MSG. It's saying that if we define being cancelled not in the way the author of the article did but the way I outlined above, someone who is supposedly cancelled would not be playing MSG. From there it makes the pretty big leap to say that cancel culture in general is not real.

I'm not even that invested in the whole debate but this article seems completely misguided or in bad faith.

I think the closest you can currently get is Seth Meyers' "Surprise Inspection" segment, you can watch it on YouTube.

Memento mori 4 years ago

If you enjoy independent films that mostly consist of people talking in very few different locations, I strongly recommend Coherence. It's pretty different but I think I enjoyed both of these for similar reasons.