Congrats for only reading the header ;) It's actually a pretty decent OpenGL 1.1 software implementation, obviously not complete and spec-correct though. It's more like those MiniGL drivers back in the day, implementing just enough of the spec so the game can run ;)
In a similar way, this implements just enough so Raylib's OpenGL backend can run! It was done so you can use the library without external graphics dependencies if you really want to.
No, the doc-header of the header! Apologies if I wasn't clear. I just thought the GP zoomed in on the word "-style" in the first line without reading more (it's probably since it's not a full 1.1 implementation, just something which can do enough to shim a good chunk of 1.1 functions so the RL GL1.1 backend can run)
Still, if you post a link to a roughly 5k line raw source file, rather than like, some post about it, roughly nobody is gonna read much of the file before commenting.
This is kind of a systemic problem with HN: all the early comments on anything substantial are necessarily themselves insubstantial because the posters have not had time to read it.
I know. I hold myself to a rule that I never comment if I didn't read the article.
I made an exception with this, because the "article" is simply a 5kloc header file. I only read some of it.
I don't have a problem with the submission but I don't know why you would expect someone to read enough of the header to realize that the opening line in the header saying "OpenGL 1.1-style" is underselling it and it's actually a "pretty decent OpenGL 1.1 software implementation".
I don't think making sarcastic remarks about someone failing to read enough of this header to work out that it's a pretty complete opengl implementation contrary to the implication at the start of the header is really doing much to fight the problem of people not reading articles before commenting.
Yes, that's arguably somewhat true of items like these:
Go Subtleties You May Not Know (harrisoncramer.me)
66 points by darccio 5 hours ago | flag | hide | 28 comments
Evaluating Argon2 Adoption and Effectiveness in Real-World Software (arxiv.org)
14 points by pregnenolone 3 hours ago | flag | hide | 1 comment
The Gypsy Life of Robert Louis Stevenson (hudsonreview.com)
37 points by Caiero 5 hours ago | flag | hide | 5 comments
That is, you might already be familiar with Robert Louis Stevenson's life story, Argon2, or the subtleties of Golang. Even if so, though, you probably won't be familiar with the book review in the current issue of the Hudson Review (of a book that came out last month), Cramer's particular take on those subtleties (which he posted two weeks ago), or even the Argon2 evaluation in the paper (which was posted in April).
I would argue that people posting comments in these threads consisting of only their pre-existing general knowledge of Stevenson and Argon2 are still failing to make substantial contributions to the conversation, because they will tend to repeat pre-existing errors whose correction is the largest contribution of the linked writings, or simply repost the predictable opinions they share with many other people. It's the opposite of the spirit of curious inquiry the site ostensibly seeks to foster.
And the majority of frontpage posts are about things that are in fact brand new:
Greenland Ditches Starlink for French Satellite Service (dagens.com)
323 points by saubeidl 4 hours ago | flag | hide | 189 comments
(news reporting from two days ago)
Knocker, a knock based access control system for your homelab (github.com/fariszr)
21 points by xlmnxp 2 hours ago | flag | hide | 29 comments
(new software project last month)
Evaluating the Infinity Cache in AMD Strix Halo (chipsandcheese.com)
90 points by zdw 6 hours ago | flag | hide | 33 comments
(news reporting from today on performance evaluations using an ASUS sample motherboard not available to the general public)
Show HN: Cadence – A Guitar Theory App (cadenceguitar.com)
55 points by apizon 5 hours ago | flag | hide | 8 comments
("Hello HN, I just released this music theory and ear training mobile app" a few weeks ago, with a trademarked name that will certainly have to be changed after a cease & desist)
MinIO (apparently) becomes source-only (github.com/minio)
144 points by LexSiga 5 hours ago | flag | hide | 107 comments
(a new release process change in this project from four days ago)
rlsw – Raylib software OpenGL renderer in less than 5k LOC (github.com/raysan5)
204 points by fschuett 14 hours ago | unvote | flag | hide | 69 comments
(a new software renderer committed on September 29)
LLMs can get "brain rot" (llm-brain-rot.github.io)
395 points by tamnd 20 hours ago | flag | hide | 245 comments
(a new paper published one week ago)
There is nothing substantial that anyone could say about any of these things without reading the article or bug thread or trying the software.
Portable multi-versioning is kind of hard to set up. E.g. compilers on Linux are not happy to emit AVX512 intrinsics when the architecture isn't enabled via -m... - this is also true for the case where you're trying to setup a dispatching system relying on cpuid, etc.
You missed that they gave an example that does work—Java Swing is bundled with the JVM, making it more or less part of the standard library. Python itself also has Tkinter, which exists inside the cpython repo and is installed with Python [0].
C++ may not work, but most other languages (especially VM-based) can and many do.
No it's not. But, the previous code was already effectively doing "c * c" for the last 15 years. So for now, just keep doing that, a bit faster.
A more proper way would be to do proper color-space aware luma calculation. Which under default settings is sRGB indeed, but not necessarily so (VSE can be set to operate in some other color space). Someday!
Yes, it's weird they used 2.0 in the original code too. Doing proper gamma for any regular space (sRGB, YUV Rec.705, etc.) isn't actually that heavy (even without LUTs).
My guess is that the code was written by someone in 1995 back when no one understood color spaces, or something (it's hard to track down who and when wrote it exactly due to all file moves and refactors etc.)
