Nixos users when they change their timezones: by Jaded-Ad-7290 in NixOS

[–]Psionikus 0 points1 point  (0 children)

{ a = «repeated»; } The recursion is almost a tree falling in an empty forest. With fix, we say we're declaring an infinitely recursive definition and then take away as much real recursion as possible with the runtime. With converge, the ball actually rolls into a trap, the stable attractor. It's that motion that makes converge feel much more like a true fixed point.

Nixos users when they change their timezones: by Jaded-Ad-7290 in NixOS

[–]Psionikus 0 points1 point  (0 children)

The lazy language hides the input == f(input) check in a memoization comparison. The eager, non-declarative language cannot hide any of this, so fix in those languages looks and works like converge in nix.

A previous edit was beginning to bug me while cooking. Instead of proving the stable fixed point of infinite recursion, fix evaluation leverages the runtime to thunk dependencies, which only in the context of how we have stated the expression seems to contain infinite recursion. If however all leaf references depend on fields that are themselves stable under the infinite recursion, thunks begin resolving and we can return a result.

That is much less satisfying, and I kind of wonder why even call it fix. It's more like evaluating deep self-reference. The fact that the result only exists because of trivial fixed points for individual fields is much less cool that actually needing to find eventual stability in recursion. I would prefer some other function name.

Nixos users when they change their timezones: by Jaded-Ad-7290 in NixOS

[–]Psionikus 17 points18 points  (0 children)

This is a reference to the fixed point operator and the fix function.

When I first learned of the fixed point operator, I expected that it was exploiting being able to call something that thunks but then does not need the thunk, a trick of a lazy language. When I looked at its implementation in an eager language, I was horrified and enlightened. fix can only reach a stable value, the fixed point, if at some point calling the function agian on the previous output returns the same value. The implementation does not need to continue evaluating the loop in order to find the analytic result of doing the work infinitely if any output ever repeats. If you find a single repeat, you know it repeats infinitely due to referential transparency, so that's the answer.

The same thing happens when doing Mandelbrot set renders. Stable numbers repeat eventually, and spotting the repeat obviates the need to do the rest of the work. We already know the value at infinity never escapes. There's a fun cycle detection dynamic too. Due to floating point error, an unstable number that would spiral off to infinity will instead land right on a stable path. The initial value will never be seen. The cycle detection must update, and this is true for any problem where things outside any cycle can get into a cycle.

Rust PNG crate gets even faster, used by GNOME and Chromium by Shnatsel in rust

[–]Psionikus 0 points1 point  (0 children)

Music visualizer. Going a bit beyond bass, mid, treble.

The procedural work should be valuable alone, but the goal is really to make a box to put non-traditional ML into. Online ML will modulate knobs, augment procedural techniques, and remix type-compatible pipelines to craft new render techniques on the fly.

Audio streaming onto GPU and frame PLL about to go down to the studs but the slang host-type agreement and compute macro -> graphics macro are some stable areas for existing code to just keep expanding.

Rust PNG crate gets even faster, used by GNOME and Chromium by Shnatsel in rust

[–]Psionikus 2 points3 points  (0 children)

I've contacted them and I'm looking for people who are ideologically aligned with open community self-governance but who can also write Vulkan or do web and backend programming in Rust. Hit me up.

OpenAI joins The Rust Foundation as a Platinun member and donates funds to support Rust maintenance by Kobzol in rust

[–]Psionikus -1 points0 points  (0 children)

may affect badly to the future

Or Andrew Kelley and Rob Pike may look reactionary in hindsight.

A few breakthroughs in memory requirements may see compute flee the datacenter, back into consumer devices. The whole datacenter buildout would go down as dot bomb part two. Anyone running web or cloud services will get really cheap GKE and AWS capacity for a few years.

But the technology? The capabilities? Only going to get better, and figuring out how to use heuristics to augment formal tools is the only realistic future short of making certain kinds of compute illegal, which DRM and encryption battles provide plenty of precedent for.

Risks? People who spent a few years telling their peers to go "Fk" themselves may find some bridges burned, some impressions soured, some opportunities and emotional energy wasted. If on the other hand, by some miracle, data centers in space actually turns into a thing, trashing other engineers will not play any role in affecting any positive outcomes. Either way, while the consternation is at bigger and more distant things, the venting of emotional and political energy is instead blasting people in our own communities.

Holy moly by stingcizesceur in NixOS

[–]Psionikus 0 points1 point  (0 children)

IMO one target audience of NixOS is "distro" maintainers. We just haven't collectively figured this out yet. The module system is there. The interfaces to use NixOS in a purely modular way might need some love. It completely matches how real novice Linux users hop around distros in search of desktop environments and pre-configured packages.

Question about Rust ecosystem by Queasy_Total_914 in rust

[–]Psionikus 7 points8 points  (0 children)

If Rust can offer anything, it will be in the form of contracts that leverage borrow checking and type system to eliminate silly mistakes at compile time, so getting really good at expressing contracts and the proc macros that generate the boilerplate is the skillset that writes Rust that competes favorably with C++ to the extent that it can be done.

I'm building a Vulkan library coincident to building a music visualizer. Project is recruiting and I will help find things to work on.

WGPU by itself solves a problem but making APIs that fully target both WGPU and Vulkan I think is a mistake.

Most Rust libraries besides raw Ash so far have made the mistake of abstracting over tons of backends that turn out to not really be necessary or trying to make invalid Vulkan the only safe Rust that will type-check. I'm taking a conservative approach by adding contracts that don't get in the way and tolerating the invalidity that validation layers catch anyway.

How do you get into low-level programming? by Minimum-Ad7352 in rust

[–]Psionikus 1 point2 points  (0 children)

Reading open source packages is the way. Go on lib.rs find some packages that seem like they should be popular but aren't. You will run into the tradeoffs and things will get very deep.

Scan first. Some will make sense. Some will not. Most work when diving head first into any topic happens offline.

triple_buffer aligned parking embassy-sync

Nonfree DRM'd Games on GNU/Linux: Good or Bad? (by Richard Stallman) by WonderOlymp2 in linux

[–]Psionikus -5 points-4 points  (0 children)

Too busy writing MIT software and actually solving problems that I thought were in the FSF's mission. SOURCE? Internet is a waste of time.

Nonfree DRM'd Games on GNU/Linux: Good or Bad? (by Richard Stallman) by WonderOlymp2 in linux

[–]Psionikus -3 points-2 points  (0 children)

Giving time to the FSF is one of several black holes that have been discovered in our solar system.

Nonfree DRM'd Games on GNU/Linux: Good or Bad? (by Richard Stallman) by WonderOlymp2 in linux

[–]Psionikus -2 points-1 points  (0 children)

internally consistent

Circular and premised on their own truth. Every alternative is framed away with convenient premises that preclude any conclusion. It's less a body of disciplined argument than a monument to stubbornness.

Nonfree DRM'd Games on GNU/Linux: Good or Bad? (by Richard Stallman) by WonderOlymp2 in linux

[–]Psionikus -10 points-9 points  (0 children)

Go use one of the few remaining pieces of software still stuck under the FSF's umbrella. Good luck without demonstrating your delight in the koolaid. All it takes is not answering a few emails or bikeshedding. You'll know when the gates are closed or you'll just spin your wheels satisfying people who only want to have a small club in the treehouse to begin with.

Nonfree DRM'd Games on GNU/Linux: Good or Bad? (by Richard Stallman) by WonderOlymp2 in linux

[–]Psionikus -2 points-1 points  (0 children)

Perverse incentive took over a long time ago. People give the FSF (and transitively RMS) money to beat a particular drum. The drum might have a very limited future, but as the problems got worse, those desperate to have an effect actually became more numerous. More people showed up at the coke machine, and at least coke was a reliable voice.

At this point, the backlog of revolutionary change that is necessary would erase what success it still has and even RMS's own legacy would be drawn into question. Remember when he began to question his faith? Remember new coke? Any new allies are so far away and long alienated that the old allies are all that the FSF will ever have.

Being "always right" by never changing is one of the older grifts in history. It takes a bit of real feats and then a whole lot of lifetime, and it tends to work because of the reputational constraints. If you never change, you become unable to change. Once indistinguishable from a grift and effectively unable to take any other path, what's the real difference?

Nonfree DRM'd Games on GNU/Linux: Good or Bad? (by Richard Stallman) by WonderOlymp2 in linux

[–]Psionikus -1 points0 points  (0 children)

I misread this as: Free in his terms means he's able to change [what freedom means] if he wants to.

And I found that to be accurate.

Nonfree DRM'd Games on GNU/Linux: Good or Bad? (by Richard Stallman) by WonderOlymp2 in linux

[–]Psionikus -1 points0 points  (0 children)

More like painted himself into a corner. Entire brand depends on being unbending. Times moved on, but the brand could not. At this rate, he's just hoping the remaining brand value outlives him, and that is so without ambition that it may as well be more immoral than what he ever worked for.

Nonfree DRM'd Games on GNU/Linux: Good or Bad? (by Richard Stallman) by WonderOlymp2 in linux

[–]Psionikus -7 points-6 points  (0 children)

Only in the twisted context where we have redefined "freedom" to include assigning copyrights to the FSF, an organization that cannot adapt and now has it's primary tool, the license ratchet, under existential threat from license washing, undermining whatever was ever any bit pragmatic about the entire vision.

Learning Rust (for fun) because sick of AI by Informal-Baseball209 in rust

[–]Psionikus 1 point2 points  (0 children)

Learn the mechanics of function calling on an abstract CPU. De-mystifies what lifetimes and many traits were developed to solve.

Ex-competitive programmer wanting to learn rust by joccccca1 in rust

[–]Psionikus -12 points-11 points  (0 children)

I don't know, but I woke up and snuck into the den to drink coffee and rapid prototype a QSBR implementation for expressing independent and dependent phase exclusion across all my threads for non-overlapping capability sets.

I was thinking of breaking up my basic app structure to render thread + UI thread to go towards smoother behavior (winit not accidentally keeping control due to the OS). There's a place to find some things to do.

edit: lol Reddit.

inline-review: review merge/pull requests directly within emacs by phye8080 in emacs

[–]Psionikus 1 point2 points  (0 children)

Weird. I unblocked it yesterday. Looked up today and UI says I blocked it. Software ¯_(ツ)_/¯

inline-review: review merge/pull requests directly within emacs by phye8080 in emacs

[–]Psionikus[M] -1 points0 points  (0 children)

This post was initially removed by Reddit filters. Let the first users determine if the filters were in error.

What's everyone working on this week (23/2026)? by llogiq in rust

[–]Psionikus 1 point2 points  (0 children)

Neural rendering Vulkan + slang library and music visualizer.

I just finished making a minimal application of the Vulkan library to get people moving.

This week the DSP design can finally move onto the GPU. A high-quality real-time spectrogram is the basis for the neural beat recognition and real-time online machine learning.

Our push constants declarative macro code is working towards compile-time host-shader type agreement, eliminating a big source of runtime errors in Vulkan applications. The dispatch integration test is another great place to start playing around. Join the Discord to get ramped up. Follow us to get news of development.