The ds grazed genz too
It's for racing cyclists. There's nothing more aero than legs and face shaved with sports shaving cream.
My dude this post is the feature request. It's how summit operates.
Quark-Gluon plasma gramps
"You know when you struggle to get a sofa through a doorway?"
Barber: "say no more"
know that I
There are a lot of binary packages now, and explicit bin versions of big ones like firefox or the kernel. Without using those an update after some months may take half a day. With them, even a weak laptop only takes a few minutes.
Gentoo doesn't want to push you into some compiled utopia, it's offering you the option of customizing or taking control where needed.
You can have your system use binary packages but then set one packet to source, download the source, modify it, write a patch, and have a package with a completely custom sourcecode modification that you can easily keep updating as normal at the cost of it now taking longer due to compiling from source.
That chart is overcomplicated.
There are 3 independent markers. A, B, and +.
Blood can have A or not, B or not, and + or not. When the body doesn't have the marker, it will react to the marker.
So when you have notA, and get A blood, you will have a reaction.
notA blood works for everyone, A blood only for A people. A people can take any blood, notA people only notA blood.
Now do this independently for the 3 markers. AB+ people have all markers so can take any combination. notAnotBnot+ people make blood everyone can take, since there are no markers, but they can't take any other blood with any markers.
Unfortunately we call not+ -, notAnotB O, notAB B, and AnotB A. So + we invert properly but for A and B we omit them and instead of emptystring when no marker is present we invent O, presumably for 0 markers. This obfuscates the pattern.
It used to be that there was no option at all, on any distro. You'd have the broken proprietary drivers, or the open source reverse engineered one with half the performance and unreliability in specialty features.
Since then Nvidia has shifted focus to get their drivers working properly, and there were also changes making them more open source, tho I'm not sure that'd mean the "proprietary driver" will go full foss at some point.
If op is to be believed, the proprietsry driver is already a lot more stable, so it's now a software licensing issue not an unfixable technical issue.
3 years ago this was true. Not sure if nvidia works properly with wayland even now, though at least the trend is different now
I checked a few people and found nothing, So I'll take that as 1 guilty and everyone else innocent then.
Some years ago in a chain of discussion the more typical simple pyramid representation of date formats was improved to incorporate every (big and) little detail of the various formats accurately.
The annotated regions of usage are debated however.
The first insight is that numbers themselves are ordered most to least significant, that's why every numeric element is sloped top to bottom. This shows why dd.mm.yyyy is not well-ordered, even ignoring the time component.
Then, am/pm is actually its own segment of the time notation when it is used, and as the biggest is misplaced when put after time.
Put between date and time it is still inefficient, but at least placed in order (and is alphabetically sorted).
Another neat detail is the quirk of 12h time to call the first hour 12 instead of 00. This is represented by the lowest section of the hour bar spiking to be the widest.
One remaining inaccuracy is that the width of the bars does not match their encoded amount of information. It would be sensible to have the day be 5x wider than am/pm, and the (4 digit) years 2.6x as wide as the days, but alas that would be too impractical for such a well-designed infographic.
I inverted the original because I prefer darkmode. Here is the original
Some years ago in a chain of discussion the more typical simple pyramid representation of date formats was improved to incorporate every (big and) little detail of the various formats accurately.
The annotated regions of usage are debated however.
The first insight is that numbers themselves are ordered most to least significant, that's why every numeric element is sloped top to bottom. This shows why dd.mm.yyyy is not well-ordered, even ignoring the time component.
Then, am/pm is actually its own segment of the time notation when it is used, and as the biggest is misplaced when put after time.
Put between date and time it is still inefficient, but at least placed in order (and is alphabetically sorted).
Another neat detail is the quirk of 12h time to call the first hour 12 instead of 00. This is represented by the lowest section of the hour bar spiking to be the widest.
One remaining inaccuracy is that the width of the bars does not match their encoded amount of information. It would be sensible to have the day be 5x wider than am/pm, and the (4 digit) years 2.6x as wide as the days, but alas that would be too impractical for such a well-designed infographic.
I inverted the original because I prefer darkmode. Here is the original
cross-posted from: https://lemmy.world/post/35218456
Ran across this broken link here. Summit shows links differently to the webui, and probably also other apps. I think matching webui behavior is best here.
There seems to be more complex regex at play, including checking for matching brackets etc.. Probably best to dig that out of the sourcecode.
Examples:
Summit: https://en.m.wikipedia.org/wiki/Orion_(spacecraft)
Raw: https://en.m.wikipedia.org/wiki/Orion_(spacecraft)
Webui: https://en.m.wikipedia.org/wiki/Orion_(spacecraft)
Summit: https://example.org/aa(aa
Raw: https://example.org/aa(aa
Webui: https://example.org/aa(aa
Summit: https://example.org/aa(aa)
Raw: https://example.org/aa(aa)
Webui: https://example.org/aa(aa)
Interestingly while writing this, I noticed the rules for android long press text select also match webui behavior.
Take this comment as an example: https://lemmy.dbzer0.com/comment/20455448
There are a few images with notable resolution (500×500) in that vote comment, that are shown at very small size. Whenever they come into view, the fps of the entire app drops notably for me, down to perhaps the tens. I've seen it go even lower on other votes with more emoji.
My phone is quite powerful, and browsers for example can display similar cases fluently even on much worse hardware.
view more: next ›
Visually you may not notice the difference, but the air flowing around you at 200m/s as you cycle up mnt Thor will.