HN user

smingo

27 karma
Posts4
Comments37
View on HN

Commodore release a new variant of their C64 computer, with a '99%' faithful recreation of the original hardware on an AMD Artix 7 FPGA, along with some more up-to-date specifications. Suitable for retro gaming.

Chinese New Year falls between 21 January and 20 February. This would be somewhere between week 3 and week 8.

Some ISO 8601 week numbers for CNY:

2022 CNY fell on Feb 1 , which is Week 5

2023 CNY fell on Jan 22, which is Week 3

2024 CNY fell on Feb 10, which is Week 6

2025 CNY fell on Jan 29, which is Week 5

indeed, with an incoming Teams meeting invite, it should be determinable from the sender's context which account should work on the meeting. Instead there is 2 minutes of waiting, and what seems like pot luck with the account.

Putting the WiFi SSID and password on the side of the energy monitor sensor box allowed for this:

The whole thing was quite dissapointing. However, I do have a few Raspberry Pico microcontrollers lying around at home. If I could connect to the WiFi network of the energy manager directly and get the data from the server, I could just extract kW consumption from the API, multiply it by a correct rate and then display it on some Grafana instance.

Love it!

Regulating here is necessary, but the challenge is steep! IoT devices may include a complex bill of materials (BoM) including software (SBoM). Vulnerabilities can appear in any of those components.

On the one hand, CVE and vulnerability databases are excellent, and with some automation of vulnerability and patch availability the's the possibility of automated re-build.

But the manifests can be huge. And some component could be vulnerable, but was never anticipated to be so, and perhaps doesn't even have the means to be patched. Update processes for sub-sub-components may not have been exercised, and could lead to bricked products.

So labelling and guarantees are welcomed. But the challenge is practically insurmountable, and until the entire industry steps up to meet it, labelling and guarantees are going to be 'best effort'.

Someone must have felt very clever when they concluded Erlang would be dimensionless.

  Calls per second X seconds per call = no unit.
But that's wrong. Clearly the number of calls ongoing maps on to lines being used for a circuit-switched network, or datagrams in flight, or whatever. Far from dimensionless.
  Call_starts per second X call.seconds per call_start = calls as the unit
Much more plausible, IMHO.

there's little coherence to the way the language has grown in the last decade.

IMHO it's been incoherent from the earliest times.

The lame exceptions without 'finally', and no consistency in exception types. Then the desperate attempts to make all resources into objects, except that practically no OS calls bothered with this.

The overloading of the shift operators in the standard library. Indeed, operator overloading itself is just a recipe for abuse. You read 'a=b+c' and you literally have no clue what that means.

Multiple inheritance with the brittle semantics.

The awful STL, with its multi-kB error messages (the allocator of the trait of the string of the tree of map of king Caractacus doesn't match ...)

There's no wonder the 'obfuscated C competition' never happened with C++ given the fact it's unreadable, right out of the box.

There is a correlation between BTC and GPU / graphics card price. And there's the stupid quantities of energy devoted to mining.

At some point, processing bitcoin will become uneconomic. It will then be unspendable, and the price will then drop to zero.