nnevatie

Yeah, I meant this from the perspective that for example, I'd love to have that environment and approach in my sleeve, but utilizing C++ and all I have built using it.

BEAM/OTP are great, but do impose an exotic language onto the user. Most programs and solutions of today aren't Erlang-based.

Hmm, is SSIM a good metric for comparing fonts? I'd imagine it isn't ideal, as fonts are mostly textureless and SSIM has no concept of glyph identity or typographic intent.

Oh look. Another random and unneeded feature appears in their legacy tool.

That's it basically. I do not think running the tool in a container really solves the fundamental danger these tools pose to your personal data.

I think detecting patterns such as this could be done without fancy ANNs, perhaps based on lightweight statistics.

Hear, hear! I knew this is AI slop before opening the link.

"It's not X, it's Y" detected.

> generated a story

Was the story any good? The model used isn't comparable to something OpenAI would offer you today. What good is a fast gibberish generator?

> Why not just use bgfx with the language bindings instead.

For me the biggest obstacle would be the weird build system the project insists on using.

There are two schools to it.

On one hand, the original meaning of "agile" hasn't changed, as one could consider that immutable - and on the other hand, words do not have inherent meaning, they have usages.

I think that funnily enough, the "semantic diffusion" itself is an example of how such things happen. I wasn't aware of that label and certainly will not be adopting it to my vocabulary. Sounds like a very complex way of saying something has changed its meaning.

Agile existed in a vacuum as a manifesto, then it existed as a driver for cults/zealots of the ideology, then as a de-facto process, and now it's just watered down to something execs repeat when they want to say "our company isn't like a regular stiff corporation, but something more adaptable than that".

> One of the problems with building a jargon is that terms are vulnerable to losing their meaning

Nonsense. Your proposed "jargon" just didn't catch on. Also, language evolves way faster than most people realize.

Trying to shoehorn static semantics to software development is a losing game, I think.

Yes, it could be there's no impact from any of it. I just remember seeing the headlines about the change.

People are using past tense, as David S. Goyer is leaving the show behind.

Introduces a lot of lag on the mouse pointer.

Someone's going to be grabbed by the president?

Everyone has values, until they get punched with a billion dollar check.

> Who's going to pay your bills when the $20k is gone after 3 months?

And who's going to maintain this turd the LLM pushed out? It's a cool one-shot sort of thing, but let's not pretend this is useful as a real compiler or something anyone would like to maintain, as a human.

One could keep improving one the implementation by vibing more, but I think that's just taking you to the wrong direction of the rabbit hole.

I'd be very interested in seeing some statistics on what could be considered confidential material pasted on ChatGPT's chat interface.

I think the results would be pretty shocking and I think mostly because the integrations to source services are abject messes.

If you get the same speeds for C++ and Java, I'd like to point out that the C++ implementation is likely very sub-optimal.

This can obviously be true for toy problems, but tends not to generalize.

That's because when the failure becomes the context, it can clearly express the intent of not falling for it again. However, when the original problem is the context, none of this obviousness applies.

Very typical, and gives LLMs the annoying Captain Hindsight -like behaviour.

All aboard the soul tra…erhm…drain!

The format of the article comes across as AI-sloppy. Each section is filled with numbered lists and there are several AIsms, such as the omni-present "not-only-x-but-y".

Looks more like trimetric projection, but cool nevertheless.

The US will be the last casino he'll bankcrupt.

> It currently supports multiple flavours of x86 (SSE2, SSE4, AVX, AVX2, and AVX512), ARM (NEON), and Intel® GPU architectures (Xe family).

Yes, works well with AMD. You can compile multi-target so that you'll have e.g. SSE4.2, AVX2, AVX512 support built to your binaries and the best (widest) version is picked by the runtime automatically.

I found this a weird article.

If you wish to see some speedups using AVX512, without limiting yourself to C or C++, you might want to try ISPC (https://ispc.github.io/index.html).

You'll get sane aliasing rules from the perspective of performance, multi-target binaries with dynamic dispatching and a lot more control over the code generated.

I was looking forward to a post about designing sprites, i.e. little graphical blobs flying across screen. Needless to say, this was not it.