jdiff

What kind of metaphor? You can be a metaphorical nanny state of something smaller like a household or comment section, I suppose, but even then not with a single statement. The problem with a nanny state is the scope. And people expressing contrary opinions isn't nannying.

Be nice if I could correct the specs when detected incorrectly, or check the specs of a different machine without needing to physically pull this up on each machine.

Model choices all seem quite out of date. Phi-3, GPT-4o? Claude 3.5? And I thought Gemini Ultra was a subscription plan, not a model.

One person is not a nation.

Even as an informal conclusion I think it's important to know who you're up against and what their motivations are. Waving that away is how we get people like known, obvious charlatans like RFK Jr in any sort of position of power. I know this is nitpicking word choice but the informal conclusion is "Not likely, and not enough to matter for anything."

I was objecting more narrowly to the notion that the driving force behind the obnoxious safeguards that are making the product useless was the current admin, rather than having been in there since launch and driven internally.

That reasoning didn't stop them from releasing this batch of models, admittedly that may be less face to lose away from the flagship position.

Weren't these obnoxious safeguards in place from Day 1, before political meddling in the most holy Free Market took place?

This statement of a lack of community is at odds with the plentiful pull requests that were open before the rewrite.

This is, as you say, unprecedented. Not impossible, cautious optimism is a fine response. But to bring back a point I made earlier in the new old light: Then let's be cautious. Let's do some announcements ahead of time. Let's get some people in and get some physical hands on the codebase. Let's not go from "Stop freaking out, it's just an experiment!" to a silent merge to main in a week. That causes reduced trust in the project from those even just a hair less optimistic than you, and that's clearly unhealthy for the project no matter how you define "the community."

I use oMLX and I'm tentatively going to be giving this a shot. oMLX keeps driving me up a wall with odd papercuts, bugs, and silent failures and fallbacks that are only visible buried deep inside logs when they should be announced out loud.

The maintainer of mlx-vlm being behind this as well is the main thing kicking me over into trying it, even if it is incredibly young. I'm confused and unenthused to see it chomping on a whole GB of disk, but the Swift makes it feel much more refined even if it's not yet as feature rich. It automatically picked up the existing models I was using with mlx_vm directly, which was nifty.

No, that's not correct. That is the discussion started by the article, and the one continued in many other comment threads, even including this one far further upthread. Conversations drift over time, and this thread has evolved into a subdiscussion on the topic of the rewrite itself. If this is not what you would like to discuss, I suggest you visit the other threads.

If you would like to join us in this thread now that this misunderstanding has been corrected, please, share your thoughts on the Bun community, what the "Bun community" even is, and how it has been impacted by a sudden, unannounced rewrite.

I think there's a lot of spare GPU compute. I don't think it'd be made available for this, or if it was, I believe it'd most likely be from a company that won't survive the AI bust. But I think there's a lot of spare compute sitting idle out there.

If there weren't, I think token prices would be higher than they are, downtime would be higher than it is, and there would be far fewer free tiers or more restrictions on free tiers.

Whole classes of bugs are fixed by safe rust. This is not safe rust. As a line-by-line translation with unsafe forced anywhere necessary to make it compile, this should result in no classes of bugs fixed by moving to rust.

Are you interested in the discussion that was taking place before you popped in or are you just here to get outraged that something you clearly identify strongly with is getting criticism for making poor choices?

"Because the discussion was interesting" is why I care.

Bun is riddled with bugs. That's what moving fast and breaking things gets you. It gets you famously bad codebases that are nightmares to work with and slow you down over time as your sins catch up with you. Vibecoding is not enough.

You don't need to look up the entire multiplication in a single move. When we do multiplication outside of our own mental lookup tables, we have an algorithm for that. The one described in the article. You can size your lookup table however large you like.

I do know how git works and in my experience, while the version number sometimes doesn't get bumped until just before a release is tagged, the version number comes from the codebase. If they're building something that says 1.4.0, then they have a codebase that disagrees with ours.

That commit (and main) still purports to be 1.3.14, the version numbers haven't changed. Does that not still suggest Anthropic is using something else?

they did put the bun 1.4.0 version bump in the changelogs for claude code a while ago, over a month almost.

Where? Is see no CHANGELOG in the root. I do see LATEST, last modified 2 months ago, and it says 1.3.14

That PR is the rust rewrite. That's some time in the past now. As of this comment, there is no tagged 1.4 release. This is the present. Anthropic is using apparently a version of Bun that is not publicly available. This is orthogonal to it being Rust-based, as all Bun releases now will be.

There were very many open pull requests from the community that were all invalidated overnight for something that same community was assured was merely an experiment.

The normal process would be "hey, this experiment is going well, we've made this plan, come help us shake out the new codebase for the switchover in X time." None of that happened. There wasn't even an announcement, just a silent commit that trashed hard work from hundreds of community members.

Similar, but with better typography and responsiveness. I like actual code being present here but the majority of the challenge is just reading anything, especially when zooming does absolutely nothing.

This site doesn't. Many don't.

No? There are many things you are not allowed to say when advertising, many ways in which you are not allowed to advertise. Fraud is not legal, and I have yet to see anyone make a free speech case for it.

The highscores don't show the run's duration, aka the error margin

Different durations have different high score lists.

No, Tangled's ATProto relationship and its social features are just the only differentiating factors.

They mirrored their repo somewhere else. An additional location does not make it less friendly.

Project's still on Github, it hasn't migrated or anything.

They're still on GitHub. This isn't any sort of official transition. It's just now also on this other ATProto-based forge.

Yes, a pox on othersite, all hail currentsite.

I severely doubt the world ever gets to such a point that the entire world melts into AI hallucination. And token consumption depends on so many other things, it's not all that deterministic either.

The entire directory (not repo) and all repo history regardless of secrets or instructions otherwise is not needed for faster cache access. I'm not going to say that this was intentional exfiltration. Sneaky motivations are not needed for this to be a bad idea and a horrific implementation.