As the great operation begins.
As the great operation begins.
It is a hardware failure. Screens are complex and sensitive parts that are exposed to a lot of (ab)use. What is cryptic about that?
I agree, it looks nice in my opinion. It doesn’t look like the house itself is crooked. It’s just asymmetrical furniture, which I find fun to look at!
we think you’d be best with a bigger team with a better support network
Sounds like they think you’re not independent enough for the position. If it is a small team, they might need someone who can immediately start being productive, while they think you will need more coaching to get up to speed.
No need to drag any disabilities into this.
Just get uBlock Origin instead. Years ago I made the switch and never looked back!
They say there are 16 screens inside, each with a 16k resolution. Such a screen would have 16x as many pixels as a 4k screen. The GPUs power those as well.
For the number of GPUs it appears to make sense. 150 GPUs for the equivalent of about 256 4k screens means each GPU handles ±2 4k screens. That doesn’t sound like a lot, but it could make sense.
The power draw of 28 MW still seems ridiculous to me though. They claim about 45 kW for the GPUs, which leaves 27955 kW for everything else. Even if we assume the screens are stupid and use 1 kw per 4k segment, that only accounts for 256 kW, leaving 27699 kW. Where the fuck does all that energy go?! Am I missing something?
Is it bad that I kinda do want to get high and have my fridge come over to me to fulfill the munchies without ever having to get up?
Honest question: do you avoid alcohol if you’ll be a passenger in a car? To me, that would seem similar to the plane situation you’re describing, but I’m sure you’ll agree the majority of people wouldn’t do that.
Well there is this thing called a speed limit, that is a very clear hard limit. If you go over, it is at the very least financially unsafe.
That is true, but from a human perspective it can still seem non-deterministic! The behaviour of the program as a whole will be deterministic, if all inputs are always the same, in the same order, and without multithreading. On the other hand, a specific function call that is executed multiple times with the same input may occasionally give a different result.
Most programs also have input that changes between executions. Hence you may get the same input record, but at a different place in the execution. Thus you can get a different result for the same record as well.
That exact version will end up making “true” false any time it appears on a line number that is divisible by 10.
During the compilation, “true” would be replaced by that statement and within the statement, “__LINE__” would be replaced by the line number of the current line. So at runtime, you end up witb the line number modulo 10 (%10). In C, something is true if its value is not 0. So for e.g., lines 4, 17, 116, 39, it ends up being true. For line numbers that can be divided by 10, the result is zero, and thus false.
In reality the compiler would optimise that modulo operation away and pre-calculate the result during compilation.
The original version constantly behaves differently at runtime, this version would always give the same result… Unless you change any line and recompile.
The original version is also super likely to be actually true. This version would be false very often. You could reduce the likelihood by increasing the 10, but you can’t make it too high or it will never be triggered.
One downside compared to the original version is that the value of “true” can be 10 different things (anything between 0 and 9), so you would get a lot more weird behaviour since “1 == true” would not always be true.
A slightly more consistent version would be
((__LINE__ % 10) > 0)
They are very busy charging an arm and a leg for crappy software with shit support.
I’m in IT in the financial industry. There is indeed still a ton of COBOL around.
Makes sense, you clearly thought about this! From a world-building perspective I do have a follow-up question: 86.4k seconds is our definition of a second, but it is essentially a convention and there is no reason for it. In a society that throws out the hours and minutes, why did they keep our second? It seems like it would have made sense for them to define the day as 100k of some new (slightly smaller) unit. That could have given them 10 “hours” of 100 “minutes” of 100 “seconds”.
Why split the day into 8?
You definitely have a point with base-12 though. If base-10 wasn’t so ingrained already, base-12 would be a very logical choice. You can even count to 12 easily on one hand, using your thumb to keep track of where you are and counting on the segments of each of your 4 other fingers.
According to this article, an average smartphone uses 2W when in use. That number will largely be dependent on the screen and SOC, which can be turned off or be placed in a lower power state when the phone isn’t actively being used. (The 5W - 20W figure is for charging a phone.)
With 8 of these cells, you’ll have 800μW, or 0.0008W, and you need 2W. You will need to add a few more batteries… About 19,992 more. If 8 of these batteries are about the same size as a regular smartphone battery, you will need the equivalent of 2,500 smartphone batteries to power just one phone.
Too bad they don’t say how much the new batteries weigh! It would have been fun to see…
If we ballpark it and assume something the size of a regular smartphone battery is 50g (1.7 oz), then our stack of 20,000 of these new batteries could be about 125kg (275 lbs).
I won’t be replacing any of my batteries just yet.
Our eyes and brains don’t perceive still images or movement in the same way as a computer. There is no simple analogy between our perception and computer graphics.
I’ve read that some things can be perceived at 1000 fps. IIRC, it was a single white frame shown for 1ms between black frames. Of course most things you won’t be able to perceive at that speed, but it certainly isn’t as simple as 30 fps!
That may be true for the exact hardware you used, and the exact tests you have done. For Microsoft the problem would be that they need to actively continue supporting older and older devices. At some point it makes sense to drop active support. If it works, that’s fine, but they won’t continue testing and fixing for unsupported configurations.
Phrased differently: Microsoft announces the end of support for a product. If you want to pay for it, they will make an exception and continue to support it just for you.
I understand people dislike Windows 11, but complaining about life cycle management isn’t going to help that.
That is what I remember too.