LLMs work by always predicting the next most likely token and LLM detection works by checking how often the next most likely token was chosen. You can tell the LLM to choose less likely tokens more often (turn up the heat parameter) but you will only get gibberish out if you do. So no, there is not.

Not necessarily: If they came out right now and said that games run great, it might build expectations that they can’t meet.

Supposedly Nvidia has become a lot better on Linux lately. They finally dropped their weird framebuffer API or whatever (the one that was the reason for horrible Wayland compatibility and also caused a heated Linus Torvalds moment), and I think they even made their linux drivers open source.

player_hand and dealer_hand are only [DECK_SIZE/2] in length, but in initialize_decks you write zeros into them unti [DECK_SIZE -1]. Since the arrays are located next to each other in memory you end up overwriting the deck array.

I think it makes more sense if you think about backend applications: If you write a Webserver with ExpressJS in typescript, you need typescript only to compile it (dev dependency) but once compiled, you only need ExpressJS in your node_modules for the app to be able to run (“regular” dependency).

Frontend development is a bit strange in that respect, because often everything gets bundled into your dist/ directory, so technically there are no runtime dependencies? In that case it’s more of a hint to let you know “this goes into the bundle” vs. “this is part of the compiler toolchain”

That’s Japanese not Chinese.

Looks to me like they’re trying to build something like office 365, but open source. Mostly by wiring other open-source components together I think?

This is probably a better starting point, unfortunately the text is in German: https://gitlab.opencode.de/bmi/souveraener_arbeitsplatz/info