snemvalts

They aren't obviously, but iirc around 70% of vulnerabilities in Chrome and Windows have been memory safety bugs.

Rust only prevents types of bugs where the game crashes because of invalid memory access, or exploits.

Wanted to say thanks for making this app, makes following races so much easier rather than looking at estimated finish time and setting alarms every day of a tour lol.

This funding does not only apply to the top level, it applies all the way down to national club level and below.

The sport wouldn't be as popular or have as much funding. The reason football is where it is because of marketing.

This can be extended to all other sports. A sport needs to be easy to follow and easy to advertise with to get funding. Being able to practice it cheaply on a grass-roots level helps.

$100M+ from the IPO isn't enough to being set for life, it has to be $1B+ from the buyout?

"I'd like a car that goes 300mph and gets 100mpg while doing it. I'm aware of a car that gets 100mpg but it is extremely slow."

You are describing fundamental tradeoffs. Getting more performance relative to model size and training token amount is what all of the labs are solving.

The lowest of the bars

But this harness app is chinese?

Most benchmarks can be trained for as well, so they are over-representative of model's engineering skills. The entire nature of a benchmark is collapsing some qualitative work (software engineering task, architecture choice, code quality) into a quantitative score which can be optimized for.

Let's say you to render conditionally when `x` is present. You do `v-if="x"`. Now you want to refer to `x.y.z` in the body, while `y` is optional.

Can you be sure that the value is present? How do you check for it? What does Vue need to do to enable this functionality with static type checking with TypeScript?

With `{x && <>{x.y.z}</>}`, it's almost vanilla TS, it's the same as `x && x.y.z` in normal TS. Type narrowings that work in TS are guaranteed to work in React, without the framework having to do anything.

Less framework/library code required to make the same thing work. To me, that's the sign of a better abstraction and implementation.

JSX is a very thin layer of templating logic inside JS. Meaning you have all the language features available while templating. Some arbitrary JS can result in templating.

Vue's DSL is whatever language the developer implemented. Which is probably not enough, depends how much effort they put into it and how good they are in language design. Given that they cargo cult HTML tags to organize components in a pseudo-familiar but not-valid-HTML way, I don't have much confidence in their language design skills.

I'd take the former any day.

How many of them can run infinitely? Or be re-triggered by humans to continue where they left off?