dragonne

If you consider this article lengthy you should read a few books to recalibrate your attention span.

FYI this site isn't paywalled, it just has an obnoxious popup.

I wouldn't call it over-engineered, but it certainly is an operational disaster. It's slow, memory hungry, and full of catastrophic bugs.

We are currently replacing it with PostgreSQL to improve performance and scalability.

> There's no reason you couldn't represent RFC5322 data with RDF as JSONLD. There's now a way to do streaming JSON-LD.

Is there a reason you'd want to? I clicked all your links but I still have no idea what Solid is.

I've endured Datomic for 4 years and I really wonder what the folks who enjoy it are doing, because for me it us utter misery.

- It's miserably slow (if you wish to contradict this statement, please provide numbers) - Consumes gobs of memory (export our data to JSON and it's orders of magnitude smaller) - Full text search will consume all your CPU cores for if you given it a short query (seriously, don't touch this feature, it is a basket full of footguns) - Resource leaks (the Cassandra backend used to leak full databases!)

I've been up to 3:00 a.m. dealing with bugs in Datomic. What use cases does it actually work for?

I've heard that this is also why American baguettes are so brutally hard (even when fresh). They're supposed to be closer to crispy, not a dental hazard.

Ah, I see what you meant. Thanks for clarifying!

I think most of your advice is solid, but I take issue with one point:

> - If your font colour is more thant #333 on white, you're being cruel, especially to those who suffer astigmatism.

A designer should think hard before reducing contrast. You may be improving the experience for one group at the expense of others:

- A low contrast page is difficult to read on a cell phone in daylight.

- A low contrast page is difficult to read at night on a dimmed display.

I don't meant to discount folks for whom high contrast is a problem, but don't they have a simple recourse? Reduce the brightness or contrast of the display. Most monitors and laptops have controls that allow this.

I guess I have no plans to buy another Nvidia card, then. Their current X11 drivers tear like crazy, and I have hope that Wayland will fix that.

This, a thousand times this.

Failing that, though, at least change the default rsyslog configuration such that:

* Timestamps are not ambiguous (the default includes no timezone offset)

* Timestamps are higher resolution (milliseconds at least, but preferably microseconds)

* The syslog severity/priority is not discarded (tools which display these files must use disgusting heuristics like searching for "err" to highlight errors)

* Rate limiting is disabled, as rsyslog sees all messages as coming from journald. This means that a misbehaving (chatty) application can cause critical messages from other apps to be dropped. journald does its own (per-source) rate limiting anyway.

* /var/log/syslog is rotated by size as well as time, so a misbehaving program can't easily fill up the partition which contains that file by accident. The current default is 1/day rotation, with no size limit.

I have a Z5 Compact as well. Nice little phone, and quite fast. However, I don't think that many developers test their apps on a sub-5" screen, because I've encountered issues with several apps where controls overlap. For example, in VLC's file list the context menu button overlaps with the invisible scroll bar track. It is easy to scroll accidentally. Amazon Music has exactly the same problem, too.

The Android ecosystem is difficult to recommend, and a small Android phone is even more difficult to recommend.