Quite the opposite. The earth's rotation can vary by quite a few seconds each year. But over hundreds of years, the variations mostly cancel out, which is why I think trying to add or remove leap seconds are a bad idea. The only people who care about such things are space agencies, and they can apply whatever offset they want, it doesn't need to affect everyone else.
Arguably, the only real-world impact this drift has on normal people is GPS, but GPS already transmits an offset from its own clock so that receivers can correct for that. The GPS clock is different both from UTC and TIA.
To me, it's useful because it frames it in terms of social connections in the target country and because how it works with an adjective.
So, British expats in Spain and Chinese expats in Spain are likely to socialise in their specific group, but rarely if ever intersect. They are all immigrants in the target country (and especially when considered as a whole as everyone from "outside"), and they are all expats (but probably in defined cliques).
I'd say these clusters of people are living the "expat life", but equally there are many immigrants who don't particularly want to hang out with other expats, because they're not trying to recreate where they left in a new place, but are trying to assimilate to the new place. They themselves are still expats even if they don't socialise much with other expats, but wouldn't be living the expat life.
Yeah, I'd like some kind of reward for having done the previous words in 4s each. Just when I get to a hard one (for me) it can take a really long time to spot it.
Also, maybe having a button (and also a key press) to randomly rearrange the letters, or allow me to drag them around to try to figure it out... like I'd do with scrabble tiles on my rack.
And they are correct according to the meaning of the word. Expats simply means someone who resides outside of their native country.
I guess colloquially it probably implies moving somewhere as an adult, but the word itself doesn't carry that meaning (it's literally ex=outside + patris=homeland). But for instance, my sister has lived permanently in New Zealand for 25 years now (and a few years prior to her permanent move) and has no intention to ever leave, but would still be considered an expat. Her children were born in the UK, but they were 4 and 2 when they moved there, and I don't think they'd ever have considered themselves expats as they've never known anywhere but NZ. In fact the oldest is visiting the UK for a week this year, it'll be the second time he's been in the UK since moving to NZ aged 4.
What happened to the original files that you uploaded to Myspace?
Why wouldn't you have made any attempt to preserve any of copy of your data anyway? Even if you believed the files would stay online forever, it's surely always more convenient to use local files than re-download every time?
(but also sorry you lost your last physical copy of your memories, that kind of sucks and sorry if my comment comes across as quite insensitive)
Hehe, I used to create a folder as some variant of "Old" and move everything in my downloads folder into it once or twice a year, and with a lesser frequency my documents. At one point when I realised this had got about 10 levels deep, I switched to yyyy-mm format directories instead of nesting them.
I also used to back up other PCs to each other somewhat regularly, and sometimes I'd end up with those files back on the original PC in a backup of another. Fortunately, when I switched to borgbackup on Windows as well [1], this massive reduplication of files became a solved problem.
[1] borgbackup doesn't officially work on Windows, but I run it in WSL which does reasonably well for all the files I really care about (i.e. the stuff I've made). When they have particular unusual characters in the filenames, it throws up a warning for that file every time, but otherwise seems fine. I've never bothered investigating whether those particular files restore to the correct filename, because I know I've also backed up the zip file those files have come from and it's just accidental that I've backed up the extracted files as well.
Converting that ID to hex gives 18,000F,C8CB,93CC which rather looks like 32 bits of random data plus the prefix 0x18000f or possibly 40-48 bits of time in ms granularity from some epoch.
> Fable turned reMarkable into Tom Riddle's diary from Harry Potter
Was this posted by AI? The title is exactly backwards compared to the original on the repo "riddle — the diary of Tom Riddle, for the reMarkable Paper Pro"
Development costs are far from their lowest at end-of-cycle.
That's exactly when the prototype development kits come out of small scale testing (maybe tens of units, all incredibly expensive bespoke units, probably hand soldered and assembled), production ramped up a little and the evaluation kits are produced and distributed to first party studios and large third party studios, with thousands of consoles produced with the expectation that their lifespan is likely only going to be 3-6 months. These are then extensively tested by developers, both to see what needs to be done to get their launch titles actually working on the machine, but often very serious hardware bugs are found in this period that may require fixes to the chips themselves or software workarounds that affect performance. For some of the recent console launches there have been 2 or 3 rounds of evaluation kits in a year, and the previous evaluation kits are effectively bricked.
After the evaluation kits seem to have converged on a final product, the development kits are produced to ideally match the final version of the evaluation kits, but again these are tested before production is ramped up because some things do change (most trivially the case, even if the board is fine). At this point tens of thousands of dev kits are produced, each different enough to retail kits (more memory, maybe extra ports, etc), usually at least 6 months to a year before console launch so studios can make a final push on the launch day or first quarter titles, and in the background the same evaluation process for retail kits (usually just stripped down from the development kits, but usually different cases etc) starts, and eventually a final design for the retail product is produced that's good enough for manufacture.
This time is definitely not just when the console manufacturers kick back and rake in their profits, this is when they're already spending big on the final push to get to the point where they even have a new console to start a new cycle with.
Separate to the console manufacturing side, the years before release are when big money is spent getting studios on board to produce launch titles, because without those, the console will be dead on arrival.
TLDR: revenues at the end of the console cycle aren't funding the next generation, because it's probably already been in development since the launch of the current console, rather those end-of-cycle revenues are hopefully paying off the gamble they took funding development for the current generation.
Interesting. Do the longer ones have some provision for increasing in line with inflation? AFAIK the 99 year leases are usually for a fixed amount every year, which obviously shrinks in real terms over time, but given that you'd want to renew it every 10 years or so anyway, would probably be renegotiated to a fair market rate at that time.
Glad I saw this - I wasn't aware tourists were allowed to rent vehicles at all. I knew you needed a Chinese licence, but hadn't heard that there was now a tourist licence and as far as I knew you could only do the regular test if you had a working or family visa.
While the majority of flats are leasehold, by far the vast majority of property in England is freehold. Only a fifth is leasehold.
While technically a leasehold has a fixed term and at the end of the lease (usually starts at 99 years) the land owner technically owns the property, in reality this scares most people so usually when someone sells the property (usually while there's still at least 80 years left on the lease) you try to extend the lease again back to 90 years. So while it is possible for the lease to run out and people lose their property, it's usually something you'd be expecting when you took over the lease (and so you'd pay a correspondingly lower price for the property). While the lease is active, there's usually an annual fee from between 100 and 10000 pounds. Obviously, the higher this is, the lower the sale price of the property is likely to be.
Personally, I wouldn't touch leasehold with a bargepole, and unless you want to live in the centre of a city there's usually plenty of freehold property available so you don't need to go down the leasehold route.
I'd imagine trucks would still be diesel, so it'd probably make sense just to remove some of the pumps and replace them with rapid chargers. I doubt the fuel stations themselves will disappear, just cater to a different market.
OTOH in the UK at least, I think public charging is way too expensive compared to home charging, so I think most public charging is done out of necessity on long journeys, so the number of people using chargers would probably be significantly lower than number of people filling up with fuel.
There was and publicly available, although the mainstream press mostly chose to ignore it.
My VW hybrid is just over 10 years. The advertising claimed 28 miles on a charge, but the reality was about 18 maximum, with stop-start somewhat less. After a couple of months when it had calibrated, it settled displaying 21 miles for a full charge. 10 years on, and it still reads 21 miles on a full charge, but the reading is less useful in use. It's common for it to drop from 21 to 15 miles after a mile, but to stay on 1 mile remaining for around 4 miles travelled. But essentially, I don't consider the range to have deteriorated too significantly, it still feels around the same ballpark.
A lot of the original thinking about batteries comes from the Nissan Leaf, introduced in 2009, when they guessed that batteries would probably need replacing after 10 years. However, from the cars that were written off from accidents, they discovered much less battery wear than predicted, and around the time I bought my car, they were suggesting batteries would be around 80% after 10 years and most manufacturers started using that figure. I'm not sure what current estimates are, but I wouldn't be surprised if it was closer to 90% after 10 years.
It's common knowledge amongst owners that range is significantly reduced in cold weather - I'd guess from my use, maybe 20% less range on a cold winter day compared to summer.
And as to why car batteries last so much longer than e.g. phone batteries, I think it's mostly because their charging limits are much more pessimistic. Typically a car charger won't ever charge beyond 90% capacity or discharge below 10%, and this is built into its estimated range (so 0 miles remaining is 10% charge).
I have a couple of points, not really sure if they should be in one post or not, but whatever.
Firstly, if you take what's written at face value, it seems there's a serious logic error in the OOM killer. If it genuinely counts shared memory against a process, then its logic is wrong because killing that process wouldn't release that much memory, it'd need to kill all the processes sharing that memory to release it. So, maybe it should ignore shared memory in its calculations, or weight them by number of processes sharing it, or whatever.
The other issue is kind of true, but shows a stubbornness from the developers to change how they approach the problem. It's true that if any task could be partially through updating shared memory when it is killed, then all bets are off as to the state of that memory. However, if that's the case, then there should already be some kind of locking mechanisms in place to prevent multiple processes updating the same pages anyway.
Probably the current solution is: something gets locked when modified; every other process would need to spinlock until it's released; locking process is killed; everything else is stuck; another PG thread notices the child has died and kills everything else; on restart the DB has to be recovered.
A different solution could be: give every process its own private part of the shared memory for when it starts a transaction; have an indirection table from page number to shared memory page; for every page that needs to be modified, a new page is allocated from the freed pages list; that allocation is recorded in the private part of the shared memory along with the page number it's replacing; the old page is left untouched and copied to the new page along with any changes; the change list is terminated; then as the last step we update the indirection table for every page that was modified. If the process was killed at any point, we can either roll back the entirety of the transaction (freeing every allocation it made for replacement pages), or if the list was marked as terminated, finish off updating the indirection table with the changes required and marking the original pages as unused. At that point, the lock can be released knowing that shared memory is still entirely consistent.
Some of that is probably happening anyway if postgres supports reading from tables concurrently with an active write transaction on the same table, in which case the logic on how to mark those now freed pages as still in use is required. In that case, each process can also maintain a list of pages it has marked as still being used in case a reading process is killed off.
Lots of people are commenting on how unique it was to have a software based disk interface instead of stand alone hardware. And in a sense that is true, but also not.
Around that time there were various iterations of floppy controllers, each having a small microprocessor at their core. Just before the Apple Disk II, NEC released the uPD765 which is contains everything needed in one chip, but actually it's mostly just a small microprocessor taking a very similar approach under the hood in terms of track decoding. In fact the uPD in the part name is a giveaway that the implementation is a microprocessor instead of logic gates (and the command and reply interface). That operates a lot more like the Commodore drive, except it has a parallel interface with the host processor instead of a serial interface.
Sadly, I don't know anybody who's attempted to extract the ROM out of that microprocessor and reverse engineer it, but I'd definitely be fascinated to see that for faithful emulation purposes (at least for my emulator, I just implemented the interface as described in the datasheet).
Or instead, they could just continue the simple route of taxing companies via corporation tax and dividend tax without having to worry about ownership at all.
> In France at least, you cannot disagree with a judgement.
This feels like it can't possibly be true as written. Given that France has a court of appeals, that rather suggests that you can disagree with a judgement.
Your argument would also suggest that continuing to maintain your innocence after being found guilty would mean you're committing a further offence.
Cutting wages is legally problematic in many jurisdictions, but certainly there's a case for reducing bonus payments by the reward amount paid to others if your code was later found to be at fault and it looked like negligence that caused it. Obviously, you'd need to be very careful here otherwise people would push back on anything that generates data traffic just in case usage of that functionality grew later on.
Arguably, the only real-world impact this drift has on normal people is GPS, but GPS already transmits an offset from its own clock so that receivers can correct for that. The GPS clock is different both from UTC and TIA.