operator-name

Cool! Will it be based on the spaces alpha?

https://knowyourmeme.com/memes/they-feed-us-poison /jk

It’s exciting to see how low the barriers to fuzzing and formal proofs and higher verification standards like property based testing has become! It’s just a shame this LLMs are what it took, and even then adoption in the industry is slow.

I’d love to hear more about some limitations/tradeoffs of docker that you made at the time that you regret in hindsight. Was there anything that you wish didn’t get baked into the “default norms” for containers, or areas that would benefit from more attention and redesigns?

I’ve been following dagger and it’s been really interesting to see the evolution of the design, and new set of abstractions. There’s also nix which has seen popularity, with their approach of building layered oci containers.

I’ve been using WindHawk for a bit, and my favourite mods have been:

- Slick Window Arrangement (better window snapping): https://windhawk.net/mods/slick-window-arrangement

- Better file sizes in Explorer details: https://windhawk.net/mods/explorer-details-better-file-sizes

Previously on HN: https://news.ycombinator.com/item?id=45925971

This wasn’t a pen test? It was a drive by “oh fuck the platform I’m using is completely insecure”.

The custom Github Actions approach is very customisable and flexible. In theory you could make and even auto approve bumps.

If you want something more structured, I’ve been playing with and can recommend Renovate (no affiliation). Renovate supports far more ecosystems, has a better community and customisation.

Having tried it I can’t believe how relatively poor Dependabot, the default tool is something we put up with by default. Take something simple like multi layer dockerfiles. This has been a docker features for a while now, yet it’s still silently unsupported by dependabot!

The refined github extension[0] has some defaults that make the default view a little more tolerable. Past that I can personally recommend Renovate, which supports far more ecosystems and customisation options (like auto merging).

[0]: https://github.com/refined-github/refined-github

I think they mean if they already have her fingerprint from somewhere else, and a secret backdoor into the laptop. Then they could login, setup biometrics and pretend they had first access when she unlocked it. All without revealing their backdoor.

I'm not sold at the idea - for most projects it makes sense that the author of the PR should ultimately have ownership in the code that they're submitting. It doesn't matter if that's AI generated, generated with the help of other humans or typed up by a monkey.

> A computer can never be held accountable, therefore a computer must never make a management decision. - IBM Training Manual, 1979

Splitting out AI into it's own entity invites a word of issues, AI cannot take ownership of the bugs it writes or the responsibility for the code to be good. That lies up to the human "co-author", if you want to use that phrase.

This is new to me, and a wonderful dive that I wish I was aware of during my OS course. Thanks!

also previously from the owner of archive.is/today: https://archive-is.tumblr.com/tagged/patokallio

> a PC laptop with Apple build quality and display quality, and there definitely aren't many options

There’s been a bunch of Windows ARM laptops that aim to directly compete with the M series Macs. Linux compatibility will depend on make on model.

Wow, that is an awesome resource and something I wish I knew about earlier!

There’s also a hell of a lot of gestures that I’ve just learned of: https://www.cnet.com/tech/i-finally-got-used-to-the-new-ios-...

The article makes an interesting point about the search focus. I wonder if there were plans for AI assisted search? That is a direction that could explain why search became so prominent.

From reading this thread I’m glad I’m not alone. It seems their “compact” mode has a bunch of invisible gestures that you’re just supposed to know about.

Luckily I’ve also discovered that you can revert back to “bottom” tab mode in the settings, which brings back something similar to the old UI.

As a long time Android user, I find these magical gestures frustrating difficult to discover. How on earth is someone supposed to guess such a gesture exists, and how am I supposed to guess the rules for when certain gestures work and certain gestures don’t?

Even long time friends who are iOS fanatics, and who have used iOS since the beginning are often surprised when I show them a new gesture I’ve learnt. Am I missing something? I’m really grateful to learn this now but I can’t imagine the “Apple way” is to stumble upon these by forum comments?

Could you elaborate how it is better?

The browser ensures that a passkey can only be used on the correct site.

In the west we have “No Animals Were Harmed in the making of …”, which I’m only just learning comes from the American Humane Society: https://en.m.wikipedia.org/wiki/American_Humane_Society#No_A...

I had always thought it were a generic phrase!

httpx also supports sync and async, but I remember seeing an issue in their repo about worse performance than aiohttp.

Not to mention sync_to_async and async_to_sync are also part of a library, asgiref that the Django developers made to wrap a thread pool runtime!

This looks similar to https://github.com/chengzeyi/ParaAttention or https://github.com/ali-vilab/TeaCache.

It’s a shame they don’t compare against or mention them.

I strongly disagree. Making invalid state unrepresentable is important.

> wastes space > premature optimisation

A timestamp is a witness of when the email was verified. Since if they’ve verified can be calculated from it, having both is not only redundant but allow invalid states to be represented.

Cases like email verified are often followed by the need to know when. Say an expiry system. Going from bools, you are faced with the hard choice of how to migrate existing state.

Databases also warrant more care as a source of persistent state - accessed by multiple versions of your software. If you don’t have this persistency, then it matters less.

> any other fields that happen to be strings or numbers or blobs were changed > implement proper event logging

Event logging is orthogonal to your database state. If your business logic needs dirty flags or timestamps they should be stored in the database, not queried.

And if you do need it for other fields, adding the bool is the perfect time to ask yourself if what you need is a timestamp.

> way we don't start with floats rather than ints "just in case" we need fractional values later on

Floats are a subset of int, and a natural migration. A bool can be calculated from a timestamp, but not the other way.

Just tested it out on iOS. It’s scored 94% against Adguard’s 79% on this test page: https://adblock.turtlecute.org/

You frame that as if python doesn’t have a choice, but it chose to have explicit syntax.

There’s no reason a python-like language couldn’t have deeper semantics for async, and language level implementation.

I think that only applies to tilde_syntax=False but way it is written isn’t very clear.