Pinned toot

I want to be able to tell my friends why is better than the birdsite, so I wrote a thing: "Mastodon Is Better than Twitter: Elevator Pitch"

I want this to be as persuasive as possible to outsiders, so I'd appreciate as much feedback as possible from Mastodon users

This is the sort of programming ethos to which I aspire:

> I was watching TV, and there was a commercial which proclaimed, "It's time to do what you want!" I replied to the TV, "It's time to write a JSON parser in 6502 assembly language?" Somehow I don't think that's what they had in mind, but the TV is right, I should do what I want.
> So, here is my JSON parser.

This may seem strange, but I'm wondering if anyone in the fediverse has any experience running Veracrypt containers on 3.5 inch floppy disks? If so, what was your experience?

@codesections Did you know that C compilers are still only required to support up to 4095 characters on a line of source code? If you have a line of code in your C program that's longer than that, the standard doesn't guarantee it has to be compiled correctly :)

TIL: many compilers allowed identifiers of any length, but only examined the first 8 characters to determine what the identifier pointed at.

So `foobarbaz` and `foobarbazqux` are both valid, but refer to the **same** variable!

What I _didn't_ learn was why anyone thought this was a good idea. I assume it was for performance reasons, since Free Pascal doesn't do it anymore ( and 8 makes me guess it has something to do with memory representation.

Anyone know?

Anyone have recommendations for writing Python in Neovim? Plug-ins, etc. Is Python-mode the go-to plug-in? Is PEp8 good to use?

I *really* like the Redis protocol, RESP. I don't even use Redis itself all that often, but I've implemented RESP (or subsets of it) multiple times – it's just a great format for programmatic communication

(err, ^^^ was intended to be a reply to @IanTester. Not sure how I messed that up)

Show thread

> Hmmm, it's never good when a new kernel is released just two days after the previous one.

What, you'd prefer that they *not* release a fix? :D

(Obligatory xkcd: )

Data is gone. Couldn't fix the issue.

Lost like 20%, but my backups covered the most part.

Reminder that backups are important!

I missed this post when it came out in December: In Defense of Blub Studies,

Some really excellent points:

> Blub studies is a never-ending treadmill of engineering know-how. It’s the fiddly technical details of how Git stores data, or how Postgres locking semantics [work], or why pip install failed this time.…Blub studies is more generalizable than it seems, and has its own way of compounding over time, too. That makes it a lot more useful than you’d expect

living room thermometer does the job in the fridge too, but is not happy about it

TIL: was released in 1990, barely a year after .

(I would have sworn that Zsh was at least a decade younger. But I would have been _confidently_ wrong, which is the absolute worst kind of wrong to be!)


No, , when I said "irclog", I certainly did _not_ mean "IRS login". You're getting to be as bad as Clippy ever was.

I regret my !g

I just observed the following exchange in a bug tracker:

user: *reports bug*
a maintainer: AFAIK, this is a known issue

something about that strikes me as ... circular? ...tautological? I'm not quite sure. Maybe it's that is raises the possibility of something being an unknown known issue?

Dear #Mastomind: Any guidelines on E-Ink / B&W/grayscale / low-refresh rate app design / UI/UX?

I've recently come into possession of an e-ink book reader, and am discovering the joys (seriously) and limitations (dittos) of e-ink displays and software designed for them.

I've just begun looking for any information concerning design guidance for e-ink devices, and am coming up very short. If you're aware of any such resources please respond to thread.

Boosts welcomed.

#eink #uiux #AppDesign #SoftwareDesign #Interfaces #BlackAndWhite #LowRefresh

I’ve got a riddle for you. What’s the best way to move 1PB if data from one state to another over a 1gbps MPLS link? I was thinking ZFS send with compression and deduplication, but really I just need anything that reduce the bits on wire as much as possible. Any ideas?

Are there any programming languages/runtimes/frameworks with a "garbage collection" strategy of just never collecting any garbage? (During program execution; obviously the memory would be freed when the process exited)

It wouldn't work for _most_ use cases, but for extremely short lived programs (e.g. CLI scripts) it seems like this would be an easy way to avoid the stop-the-world costs of a GC without any memory safety risks.

Does this exist? Or am I missing some reason it'd be dumb?

Show older

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.