I could easily imagine the right films renting these cars for a stunt. Film cameras and practical effects are having a resurgence.

Here in Australia, representatives of the various political parties observe the counting as scrutineers. I did it once. It’s absolutely fascinating seeing the system and rules. All (lower house) votes are physical slips of paper. Officials sort them into piles of 50 based on their first preference, in a big warehouse. Scrutineers watch them do it. We are allowed to contest their reading and sorting of a vote, but not physically touch anything.

I’m sorry to hear you can’t see your own democracy in action. I have more trust in our election process seeing it up close, in person.

They're explicitly advertising selling exactly that car. They just say it's by "invitation only". Do you think it's just a marketing gimmick? I dunno who's crazy enough to buy one. But for the right price, they could definitely sell a few.

GetRight did all this in 1997.

    #[component]
    fn App() -> impl IntoView {
        let (count, set_count) = signal(0);
        view! {
            
                "Click me”
            
{move || count.get() * 2}
        }
    }

Not in my house. What is even the point of connecting a coffee machine or a washing machine to the internet? I think my washing machine advertised that I could download new washing cycle programs in the app. Who on earth cares?

LLMs are excellent at making prototypes though. And prototypes can be an excellent way to stop yourself from implementing the wrong features in the first place.

Yeah but let's be honest; GC languages (Go, Java, C#) usually are slower than systems languages. Systems languages just give you more, low level control over the computer from within your program. You can use that control to improve performance. Eg, you can control data locality, memory access patterns, the emitted assembler, and way more stuff.

Of course you're right - if you misuse arc, you can make your program slow. So don't misuse arc then. Rust gives you lots of options for structuring memory. If you choose badly, that's on you.

A waste of what resources? Other people's time? That isn't up to you to decide. I think your comment is a waste of resources. But how you spend your time isn't up to me. And how wasm people spend their time isn't up to you.

> The current trend is porting source code to languages that generate native code.

Cool story, but without wasm, how are you gonna run that native code in a browser?

I’m mostly happy with implicit casts from void* to int* or something. But in this code example, we see an implicit cast from void* to int, casting the pointer itself into a number that might not even fit the pointer. This is rarely what you want. I’d much rather explicit casts in this case.

Hooks came much later, long after react was already popular.