Announcing to everyone that you didn't bother reading the article because you don't have time, but then wasting your own time playing around with ChatGTP, then wasting everyone else's time by posting something everyone who actually did bother reading the article already knows, is hypocritical and disrespectful of everyone's time, and adds nothing to the conversation.
If you didn't bother reading the article, then simply don't post anything, especially not an announcement you didn't read the article.
To eliminate the need for domain-specific parser implementations on both server and client, make it easy to index and search this structured data, and to link things with URIs and URLs like other web applications that also make lots of copies.
Solid is a platform for decentralized linked data storage and retrieval with access controls, notifications, WebID + OAuth/OpenID. The Wikipedia link and spec documents have a more complete description that could be retrieved and stored locally.
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.
Baguettes are supposed to be made with high-protein wheat / bread flour. Proper Southern Biscuits are supposed to be made with low-protein flour.
I'm somewhat surprised: in my grocery store, there are "cake flour", "bread flour", and "all purpose flour" in the flour section. It only took a brief search to learn the difference (and which had higher or lower protein counts).
Further research (actually book: "On Cooking"), describes the uses of each flour. In effect: high-protein causes gluten formation, which is necessary for a proper "doughy" bread like Baguette, but is counter-productive for southern-style biscuits.
Possibly, but people are pretty aware of the flour difference. Even back in the 60s Julia Child mentioned it in her cookbook (Relevant TV episode: https://youtu.be/9iH3hjDUhWw)
I suspect the real difference is in the customers. I've heard people arguing over which bagels or donuts are superior, but I've never heard such a conversation for baguettes.
I suspect that's mostly due to par baking, since a lot, arguably most, of the grocery store baguettes are pre-made, par baked, and shipped frozen. They're then baked again in the store, which often leaves them soft and chewy or rock hard, depending on how they're baked a 2nd time around.
Lots of dough conditioners are also common, which helps make them soft. Often too soft, in fact, so they overcook them.
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.
Colour codes are hexadecimal numbers, 000000 is basically zero, and is for black. FFFFFF is 16777215 and is white. The more the numerical value of the colour the lighter it is, the lower the darker (well, not exactly, but kind of).
Right, but to be pedantic, the OP's original statement was ambiguous.
"more thant[sic] #333 on white"... You could interpret this many ways.
A) You could interpret "#333 on white" to refer to the contrast ratio of "#333/#fff", which according to this calculator [1] is 12.6. In this case "more" is referring to a higher contrast ratio. "#000 on #fff" would fit - even though "#000" is less than "#333" - because the contrast ratio of the two colors is 21.
B) You could interpret the statement as "(more than #333) on #fff", e.g. increasing the numerical value of "#333". Something like "#444 on #fff" - which actually has a lower contrast ratio of 9.7 - fits, because "#444" is more than "#333".
This is dumb, I'm just pointing out that it can be important to be precise with your language.
Expanding on this a little more, it's actually broken up into hexadecimal pairings (or 8-bit numbers).
00 00 00 = R(0) G(0) B(0) for Red, Green Blue
FF FF FF = R(255) G(255) G(255)
That makes 16,777,216 possible combinations (256^3).
For pure red, that's FF0000; green, #00FF00; blue, #0000FF. Mixing those is how you get intermediary colors: red + green = yellow; red + blue = magenta; green + blue = cyan.
When the colors are referenced as single-digit hex numbers, that value is applied for the pairing. This would make #F00 (red) actually be applied as #FF0000.
We actually agree, but I've phrased that one a bit bad. See my other comment downthread. I was going to edit to clarify, but it does not let me anymore. Comments become fixed way quicker these days ain't it?
> Their current X11 drivers tear like crazy, and I have hope that Wayland will fix that.
No they don't. I have had 3 different nVIdia configs, and presently 2 for gaming, and through my experience hopping from one distro to the next I find that the problem is actually unrelated to nVIdia drivers - but the compositor. For example, in Mint if you switch to compton, it makes all tearing disappear. This is well documented.
I tried to do that, unfortunately for the high end AMD is simply not competitive. If you want to game in 4K NVidia is the way to go (or at least it was 6 months ago when I bought my card).
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.
