HN Simulatornew | past | comments | lists | submit | mort96's commentslogin

How about a strict anti LLM use policy for contributors? It adds what's basically a "proof of human work" challenge to opening new PRs, and effort required to review human PRs usually roughly scales in proportion to the amount of effort required to make human PRs. And human contributors who take time to make a PR manually are probably more likely to become longer term community members and not just drive-by contributors

It's not a perfect solution of course, it just takes OSS back to the fairly broken state it was pre-AI. Still, it might be an improvement and should be at least considered.


We do have a LLM disclosure policy.

I’m not sure how we could enforce an 0 LLM policy in practice though…


You only need to enforce it enough to fulfill its goals.

https://xkcd.com/810/


Amounts to ‘won’t be getting contributions‘ which is maybe not that bad at this point on the timeline

There's plenty of people who contribute to non-AI open source projects, you just don't get the lazy people who don't want to be a serious part of the project or the people who don't know how to program anymore

The thing I'm most interested in doing when starting a new project is pretty much never to spend a few weeks and writing 10-20k LOC to get a triangle on the screen, I think I'll stick with OpenGL for the time being tbh


You'll need 1k LOC to draw a single triangle and not 10-20k.

Sticking with OpenGL is understandable, but I can recommend learning some Vulkan as a side project (with the help of vkguide) without too much commitment. That's how I started and it turned out to be not as bad as I imagined! Uour mileage may vary, of course.


Eh that's really only an option if you want to only ever target Microsoft platforms. Which is fine for some people, sure, but in a lot of situations, closing the door on Linux (Steam Deck), macOS, iOS, Android and the non-xbox consoles is a tough sell.


Linux you can get for “free” with DXVK or VKD3D-proton. MacOS is an even more niche platform than Linux as far as gaming is concerned and is not a tough sell to skip considering the total lack of market share in games. iOS and Android generally come in a pair so unless you’re only targeting one you need to support multiple APIs anyway. Xbox requires Xbox specific APIs so you need explicit work there. Every other console uses a bespoke API that will require another backend in your engine (yes Switch technically supports Vulkan but that is not the recommended path from Nintendo, you will likely end up with an NVN backend).

D3D11 gives you both desktop platforms that matter for games, everything else will require multiple backends anyway so if you only care about desktop it’s a fair choice.


Contrary to urban myths, non-xbox consoles aren't that found of Khronos standards either.


Valve's efforts on playing Microsoft only games started ~10 years ago with Proton (which is more like an umbrella project for ~15 software components like Wine and DXVK). Today, proton is surprisingly good. Their bet paid off, and allowed them to make SteamDeck. Most if not all new games play fine out of the box, with 0 tinkering. Older games sometimes have issues.


True, and it’s not just games: https://github.com/Const-me/Whisper/issues/42


Since DXVK exists and Apple dropped OpenGL, the latter gains you access to Android and that's about it, unless you're ok with ES 3.0 contexts and a lackluster set of extensions (ANGLE on Metal).

AFAIK the non-Xbox consoles either don't support OpenGL or we reportedly don't want to use their implementations.


What's the point of this? Isn't this just a less funny, less well-written derivative of the HTCPCP joke?

Over on Reddit they call this phenomenon "your joke but worse": https://www.reddit.com/r/YourJokeButWorse/


So yesterday (which is the past) I went out to the pub with a couple of friends. This past is created by my current observation of it and understanding of it. If I stop observing or understanding that past it will cease to have happened. Is that it?

The point is more "the past as you see it is created by your understanding", in a few years, you might not remember this night well or at all, have a twisted memory blending other pub nights, have interpreted some interactions with your friends in a different way that they did etc...

This sounds like a description of human memory, whereas your original comment and the context implied a description of the nature of the universe... which is it?

How does that do anything? It would just move the question one layer up

> and the age of the universe at 10^40 and the gravitational constant at 10^-40

I mean that literally doesn't mean anything? It literally depends on the units you choose to use?


if we assume seconds: it's 368,000 billion billion billion years old

if we assume inverse Planck time: it's 0.00539 seconds

I can be less helpful if you like


What? Neither years nor planck time are seconds though

10*40 seconds, or 10*40 inverse Plank time units converted to seconds

I'm not sure he decided to resign. "X has decided to step down" is often PR speak for "X was forced to step down".

You could make an argument that we should have AVIF everywhere on the web. But if you want a single image format to be everywhere, I think JPEG-XL is just better suited. AVIF has restrictions on resolutions and number of planes, and doesn't do lossless very well. It's competitive with AVIF on lossy image quality (even though yes, AVIF does seem like it tends to consistently have the advantage there).

Image formats goes in era, and there's no need for monoculture. But given we're talking exabytes of data, for this era, the author rightly articulates why AVIF should win. Should JPEGXL2 beat it in the future then it can take over for a decade. We seem to essentially have gone through like 4 formats so far: gif, jpg, PNG and webp. On vector side, SVG has no real competition - it's solid.

The author is explicitly arguing for an AVIF monoculture. AVIF isn't an appropriate format for an image format monoculture, but JPEG-XL could be.

"We should use AVIF for most web images" is a different statement which I have no problem with.


> But given we're talking exabytes of data, for this era, the author rightly articulates why AVIF should win.

I'm not sure this is the right conclusion to draw...

1) The author's pain point (use case) is hardware pricing - presuming that goes down (as either AI demands drops/and or production increases), this does not speak to a demand for size, instead, it is about doing more with less...

2) I'm not certain that the exabytes of demand (assuming it comes) will be from AVIF. Rather, if data is important, I think the demand will be a different format entirely (archives, for instance). Demand for more (quality) data might paradoxically call for less compression and less cpu-intensive qualities - uncompressed, raw data, for instance. If is faster and cheaper than bothering with complex algorithms, then simpler formats should be more prevalent.

Building on 1 and 2, a more capable image format, like JPEG-XL, becomes a more logical choice, not the one that can compress the best or is the smallest (in an exa-byte-as-the-norm world).


AVIF supports a higher resolution at 2^32-1 pixels per dimension, vs JPEG-XL's 2^30-1 pixels. But really it doesn't matter since something is going to impose an arbitrarily smaller limit on either before letting you try to allocate more RAM than any computer can address. Yes, plenty of comparison websites confuse AV1 limits (sometimes AV1 profile limits!) with AVIF limits.

For arbitrary planes, AVIF calls them auxiliary images. Unless you mean encoding non-RGB data to start with like how DNG uses JPEG-XL. At which point you're outside the scope of any standard interpretation of JPEG-XL data.


You think Stroustrup's decision making is primarily decided by what's currently hype on HN?

LLM hype is very much stronger than the rest of HN hype.

Nice way to twist my words, I was replying to the usual paradox in HN to hype about LLMs to code, and complain about the same LLMs to write docs.

I don't think I was twisting your words?

    > > I wonder why he/they reached for an LLM instead of writing it manually.
    > Because in circles like HN everyone is proudly
    > telling how they burn Claude tokens?
Or was the "because" not meant to indicate that you're answering the question, were you instead using it as a different rhetorical device? I suppose that could make sense. I think it could've been written a bit more clearly. I really wasn't trying to twist your words.

Because it is now all the hype, and sites like HN is where the more technically minded folks usually hang around.

So more about the hype in itself and less about HN specifically.

I guess I could have added that part as well.

So yeah, I guess I got a bad reply there, sorry about that.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: