Few thousand? Really? Larousse Gastronomique is 3600 pages, averaging maybe 1 recipe and 1 ingredient per page - and that's just classic French cooking.
Me too. The number of "revolutionary" designs that are announced but disappear makes me cynical. Looking wings on real aircraft, unless freshly painted, they're pretty close to finely sanded :) If the airlines and engineers saw a significant performance degradation with wear, they'd be out there polishing and repainting wings.
On a similar note - How many times have you seen announcements about someones blended wing that is going to save 50% fuel? But there are very few blended wings in nature (eg. rays), and those are in a very slow-speed regime.
The real obstacle to blended wing designs, I imagine, is more boring: airports are likely to be difficult to retrofit to support those, well for cargo anyways, and for passengers there's probably less appetite to board such a plane
I'm inclined towards keeping an ancient android for those apps that require it, and maybe something open for actual use. Or perhaps a crappy old android for android and a small non-android tablet/laptop for daily-driver stuff, which always works better as a computer anyway!
I'm also becoming open to using software that lies to google about what it is :) Google will treat us like sh*t, why shouldn't we reciprocate.
Same reason as "make another (better) windows" is very difficult - almost everyone wants to be able to run existing apps and drivers, so you're forever playing compatibility catchup with android (or windows).
That's the reason companies are desperate to be first/biggest - once you're it, you're it until you finally fall on your face and dwindle to a nobody.
AOSP is open source. There are plenty of AOSP-based systems (starting with GrapheneOS). No need for a new one.
The thing here is that Google is building technology to prevent alternatives from connecting at all. We fundamentally cannot solve it by building more alternatives, we have to prevent Google (and TooBigTech in general) from doing it.
I've always felt that to treat infinity as number is to commit a category error (aka type conflict), to confuse the process with the outcome of the process. Infinity has proven to be very useful, but usefulness doesn't make it always valid.
It's a great pity but I won't be buy more Ubiquiti hardware unless their direction improves. I loved the Ubiquiti hardware until a year or so ago. It was well spec'd, well priced, reliable, and it was easy to upgrade to OpenWrt. (Changing to OpenWrt was definitely an upgrade - get away from their you-must-do-it-our-way software. OpenWrt isn't perfect but mostly just works.)
But Ubiquiti have changed. The new hardware is silly - little screens and do-everything-on-an-app-with-our-cloud firmware. It's my infrastructure, I don't want to rely on your cloud! I only hope they go back to making good hardware and letting us use it for what we want.
>> However, the tech exists for a reason and is not inherently bad, the issue is the lock-in, the lack of choice and interoperability.
The marketing excuse for the tech might be features or efficiency, but the reason for the tech is lock-in and minimising product lifetime.
The days when manufacturers had friendly, cooperative relationships with their customers are long gone :( Can we bring them back? I hope so, but am not hopeful.
How far below is the question. It could level out at 60% - that is believable. However it can't level out at 99% - Somewhere around 95% major sites will decide IPv4 isn't worth supporting and they will just ignore that final 5% of customers, which will force them to upgrade - which in turn will give others confidence to remove their final 4% of customers - until IPv4 dies.
There are also still Telex and X.25 networks around there, not to forget the whole public telephone network!
But at some point, getting a native connection to all of these started becoming increasingly rare, and now these are largely emulated/tunneled on top of IP. The same can happen for IPv4.
>> DDR5 technology comes with an exclusive data-checking feature that serves to improve memory cell reliability and increase memory yield for memory manufacturers. This inclusion doesn't make it full ECC memory though.
"Proper" ECC has a wider memory buss, so the CPU emits checksum bits that are saved alongside every word of memory, and checked again by the CPU when memory is read. Eg. a 64 bit machine would actually have 72 bit memory.
DDR5 "ECC" uses error correction only within the memory stick. It's there to reduce the error rate, so otherwise unacceptable memory is usable - individual cells have become so small that they are not longer acceptably reliable by themselves!
As I understand it, the 50-move rule must be invoked by one of the players, lets assume our immortal players agree not to invoke that rule.
The 75-move rule is automatic, so that would be the limiting factor.
Note, that 75-move rule is only applicable after no pawn has moved or a piece has been captured. So our immortals can do a lot of shuffling things around.
I'm thinking that the number of moves of the longest game is going to be (16 pawns * 7 moves each + 16 pawns being captured + 14 other pieces each being captured, not the kings) * 75 moves for shuffling around = 10650 moves.
That's only 1 week at 1 move per minute! But given the permutations, it might take much longer to calculate the actual moves required to get to the end state :)
Pawns only get 6 moves :) But also they can't all make 6 moves because they can only move past each-other via capture, so half of them would get 5 moves instead (if you're counting all the captures), so that gives a maximum of ~8850.
reply