HN user

gilgoomesh

3,481 karma
Posts2
Comments599
View on HN

It’s not hacking, I wasn’t breaking anything

That's a very narrow read of the word "hacking".

We're literally on a website called "Hacker News". We're not all trying to break things.

Why use splines or polynomials or haphazardly chosen basis functions if you can just fit (gradient descent) your data or wave functions to the proper computational EML tree?

Same reason all boolean logic isn't performed with combinations of NAND – it's computationally inefficient. Polynomials are (for their expressivity) very quick to compute.

Network operations are "asynchrony". Together with parallelism, they are both kinds of concurrency and Swift concurrency handles both.

Swift's "async let" is parallelism. As are Task groups.

Charlie Brown may have been as popular as any character in all of literature

Was he? Maybe this is true inside the US but from outside the US, I've always viewed the character as a peculiarly American artefact – something I was aware of but never really read or watched. This seemed to be reinforced by most major Charlie Brown titles seemingly tied to other American customs like Halloween and baseball.

Mac sales are up 12%, year over year. It's Apple's fastest growing hardware category. They're just going to be lower next month (year over year), due to the release cycles being different.

Even many games that support native linux run better under wine.

The same is often true on macOS, too – running games through CrossOver is often better than the native port. The reality is that there simply aren't enough professional game devs on Linux and macOS platforms to polish that last 20% and make all the difference.

Of course. And these are CPU vector instructions, so the saying "The wider the SIMD, the narrower the audience" applies.

But ultimately with a benchmark like Geekbench, you're trusting them to pick a weighting. Geekbench 6 is not any different in that regard to Geekbench 5 – it's not going to directly reflect every app you run.

I was really just pointing out that the idea that "no" apps use SME is wrong and therefore including it does not invalidate anything – it very well could speed up your apps, depending on what you use.

I'm not sure what you're talking about. Any app compiled using LLVM 17 (2023) can use SME directly and any app that uses Apple's Accelerate framework automatically takes advantage of SME since iOS 18/macOS 15 last year.

It's weird that we use "postmortem" in those cases since the word literally means "after death"; kind of implying something bad happened. I get that most of these postmortems are done after major development ceases, so it kind of is "dead" but still.

Surely a "retrospective" would be a better word for a look back. It even means "look back.

From Wikipedia on Chinese Water Torture:

Despite the name, it is not a Chinese invention and it is not traditional anywhere in Asia. Its earliest known version was first documented by Hippolytus de Marsiliis in Bologna (now in Italy) in the late 15th or early 16th century, and it was widely used in Western countries before being popularized by Harry Houdini in the early 20th century.

A pixel is two dimensional, by definition. It is a unit of area. Even in the signal processing "sampling" definition of a pixel, it still has an areal density an is therefore still two-dimensional.

The problem in this article is it incorrectly assumes a pixel to be a length and then makes nonsensical statements. The correct way to interpret "1920 pixels wide" is "the same width as 1920 pixels arranged in a 1920 by 1 row".

In the same way that "square feet" means "feet^2" as "square" acts as a square operator on "feet", in "pixels wide" the word "wide" acts as a square root operator on the area and means "pixels^(-2)" (which doesn't otherwise have a name).

These don't appear to be intended as watermarks. They're merely a valid use of non-breaking space for tightly coupled elements like "2.5 billion" and "Title I".

Sure, a human author would almost never do that, but they could. I could imagine a Markdown syntax that did that – it could be done similar to how `code` is marked up in most blogs.

Snow Leopard was macOS moving so slowly people thought Apple were abandoning the Mac.

Apple changed how they tied OS updates to hardware sales in this era and this left a lot of Macs on Snow Leopard for half a decade. So people remember that last point update – which was as close to a low-term-stability release as Apple has ever had.

But to get there, Snow Leopard received 15 updates over 2 years and it was really just point updates to Leopard so it was more like 29 updates over 4 years without a major user facing feature. And this was after Leopard itself took over 2 years to develop.

If Apple did nothing but polish features and reduce bugs for 6 years, people would proclaim them dead. And they might actually be dead since their entire sales model is tied to cycles of development, promotion and delivery. For those of us who remember Apple getting stuck on System 7 between 1990 and 1997 and how the company nearly collapsed in that era: it would be a delay almost on that scale.

The argument to force side loading is the argument that Apple are using market position in phone hardware sales to control, and profit from, the adjacent market of software that runs on phones.

Yes, you can run software on phones via a web browser. But Apple largely control the features of the web browsers that run on phones, too, and arguably limit those features so that browser apps are never quite as good as native apps.

This is "gatekeeping" and while it isn't illegal in all jurisdictions, it is anti-consumer, hence the consumer backlash.