DocFx could do what you’re looking for. You would write your stuff in markdown and it generates an interactive and customizable site.

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?

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.

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.

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.

You want to translate COBOL to another language? That exists as a commercial product! The complexity is not the syntax though, it is the environment and subsystems surrounding the code. A lot of COBOL is designed for mainframe systems, and emulating a mainframe is complex.

You also end up with code that is still written as if it were COBOL. The syntax for COBOL is the easy part and that is all you can easily replace. Afterwards you’re still stuck with the way of working and mindset, both of which are quite peculiar.

The company I work for recently looked at all of this, and we decided not to translate our code.

I manage a team of about 30 people in IT. Your job is not valued enough, and I know the importance of what you do. Thank you for your work!

You’re absolutely right! USB storage devices are blocked and we don’t have the right to execute arbitrary executables anyway. It is a pretty secure environment.

For me it’s Chrome for work, because we’re not allowed to install anything on our machines :(

With my professional experience in COBOL, I can honestly say I’m not surprised at all!

Good point, somehow I completely missed the point you were trying to make about getting samples and analyzing them outside of the original laboratory. That would indeed be completely scientific.

Somehow taking the samples out of the original laboratory didn’t cross my mind. What I understood was a team going over there to look at the samples. In that case I would be very weary of any possible manipulations, like with magicians’ tricks or such.

I’m really having issues thinking straight these days with the stress I’ve been under and the stomach flu I just had. Sorry about that brainfart!

Sure, but that isn’t the scientific process. Typically a first team publishes what they did and the result they obtained, then others will try to replicate and improve on those results.

What you describe is interesting, but more of a closed/proprietary approach. A team says they have something and invite others to take a look, and then the second team will need to make sure they aren’t being bamboozled somehow. But until the second team can actually recreate the entire situation, it isn’t very useful to them. They just get to be onlookers, and will remain sceptical that there is some bamboozling being done.