johncoltrane

I tried all the DD alternatives (on macOS) and I think OrbStack is the easiest to use and least invasive of them all.

But it is not cross-platform, so we settled on Podman instead, which came (distant) second in my tests. The UI is horrible, IMO but hey… compromises.

I use OrbStack for my personal stuff, though.

That's a very liberal use of "we".

That's the French postal service's "identité numérique".

I find the way the amount fluctuates over time mildly funny. It reminds me of the joke where the police makes a bust and the total weight of drug seized diminishes at each report.

Interesting for sure but videos of the OS in use for actual work and of the hardware would be even more interesting. Also choice of keyboard.

First, the obvious: legal ways to stop anything have never succeeded in stopping anything.

Second, what would you loose from your book being used to train LLMs and what would you gain from preventing that? Are you afraid of loost sales? Or maybe plagiarism? Those problems have existed for a loooong time, LLMs or not. Or is it that you don't generally like the current AI craze and don't want to fuel it?

Democracy is when people get to decide how the nation will be run for the n next years without a gun pointed at their head, not when a party with "democrat" in its name gets the majority of the votes.

Those places all have ticketing systems and operate at capacity to maximize money flow. Rising prices won't change much I'm afraid, but forcing those places to run at a fraction of their capacity, possibly with some subsidy, would.

(Barely tangentially related) Each time I visit Japan I can't help but notice how low people tend to wear their (usually Coleman) backpacks. So much that I came to mentally call them "asspacks".

The problem is that the light emitted by the background "eats up" the light emitted by the foreground object because there is, simply, more of it. The background is larger than the foreground and the intensity is higher. Ironically, the effect is easier to visualize with a light foreground against a dark background: that halo around white lines and text is also produced by a light background. The light halo eats up its darker neighbors.

So there are basically two ways to mitigate that effect: make the foreground elements larger or reduce the delta in intensity.

We can make lines thicker, boxes a little bit larger, and use bold text.

We can reduce the intensity of the background, from pure white to rgb(246, 246, 239), for example.

We can choose brighter colors in a kind of arms race against the background.

All three options have inherent limits, though.

Thick lines and large boxes kill details and bold text lack nuance, darkening the background is not always possible, and the catalogue of bright-enough-colors is pretty small.

One of the reasons why we, colorscheme authors, tend to default to dark backgrounds is that doing so gives us more colors to play with and thus more creative leeway.

Actively using Vim is what makes the subset of commands you need stick, which makes things like this generally pointless. Writing that program with Vim, assuming you actually did, did a much better job for you than the program will do for its eventual users.

Learning Vim is easy.

I know. It comes up a bit later than the .uk domains, though.

Great write-up. Note that the UK is no longer part of the EU so even those .uk domains are a bit of a red flag.

FWIW… Tech fads used to be pretty limited to tech circles. You would be bombarded for a few months by content about this or that on HN and elsewhere without ever hearing about it on the subway or at a dinner. Crypto kind of crossed the line at some point, but it is still a niche thing. ChatGPT and that whole ML-marketed-as-AI thing, on the other hand… it is everywhere.

"Get rich quick" schemes are somewhat attractive to the masses but nothing seems to beat those new "don't do the work you are paid for" schemes.

I want that world.

This and Frances The Mute are some of the finest rock ever produced.

Because the distinction is meaningless for most people.

What are you trying to achieve by showing a one year chart of _something_ and a twelve years chart of _something else_ side-by-side?

"def" is too generic.

"fn" is too cryptic.

"function" is better than the two.

In 2016-17, I was involved with a rather large mictoservice-heavy rewrite project tha didn't go particularly well. The main reason was that microservices were actually a good fit for the _planned_ organisational structure, but not for the one that was eventually put in place. When you go from 4 vertically integrated independent teams to 2 backend devs, 2 frontend devs, and 1 "devops" without stopping 5 minutes to rethink the architecture, of course shit will happen.

FWIW, sub-5kb banners were probably the only Flash projects that didn't include GSAP before we collectively jumped ships to JavaScript and CSS for animation on the web. It was everywhere.

I --still-- don't care about cookies so I use https://chromewebstore.google.com/detail/i-still-dont-care-a....

> The general consensus among web developers seems to be to just let a third party do it.

Outside of personal projects, third-party auth providers must be audited (think GDPR or PIPL), budget must be allowed, contracts signed, etc. so web developers rarely, if ever, have their say on the matter. The decision is taken long before anyone wrote a single line of code. From a project management perspective, it's an easy trade-off to make: one sprint for integrating Okta versus who knows how many for badly implementing something that requires a level of expertise that no one on the team has reached.

For personal projects, the trade-off is a bit different. Resources are scarce so, even if implementing auth is actually not very complicated(1) and can even be quite fun, there are probably more immediately interesting things to do. So you integrate a third-party solution in a wednesday night and you move on.

[1] https://thecopenhagenbook.com/

Do fewer meetings. Hire a stenotypist.

You said it yourself:

> bikeshed

> Wouldn't it be nice to be able to have a standard place where people could share database designs and build up a collection of well designed, well tested database designs?

That doesn't sound like GitHub at all.

> Convoluted and unreasonable workarounds for a growing police state.

Well, those are _basic_ OPSEC for people whose life/safety/freedom would actually be threatened by a search ("good guys", "bad guys", it doesn't matter). If the only things threatened by a search are your pride/moral principles, then yeah, those might seem unreasonable.

> Please don't try to minimize the egregiousness of having your personal documents searched for the sake of security theater.

I don't know if that term has been coined before, but "privacy theater" is also a thing, and it is just as grotesque as the other theater.

Like before we surrendered ourselves to "gadgets": simply by not bringing anything that could be a liability.

Random and targeted checks have always existed at borders. They would go through your stuff and move on to the next target if they didn't find anything suspicious. If you had folders, envelopes, etc. in your trunk or luggage, then they would go through them as well so, if you didn't want them to go through your most sensitive stuff, then you didn't bring that stuff with you. It's as simple as that.

But "privacy minded" people had it easy, back then, because they didn't travel with 20 years of correspondance or porn search history in their luggage.

Just leave your gadgets at home if you are worried about what could be found on them.

- If you really need to bring _your_ laptop, then image it anew before leaving.

- If it is a work laptop, then let your employer's IT department deal with the issue. You don't have personal stuff on it, do you?

- If you only need _a_ laptop, then buy the cheapest you can find upon arrival.

- Get a cheap SIM card and a disposable phone upon your arrival.

https://github.com/scrod/nv/tags works, here.