Demoscene Passivist retweeted
Actual curl rewrites in rust
> curl gets two Rust rewrites, but its creator argues that code is easy; sustaining decades of fixes, stability, and community is harder.
Demoscene Passivist retweeted
Both NeXT and 3DFX tried to “do the right thing” with color spaces, and it wound up generally making them look worse than competing options. I didn’t really understand it properly until years later.
It is natural to think that a pixel with a value of 1.0 is emitting twice the photons as a pixel with a value of 0.5, so you can do the obvious linear math to calculate partial pixel coverage, blending a foreground over a background, or interpolating between colors in a texture.
If displays are “linear”, that is correct. NeXT and 3DFX were much closer to linear than other contemporary displays. NeXT had crossover from the deep graphics understanding at Pixar, and 3DFX had the SGI heritage. They did this intentionally.
If you have 10+ bits per channel like the professional rendering systems, linear displays are The Right Thing.
Unfortunately, NeXTStation Colors were 4 bits per channel and 3DFX was 5 or 6 bits per channel, and there… it was not the right thing.
Human eyes aren’t linear intensity sensors. We mostly register relative changes in intensity, so we can tell the difference between 0.01 and 0.02 as a huge doubling, while 0.99 to 1.00 is almost imperceptible.
This distribution of intensities is often referred to as the “gamma” of the display system, but the actual curves like sRGB are a bit more complicated.
If you only have a small number of discrete pixel values, you definitely don’t want to spread them evenly from 0 to 1! If you do, you will have good precision in the brights, but very stark “intensity bands” in the dark colors.
If everything was authored specifically for 3DFX, you would still have the fundamental problem with the dark bands, but more accurate blending and filtering. The problem was that artists made all of their textures in paint programs on conventional non-linear displays, so when they were drawn by 3DFX cards, they got the characteristic “washed out color” look.
You can mathematically correct textures for differences in display gamma, but I didn’t really understand the issue back in the glQuake days, and we were so enthralled by the absolute performance of 3DFX that the color fidelity didn’t get as much attention as it should have.
Even today, tons of games don’t properly handle gamma across their textures and render targets. High resolutions and 24 bit color masks most of it, but you still see it in some slight shimmerings in high contrast textures and edges.
Demoscene Passivist retweeted
Anton @antovsky had delivered an incredible State of the Software address - if you’re programming and want to learn - give it a listen!!
youtu.be/mf4doUWkZz4
Didn't expect so many people interested in this, so I took this a step further, made it possible to interact with 3D objects, even though the fluid sim still runs on a 2D plane. #gamedev #vfx
Demoscene Passivist retweeted
AWS open-sourced AWS Emulator
> It's a local, open-source AWS API emulator (Rust) for testing without real AWS accounts, costs, or network calls.
github.com/aws/aws-emulator
Demoscene Passivist retweeted
Microsoft has a new tool to help you figure out what’s actually eating your GPU memory.
Called gputaskman, it’s a free, open-source project created by Microsoft VP Scott Hanselman. It works like an advanced Task Manager, but runs in your terminal with an htop-style interface.
It shows which processes are using your GPU, how much VRAM they’re consuming, GPU activity, temperature, clock speeds and power usage.
It also has some interesting features for AI users. It can identify loaded LLMs, their quantization, model weights and estimated KV cache usage, with support for Ollama and LM Studio.
github.com/shanselman/gputas…
Demoscene Passivist retweeted
UX latency is the most frustrating (lack of) advancement in computing over the last ~50 years.
IBM, way back in the 80s, found that user productivity shot up *exponentially* as system response time dropped. The "Doherty Threshold" was defined as ~400 milliseconds; the maximum amount of tolerable UX latency before interrupting user flow state.
It's unbelievable how many modern operating systems (*cough* win11) violate this threshold constantly.
Literally all you need to do as a Dev is pay attention. Add a "Doherty Threshold" to your test suite. There's so many different profiling tools, and especially with how good models are, really no excuse. Sure, some stalls are unavoidable, but that's when you pull out other UX tricks to at least give the illusion of responsiveness.
Crazy how much vintage computing hardware feels immeasurably more responsive despite having thousands of times less overall performance.
Demoscene Passivist retweeted
The realization of the large gap between production of bits (images, 3D models, lines of code, commits, etc.), and production of something which is economically valuable to people, will be a very rude awakening to many people.
Demoscene Passivist retweeted
Replying to @pikuma
One of my first 3D "epiphanies" that I remember was Magic Carpet. Not just the way it renders, but also that it's a spherical world with destructible terrain :)
youtube.com/watch?v=7umaSjvo…
Demoscene Passivist retweeted
I have been enjoying my free time learning how old games encoded their 3D object info (vertices, colors, terrain data, etc.). The last two games I explored had no z-buffer and did not sort polygons at run time (sorting is expensive). Instead, the 3D models themselves carry a tiny decision tree (BSP) that gives a correct back-to-front order for whatever angle it's being viewed from. I remember @kr1shty mentioning this was the case for DID's F-29 Retaliator, but I found out that that is also the case for Amiga's Zeewolf. Cool! I'll try to either write a blog post about this or dissect this one of my new courses.
Don't let billionaires convince you slop is the future. They're used to managing & directing, not making things themselves. Of course they can't see the difference. They don't understand your love for the craft. Keep making personal, beautiful games.
You've got my support 💖
Demoscene Passivist retweeted
live footage from anthropic office
We discovered a sophisticated recording device that was hidden inside one of our offices. We used our models to understand the device and where it had come from, identifying that a specific employee had planted it a few days earlier. We referred the matter to the FBI, and we’re grateful to the agents and prosecutors who moved quickly to make an arrest. The FBI’s investigation is ongoing and we will continue to support their work.
At this time, we have no indications of this individual inappropriately accessing or exfiltrating model weights, source code, or customer data. The employee was terminated.
We take protecting our technology, data, and people seriously, and as a matter of national importance. Our security program is designed to protect against a wide range of threat actors, from insider risks to cybercriminals to nation states, and this case is an example of how AI can help address these sophisticated security threats.
Demoscene Passivist retweeted
We're excited to announce Zeiger! a fast, free image viewer for Windows and macOS, from the Blick team. Now in public beta.
Sharp pixel zoom, quick edits, a color picker, EXIF, GIF scrubbing, and more!
Completely FREE for personal and commercial use, link in comments.
Demoscene Passivist retweeted
Blick 0.3.0 is out with a full-fledged keyframe curve editor.
Bezier handles, easing presets, a curve per axis, and dope sheet, curve or combined views.
Also new: audio recording, keyframeable text, and a command palette that finds settings.
Get it here:
blickeditor.com/download





























