b_e_n_t_o_n

You appear to have taken offence, at people taking offence, to people taking offence!

I mean, we all have things we'd rather not have people reject us for, that doesn't mean it should be illegal to do so. We already have the (legal) right to keep our software preferences private.

In general I'd caution against trying to use legalisation to solve problems like this because they usually introduce more problems. At the very least I'd expect banks to no longer carry liability for fraud, so perhaps one intended consequence of this is that if you get defrauded the bank no longer protects you. That would suck imo.

Perhaps they could make it so you waive all protections by using unauthorised software. That would probably require changes to existing legislation, and then of course people would complain that the banks have too much power etc...

For some reason I thought it was for toddlers to call other toddlers. I think if you were looking for a feature to add, it would be to let kids call their friends. Could lead to some cute moments :)

And 3 is worse than 4.

Yeah I'm not exactly sure what the appeal is of a world in which none of us are rewarded for our time and labor...

> If some piece of software I'm running is the only reason for you to refuse the connection, then you should be obligated.

Obligated how? Like through violence? What happened to freedom of association?

Depends if you ask someone who gets defrauded of their life savings and work and is financially ruined I suppose.

Is it? I figured it was halloween themed.

Hahahaha right

Absolutely incredible to see a snarky nit on a project like this. Hackernews never fails haha.

What are they?

I'm far from an AI enthusiast but I really appreciate Simon for his articles and takes on AI. He's enthusiastic and optimistic but that doesn't make him a hype man.

Woah, finally something with actual metrics instead of vibes!

> Trial participants saved an average of 56 minutes a working day when using AICAs

That feels accurate to me, but again I'm just going on vibes :P

I haven't written much Java but I am learning Kotlin and I really appreciate the language and the whole JVM ecosystem. Yeah yeah, Gradle is complicated but it's waaaaay easier to figure out than my adventures with Cmake, and when I read Java code there is a certain comfort I feel that I don't get with other languages, even ones I'm experienced with like Go. Java feels a bit like a stranger I've known my whole life, same with Kotlin. Perhaps despite all its flaws, there is a certain intrinsic quality to Java that has helped make it so popular.

> Update 7 Oct 2025: Some screen readers have been found not to announce updates to the tag, so explicitly emphasising the role attribute might be worthwhile for now until support improves: <output role="status">.

Maybe it's because like most things html/css related, it's a semi-broken implementation of a half-feature?

Have you played it? I haven't so I'm just basing my opinion on some YouTube footage I've seen.

BF1 is genuinely gorgeous, I can't lie. I think it's the photogrammetry. Do you think the lighting is better in BF1? I'm gonna go out on a limb and say that BF6's lighting is more dynamic.

It sounds like there is one client and multiple servers, so I assumed that it would be easier to change the single client versus multiple servers. I guess it also depends on what the in-house developers are experienced with.

But I'm not so sure that it really minimises future work. Like if they decided they want a button that toggles both the sound and lights in a room, that's trivially implemented on the client. Or if they want to reposition a button from the top of a stack to the bottom. My assumption rests on the idea that changing the client is easier though.

idk, battlefield 6 came out today to very positive reviews and it's absolutely gorgeous.

It's quite cool honestly, well done to the developer. It works, so it's de facto a good solution.

> The hard parts weren’t the architectural pattern - they were embedded systems constraints. Tuning buffer sizes and designing components shallow enough to fit in 512 bytes required iteration.

I am a bit confused by the choice to use HATEOAS for this. Given the hardware constraints of the controllers I wouldn't have figured that doing handlebars style html templating is a good use of resources, rather than just sending raw data to the client and having it handle the presentation. I probably would have returned a blob of data from the servers and handled everything on the client, but I also am a UI guy first and foremost...

Yeah reduced motion would probably toggle opaque backgrounds as well. But you can't really get that glass shader with css anyways so I imagine there wouldn't be many transparent effects, it's more just the layout I'm talking about for web.

I don't agree with that assessment.

I like it, but regardless of one's aesthetic opinions I think an important thing people are missing is the move towards UI elements being overlays on top of content instead of sandwiching or interleaving with content. This is very apparent on some apps like iOS Safari, Maps, etc. The general idea is your app content is a full screen/window canvas and your UI sits on top of it, which allows it to get out of the way of the content. I actually really like this move. The transparency serves a purpose here, it helps retain that full size appearance even when UI elements are visible. The glass effects essentially serve as a way to generate some contrast while still making the underlying content visible. Even with large UI elements on screen like sidebars, you still get the feeling that the content is prominent. I think this is going to influence how I build my own web ui's moving forward.

No you aren't, I like it too. I did notice some slowdown with my iPhone 14 in low battery mode though, which is a shame but not unexpected.

Yep. At one point it was probably the case that it always caused reflows but browsers have had so much investment into optimizations that it probably realizes those layout changes don't require reflows and skips them.

If you were an x86 assembly expert would you still feel the same way? (assuming you aren't already)

Interesting article, I'm generally sceptical of vibe engineering but Simon seems really balanced in his approach to it and in general his experiences line up with mine. AI can generally be outsourced to do two things - replace your thinking, and replace your typing, and I find the latter much more reliable.

Multithreading in the browser kinda sucks though, it's too slow to share significant data between workers (threads), and if you try it with SharedArrayBuffer you eat the serialisation costs.

I actually did that for a campaign. It wasn't extremely overpowered but I did have some abilities that could have been extremely OP if abused. I don't even think it was really legal as far as RAW was concerned. In the end I was probably one of the least effective characters, but I was able to do some cool things with those powers and we had fun roleplaying it.

Thanks for letting me nerd out a bit

It might be more useful to think of React as having a very simple reactivity system. In essence it just compares state values by referential equality (===) and if they're different, rerenders the component. And that includes children. In order to optimise, you need to both maintain referential equality of objects across renders (i.e. don't recreate them each render) and then tell React to compare the props passed into components by said referential equality before rendering.

Whereas other frameworks have a full blown reactivity system with signals (basically implicit observables), so your state values are not just regular javascript objects but either proxies or some other object which can be tracked by access in components to update things granularly, eg. setting an elements innerText but automatically.