IshKebab

> The article does nothing to address that.

I dunno if you've been living under an enormous rock, but they used AI to make this.

Yeah except price differentiation exists. There's a reason Nvidia doesn't allow consumer GPUs in data centres.

It's already much smarter than most humans in a lot of ways.

It's not the same kind of intelligence as humans so it'll probably always have weird areas where it can't do as well (like counting letters in words), but that doesn't mean it isn't smart. If AI were sentient it could point at humans and say "haha look how dumb they are; 99.999% of them can't even write a basic Lean program".

We're way beyond the point where "it's not as smart as humans" is meaningful.

Yeah the "new here" instructions are completely wrong on mobile.

Also the control could just be a slider. Much easier and simpler on all platforms.

Nice idea though.

Definitely a worthy goal but they've gone down a super weird route by providing clones of other GUI toolkit APIs on top of this. Your target audience is people that are ok with vibe coding. They don't care about switching to a proper Blender-style API.

Just because you can...

I'm not sure it matters anymore unfortunately. I've vibe coded a few apps using gpui-kit and it works well. It helps that gpui-kit provides a number of high quality components (e.g. the data table is especially good). But even where it doesn't (e.g. log output) Opus 5.5 was able to easily write one that worked perfectly.

It even added ANSI colour support... which I am still on the fence about but it did make the very good point that it means the logging is exactly the same in GUI and CLI mode.

How obvious though? Obvious enough for 3 random people to agree? 10? 100?

You don't magically avoid a threshold just by saying "obvious".

Right, the context was missing out on "top talent". Top talent gets those crazy salaries.

Let's be real here, the main culprit is C. People love to say "but you can still get logic errors with Rust", and no shit of course you can. But it's much less likely. You wouldn't have gotten this bug.

This is very clearly the best design for operator precedence IMO and it's nice that Zig has converged on it. It would be good to get it as a linting/formatting rule in Rust too (maybe that already exists?).

There aren't any open commercial FPGAs as far as I know. Some have had their bitstream formats reverse engineered though.

We're starting to see open source FPGAs but they are miniscule: https://tinytapeout.com/chips/ttihp26a/tt_um_fabulous_ihp_26...

I'm not skeptical. Linux has had so many LPE bugs in the past that most people consider it to be a "best effort" thing and nobody actually relies on it. Shared machines are mostly used in companies or universities as a kind of admin tool - the users are more or less trusted.

The only exception I know of is Android. It would be interesting to know how many of these vulnerabilities work there. Can't be zero anyway...

Given their salaries, I really doubt it.

Why though? Let's be real, juries are human and requiring a unanimous verdict will 90% of the time just mean that people that disagree with the majority will give in so that they get to go home.

There's no fundamental difference in justice, just minor differences in thresholds.

Speeches have always over-used these writing techniques. The problem is Claude uses them all the time, even when not writing speeches.

Better you mean? Or are you saying you prefer having unfixed bugs?

IMO that is still kind of true. Windows 11 LTSC gives a totally bloat free experience, the only downside is you can only reasonably get it through grey market cdkey sites.

Linux, sometimes works without faff. But in my experience it's at best 50:50 if you get that, or constant crashes, hangs, broken peripherals, etc. (Of course any time you mention this the luck 50% pipe up with "it works for me".)

Oo that does look interesting. You might want to tone down the slop prose on your website though. It's a real turn-off.

OpenSCAD is useless for almost all of the things that people actually use CAD for. There are a few minor exceptions like fasteners, gears and procedural art. Most CAD is more like a motorbike or a vacuum cleaner. Good luck with that.

I was all ready to say how useless code-based CAD usually is (like OpenSCAD), but this actually looks pretty sick.

If you could add support for SolveSpace's 2D sketcher, and also bevels/fillets, then this might actually be useful.

You registered a domain just to post one-off slop? Pff.

Likewise. I'm a RISC-V fan but a slop page like this is not a good look.

A blackout that severe would surely affect POTS too.

They will sometimes choose the simple slow options, true. But there's a very trivial fix. I just regularly ask the AI to review the entire codebase for bugs, performance bottlenecks (it will happily profile your code), possible simplifications and YAGNIs. I get it to give me a ranked list and then I review that and ask it to do some of them.

Occasionally I do spot things and get a "you're right, I was wrong". But it's got to the point that my thought is no longer "of course I am... shitty slop machine" but "phew, I'm not totally obsolete quite yet!".

I agree with you. It's gotten extremely good very recently and I think a lot of people haven't realised.

And they also won't believe you since they formed their opinion 6 months ago when code quality was 80% slop. Their loss though I guess? At least they'll be more surprised than us when they actually do lose their jobs? Maybe blissful ignorance is better!

This is like claiming that the web is a failure in 2001.

The tone of this article is "I guess everyone else is stupid now", but his reason for not using LLMs is that he likes doing it the hard way.

Good for him but I don't think that justifies such a snooty position.

I will agree that it kinda sucks not being able to claim credit for your work. I've vibe coded or vibe finished several apps now that are extremely impressive, better than the existing alternatives. But I feel weird saying "I made this" because it feels like I barely did anything.

I wouldn't go as far as evil but they are bad for code quality because they obscure the behaviour of functions. You never know what exceptions can be thrown. Can a function even fail? Impossible to tell. (Don't say "documentation" lol)

The standard answer is checked exceptions, which I'm on the fence about, but they don't seem to be very popular in any case. Python doesn't have them. C++ removed support for them which shows you how unpopular they were. Java has them and IIRC they were kind of ok to use in Android. Kotlin doesn't have them though so I guess the Java people didn't really like them either.

Err yeah except actually you'll just pull out your mobile phone and use that.

> Meanwhile, some other projects will take the core idea of "language aware differ" and release BSD, and one of those will win, including perhaps making it into git/future version controls.

Diffsitter and Difftastic have been around for a while, both MIT, so I doubt it.