fallat

They really were the sleeping giant and I think everyone understood that - OpenAI especially, hence their need to scale up hardware as much as physically possible. Google is trying their best to keep their heads down and focus on their lane. It's starting to pay off, but I'm sure they've felt the heat more than once.

Yep. You've nailed it

Hahahahaha, nice one!

The standard library is lacking some really nice conveniences. I'm working on correcting this and teaching Forth as a "grassroots" language for people who want to go back to the joy of programming as an art. The 100rabbits folks have already done a lot of work around proliferating that idea but I want to work outside of the Uxn machine that they use. Mark my words, us programmers are not phased by AI stealing the joy of programming :) The day job business programming, sure. But that was only fun sometimes. Forth will continue to exercise our brains and work through logic and data flow problems - skills we can bring to guiding agents for the day job.

For some... that is sadly a better existence in cases.

'Ey 'ook 'e' 'obs!

In a sense pixels arent even real today right? It's an abstraction

> CRAP1(m) = comp(m)^2 * (1 – cov(m)/100)^3 + comp(m)

and

> Here’s why we think that CRAP1 is a good anti-pattern to detect. Writing automated tests (e.g., using JUnit) for complex and convoluted code is particularly challenging, so crappy code usually comes with few, if any, automated tests.

This is so wrong.

The formula uses code coverage as a fundamental metric, when in reality, a lot of people write code "correct from construction", so coverage is not even applicable. Many times too, people only care the use cases they care about work perfectly.

There are also many other reasons code is not tested, not because it's complex, but because it's simple.

such a garbage post for various reasons, but the ending is the kicker

after making SEVERAL observations that cadquery is pretty much better overall, they say "ehhh we're going to stay with openscad".

Major market gap for sure.

Someone will have to explain the value proposition to me...

We have git.

jujutsu works with git.

git can do everything jujutsu can do (otherwise, jujutsu couldn't work with git).

Thus, jujutsu is a UX / new steering wheel.

ERSC is trying to be a GitHub competitor with what surplus value?

Don't get me wrong, GitHub has a slew of its own problems, but I have not seen any commentary on how ERSC addresses any of the downfalls GitHub has too. We're jumping from one frying pan into another, currently-cooler one?

What about SourceHut? Codeberg? They could offer the same steering wheels.

Edit: Thank you to everyone who replied. The enterprise/teams infrastructure angle makes sense.

Brutal

I hope when people read this though they understand this is a communication style; they're clearly trying to strongly discourage people from thinking they are suddenly protected. Effective? Maybe at one time, where "macho dev energy" was a thing. Today, not so much. You can tell they mean well because the intro sentence is actually pretty cheeky!

This is the strongest argument I've seen against CLI for LLMs. Thank you.