News for hackers. Stuff that matters.

hgs3

Re:I know why Mathematicians weep on Thursday October 15, 2026 @02:13PM (#50107799)
And remember, these AI models were trained on your work, your culmination of effort and sacrifice, without any consent, credit, or compensation, then sold back to you for a subscription fee.
Re:The Double Headed Stack Allocator on Thursday October 15, 2026 @01:37PM (#50107202)
Interestingly, Quake 3 did use a double sided stack allocator as the article describes. The engine made one big allocation at startup called the "hunk." The "low hunk" allocated long-lived data and the "high hunk" temporary data. Search for "hunk" in this source file to see the implementation [1].

[1] https://github.com/id-Software/Quake-III-Arena/blob/master/c...

Re:I know why Mathematicians weep on Thursday October 15, 2026 @01:01PM (#50106672)
What an asinine comment. Do you think I, as a software engineer, am sitting around twirling my mustache, cackling as I plot to destroy livelihoods? I'm trying to make a living like anybody else. I've had my own opportunities lost to outsourcing and H-1B's since day 1.

The economist John Keynes predicted almost 100 years ago that technological advances would lead to a 15 hour workweek. If AI now makes you 5x as productive, then why aren't you working 1 day a week for the same pay? Why didn't Keynes' vision come true.

Re:Programming Isn't Special on Friday October 09, 2026 @03:00PM (#50025177)
Programmers don't need to justify code as art to reject AI. Programming is building and people who care about building do so because they take pride in the craft, because they take joy in mastery, because they are relentlessly curious, because they learn by doing, because they want to manifest the abstract because it's a natural desire to leave a mark, a legacy.

AI is the antithesis. You don't build, you commission. Mastery requires struggle, AI eschews it. Mountains of slop bury your handcrafted work, your culmination of effort, your capacity to inspire others as you yourself were inspired.

The reason you see less rejection of AI in tech circles is because tech is infested by capitalists who see programming as a means of extracting a buck, not as a craft. AI made their stripes more visible.

Re:C for Rust Programmers on Thursday October 08, 2026 @03:31PM (#50010840)
> I really love Rust's error handling. Result forces you to address errors ...

> C's error handling story, in comparison, is straight up tragic. It seems to boil down to functions returning a "magic integer" like -1 or a null pointer to signal there was an error.

In C23 you can add the [[nodiscard]] attribute to the declaration of an enum or struct type, then at every call site of every function that returns said type, the C compiler will emit a warning if the result is unused. Instruct the compiler to treat warnings as errors and you can't ignore them.

Interestingly, Zig's error handling is conceptually C like, but limited to integer-like enums (no structs). It's basically a union of error integer code and success result. However, despite being limited to integers, Zig has dedicated compiler machinery for this so there's idiomatic consistency in Zig error handling.

The 3rd U.S. Circuit Court of Appeals recently ruled [1] that using AI to train on a competitor's copyrighted material to build a competing product is _not_ fair use. This is a recent ruling (September 30, 2026). GitHub policy has surely not caught up yet and who knows when it will.

> Do you think I should look for a lawyer to deal with it outside the digital world?

Absolutely. This is a copyright infringement case and there is now an appellate precedent to cite. Gather as much evidence as you can and speak with an IP attorney.

[1] https://www.reuters.com/legal/litigation/unsealed-opinion-sh...

Re:Type Safe Generic Data Structures in C on Tuesday October 06, 2026 @02:20AM (#49974909)
Have you tried Objective-C? It’s Smalltalk-style OOP meets C. It’s also a strict superset of C, unlike C++.
Re:OpenLogi on Wednesday August 19, 2026 @01:52PM (#49364811)
> you trusted 22-year-old coffee junkies copying and pasting from stack overflow 10 years ago

Absolutely. There is a limit to how much code can be shared on stack overflow and, in the pre-AI days, code snippets had to be understood well enough to integrate into a larger hand crafted work.

Furthermore, stack overflow code is shared by consenting users and is licensed per the terms of service, unlike AI generated code which is trained on non-consenting users and is both ethically and legally dubious.

Re:Ask HN: Add flag for AI-generated articles on Monday July 13, 2026 @02:35AM (#48888723)
Can we also flag AI generated projects posted on Show HN?

I used to love reading HN for the handwritten articles and handmade projects, but in the LLM era the quality has deteriorated significantly. I find myself flocking to other message boards where LLM content is flagged, discouraged, or banned.

Re:AI Outperforms Law Professors in Stanford Law Study on Wednesday June 03, 2026 @02:41PM (#48388015)
> what’s left to get to is relatively small

Not necessarily. In many (most?) areas of tech the rate of advancement follows a logarithmic curve. That is to say, the first 90% is achieved quickly but the last 10% takes significantly more time.

I blocked AI overview because it starves websites of their own traffic and revenue.

Websites accepted Google scraping their content because it gave them a prominent blue link plus excerpt to drive traffic. Now everyone’s content is blended together and maybe, if they’re lucky, their site is chosen amongst the blend to get a tiny citation link.

Re:C constructs that still don't work in C++ on Monday May 25, 2026 @12:43AM (#48263454)
Not sure if you're aware, but defer is proposed for C2Y [1]. It's already available in Clang behind a compiler flag. It is interesting how the languages continue to diverge.

[1] https://www.open-std.org/JTC1/SC22/WG14/www/docs/n3734.pdf

Re:BBEdit 16 on Thursday May 21, 2026 @04:31PM (#48228503)
I think there is one major difference that separates the two eras: in ye olden days you bought software for a fixed price and while it's understood you might only receive updates for a limited time, you could continue using it so long as you had the ability to run it. For example, you didn't have to upgrade to Windows XP if you were satisfied with Windows 98. With subscriptions, it's a recurring fee to continue accessing the software at all.
Re:AI is just unauthorised plagiarism at a bigger scale on Thursday May 21, 2026 @03:16PM (#48227630)
Data is being licensed by AI companies, but negotiations are limited to those with the capital [1][2][3]. You write about "imbalance" but ignore that large firms can cut deals while small creators languish.

You seem to believe advancement only happens in the private sector while ignoring academic institutions and publicly funded research. You've dismissed the possibility of public models entirely.

You fail to consider that when you financially disincentivize individual creators from publicly distributing their work, you starve future models resulting in a world were data is licensed only to those who can afford it anyway.

[1] https://openai.com/index/disney-sora-agreement/

[2] https://openai.com/index/axel-springer-partnership/

[3] https://openai.com/index/openai-and-reddit-partnership/

Re:AI is just unauthorised plagiarism at a bigger scale on Thursday May 21, 2026 @01:41PM (#48226424)
> concrete steps

Start by legally compelling companies that trained on unlicensed data to either (1) license the data, (2) publish their model, or (3) destroy their model.

Re:AI is just unauthorised plagiarism at a bigger scale on Thursday May 21, 2026 @01:26PM (#48226223)
If models are trained on the collective whole, they must be owned by the collective whole. If you believe funding creators for the training of private models is too slow, inconvenient, or creates a global disadvantage, then embrace collective ownership.
How about forcing businesses to be owned by their employees [1]? Instead of taxing the owning class and being paid UBI peanuts, you become the owning class and reap the rewards directly.

[1] https://en.wikipedia.org/wiki/Worker_cooperative

Re:AI is just unauthorised plagiarism at a bigger scale on Thursday May 21, 2026 @11:48AM (#48224734)
How about requiring AI companies to pay creators for training rights? Alternatively, models trained on the commons must be owned by the commons. Right now these AI companies are trying to have it both ways: it’s The People’s Data for training on comrade but ownership is privatized.
Re:Is Show HN Dead? No, but It's Drowning on Tuesday February 17, 2026 @06:57PM (#47055228)
> In my opinion, for open-source projects, scoring the project's AI sloppiness based on the timeline of commits would be a good indicator.

You can’t necessarily judge by timeline. I’ve always developed my projects privately and then squashed to one initial public commit. I’ve got a private repo now with thousands of commits developed over years and I still intend to squash.

Re:SectorC: A C Compiler in 512 bytes on Sunday February 08, 2026 @01:17PM (#46936947)
Great read. It would be neat to see a mini operating system under 1 kb of code.
Re:We mourn our craft on Sunday February 08, 2026 @01:03PM (#46936841)
> We're on the precipice of something incredible.

Only if our socioeconomic model changes.

Re:Slop Terrifies Me on Sunday February 08, 2026 @09:38AM (#46934562)
Why is slop assumed inevitable? These models are plagiarization and copyright laundering machines. We need a great AI model reset whereby all published works are assumed to opt-out of training and companies pay to train on your data. We've seen what AI can do, now fund the creators.
Re:Slop Terrifies Me on Sunday February 08, 2026 @09:29AM (#46934482)
> It's called Universal Basic Income.

I'd rather we democratize ownership [1]. Instead of taxing the owning class and being paid UBI peanuts, how about becoming the owning class and reaping the rewards directly?

[1] https://en.wikipedia.org/wiki/Worker_cooperative

Re:We tasked Opus 4.6 using agent teams to build a C Compiler on Thursday February 05, 2026 @04:42PM (#46905790)
> As far as I know, there aren't any Rust based C compilers with the same capabilities.

If you trained on a neutral representation like an AST or IR, then the source language shouldn't matter. *

* I'm not familiar with how Anthropic builds their models, but training this way should nullify PL differences.

Re:Microsoft is walking back Windows 11's AI overload on Monday February 02, 2026 @11:12PM (#46866389)
I miss the Bill Gates and Steve Jobs days. At least there were positive improvements to Windows and Mac in those days.
> reflects the software engineering philosophies of the 1980s.

It has a microkernel architecture. That's already an improvement over the "modern" monolithic kernels we are stuck with today. Given Big Tech's interest in hardening security and sandboxing you'd think this would get more attention.

Re:Swift is a more convenient Rust on Sunday February 01, 2026 @12:38AM (#46843930)
> Apple being the largest sponsor of Objective-C would suggest that you get greater vendor lock-in out of it than Swift

Fun fact, you can use Objective-C on non-Apple platforms [1] and with Cocoa APIs courtesy of the GNUstep project [2].

[1] https://github.com/gnustep/libobjc2

[2] https://www.gnustep.org/

Why is there no C benchmark? The C++ benchmark appears to be "modern C++" which isn't a substitute.
Re:Why I Always End Up Going Back to C on Friday January 30, 2026 @01:22PM (#46827922)
I'm being pedantic, but on modern hardware, the ISA is an abstraction over microarchitecture and microcode. It's no longer a 1-to-1 representation of hardware execution. But, as programmers, it's as low as we can go, so the distinction is academic.
> it's been mostly static

In a well-functioning competitive market, no company should be able to rest on its laurels. The problem is industries have consolidated and trustbusters are nowhere to be found.

Notice when tech is new (the web, smart phones, AI) there's an initial burst of competitive companies? That's because the market hasn't consolidated yet. Ask yourself how many dot-com millionaires would realistically be able to duplicate their success in 2026, given the same product but launching today.

Aside from consolidation, discoverability is a huge problem, especially in the era of AI slop. Building a superior product is easy, getting it noticed and building traction is hard.

Older »