SquareWheel

> I'm using OSI's definition

You shouldn't. The term existed in the community before they tried to prescriptively define it. They have no authority over the term.

This seems like an impressive improvement, and I'm looking forward to it eventually being upstreamed. Though unfortunately I'm on Nvidia right now, and have been struggling with vram. They don't seem to support any kind of paging at all.

I am curious about the bit on virtual memory fragmentation. Would it make sense for the kernel to occasionally defragment that memory in place? I assume that would create a noticeable hitch, but might improve performance otherwise and allow for some applications to just fit in.

I would imagine that both companies have extensive internal tooling to address this concern; likely at multiple levels.

I'm not sure how much insight we can glean from looking at the number of commits and release cadence here. In the aftermath of such a major refactor/rewrite, I would expect it to take some time to get back up to their usual development speed.

Jared and the other developers are new to the Rust codebase, even if the structure is largely familiar. They're also likely focusing on other priorities right now such as tracking down instances of 'unsafe', rather than making user-facing changes (which might encourage a release).

Bugfixes could encourage rapid new releases, but perhaps the rewrite simply hasn't been very buggy? As far as I know, those on the canary channel haven't reported any major issues, or even really noticed the change. So perhaps there's little reason for new releases right now, as the team slowly churns through the backlog.

> P.S. Anthropic’s C compiler and Cursor’s FastRender web browser haven’t had any commits for months.

I always assumed those were just experiments in capability, and weren't meant to be ongoing projects. I would hope that nobody is using them directly today.

Well, I wasn't intending to violate any guidelines, and I don't believe I've dismissed the article besides. I was just trying to save some people from potential frustration, as there was no warning provided upfront.

edit: Ah, I see. You left this comment after having your last response flagged.

Note that this post includes a major spoiler for the show The Good Place. The show is fantastic, so I'd suggest not reading unless you've already finished season 1, or have decided it's not for you.

I know that an uncommon name needed to be chosen, but something about the hyphenated /.well-known/ just turns me off.

I'd have really preferred another term: registered, reserved, defined, meta -- or really anything else.

Yep, they solve the same problem. I built my blog on Harry Roberts' ITCSS paradigm some ten years ago, and found it extremely easy to migrate to cascade layers. They're an underutilized solution to addressing growing specificity.

They're admittedly less useful if you're already using component-based design. That's closer to something like BEM in hyper-targeting each element.

Personally, I forget syntax all the time. There's always a warm up period after I switch languages, and it takes me longer to be start writing good, idiomatic code.

Like sure, I can probably write some python, but will it be pythonic? I might still be Java-minded for a while, trying to OOP my way into solutions.

Earlier today I needed to write some PHP and couldn't remember if it used length, count, or size. I had to look it up. I've been doing this for 20 years.

Sure, and Microsoft acquired DOS, and Adobe acquired Photoshop. At a certain point though, after 20+ years of development, you need to give some credit to the new owners for making it into what it is today.

> Did vibe coding the business page inject it into ChatGPT's training data?

No, at least not directly. Inference does not train models. It is possible that OpenAI may separately collect the chat data, clean it, and feed it back into the model for future iterations. Or they could have extracted URLs for future indexing.

More likely though, I suspect, is your site just managed to be indexed naturally, and LLMs are very efficient at matching obscure data to relevant queries.

"Open source" as a term has evolved due to its success. It wasn't some malicious attempt at redefining things from the technical elite. It was a natural shifting of language, as happens with all words, as it entered more common usage.

It's entirely reasonable that this colloquial understanding would be applied to new categories such as AI models. I'm sure it'll be applied to many other things that don't fit the OSD either. That's just language for you.

Sorry, too busy "stealing code" to answer right now.

This is a pretty banal comment at this point. Open source is the term used in the LLM community. It's common and understood. Nobody is going to release petabytes of copyrighted training data, so the distinction between open source vs weights is a rather pointless one.