![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/e8842a5a-3702-4103-8102-b71875cd9eda.png)
ever notice how most of them look like a rectangle and have glass on the front?
ever notice how most of them look like a rectangle and have glass on the front?
the results are random therefore the dataset is useless.
tell that to any fpga toolchain
you released it under a non open source license. So very clearly: no it is not
it is only open source if i can build it myself. Which I can’t if you just give me the weights.
The weights are the “compiled” version of the dataset. It’s the dataset that’s the source, not the weights
even if that wasn’t the case, a 90% success rate is absolutely abysmal in practice.
cue the "one of our devs slipped and fell on a keyboard, completely coincidentally hitting all the right keys in the right order to code this. Completely coincidentally! "
that’s not how asymptotes work.
this has “draw the rest of the fucking owl” vibes to it. especially step 3
I will, in turn, be very thoutful about buying any of your games.
the fact that it was found by luck, not methodically, to me implies that there probably are other backdoors we didn’t get lucky with.
i dread the new expansion coming out later this year
how is this news. They’re called “general purpose processors”. You can literally run anything on them. It is even mathematically proven that they can do the job. This has been known for about a century now.
Heck, most raytracers run on the cpu…
lol. Of course there is. Ai cannot code. it’s a glorified autocomplete that mostly gets things subtly wrong. So you’ll spend more time trying to understand the code you didn’t write and look for any bugs, than if you had written and understood it yourself.
that doing more work, takes more time.
Gamers are especially guilty of this.
"that 2013 game runs at a smooth 60 fps. This medern game running at quadruple the resolution with raytracing sometimes dips to 58 fps on the same hardware. Devs must be lazy, they just need to add OPTIMIZATION to the game
i do use json instead of yaml precisely for the reasons you mentioned. That was my original point in the first place that json does not have these problems. something must have been lost in transmission
cut out a random piece of your document. is it a partial or a complete document?
paste it somewhere else in the document. you have to fix the indentation because if not then the document won’t work or mean something completely different
because of the cut and paste problem. It works in json.
write json with comments. Use a yaml parser.
note: on most computers, it worked the opposite to how one would think. Turning it on slowed your cpu to around 33 MHz