Hacker Newsnew | past | comments | ask | show | jobs | submit | pmarin's commentslogin

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


The C way is to avoid abstractions in first place.


Yet it is one in itself, otherwise UNIX would still be written in Assembly.


Assembly itself is an abstraction. UNIX should have been written in machine code.


It was until version 4, when the C rewrite took place as it wasn't fun to keep writing it in Assembly.


Assembly code != machine code


Depends if you have an Assembler at hand, or a plain hexdump monitor, hopefully with a checksum entry on each row.


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


Yeah, I could also be writting in a macro assembler for some Lisp inspired ideas and optimal performace.


That sound more like software pseudo-engineering to me.


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.



I used it on my really old dell laptop with tinycore 32 bit and dillo

Awesome stuff.

I was able to run modern firefox on that 1 gb puny laptop too but it took 800 megabits of ram but I was able to run https://pomodorokitty.com/ on it.


What's up with all the space waste, the search button is almost as big as the input box, so you can't fit a long query on a phone (and the query box doesn't expand to fit more than one line)


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


A demake would be a reimagining of a modern game into the style and aesthetics of the time. E.g. taking God of War and turning it into a 2D Shinobi-style platformer for Sega Genesis. Or turning Gran Turismo into a Mode7-style racer on SNES.

In this case, the creator wrote a custom 3D renderer and recreated the models/meshes to get as close of an approximation of the N64 experience onto the GBA.

I wouldn't call it a port necessarily ("recreation" seems more apt), but it's closer to that than a demake.


20 years on Debian. Not a single crash with apt


Almost 30 years for me, both on my personal machines and at work.

I went through a period about 25 years ago where apt crashed on my (rather janky) desktop almost every other run, and sometimes left my system in a state so inconsistent that I had to fall back on 'dpkg-reconfigure --force' and the like to fix it.

Turns out that it was due to a bad interaction between a failing stick of RAM and reiserfs' tail-packing feature, which was causing frequent silent corruption in /var/lib/dpkg/status and friends.

I don't think I've seen any similar issues since, across what must be many millions of apt runs I've been responsible for.

Perhaps gp is suffering from some similar underlying problem?


I don't use a compositor in XOrg.


Win32 has already a pretty good opengl 1.2 software renderer.


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."


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

Search: