Hacker News: pmarin

New comment by pmarin in "Wolfram Language and Mathematica version 15"

pmarin — Wed, 17 Jun 2026 11:09:47 +0000

It used Maxima many years ago.

New comment by pmarin in "Port React Compiler to Rust"

pmarin — Wed, 10 Jun 2026 13:05:05 +0000

The arena is replacing the javacript garbage collector not memory managament.

New comment by pmarin in "Android developer verification: Balancing openness and choice with safety"

pmarin — Sat, 21 Mar 2026 07:25:06 +0000

WHy not just add a hardware switch to allow Android sideloading?

Are these multibillion companies so incompetent to not think about it?

New comment by pmarin in "Separating the Wayland compositor and window manager"

pmarin — Sun, 15 Mar 2026 18:54:04 +0000

I am sorry if I mistaken you for a bot but the model you are describing have not been implenented by any graphic driver in decades.

New comment by pmarin in "Separating the Wayland compositor and window manager"

pmarin — Sun, 15 Mar 2026 18:40:52 +0000

Just to be clear the hardware abstraction layer used by wayland and any current Xserver is exactly the same.

New comment by pmarin in "Separating the Wayland compositor and window manager"

pmarin — Sun, 15 Mar 2026 17:51:45 +0000

>i don't think it has a huge impact on the discussion here. but this is such a key difference versus X, that i think is hugely under-told: Wayland compositors all rely on lots of kernel facilities to do the job, where-as X is basically it's own kernel, has origins where it effectively was the device driver for the gpu, talking to it over pci, and doing just about everything. when people contrast wayland versus X as wayland compositors needing to do so much, i can't help but chuckle, because it feels like the kernel does >50% of what X used to have to do itself; it's a much simpler world, using the kernel's built-in abstractions, rather than being multiple stacked layers of abstractions (kernels + X's own).

Are you an AI bot? Modern X11 server using DRM are more than 20 years old. You are talking about how X11 servers worked in the 90's

New comment by pmarin in "Nvidia Stock Crash Prediction"

pmarin — Tue, 20 Jan 2026 21:57:55 +0000

I don't think is about China, it's more about Winnie the Pooh's legacy.

New comment by pmarin in "Is Rust faster than C?"

pmarin — Wed, 14 Jan 2026 16:12:18 +0000

The C way is to avoid abstractions in first place.

New comment by pmarin in "Is Rust faster than C?"

pmarin — Wed, 14 Jan 2026 16:08:49 +0000

C++ compile time execution is just a gimmicky code generator, you can do it in any language.

New comment by pmarin in "Don't fall into the anti-AI hype"

pmarin — Mon, 12 Jan 2026 07:50:21 +0000

That sound more like software pseudo-engineering to me.

New comment by pmarin in "Some surprising things about DuckDuckGo"

pmarin — Sun, 14 Dec 2025 06:23:56 +0000

How many people know about https://lite.duckduckgo.com/lite/ ?

Is a version of DuckDuckGo without Javascript. Very fast and compatible with minimalistic web browser like lynx.

New comment by pmarin in "Super Mario 64 for the PS1"

pmarin — Thu, 11 Dec 2025 11:05:43 +0000

That sound more like a demake than a port. Very cool anyway.

New comment by pmarin in "APT Rust requirement raises questions"

pmarin — Tue, 25 Nov 2025 18:16:02 +0000

20 years on Debian. Not a single crash with apt

New comment by pmarin in "Gnome Mutter Now "Completely Drops the Whole X11 Back End""

pmarin — Wed, 05 Nov 2025 17:06:29 +0000

I don't use a compositor in XOrg.

New comment by pmarin in "rlsw – Raylib software OpenGL renderer in less than 5k LOC"

pmarin — Wed, 22 Oct 2025 11:45:08 +0000

Win32 has already a pretty good opengl 1.2 software renderer.

New comment by pmarin in "XScreenSaver for Android • Privacy Policy (2024)"

pmarin — Wed, 19 Feb 2025 16:49:54 +0000

Archive.org because jwz doesn't like HN.

He updated it later on:

"Update: On June 8th, 2024, I submitted this privacy policy to Google, and on June 10th, they accepted it. I take this to mean that they found it to be 100% factual and endorse it entirely. XScreenSaver was restored to the "Play" [sic] store, and people were able to again downloaded and enjoy it freely.

But then!

Barely 6 weeks later, on July 24th, 2024, Google instituted yet another new policy: basically they told me that if I didn't give them a sample of my blood a copy of my driver's license, they would remove XScreenSaver from the "Play" [sic] store, again.

Obviously that's never going to happen. Do I, the person who wrote the above list cataloging Google's various predations, seem like the sort of person who would willingly give Google my private details? On purpose? I do not think so.

Having distributed XScreenSaver for over a decade to I-don't-even-know-how-many users (I actually don't know, I never looked) Google suddenly decided that it was a huge problem that they don't have a lock of my hair.

Since I enjoy wasting the time and money of multinational superpredators, I spent a few weeks going back and forth with what passes for developer "support" over there. You can read about it over on my blog. Eventually they just started ignoring my emails, and in November 2024, XScreenSaver was again de-listed from the Google "Play" [sic] store, presumably this time for good.

However, we can take solace in the fact that Google endorsed the above privacy policy, and found no fault with it whatsoever."