Each have their trade-offs, both can support native compiled application code. Some architectures are easier to review and code in golang, but others go much better with Javas richer ecosystem and better composability.

Token use didn't seem to be a criteria from my casual reading, but maybe you can illuminate me what section pointed to that, I may have been too superficial in my reading

It's like they haven't maintained any actual software, because the criteria they choose is... Completely irrelevant?

The things that matter are tooling, orchestration and ecosystem - as well as how the LLM will actually implement the solution for a task

LLMs constantly do idiotic things. If you have good libraries to utilize, the likelihood of the solution actually working goes up because they no longer need to implement the hard part.

If you have orchestration for dependency injection, code generation, meta analysis etc

Tooling like the way otel tracing is integrated, openapi generation etc is also invaluable because every time the LLM does something the likelihood of it being hallucinated/wrong increases etc

You'd need to implement a nontrivial project in different languages, then add nontrivial features across them and only then start by rating eg correctness and incident occurrence after the final output

But token use on a one shot? Completely irrelevant as far as I see it.

If it was about the latter then I'd agree that there is no usecase for them

This may be a body camera or a camera built into glasses. That is a very legit usecase as far as I'm concerned.

There are other professions in which such a device would be a net benefit, that was just a simple example.

Fraunhofer didn't do licencing before joining up with Thomson. That's why - back in the 90s - there were no litigation anywhere even though everyone ignored their patents.

Then Frauenhofer joined up with Thomson and that's where your understanding joins up with reality: now the Frauenhofer does licencing and sues anyone that's not paying them.

My whole comment was a technical tidbit - maybe meaningless from today's perspective... But the previous view interpreted a forward thinking strategy with the monetization of mp3 that just wasn't there

Fraunhofer is a research institution. They didn't really do licencing, that's why they never went after anyone.

Then Thomson joined the venture (wouldn't you know it, French!) and the fun with litigation got started

Not trying to protect Frauenhofer there at all, if they didn't smell opportunity they wouldn't have teamed up with Thomson after all... But I think the trend is very clear. Germans are generally a lot worse at the litigation game then the french. Historically that makes sense, but it's definitely surprising that it still holds true in modern times

Which I may add: you could've easily found out yourself too if you looked up what I wrote.

(At least that's what people keep telling me, im not a lawyer)

as a german i feel the urge to point out that this technically also applies to european companies... With more hurdles for the US, but still technically applicable

i mean its neat from a minimalism perspective, but the decision to not ship with a regular installation UI in OG macOS X came with the tradeoff of not cleanly _uninstalling_ software either. config files etc were always left over.

but i guess - as Apple keeps locking down good old macOS X in favour of forcing software to go through the Apple Store this is going away as a sideeffect?

mate, if youre not using subscription then youre spending waaaaaaay more. the plan itself with fable/sol will most likely have already cost more then $80 -- ime thats more like 500-2k/day of usage.

most harnesses let you see the usage in the status bar, i encourage you to enable it

It really doesn't. Climate change is a global problem. It would need a global solution, and everyone should know that that's beyond unlikely to appear... So the only thing you can do is reduce local pollution - which is meaningful in it's way (better quality of life), but has no long term impact on the climate.

Did you read something into spwas comment he didn't actually say?

They generated lots of documentation across the whole stack and now makes all PO/BAs read it if it's correct. So not just 300 lines - he unironically generated thousands of lines of "documentation" and is now making hundreds of people review it for him

Complete brainrot

Au psychosis is getting seriously outrageous at this point

Thankfully I'm a dev and thus aren't in the blast radius of that genius idea

It's a utility to generate deduped/treeshacken css classes - according to a config file the parent mentioned

It's not some grand framework or something.

It's literally doing exactly what the grand parent said. Define root css variables, and generate the applicable/used css classes that were used in the code

Now you've successfully mitigated them

As an extra aside you can add a contributors guidelines there that contributions explicitly accepts the privacy notice, and then write in it that you will continuously subscribe all authors to all spam lists you can find and will publish SEO optimizees articles about them how they're a danger for employment etc