snemvalts

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?

Tai's Model (https://en.wikipedia.org/wiki/Tai%27s_model) is a perfect example of this

What about other benchmarks? Benchmarks where the contents are freely available have become useless for evaluating models.

Scaling law is a power law , requiring orders of magnitude more compute and data for better accuracy from pre-training. Most companies have maxed it out.

For RL, we are arriving at a similar point https://www.tobyord.com/writing/how-well-does-rl-scale

Next stop is inference scaling with longer context window and longer reasoning. But instead of it being a one-off training cost, it becomes a running cost.

In essence we are chasing ever smaller gains in exchange for exponentially increasing costs. This energy will run out. There needs to be something completely different than LLMs for meaningful further progress.

The ability to learn and infer without absorbing millions of books and all text on internet really does make us special. And only at 20 watts!

Math and coding competition problems are easier to train because of strict rules and cheap verification. But once you go beyond that to less defined things such as code quality, where even humans have hard time putting down concrete axioms, they start to hallucinate more and become less useful.

We are missing the value function that allowed AlphaGo to go from mid range player trained on human moves to superhuman by playing itself. As we have only made progress on unsupervised learning, and RL is constrained as above, I don't see this getting better.

In simpler terms - they create an MCP server, essentially an API that the coding agent can call, that can fill in context about previous decisions done by the coding agent earlier in development. Agent equivalent of asking someone who's been working there longer "why is this this way".

This means that the agent will can have context of previous decisions, something that they currently struggle with as they are always starting from a blank slate.

MCP server with RAG to feed it back to agents when they are working on a piece of code, and bob's your uncle

Treating T2D and preventing T2D are completely different things from a dietary perspective. Same way you wouldn't give chemotherapy to a healthy person to prevent cancer

Red meat (a known carcinogen) at the top is gold. All that saturated fat the energy will come from (not from protein or veggies) will probably cause heart problems and plaque formation in arteries, not to mention insulin resistance just from increased FFAs in blood.

Vegetarians and vegans have lower T2D incidence on average FWIW.

i would interpret physical fitness as cardio exercise routine and depleted muscle glycogen stores: so breakfast is very welcome and without it is not possible to keep up exercise routine

Yes, but it is not syntax. It's a contract with the library. React is completely usable using vanilla JS syntax. Same cannot be said for Vue and Angular. It feels a bit like talking about apples and oranges in this thread.

You can write const [a, b] = useState('x') in vanilla js and typescript. Hence it is not magic syntax.

The swapping is indeed faster as the SSD is on the SoC and so fast to access. To the point that an 4 year old 8gb M1 Air is enough for simpler development work, at least for me.

I'm speaking from experience regarding mental illnesses and exercise. And I never discounted medication. Just that exercise is critically underprescribed, I'm fairly sure it would work better for milder cases compared to meds. Not to mention the other health benefits listed in the thread.

Same way an opioid pill is still prescribed in cases of cancer or severe pain. Just that there are probably better, milder alternatives that don't have as many side effects that could fit a lot of these people with milder problems.

If you have to measure time spent and do cost/benefit analysis, you're most likely not going to stick with it for the entirety of life.

In Amsterdam they are commuting, and in a fantastic infrastructure where cars get red lights when bicycles approach on an intersecting cycleway. That's probably the main reason for safety and why they ride so much.

Instead, people try to fix it with antidepressants, benzodiazepines or something else.

It feels a bit like the US approach to pain management – instead of massages or physical therapy, some opioid pill is cheaper to prescribe.

It was also tested only in overweight and obese patients. Pretty much most people are overweight and obese in the US as well, I wouldn't draw any results from this study for people at normal weight.

And yet they have the clickbait headline. Overweight and obese people already have their body in a constant state of inflammation, and their blood sugar control probably isn't great either. I wonder if they controlled for insulin resistance and prediabetes, which is related to obesity.

Very dystopian. Can't wait for them to be required for work like smartphones /s

x86 specific optimization for a language so focused on *portability*, heavy abstractions and business logic is kind of ehh. Especially with ARM is rearing its head.

If you desire performance close to the chip, you chose the wrong language and should write code in a language closer to the chip. Unless the abstractions and concepts required for your primary work are so different from what you are using for day-to-day work (data science, ML python and C++ bindings for interacting with the GPU)

The angular plugin for webpack is still an opaque black box.

The entire library is so spread out, with so many half-assed features.

When I wrote Angular I spent 2 weeks on getting something similar to `props.children` working. <ng-content> didn't work if the elements were dynamic. Outlet system was way too verbose.

The 2 way databinding is anachronistic and belongs in 2010.

The i18n system they shipped with is awful. No way to have translations in code, only in template. This breaks down very fast when building generic components.

The DI relies on https://www.npmjs.com/package/reflect-metadata, which makes the builder an opaque black box unlike a webpack configuration.

Because of the opaque CLI I've spent 2 weeks figuring out why every third dev build resulted in a 150 line long tsc stacktrace, and it turned out to be angular's 1.x types package. Would have been so much easier with a webpack configuration.

JSX can be syntax highlighted and linted easier. What if a variable that is being referenced is missing at that time in the component's lifecycle?

JSX makes so much more sense, making code the parent of the template, instead of keeping code and template as siblings.