UT1 is a disaster for many purposes. It is, quite simply, a measure of the Earth's current angle in space. This is ideal for pointing an Earth-based telescope. Trouble is, we can't reliably predict how fast this will tick. You may think leap seconds are bad, but how about if you simply can't know the current time without having a current measurement of the position of quasars in the sky? The length of a second isn't even constant.
TAI matches up with the atomic second, and UTC is that plus enough leap seconds to approximate UT1.
It all sucks, but this is reality. You can't fix reality. You'd have to tell the Earth to obey an atomic clock.
> It all sucks, but this is reality. You can't fix reality. You'd have to tell the Earth to obey an atomic clock.
The question might be super naive, but I wonder how useful/workable a time-system would be that's completely decoupled from celestial body movements? Isn't Swatch Internet Time something like that?
Gonna be really interesting once humanity becomes interplanetary or even interstellar. Will we have whole different calendars and time zones for different planets and solar systems?
You'd imagine an internet time (or civilisation time) used for timekeeping in interplanetary protocols, synced (relatively) well to Earth- or wherever the centre of human Civilisation ends up being. Because clock speed changes due to relativity, your Civilisation Time counter would have to take into account your position and velocity relative to earth to not slip- while syncing often enough to counteract
This way you can have relatively stable time measurement, even when time strictly speaking passes faster for some computers than others.
Time slows down as you go faster. The people leaving earth are the ones accelerating, so they're the ones who travel faster into the future- less time passes for them. If we colonise stars around us, the people going to the further stars (assume all ships leave from earth) will lose more time: Civilisation Time will be ahead of the time they measure on their regular clocks.
Maybe we could use pulsars as clocks? I think they pulse pretty regularly.
I think you've wrapped your head the wrong way around this. The stupidest thing ever is the idea that a country's government can be shut down as an extortion method. It's a concept so alien to me that I cannot fathom the logic of the person who came up with the idea.
Nobody "came up with" the idea. It's the consequence of a principle of the American Constitution, wherein only Congress can appropriate money. This is a bedrock principle, because it provides a check on the Executive: The President can yell all he wants, but unless Congress appropriates money to pay for whatever it is he is yelling about (in this case, a border wall), he doesn't get it.
For observers outside the US, the idea of "the national government shutting down" probably seems way way more alarming that it does to most Americans. Almost all basic services in the US are handled by states and municipalities. This includes garbage collection, policing, firefighters, schools, local tax collection, road maintenance, the majority of prisons, most courts, most water and power infrastructure, building inspections and permitting, and many more.
Even airports, the site of a lot of hand-wringing during the shutdown due to the TSA (security screeners) and air-traffic controllers being federal employees, are usually (always?) municipally or state-owned. I have no idea of the legality of these municipalities or the airlines themselves stepping in to pay the ATCs or screeners, but it doesn't seem totally bonkers.
The Swedish tradition is that you cannot vote to stop a budget, you can only vote for another proposal. That is, if there is only one proposal, you only allow 'yes' or 'abstain' votes, and if there are several, you do a series of votes to eliminate the lesser proposals until only one stands, and then only allow 'yes' or 'abstain' again.
I hope that explains why I find it so strange.
Another peculiarity we use to avoid stand-offs (it has always worked up until last election) is negative parliamentarism, where the prime minister is tolerated, not elected by the parliament. What it means is that a majority of MPs have to vote "no" to not elect a prime minister, which means that a lot of parties vote "abstain" (we had such a vote yesterday where the PM was tolerated with the numbers yes: 115, no: 153, abstain: 77, absent:4). This has historically meant that minority governments have been able to flourish.
So is the current problem is because the president can veto congresses appropriations? In a functioning government this seems sensible so the executive has a symmetric check on congress, but currently it gives the president unwarranted leverage.
Congress can override a Presidential veto, but it requires a 2/3 majority, which neither party has by itself (due to parliamentary rules, it's slightly more complicated than that in ways that I don't totally understand, but that's the high-school-civics-version). The President isn't actually necessary to reopen the government: Congressional Democrats and Republicans could come to a deal that got them to the 2/3 mark if they wanted to, even over the President's objections. Whether or not that will happen in this cases is anyone's guess.
1) it's not a true shutdown because the military still get paid. There is a builtin rightwing fudge of what gets deemed "essential".
2) Most governments have a similar possibility of not being able to pass a budget; but, in the Westminster system, this forces fresh elections. The people get to decide on what compromise is necessary to resume business.
3) Businesses should not make their employees into creditors. Failing to make payroll is usually a sign that a business is either unethical or nearly bankrupt. This screws over people badly, e.g. https://twitter.com/shawndgoldman/status/1085733207469891585
"The NASA Postdoctoral Program contract runs out of money tomorrow. This means its fellows - some of the best and brightest space scientists in the world - will go without pay starting Friday. These folks are contractors, which means they aren't covered by the backpay bill."
(There was also some suggestion that not being paid would automatically terminate their J-1 visas, but I can't find that now)
>1) it's not a true shutdown because the military still get paid. There is a builtin rightwing fudge of what gets deemed "essential".
The military still gets paid because congress was able to agree to pay for that. It's certainly possible, for congress to be unable to agree to a DoD budget. Separating the budget process into a series of sub-budgets allows for continuity in areas where there's room for consensus.
> 2) Most governments have a similar possibility of not being able to pass a budget; but, in the Westminster system, this forces fresh elections. The people get to decide on what compromise is necessary to resume business.
Presumably, the government is shutdown until the votes are certified? And how long do the newly elected representatives have to form a budget, before a second election would be triggered? Regardless, for better or worse, the US system does not allow for snap elections, and that would be a big change, especially given the design of different term lengths for different offices.
> 3) Businesses should not make their employees into creditors.
Yes, this is pretty awful. I would be raising some hell if my employer expected me to work without paying me contemporaneously.
>Presumably, the government is shutdown until the votes are certified?
This can be solved by setting the budget deadline some time before the expiration of the past budget.
You have until July 1 to pass a budget for 2020; if there isn't one, we hold elections in August for your replacement, giving them several months to pull together something workable.
Presumably, the government is shutdown until the votes are certified?
No. I'm not an expert in the details, but there are rules about how government services continue to operate during the period that Parliament is dissolved. The key principle, however, is that it continues to operate.
Most of the military is still being paid because the DoD isn’t one of the unfounded agencies. The coast guard, however, is currently working without pay, because they’re part of commerce.
We could easily define a time system that is simply "number of seconds since 00:00:00 January 1, 1970" (other than epoch being different, we have this with GPS and TAI time, but the network effects for UTC are strong) and used that as our base time system. Leap seconds could then be added at higher layers simmilar to how leap hours are. Instead evryone has to deal with leap seconds weather they care about the orientation of Earth or not.
Also, at least for computer applications, a variable lenfth second is easier to deal with than a leap second.
That brings up an interesting question: Is that the current, best, or only basis for time?
I'd argue that many relevant time concepts are more framed by social conventions than the sun.
Most of us are more interested in concepts like "when does work start", "lunch time", and "when the store closes", than "when does sunrise occur" these days. In a pre-industrial society, those might be closely synched, but less so today.
Those are important events in the day, but they don't serve as a basis for defining time.
When does work start? Well, it starts when the hands on the clock points just so, there really isn't any more fundamental definition. But clocks are tools for measuring time, they don't define it.
If your clock slows nothing particular happens to other clocks, and time marches on unslowed. But sunset will bring night whether you notice it or not, and that's a pretty definite marker of the passage of time.
Time is a well defined physical property that has nothing to do with the posistion of the sun.
We already have time localizations, time zones, daylight savings time, and leap days all handled by layers above UTC (actually, all in the timezone layer). Leap seconds should be part of that layer, not the UTC layer.
Once we get into relativistic effects, there is more complication to the lower layers, but we (mostly) don't need to deal with that.
Just like the amount of mass in a gram doesn't change based on location, time, or any other variable it's very important to have some measurement of time that is as constant and precise as possible. This helps us conduct science, where many types of experiments take place in less than a second. The measurements taken today should be readable decades or centuries from now without having to adjust for the slowing of Earth's rotation.
Now, maybe this unit of time needed for scientific purposes doesn't need to be the same one used for daily life.
> maybe this unit of time needed for scientific purposes doesn't need to be the same one used for daily life.
Don't think the unit is the problem, it's the offset. And when it comes to that, we already have a virtualization layer which assures alignment with the sun for social purposes: time zones. No need to add another one over TAI.
Except that’s not entirely the story of time zones. They’re political divisions. Some of them match up with the sun better than others. For instance, the sunset time gets pretty weird in LV over the winter.
Which I think is perfectly fine (if not necessary) for that layer. The human body doesn't care for extra seconds, and science doesn't either. So who do we do the "coordination" in UTC for? If - over hundreds of years - the time zone drifts off into weirdness, it can be changed politically. What more do you need?
Oh. In UT1 there number of seconds in a day is constant, so it's value is defined by the rotation of the earth which is slowing. UTC is better than UT1 in that regard. Maybe UT1 is fine for humans, but really humans just assume ut1.
UTC adds little of value on top of TAI, except some headache for clock synchronization. So I argue for basing timezones directly on TAI, as I see TAI as the least impractical reference.
I beg to differ, Dst is the stupidest time related thing ever. From a software development perspective it is a tremendous pain in the ass and is stupid. From the non software aspect it is just stupid and annoying.
Leap seconds are a lot worse for software development, because Unix time does not include DST adjustments, but does include leap second adjustments. This means that if you use unix time in an application, you can just use a library at the input/output edge and not worry about it, but leap seconds can screw up anywhere that you use a timestamp.
TAI matches up with the atomic second, and UTC is that plus enough leap seconds to approximate UT1.
It all sucks, but this is reality. You can't fix reality. You'd have to tell the Earth to obey an atomic clock.