Show newer

> 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: m.xkcd.com/463/ )

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, benkuhn.net/blub

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!)

citations:
zsh: en.wikipedia.org/wiki/Z_shell
bash: en.wikipedia.org/wiki/Bash_%28

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?

Re: Your Privacy 

We care about your privacy.

Your privacy is delicious to us.

Your privacy is juicy-sweet and crunchy and wine-dark red and breathes a rich, savage musk-like scent, heavy on iron and with notes of truffle and mushroom and old, buried bones in the forest floor.

Your privacy dribbles gently down our lips as we chew, and after long, fragrant, eternities, swallow. Gulping, wolfing it down.

We would do ANYTHING to keep you handing us your precious, precious privacy.

Please click.

Oh no, the program correctness verifier has SIGSEGVed and crashed. "You've become the very thing you swore to destroy"...

Show thread

After some thought, I've decided I can call myself a "software developer". I'd previously been disqualifying myself, but I've made some small pip-installable packages and contributed to a handful of projects... so might as well stop gatekeeping myself

Discussions on which programming language is the best compares to discussing whether a hammer or a screwdriver is the better tool.

HOWTO:

$ mkdir -p ~/src/myproject
$ cd ~/src/myproject
$ git init --bare
$ cd ~
$ git clone ~/src/myproject
$ cd myproject

There, done. Now you have a 100% fully functional git repo that doesn’t require a network connection and supports every single git feature. Pull it, push it, branch it, revert it, whatever: it’s your own repo and you can do whatever you want with it. And you don’t have to sign up for anything or agree to a Terms of Service or share your work or trust a company you dislike.

Show thread

Stats from my last open source contribution:

lines added: 79
lined deleted: 82
lines in commit msg: 870

I can't decide if I'm doing software development really _wrong_, or really _right_.

Show older
Fosstodon

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