Speaking as growing up in Fort St John, BC, sunrise was after school began, and sunset was before school was out - more or less - in the middle of winter. But then, that city (in BC, and nowhere near as far north as that province gets) - is rather more arctic in every sense of the word. But then, that corner also opted out of time changes, so ... the rest of the province is catching up :)
technically yes, because there's a failure path for every single failure that an OS knows about. And most others aren't so resilient. However, mmap bypasses a lot of that....
I like C. You can take away all memory management (yes, including some of the unsafe glibc calls that have hidden memory management) and everything can be so smooth and clean. Since rules like MISRA require up-front allocation - if any is in use - this can be tightly controlled.
Very useful if you don't want (or need) surprises anywhere. Or if you want all the surprises (exceptions, errors, etc) all better tied to the hardware that provides such.
It's also fairly easy to write unit tests for everything.
clang and ECL both seem interesting, as long as LGPL license is ok. They both are complex to embed though - neither are well tuned to be embedded in other applications. (I've been exploring on MacOS). Julia could be interesting too under same questions (and a better license for commercial products) but similarly has a fair bit of glue code needed - especially if you want to restrict (say) filesystem access.
hunting dangling references in a reference counted system is like that.... that's all I can guess is going on here. Good hunting! I wonder if there's a resource debugger? So far when I have really had to look, xcode was suffiicent... but there's likely better out there for finding this kind of thing.
4) no, unsafe. (this is a me problem. Until people stop smoking on or near public transit, it remains unsafe for me)
5) no, this is a really REALLY rude question. Part of it is city design prioritizing suburbs, but part of it is that the moving has a very high cost, and only increasing as property / rent prices continue to skyrocket. Mind, that's mostly a Canadian problem....
6) An interesting question. This one works.
7) Not really, infrastructure isn't much present yet for used EVs. Mind, it's possible, just not easy to find.
8) same as previous
9) Not easily, prices are much too high. This may change with introduction of Chinese EVs though.
10) same as previous
11) MUCH easier than other options. In some parts, going back as far as 100 years is doable in getting a car.
So we - when we finally needed a second car - went 11. Moving is out (cost of moving is comparable to buying a new car), and a new car is expensive enough that the cost is too high to carry. But then, we are not wealthy either, and I have no idea who can afford to buy that many new cars, but it ain't most people I've met or worked with. I see cars - like public transit in far too many cities in Canada - as pricing itself out of usability.
Thank you for the step-by-step execution! And 11 is the best solution when none of the above work. There are still scenarios where gas cars cover the edge cases. The first thing is to completely stop buying new gas cars. A new gas car will continue to pollute for the next 20 years. We can immediately stop all new gas car production and in the next 2 decades transition entirely to EVs.
Norway is a LOT warmer than prairie Canada. You want an equivalent, go maybe 600km north. heh. (not entirely a joke. Mind as far as I can tell, typical North Pole weather is also warmer than Saskatchewan winters, so ... weather is weird)
I know the Antarctic is typically a lot colder, though.
Siberia is a FAR better comparison than China. Among many other reasons, most of the prairies are similarly arid, and temperatures are definitely similar. Similar range of climates too (Siberia's got people a lot more spread out though).
Harbin is north of Vladivostok you know? But yah, Yakutsk is where you can’t turn your car off in the winter (well, they have auto start and stop now to keep the engine from freezing, no power outlets like in Fairbanks for block heaters) and often have to encase the whole car in a warming sock (which is exactly how you imagine it). Yakutsk is east of Siberia in the Saka republic though, the closest comparable city in Siberia is Norilsk (not as cold or populous as Yakutsk).
Yakutsk sounds similar to where I live now. Mind ... a lot of the Canadian prairies are "empty" (not really, lots of farms... but not a lot of cities that aren't close to the US border). Similar weather at least.
Yakutsk is the coldest city in the world. But cities like harbin and Mohe in China get really really cold for their latitudes, Harbin is on par with Winnipeg:
> Harbin's winter temperatures are closest to Winnipeg, Manitoba. Both cities are known for having extremely cold, dry, and windy winters due to their inland locations, with average January temperatures in both cities often falling in the range of -15°C to -20°
Mohe is worse:
> Mohe, China—known as "China's Arctic" with winter temperatures often dropping to -40°C or lower—has a winter climate most similar to Canada's coldest northern or subarctic communities, such as Yellowknife, Northwest Territories.
They both have EVs and used by Chinese EV companies for winterized testing.
Winnipeg is far south of where I usually am, and rather near the US border. It might be comparable to China what with the sea nearby and all those lakes.
I'm out in the middle of the prairies, where -40C is a normal winter day, and 100km winds are also ... normal. Mind, -20C to -30C is far more common, and -50C almost never happens where I am now. (it was a lot more common in FSJ, or in the badlands near Drumheller).
Fort St John BC however has almost exactly the same temperatures and weather as Yakutsk. Mind, it wouldn't be considered a city on these scales.
People do NOT understand how cold Canada gets. And I'm way south of places like Nunavut, the Yukon (mind, Yukon is warmer than Saskatchewan, mostly), or any of the Northwest Territories. I guess y'all think of balmy Toronto or the like. (or - by comparison - tropical Vancouver BC. Vancouver is warmer than Seattle, for the most part. Wetter too, largely, but not as wet as Prince Rupert or Kitimat).
Anyway that's mostly not here or there for EVs. EVs on the whole work really well on the prairies - especially if they've got mitigation for -50C and +50C (both temperatures happen regularly, at appropriate times of year). For the most part, more reliable than diesel at those ranges too.
The local frustrating part is while Alberta has an ok electrical grid, Sask is an unstable grid dependent on coal and low maintenance. (I mean, we do have Uranium City too ... heh..). Saskatchewan is poor, by Canadian standards.
eh, 30cm of broken ragged ice, a light layer of snow over top ... that's a Saskatoon Saskatchewan winter road.
so a LOT worse. heck the car does not handle it very well.
the wind makes it worse for clothing too, mind I have driven a jeep without a windshield or roof at -40C and that was more cold than I ever want to repeat. It was rather worse than working out in a field with survey gear at -55C and white out winds...
The go standard library has an implementation of ed25519 although I did not find ed448 it also has some NIST curves. There are a few libraries that do ed448 like one from cloudflare.
To test a Claude Skill for analyzing cryptographic implementations of cryptographic side-channels ([1] see constant-time-analysis), I had Claude vibe-code an Ed448 implementation.
This includes:
1. The Ed448 signature algorithm
2. The Edwards448 elliptic curve group (which could conceivably be used for ECDH)
3. The Decaf448 prime-order group (a much better target for doing non-EdDSA things with)
I've been putting off reviewing it and making the implementation public (as it was an exercise in "is this skill a sufficient guard-rail against implementation error" more than anything), but if there's any interest in this from the Go community, I'll try to prioritize it later this year.
(I'm not publishing it without approval from the rest of the cryptography team, which requires an internal review.)
Presumably one would want to use Ed448 in order to achieve for session key establishment or for digital signing a level of security comparable to using for encryption AES with a 256-bit key.
ED25519 has a level of security only comparable with AES with an 128-bit key.
Nowadays many prefer to use for encryption AES or similar ciphers with a 256-bit key, to guard against possible future advances, like the development of quantum computers. In such cases, ED25519 remains the component with the lowest resistance against brute force, but it is less common to use something better than it because of the increase in computational cost for session establishment.
> Presumably one would want to use Ed448 in order to achieve for session key establishment or for digital signing a level of security comparable to using for encryption AES with a 256-bit key.
Ed448 is an instantiation of EdDSA (the Edwards curve digital signature algorithm) over the Edwards448 curve (a Goldilocks curve), as defined in RFC 7748 and RFC 8032.
Key establishment would use X448 (formerly "Curve448") for Diffie-Hellman, although ECDH over Edwards448 is also (strictly speaking) possible.
Using Ed448 for key exchange is a TypeError.
But that's neither here nor there. I was asking about real world applications that need Ed448 specifically, not a vague question of how cryptography works.
> ED25519 has a level of security only comparable with AES with an 128-bit key.
No. The whole notion of "security levels" is a military meme that doesn't actually meaningfully matter the way people talk about it.
There are about 2^252 possible Ed25519 public keys. Recovering a secret key from Pollard's rho takes about 2^126 or so computations (where each computation requires a scalar multiplication), and that's why people pair it with an equivalent "security level" as AES-128, but the only meaningful difference between the algorithms (besides their performance footprint) is security against multi-user attacks.
With a 256-bit AES key, you can have 2^40 users each choose 2^50 keys and still have a probability of key reuse below 2^-32.
With 128-bit AES keys, you don't have that guarantee. 2^90 keys is well beyond the birthday bound of a 128-bit function, which means the probability of two users choosing the same key is higher than 2^32. (It's actually higher than 50% at 2^90 out of 2^128.)
However, despite the "security level" claims, Ed25519 has 2^252 keys. The multi-user security of Ed25519 (and X25519) is meaningfully on par with AES-256.
As things stand today, the 128-bit symmetric cryptography "security level" is unbreakable. You would need to run the entire Bitcoin mining network for on the order of a billion years to brute force an AES-128 key.
> Nowadays many prefer to use for encryption AES or similar ciphers with a 256-bit key, to guard against possible future advances, like the development of quantum computers.
This is a common misunderstanding. So common that I once made the same mistake.
Grover's attack requires a quantum circuit size of 2^106.
> In such cases, ED25519 remains the component with the lowest resistance against brute force, but it is less common to use something better than it because of the increase in computational cost for session establishment.
I do not understand what this sentence is trying to say.
Don't forget large scale purchasers using property for tax evasion, money laundering or other such uses. They largely don't even care if the property is maintained.
(eventually properties collapse, but if they keep the values inflated this way, that won't matter to them)
If you want to know more, look into RCMP reports on high property prices in Vancouver BC/Canada circa 2010s+, for example.
