Silphendio

It's a 3 bit quant of Llama3-8B. I'm sure there are use-cases for that, but it's useless when it comes to tool calls or coding and I wouldn't trust it's factual accuracy either.

From the flatpak docs:

> A given branch of the Freedesktop runtime has a 2 year support period after which they are declared EOL.

You're right, I must have gotten that mixed up. Sorry.

I guess floats are still mostly deterministic if you use the exact same machine code on every PC.

You don't need to tun the whole game at a fixed framerate, only the physics. That's actually common practice.

The bigger problem is that floating point math isn't deterministic. So replays need to save key frames to avoid drift.

Quake used fixed point math.

Nim compiles to C, and it has a compiler iotion that does this.

Both of those flavors are based on the CommonMark spec. There's just some extra features and some forbidden html.

Choosing names like `App`, `ok` or `get` in a language without namespaces is a bold choice.

JSON 5 is pretty good. It just needs to make the top-level brace and all commas optional, and add proper support for multi-line strings (writing '/n/' at the end of every line doesn't count).

Allowing only valid JavaScript identifiers to be unescaped keys is also a bit quirky (You have to quote reserved keywords).

But they will never change any of that because it would break JavaScript compatibility.

I think the problems with big network were diminishing gradients, which is why we now use the ReLU activation function, and training stability, which were solved with residual connections.

Overfitting is the problem of having too little training data for your network size.

There's a German Wikipedia page: https://de.m.wikipedia.org/wiki/Coinhive

It does work on mobile,but the instructions are cut off.

And it doesn't play like normal solitaire. You can move any card, no matter what's on top of it. That makes it much easier.

I find json5 much better than json, but it has still many of the same annoyances.

- instead of trailing commas, how about making them completely optional? It's not like they are needed in the first place.

- curly braces for top-level objects could be optional too.

- For a data exchange format, there should really be a standard size for numbers, like i32 for integers and f64 for floats.

- parsing an object with duplicate keys is still undefined behavior.

At the very least, division by zero should not be undefined for floats.

Shouldn't it be `round(x/5)*5` ?

JSON??

I don't want to programm anything without comments.

I guess you can easily convert from use yaml or json5, but all the examples are still in json.

AFAIK a steam ban in this case just means that you can't buy stuff or activate keys anymore. You should still be able to play previously purchased games.

You can still make stuff that runs from the boot sector. You just won't have access to fancy graphics drivers.

I found this: https://github.com/nanochess/RayTracer

Child porn is already heavily "regulated". Producing the stuff is illegal and AI service providers must take steps to prevent it.

How useful is such a feature in reality? On smaller devices, the web brower almost always covers the whole screen, and even on big monitors, it usually touches at least one corner.

You mean searching for keys?

  $..book[[email protected]<10]

Yeah, I don't think javascript has that function in the standard library. Writing one is not super complicated, but having to put that into every file (or importing it) is not ideal.

  find_key = (data, key) => {
    if(data instanceof Array){
     return data.map(x=>find_key(x, key)).flat()
    }
    if(data instanceof Object){
     let res = Object.keys(data).map(x=>find_key(data[x], key))
     if(data.hasOwnProperty(key)){
      res.push(data[key])
     }
     return res.flat()
    }
     return []
   }

  find_key(data, "book").filter(x=>x.price < 10)

JSON Path:

  $.store.book[[email protected] < 10].title

Python:

  [x['title'] for x in data['store']['book'] if x['price'] < 10]

Javascript:

  data.store.book.filter(x=>x.price < 10).map(x=>x.title)

Someone did actually create a scripting language specifically designed to work with rust: https://rhai.rs/

I use the binary package because Ubuntu only provides a Snap, and that lacked some permissions I wanted (reading installed html docs).

It's worth noting that Stable Diffusion XL uses the OpenRAIL++-M License, which removed the update obligation.

If the schema allows union types, I don't want to deal with unquoted strings.

I thought this would be very simple to do, so I tried it. https://silphendio.github.io/word2vec_alchemy/

That simple demo took me way too long and all that time is wasted because word2vec simply sucks for this use-case.

Matplotlib isn't very friendly to casual users.

For even the simplest possible plot, I have to create a subplot and axis.

Sometimes I'd like to just plot a function. I don't want to initialize arrays for that.

It's easy to forget that I have to `import matplotlib.pyplot`

I don't need to plot things often, but whenever I use matplotlib, I always have to spend a few minutes to look up how to use it.

I really hate this article. They compared training ChatGPT to actual copy&paste sites without any supporting argument, complained about how much money OpenAI is making without paying them, and finished with blaming generative AI for the declining quality in Google search results.

It depends on the kind of game he wants to make.

If it's about 3D scenery or physics, I would recommend Godot. Just import some 3D models, place them into a scene, add lights and physics, and you need very little coding to have a simple 3D game. You can add complex logic and UI later on.

If the focus lies on UI, NPCs, combat, or inventory, I would recommend GameMaker instead. It's 2D, but it's made for that kind of stuff.

Have you thought about turning this into a linux desktop environment? It wouldn't even be the first Wayland compositor using Godot.