how does a debug file output 8GB+? Is it running for minutes/hours? Or is it in a format that uses a lot of rich text? I would assume a text file in hex or unicode wouldn't use very much.. Is there a way to create intervals of log files so they have a cap on the size?
It is a simple debugger log in the transputer emulator (enabled by compilation option) which outputs each instruction executed so far, around 70 bytes per line displaying the 3 registers, the stack pointer, the instruction pointer, and the disassembled instruction.
The emulated C compiler processed a whole file ccvars.c before getting stuck in ccinter.c (this is the 5gb mark, approximately 78 millions of instructions executed). I stopped the process as soon as I saw it was stuck, but the emulator is fast, and I got extra 3 gb in the log. All this happened in less than two minutes.
Another reminder of how easy it is to forget how ridiculously fast computers are these days (especially when you're like me and not writing stuff close to the metal for your day job).
In terms of latency... well... we also could do a lot better there, but as I understand it, even if you do your best to cut away as much software bloat as possible, the latency "floor" seems to be higher than in the old days[0]. And the many layers of abstraction that is the average software stack don't help. Like, I'm doing my best to keep a web-app snappy, but there's only so much you can squeeze out of a browser.
I think we're talking about different interpretations of the word "latency", both valid. You are thinking more about UI freezes and missing input, right? EDIT: or do you mean that bad latency numbers are less crucial as long as input isn't dropped or out of order? In that case I think it depends on the task.
I meant "time between input and visible change on screen", or lag between writing on a tablet and the screen or eink showing the drawn line. It's not really as crucial when typing, but especially for writing or drawing on a tablet low input latency is the difference between getting in a real flow state or not.
Latency is subjective, but yes, I was referring to GUI latencies mainly. System design is increasingly more important when building new alternatives to existing architectures. x86, ARM are much larger chipsets than before, but smartphones do not really need a single operating system for making phone calls and browsing Youtube. What I'd like to see is more low latency devices that can compartmentalize applications and cores based on power consumption and speed requirements. Thinks like a notepad, calculator, and SMS app do not require Android 17, which, on my newest phone, takes over 2 minutes to reboot. In the past, the CPU would use big.LITTLE cores (like the ARM Cortex A53 and A72), but there's also a bootup cost to running those compared to a simple calculator or microcontroller. It would be ideal to have a dual display flip phone that is always on for phone calls and SMS (using something like Symbian OS), whereas the larger cores and OS can be turned off when not needed.
Refresh rate is only one component of the system- an integrated display controller can lower the latency, and of course, the choice of computer affects the speed as well. Their choice to go with USB-C Alt is a good idea.
I'm a huge solar fan, but I don't see energy transition happening as quickly as I'd hoped 10 years ago, and what seems apparent now is that it will only happen when energy storage gets 10x cheaper, which is why companies like Form Energy developing iron-air batteries might be the catalyst. You also need grid-forming inverters that balance the loads since relying on hundreds of thousands of residences for grid-tie is a real engineering challenge.
"Between digital economics and the wholesale embrace of King's Gillette's experiment in price shifting, we are entering an era when free will be seen as the norm, not an anomaly. How big a deal is that? Well, consider this analogy: In 1954, at the dawn of nuclear power, Lewis Strauss, head of the Atomic Energy Commission, promised that we were entering an age when electricity would be "too cheap to meter." Needless to say, that didn't happen, mostly because the risks of nuclear energy hugely increased its costs. But what if he'd been right? What if electricity had in fact become virtually free? The answer is that everything electricity touched—which is to say just about everything—would have been transformed. Rather than balance electricity against other energy sources, we'd use electricity for as many things as we could—we'd waste it, in fact, because it would be too cheap to worry about."
... What Mead understood is that a psychological switch should flip as things head toward zero. Even though they may never become entirely free, as the price drops there is great advantage to be had in treating them as if they were free. Not too cheap to meter, as Atomic Energy Commission chief Lewis Strauss said in a different context, but too cheap to matter. Indeed, the history of technological innovation has been marked by people spotting such price and performance trends and getting ahead of them."
My issue is that datacenter energy costs are being prioritized for commerce over residential use, so the average consumer is paying more for electricity, because a datacenter needs more electricity and they're getting tax breaks. Assuming this all improves efficiency for new products like automated robotics, there is a debatable benefit. Jevon's Paradox has no ceiling, except the environment, and people's 401ks.
Seeing the number of holes in that ceiling I really am concerned that the floor the clock is on is the same as the one with the holes, and I would advise that you secure the floor if you return to the attic.
There's a non-zero chance the "floor" is just plywood laid across some of the beams and the holes are from people missing the beam in areas there's no plywood
The other thing of course is that those beams are *massive*. They weren't dicking about when they built it. It wasn't built down to a price like things are today.
It being a municipal hall at first, I wouldn't be surprised the town wanted to spend a little extra, but at the same time, I imagine they needed to calculate the weight of the clock tower and over-engineered it in case the weight put too much strain on one end. Seeing that it's all stone on the outside. Were you referring to the white beams on the blue ceiling, or other beams? I'm guessing it's to support the weight of the machinery.
Funny enough you're doing an Italian/Brooklyn accent but the example I was thinking of is birds that mimicked the car alarms in Brooklyn in the 90s/00s and I'm wondering if they still do that now that alarms aren't as common.
Trademark, rather than a trade dress issue. https://www.greenbergglusker.com/publications/when-copycats-...