montroser

Makes sense to split the foundation, as the communities have split (and withered).

From its inception Perl 6 was an incredible journey that resulted in a genuinely weird and interesting new programming language, and squandered a broad wealth of momentum and good will and enthusiasm from the Perl community at large. It was a dramatic slow death over the course of a decade, where people who had built their careers, and small and large companies who had built their economic engines on Perl got to come to the realization that the whole thing was over, killed somewhat inadvertently by its own creator...

Well, this is certainly not benchmaxxed, I'll give it that. And props for being honest about how far behind Qwen 3.6 MoE is this model.

But yeah, it's not the best look to have to stretch and say it's "competitive" with other models in it's weight class, when it offers not much else that's useful or novel.

deepseekv4 pro via opencode go is $10/mo and has very generous limits. I use pi for the harness and go just as a model provider. It goes a good long way...

This is a finetune of Qwen-3.5. Interesting to see this coming from the government of Brazil.

https://www.reddit.com/r/LocalLLaMA/comments/1u4fzg1/new_mod...

Well, this is the exact opposite of his point. Of course it should make sense when not animating! That is given. The entire crux of his point is that it should also make during an animation.

In an ideal world, it is hard to argue with. Yes, sure it should make sense. But also, please don't spend precious cycles on this unless all the other bugs are fixed, and this animation consistency is truly the most important remaining issue to address.

> In Cellpond, I handpicked hexadecimal values for each channel so that the resultant colours would better fit my app's theme and needs.

Well, this is an admission that trying to balance "wiggle room" without too much "fussing" with 1000 colors didn't really work.

Evenly sampled in rgb space, a 1000 color palette yields neither enough flexibility (especially in the blacks, greys, whites), nor enough constraint to really make it dead simple.

For app development at least -- choose 20 gradations of blackish to whiteish; 8 gradations of an accent color and so too for a couple of secondary colors...and you're good. That's like 48 colors instead of 1000.

Result is ~12 tokens per second, as reported by OP down in these comments here.

An impressive effort, and better than I would have thought possible on this hardware -- but still pretty far short of what one needs for an satisfactory interactive session.

This is my daily driver laptop. It's pretty good for what it is. Runs Linux perfectly, not trying to be especially too fast, very nice pixel density, all metal case, sturdy build. Battery life is not the best. Beautifully compact.

In practice, my experience is that it's mostly a lose-lose proposition. You have to invest in learning a bunch of same-but-difterent framework apis to do what the language already does natively. And in return, the code is more complex, and harder to debug, and so it has more bugs.

We once hired a very smart fellow to build out a media processing pipeline. He did with rxjs, but it wasn't scaling well. We tried to get with the paradigm for a bit and help scale it up, but flame graphs in profiler output were all crazy, and it was a pain to wire in timing traces, etc. We built a POC imperative version just to prove that we could indeed achieve the throughput we thought we could, and then we just said, well hey, this is faster and simpler, so... let's just go with this instead. And so we did.

Come on, now. The human writes the plan up front, which includes guidance on testing strategy, classes of tests, particular test cases to cover, etc. And just like normal, of course you don't just ship the code without doing manual verification, code review, auditing the test cases, and all the rest.

It matters for at least a few reasons:

- Depending on the nature of your application, it may be very important to be able to audit the business logic and intended behavior. For compliance reasons, for operational reasons, for moral/ethical reasons -- you very well might want to affirm what the code is actually trying to do.

- A coding agent may get very creative in order to write code that passes a tightly-defined unit test. It may come up with approaches that technically pass, but work against the overall intention of the app in the first place. This becomes an arms race rather than a productive collaboration, where the agent's increasing creativity has to be matched by a sprawling test suite.

- Eventually, inevitably, business requirements will change, and the blob will need to evolve. It will be much easier for an agent or a human alike to understand how to safely make the change, if the existing implementation is transparent and understandable.

Well, my team does what we call vibe engineering.

You do ask hard questions up front, define boundaries, give lots of high level architectural guidance, declare interfaces, and bounds of abstraction... And then you ask the LLM to make it so, and it does. You give it the structure, and it fills in the implementation.

This is engineering, more or less.

Slate is just some renderings though, right? Is there anything actually real about it more than just marketing?

Many have succeeded writing functional alternative shells for sure, but none have replaced bash at any meaningful scale.

This could very well be a pattern that some teams evolve into. Specs are the new source -- they describe the architectural approach, as well as the business rules and user experience details. End to end tests are described here too. This all is what goes through PRs and review process, and the code becomes a build artifact.

Many, many people have tried...

Dial-up BBS checks all these boxes. Now have at it!

You are correct. But it's a ridiculous suggestion. Can you imagine the local corner store with a bulletin board, and some patron tacks up a picture of a swastika, and the owner of the store is not allowed to take it down?

You don't have a constitutional right to post on Facebook. When you invest your life into platforms run by for profit corporations, you agree to play by their rules. Merging state and big tech is not going to help.

Good stuff, except don't get too excited about `datalist`. It just doesn't have enough hooks to be actually useful for anything other than a little prototype.

What do you mean by open and closed? ChromeOS is based on ChromiumOS, which is open source. I guess macOS is based on Darwin technically, but the ratio of open source to proprietary is much higher for ChromeOS than macOS, no?

It's only one sliver of the problem here, but -- do you know how often I update my code editor? Like once every five or ten years, to the version that was released a year or two ago.

I do my own commits by hand so it's moot anyway, but there's a fair bit of "leopards ate my face" going in the GitHub thread.

Welcome to 2026, in which a browser is an operating system!

This tracks. Tasks that used to be a day or two of grunt work are now an hour with Claude.

And there is a lot of that type of work to do if you're trying to grow a business. But, something in there should be trying to be exceptional or else you have no moat. Claude will probably not be able to breeze through that part with the same amount of ease...

Average is all you need, if your needs are average.

> I sometimes wish I had never put my name on it so I could just take the money without harming my reputation, but I did, so I’m stuck with being honourable.

This distills down to: "I don't want to be honourable." They signaled right from the beginning.

> It just adds an extra layer of abstraction, which I happen to also find unnecessary.

Can't tell if you're talking about React or Tailwind

I like the big link to their Twitter profile at the top and bottom of that post!

Not sure if I actually want this (pretty sure I don't) -- but very cool that such a thing is now possible...

That is a lot of complaining for having no suggested better alternative.

And there is your answer to the clickbait title -- we're still using markdown because there's no alternative that is so much better that it is going to dethrone the one that has all the momentum from being the first good-enough take on this that got any traction.