HN user

colejohnson66

9,950 karma
Posts72
Comments4,928
View on HN
unsung.aresluna.org 15d ago

I was wrong about Duff's device

colejohnson66
2pts0
github.com 2mo ago

Top why you should use std:SIMD

colejohnson66
4pts0
curves.xargs.org 2mo ago

The Animated Eliptic Curve

colejohnson66
1pts0
wadetregaskis.com 2mo ago

Claude Says No

colejohnson66
1pts0
www.windowscentral.com 4mo ago

I'm locking down updates until Nvidia's drivers and Windows gain back my trust

colejohnson66
4pts2
paultendo.github.io 4mo ago

96.5% of confusables.txt from Unicode is not high-risk

colejohnson66
2pts0
dannorth.net 5mo ago

The Worst Programmer I Know

colejohnson66
21pts2
posts.cgamedev.com 6mo ago

The Cost of Software Libraries

colejohnson66
4pts0
www.righto.com 6mo ago

Conditions in the Intel 8087 floating-point chip's microcode

colejohnson66
3pts0
theaidigest.org 6mo ago

What Do We Tell the Humans?

colejohnson66
3pts0
arstechnica.com 7mo ago

Apple hit with $115M fine for "burdensome" App Store privacy policy

colejohnson66
3pts1
www.windowslatest.com 8mo ago

Windows 11 update names drop YYYY-MM

colejohnson66
7pts0
www.eskimo.com 9mo ago

C Undefined Behavior

colejohnson66
16pts0
www.windowscentral.com 9mo ago

Microsoft blocks more Microsoft Account bypasses on Windows 11

colejohnson66
3pts1
www.phoronix.com 9mo ago

Linus Torvalds Lashes Out at RISC-V Big Endian Plans

colejohnson66
25pts9
www.joelonsoftware.com 10mo ago

Choices (2000)

colejohnson66
1pts0
changelog.complete.org 10mo ago

ARM is great, ARM is terrible (and so is RISC-V)

colejohnson66
3pts0
github.com 11mo ago

XSLT removal will break multiple government and regulatory sites

colejohnson66
160pts146
overreacted.io 11mo ago

Beyond Booleans

colejohnson66
1pts0
www.experimental-history.com 11mo ago

Bag of words, have mercy on us

colejohnson66
4pts0
arstechnica.com 11mo ago

Wikipedia loses UK Safety Act challenge

colejohnson66
2pts2
yosefk.com 1y ago

C++ FQA (2009)

colejohnson66
2pts0
mastodon.social 1y ago

C mistakes among the vulnerabilities present in curl code

colejohnson66
5pts0
utcc.utoronto.ca 1y ago

What is going on in Unix with errno's limited nature

colejohnson66
2pts0
jsgroth.dev 1y ago

Donkey Kong Country 2 and Open Bus

colejohnson66
265pts64
yurichev.com 1y ago

[Dennis Yurichev] was forcefully draften/enrolled to Ukraine army

colejohnson66
17pts23
harihareswara.net 1y ago

A Story About Jessica (2014)

colejohnson66
10pts2
hackaday.com 1y ago

RTEMS Statement Deepens Libogc License Controversy

colejohnson66
1pts0
lwn.net 1y ago

A Look at the Recent rsync Vulnerability

colejohnson66
3pts0
github.com 1y ago

Slopify – The Ideomotor Effect of Software

colejohnson66
2pts0

I should not need extensions for a business to respect my privacy. It's as simple as that.

If you look at it through an equity angle, needing extensions relegates the negative effects to those that are already not "well off" — the technologically illiterate who don't know what to do or know someone who does.

Why I forked httpx 4 months ago

I didn't mention IHttpClientFactory - just HttpClient. I will concede that ASP manages to be confusing quite often. As for the latter, guidelines are not requirements anymore than "RTFM" is; You can use HttpClient without reading the guidelines and be just fine.

Why I forked httpx 4 months ago

The boilerplate of not having sane defaults. .NET is much simpler:

    using HttpClient client = new();
    HttpResponseMessage response = await client.GetAsync("https://...");
    if (response.StatusCode is HttpStatusCode.OK)
    {
        string s = await response.Content.ReadAsStringAsync();
        // ...
    }

When we stopped paying for things. Seriously. If you pay for software, you can modify it. If you pay Google, they’ll modify it for you.

Yes, the EULA may prohibit modifications of local installations, but you’re not physically restricted from doing so - only contractually.

Somewhat. Stallman claims to have tried to make it modular,[0] but also that he wants to avoid "misuse of [the] front ends".[1]

The idea is that you should link the front and back ends, to prevent out-of-process GPL runarounds. But because of that, the mingling of the front and back ends ended up winning out over attempts to stay modular.

[0] https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00...

[1] https://lists.gnu.org/archive/html/emacs-devel/2015-01/msg00...