The point is that quantizing the range makes it easier for humans to choose colors. But there's already the #ABC hex format, which while less intuitive to non-techies has the huge advantage of being well-established.
But it doesn't make it easier for humans to choose colors. For a specific list of detent colors, it reduces the amount you have to memorize relative to full RGB. But to actually reason about colors, you want a non-arbitrary scale; HSV (for instance) gives you hue direction and then you can slide saturation and brightness around.
I don’t know, but I use #ABC a lot, it’s much more convenient than #ABCDEF, never mind [0, 256) or [0, 1]. There are of course more intuitive coordinate schemes and color models, but I find RGB easy enough when you’re not actually doing serious graphic design. This is not about having a GUI color picker either, this is about hand-typing colors.
Maybe it’s just because I’m old and wrote CSS way before it got HSL or other fancy color functions, but personally, RGB colors are really deeply entrenched in my brain.
I think my thing here is, you can do any notation for colors you want. "Splash" is custom. So you might as well do a better custom. "rrb85" for "red, red, blue, 80% sat, 50% value" for a dark purple --- one step towards red from the midpoint between red and blue. I don't know, something! RGB is kind of bad!
Despite my background in color science, I find RGB more intuitive. With HSV I have to remember the chirality of hue and it's zero point, and when changing hue I find it difficult to reason about saturation. In practice this means I must "nudge and judge" with both systems. With RGB I can always make progress. With HSV I guess hue wrong about half the time. I could probably improve this.
To be fair, I'm also colorblind. That's probably relevant.
Anyway, I'd say the answer to both your questions is: "sometimes"
All you're arguing is that it's easier to memorize primary and simple secondary colors in RGB. No question, it is. Once you've got one of those detent colors locked in, how do you vary it? What does it mean to bring up i% of the first channel, j% of the second, and k% of the third? That's the problem HSV solves.
"Commercial Use" is only one part of the four prongs of the fair use test. For example, commercial Parody is generally considered Fair Use. Look at Space Balls, which is a direct transformation from Star Wars.
This is all new territory. We don't have court-settled law yet.
I'll pursue this when "they" decide to get real and make this not suck. Until then, I have sufficient alternatives.
I appreciate the writeup. It convinces me that integrated KVM stuff ~~ except for fewer wires ~~ isn't much better than the mess that's prevailed for years now, and I'm not missing much.
Why does video input source switching suck so much?
Back in the old analog CRT days I could forgive the switching latency. With today's all-digital signal paths I feel like video input switching should be pretty close to instant.
Is the technology in a broadcast switcher really so exotic and expensive?
> Is the technology in a broadcast switcher really so exotic and expensive?
No. My characterization of the problem was precision flippancy; the demand for this is niche enough that optimizing for it is a low priority, so "they" simply don't. That failure is stack-wide; the specifications around display negotiation would need extension to manage the additional state necessary for the "agile" KVM use case, and then the hardware+firmware would need to exist and become cheap, somehow despite Imaginary Property laws, so that one could hope to find it in real products.
There is regulatory friction here as well: it would complicate power management. Not infeasibly so, but enough that unless a need appears of such import that it motivates people to dare to disturb that writhing ball of copulating tapeworms, it simply won't happen.
So don't hold your breath. Unless you're relatively young, you won't live to see it. More likely, some other paradigm will obviate the problem first.
I also have a $900 monitor (provided from work) which is also a built in kvm switch, and it can show two desktops, one HDMI/windows and one usb-c/mac, side by side or as an inset as well. There's no delay switching either.
It is supposed to hot-switch the inputs if I move the mouse to the edge, but it does not, I guess it's because one of them is HDMI.
I used to have a Lenovo dock that I used as a switch, but not anymore and there's definitely less clutter.
Yeah, I read the whole article looking for any meat in there and there is none. I played with different setups as I, too, use both macos and linux. I remember doing a two screen setup where if you move the mouse to the edge of the linux screen, it appears on the macos one.
A two screen setup is not a one screen setup. I have a two screen mouse-edge setup and I was still interested to learn about being able to use a keyboard shortcut to control a monitor with a built-in KVM to switch between two computers on the same screen. That is, in fact, new to me.
Paper ballots are a must. Vote on a touchscreen, then have the terminal print out a voter-verifiable paper ballot that can also be machine counted.
Make the ballot printout layout a standard format. Then machines from multiple vendors can verify the counts on a subset of the ballots. And as a last resort, the ballots can be hand counted as well.
This is an eVoting system - not at a ballot box. There is no printer. And even if there was, a similar problem can occur if you lose the keys. And you need keys because the printout cannot be voter verifiable, or you enable the various forms of vote fraud that anonymous ballot boxes were introduced to stop.
Leap Seconds need to be abolished. The only people who need it are Astronomers. They could just use an offset. Implementing leap seconds correctly is a huge burden, for no gain.
Where I live, high noon today occurs at 1:03 PM. No one is complaining that it is 3 minutes (or 63 minutes) off. It's a non-issue for 99.9% of the population.
Hmm. I understand that perspective, but I'm not sure I agree. It does seem to matter over a relatively short & realistic time scale. According to the Wikipedia page, there have been 27 seconds added since 1972, which is only 44 years ago. At that rate, that's about 1 minute per 100 years. We have many systems that have existed for several centuries and I think it's not unreasonable to start making plans for systems that may exist for millennia, where you're starting to talk about a 10+ minute offset at the current rate.
But I do think there is a valid argument that the infrequency of these events cause more issues than maybe one large adjustment 500 years from now would cause. Not sure where I land on this one.
I ran into this trying to view the meridian line at the Basilica of Saint Mary of the Angels in Rome.
I was told the sun would show up on the calendar in the floor at noon. As noon approached, I saw nothing. Then I figured it probably needed to be solar noon, so had to look that up and wait around until that time. Today, that will be 12:20pm.
Nothing would have broken had I missed this, and nothing of critical importance is running on a solar clock (I don’t think), but it still led to a discrepancy in what was expected and where I needed to be when, based on drift from solar noon.
The problem is that Earth's rotation isn't consistently faster. Some years leap seconds need to be added, some years they need to be removed. Would be far better to leave them alone, let them average out, and as the GP said let the people who care about this add the offset they need.
> Some years leap seconds need to be added, some years they need to be removed.
Is that true? Per Wikipedia:
> Since [1972], 27 leap seconds have been added to UTC, with the most recent occurring on December 31, 2016. All have so far been positive leap seconds, adding a second to a UTC day; while a negative leap second is theoretically possible, it has not yet occurred.
Either way, it's due in part to Earth's rotation slowing down, so the average drift would still be non-zero.
We've not had to apply negative leap seconds yet since leap seconds were introduced in 1972, but that wasn't the point.
The time period of the Earth fluctuates a lot [0] and actually in 2020 it was less than 24 hours, but not a large enough change to warrant a negative leap second. If you go back to the 1940s, we would had needed negative leap seconds if we had leap seconds at all then, and going back 150 years we would have needed multiple negative leap seconds every year for several consecutive years.
What we can say is that on average, it is close enough to 24 hours and the average over hundreds of years is even closer to 24 hours that it's not worth adding these extra seconds as you'd then need to remove them again later on.
You make a good argument for the opposite of your conclusion. If you’re planning a system that’s supposed to last for millennia, that system shouldn’t depend on the fiat of the International Earth Rotation and Reference Systems Service.
Let's just do leap minutes. If humanity survives long enough to witness a leap minute without destroying ourselves then that's ample compensation for the minor inconvenience.
Astronomers do not need leap seconds, because even with this adjustment UTC cannot be used to determine anything in astronomy.
Astronomers need either true time, which is TAI, to be used in computing the positions of celestial bodies, and they need for observations the so-called Sidereal Time, which is not a time but the angle between a coordinate system attached to the Earth and an inertial system of coordinates attached to distant celestial objects that have negligible angular movement (in the past those were distant stars, now they are distant galaxies or quasars).
The Sidereal Time can be computed in a complex way from TAI, because it is determined by the periodic rotation and precession of the Earth and by various superposed periodic or random movements.
The UTC is not adjusted to match the current true rotation angle of the Earth, which you can measure by looking up to the stars, but it is adjusted to match within 1 second a fictitious angle that would be the rotation angle of the Earth-Sun direction corresponding to an Earth that would rotate uniformly both around itself and around the Sun, so that the duration of a day would have been constant.
In reality, the duration of a Solar day, i.e. the time between 2 consecutive noons, varies a lot during the year, by a large fraction of an hour (by about a half of hour peak-to-peak), so using UTC directly for estimating the position of the Sun gives a very big error, of many minutes of hour.
So what you need for astronomy is to know the current TAI and you need a Sidereal Time calculator, which you need for knowing in what direction to point your telescope, to find a given celestial object.
UTC cannot be used directly in astronomy, but only after passing either explicitly or implicitly through TAI. The fact that astronomical almanacs are published using UTC in their tables is obfuscating this, because the values in the tables have not been computed using UTC, but everything has been converted to UTC to match the time that is presumably shown by the watch or clock that the almanac user may have.
Unless you want to abolish timezones entirely, which would simplify clocks but complicate a whole lot else in society, you're going to need leap-something. Would leap minutes or hours really be much better? The idea that doing things less often causes more problems is a reasonable one.
In the 56 years since UTC was established, there have only been 37 leap seconds. At that rate it would take more than 5400 years before it would affect solar noon more than DST does. I'm more than okay kicking the can that far down the road in the name of avoiding all the ridiculous solutions that are needed to accommodate leap seconds. We've endured these headaches to potentially solve a problem for people who might not even still be using UTC.
Compare that to removing the leap day, where the start of seasons would be noticeably affected within just a few decades. Hundreds of years ago, a pretty insignificant headache was invented which is providing constant payoffs.
We need to do "leap hours" anyway--just today they changed to daylight saving time in the U.S.! And time zones are also adjusted every now and then, which also amounts to a one-hour change in the affected regions. Even if we didn't have continous practice with leap seconds, I think we could definitely include an extra one-hour shift for earth rotation reasons along with all the other ones.
Before modern standardization, maintaining calendars and clocks was typically the responsibility of states or similar authorities, often guided by astronomers. Now it seems that international organizations are effectively following the early UNIX/POSIX model, and astronomers no longer have the same authority over timekeeping.
Which means that time changes slowly enough that we don't notice. At some point everybody goes work half an hour earlier because it makes sense. Schools start earlier, shops open earlier. It doesn't have to be coordinated worldwide. Every region or even town can have its own customs. Then people notice they are in the wrong time zone and a country moves to a different time zone.
Statistically, nobody on Earth knows what UTC is. People know about their local time zone and how it related to time zones in other countries. Where the position of the sun is relative to UTC, almost nobody knows.
Yet high noon at my current location comes at 12:03 (1:03 with DST). It's three minutes off. If I lived further west in my timezone, noon would come much
later.
How can people manage with noon off by minutes, yet want leap-second accuracy every 6 months?
reply