You should just find a good shadow box for it, it'll look good

To my knowledge, while authoritarian it's not a totalitarian state, and Singapore has fairly effective means of redress (aka, rule of law).

I think a good protocol however is key for adoption. Many a good idea has died an early death because the implementation of it was, too complex, insufficiently robust, or poorly thought out for the future.

Only at the point of emission however...

I'd actually assume closer to 100km of coverage, 60 miles or so is a conservative estimate of coverage, in the prairies I would expect it to go much further - 500w of output on high band VHF goes quite quite far - I know how far the US NWS stations cover, and its much closer to 60+ miles.

Environment Canada assumes 60 km on their Weatheradio page ( https://www.canada.ca/en/environment-climate-change/services... ), so that's what I went with. Having said that, I very much agree that the range is probably considerably greater in many cases.

While there are a handful of 500W stations, most are in the 100-200W range: https://www.qsl.net/ve7hce/weatherradio.htm

This seems insane, particularly given the short notice period for the shutdown.

I wonder if CarPlay will work on that, its still broadly broken on my 17.

Must vary by car — not had any problems with my iPhone 17 + Renault.

This feels like... just because you can, doesnt mean you should.

This so much.

We just got code complete on porting a 30 year old Delphi app to C#, because of all of this.

Even now, our pure Delphi components are performant and wonderful, but hiring people who want to learn or know Delphi is hard, so off to C# we trundle forward.

Didn't the same people who wrote Delphi write also C# and .NET? When I first saw .NET it felt very much like VCL/CLX. And then came TypeScript from the same guy.

But then the C# people make writing code in it.. a horrible experience. They really like to over engineer and architect.

Had to look at some c# backend code. To write any kind of endpoint that talked to a database they had to write at least... 7? different files, lots of empty interfaces that has to be created and implemented, command, mediator patterns everywhere, etc. Looked like insanity compared to Spring Boot

You can have it as short as you want. For example check this minimal API

https://learn.microsoft.com/en-us/aspnet/core/tutorials/min-...

—

But if you want it to be mockable, concerns-separated and what have you, you’ll end up with at least 3-5 files. But it ain’t got nothing to do with either C# or .NET in general.

> Had to look at some c# backend code. To write any kind of endpoint that talked to a database they had to write at least... 7? different files, lots of empty interfaces that has to be created and implemented, command, mediator patterns everywhere, etc. Looked like insanity compared to Spring Boot

Programming against interfaces. That's what you are seeing. Makes unit testing easier.

Somehow it is not required in other languages. It hurt our eyes at the office when looking at all these empty meaningless interface files. It just looks like bad language design from the outside, but when you are in there then you are used to all the weird things

You know things are bad when someone compares something to Spring and says: "this is thing is more complicated!".

the difference between gosub and if blocks calling a function is more academic than practical, you still have a main event loop sending your path of execution someplace based on something that happens.

I might not be a basic practitioner, but as someone who as written serious things in bash and powershell, I can see the allure.