Deebster

I like the take that they have in that thread: Perforce is forking Puppet into a non-Open Source version (but they’re keeping the name).

I assume Peta just wants to be in the news? The Sly Old Fox is not an offensive name.

That’s the first argument they make in their petition.

While I don’t disagree, this article is pretty bad and unconvincing. Is it a draft or something dashed out to collect referral fees?

I think there’s a lot of people who would be happy with a Chromebook in computer form, and those are also the market for Linux.

Bad wording on my part, I wasn’t disagreeing. My file server has a /files directory because it saves me a few key strokes and because I can.

Is Gobo case-insensitive by default? Typing those seems annoying.

That’s an old image, though - Windows has a C:\Users\youruser setup like /home/youruser for a while now.

I find the %APPDATA% thing way less convenient than ~/.config and I’m quite happy when programs have the “bug” that they still use ~/.config on Windows.

I like that idea of using the different fonts for e.g. Copilot suggestions - reminds me of reading Asterix comics as a kid when they’d use gothic black for the Goth’s speech, etc.

edit: e.g.

There’s kroki as well, which includes Mermaid, Excalidraw, GraphViz, PlantUML, etc.

Probably not; I’d expect the places where you need something like UUIDv7 (large, eventually-consistent systems) to not be entirely suitable because you can have records added out of sequence. You’d have to add a received-at field - but in that case you may as well just use a standard incrementing ID as your primary key.

In time-based pagination, the suggested fix to lots of data in a selected timespan is:

simply adding a limit to the amount of records returned (potentially via a query parameter) transparently solves it.

This means clients can’t see all the results, unless you add a way to view other pages of data, which is just pagination again. Or is the intended design that clients view either the first x results (the default) or view all results?

The problem with articles like OPs and others is that they don’t allow custom sorting, which is often a requirement, e.g. interfaces that present the data in a table, where column headers can be clicked to sort.

Yup, I think a lot of people just use their web browser for everything, and they can definitely just switch. Outside of work, how many non-techies have set up their email to use a native program? Very few, in my experience.

I think documents are sometimes the exception, since there’s a sizable (perhaps older) group that like to use Word for everything.

I felt the same when reading that book, and I never finished it because following the rules he suggested produced horrible code.

If memory serves, he also suggested that the ideal if statement only had one line inside, and you should move multiple lines into a function to achieve this.

I once had to work on a codebase that seemed like it had followed his style, and it was an awful experience. There were hundreds of tiny functions (most only used once) and even with an IDE it was a chore to follow the logic. Best case the compiler removed most of this “clean” code and the runtime wasn’t spending most of its time managing the stack like a developer had to do.

Oh, that’s LAN - I thought you’d put ian and I was trying to get the joke. Stupid sans-serif fonts.

I know of it because Helix uses it, and it works really well.

If you need to refer to a key with ~ or / in its name, you must escape the characters with ~0 and ~1 respectively. For example, to get “baz” from { “foo/bar~”: “baz” } you’d use the pointer /foo_1bar0.

I guess they’re using ~ for escaping since backslash is already escaping text content, not that you’d see it very often in keys.

Having magic values instead of using ~~ and ~/ feels ugly.

I’d agree, for the same reasons. Communicating intent is definitely one of the main things that separates mediocre from amazing developers (and software can’t check that).

It’s interesting to consider a tool that does all of levels 1-3 (and more) as a way to verify that a style refactoring hasn’t changed logic. I assume that’s what they meant when they wrote “modifications that were supposed to be no-ops but aren’t”.

Thunderbird on desktop, although I don’t love it.

FairEmail on Android.

A great read, thanks for sharing.