1,084 karma · joined July 24, 2019
- 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
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!
> 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.
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.
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.
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?
I had always thought it were a generic phrase!
It’s a shame they don’t compare against or mention them.
> 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.
There’s no reason a python-like language couldn’t have deeper semantics for async, and language level implementation.
Does this not add further function colors - that of a transfunction, tiddle superfunction and non-tilde superfunction? Now every time you call one from another you need to use both the context managers and know what variant you are calling.
asgiref provides the simple wrappers sync_to_async() and async_to_aync(). Easy to understand and to slowly transition. Caveat is the performance impact if overused.
synchronicity uses a different approach - write 100% async code and expose both a sync and async interface. async def foo() becomes def foo() and async def foo.aio().
https://github.com/django/asgiref https://github.com/modal-labs/synchronicity
But it is correct that the article does not reiterate the technical details of the exploit.
Ninja compatible, for the flags that chromium uses. There’s some behaviour they’ve tuned for their use case.