desdenova

Its slop, though.

Was it supposed to be scrollable? Because it doesn't scroll.

Also missing a slop warning.

Most of musl's performance issues come from their allocator. Using it with a third party high performance allocator allows you to benefit from static linking with very little performance loss.

Coding is not programming.

Typing code is indeed not the hard part, programming is.

This is closer to an open Sketchup than a Blender. I think they fill different niches.

You could've changed the setting that puts the button back on the lower left corner and saved your relative the trouble.

The new default is truly terrible, though, and this was the first setting I had to change when I was forced to use a windows laptop by the company I work in.

Wouldn't hurt if interactive elements didn't require me to zoom in order to interact with them on mobile.

Wtf did I just read?

The fact you started the text with is true: there aren't vibecoded complex apps, because vibecoding doesn't work.

The rest of the text is an incoherent rambling that looks like two people arguing and doesn't make any sense.

You should probably stop using gen AI and seek therapy.

The purpose of not wasting memory is so we have free memory to use productively.

What's the point of having 64-128GB of RAM if we're using apps that eat 10GB to do the same things we were doing 20 years ago using a few MB?

Believing something to be real that isn't is basically what psychosis means.

A very good alternative to this vibecoded slop.

It's slop though, which is even worse than the ads.

The fact someone who works on Bun is willing to create and even push a branch generated by a stochastic parrot is very telling of the direction the project is going.

Doesn't matter if it's "experimental", it's a dumb experiment that shouldn't exist.

> or can't be used (private projects)

As if they cared about that

The problem with floating point comparison is not that it's nondeterministic, it's that what should be the same number may have different representations, often with different rounding behavior as well, so depending on the exact operations you use to arrive at it, it may not compare as equal, hence the need for the epsilon trick.

If all you're comparing is the result from the same operations, you _may_ be fine using equality, but you should really know that you're never getting a number from an uncontrolled source.