Live data from Hacker News

I think I found a Mac kernel bug?

jvns.ca

91–100 of 126 posts

Re: I think I found a Mac kernel bug?

#91
At first I remembered this and wondered if it was related:

"The rules for using Objective-C between fork() and exec() have changed in macOS 10.13. Incorrect code that happened to work most of the time in the past may now fail. Some workarounds are available."

http://sealiesoftware.com/blog/archive/2017/6/5/Objective-C_...

But seems like no, actually, at least not obviously.

Re: I think I found a Mac kernel bug?

#92
post #84

Earlier quoted context omitted.

[flagged]

No doubt, but by getting further into it like this, you blew it up by a lot and produced by far the least interesting thing about this thread. The internet is replete with opportunities for getting triggered and starting flamewars. For HN not to sink into a deeper circle of hell, we all need to resist these temptations. So could you and everyone else please not take HN threads on generic, divisive tangents in the fut…

I apologize for how this blew up, I did not anticipate that. I was trying to channel the guidelines similar to "it never does any good, and it makes boring reading", hoping HN could focus on the substance of the article, rather than the politics of whether or not it's okay to use "he" as a generic gender term.

It does get extremely boring to read on every article written by or about a woman someone correcting every comment that uses "he" as a generic antecedent, but in the future I will just ignore it instead of inciting a potential flamewar.

Re: I think I found a Mac kernel bug?

#93

I think High Sierra is the worst Mac OS release yet. I’m sure there’s a cognitive bias partially to blame (since it’s the most recent) but it looks like we are way past that.

10.0 was pretty bad - as in unusably bad. Like everyone I really miss snow leopard.

Re: I think I found a Mac kernel bug?

#94
post #53
post #28

Earlier quoted context omitted.

Thank goodness that Linux is consistent and has no bugs :-) Ubuntu still doesn't let me change my IP address to a static one via the UI and video drivers still crash or result in hours of googling and reading contradicting articles on how to change xorg.conf Software has bugs. Operating systems are hard. It doesn't matter where you will go, you will most likely deal with similar issues. Whether it be Linux, Windows o…

The difference is you pay a huge premium for Apple products, Linux distros are generally free (unless you want enterprise-style support). The same criticism applies to Windows - give it away for free and I might care less about crashes and the huge slide in quality over the last ~5 years.

You’re not paying for the OS; you’re paying for the hardware. If Macintosh hardware was buggy when running Linux or Windows, for reasons to do with, say, badly-written ACPI tables, then you’d have an argument.

As it is, it’s the opposite: Macs run both Windows and Linux “easily”, while other vendors’ buggy hardware has to be patched over with heuristics in these OSes because it has non-conforming device names, responses to introspection queries, etc. Apple hardware is uniquely well-engineered. If you’re writing your own hobbyist OS, it’s a breath of fresh air to run it on a Mac, compared to other kinds of PCs.

This is, coincidentally, also the reason it’s so hard to run macOS on other vendors’ machines. Windows and Linux paper over all the brokenness in hardware land, and so machines built for Windows/Linux rely on these heuristics with sloppy integration work. Apple, meanwhile, just does the integration to the standard in their hardware, and then relies on said standards-conformance in their OS. If everyone conformed to hardware ABI standards as well as Apple does, Hackintoshing would be a matter of just dropping a patched dont-steal-osx.kext into your install disc and calling it good. Everything else you have to do is the hardware vendors’ fault.

Re: I think I found a Mac kernel bug?

#95
post #84

Earlier quoted context omitted.

No doubt, but by getting further into it like this, you blew it up by a lot and produced by far the least interesting thing about this thread. The internet is replete with opportunities for getting triggered and starting flamewars. For HN not to sink into a deeper circle of hell, we all need to resist these temptations. So could you and everyone else please not take HN threads on generic, divisive tangents in the fut…

I apologize for how this blew up, I did not anticipate that. I was trying to channel the guidelines similar to "it never does any good, and it makes boring reading", hoping HN could focus on the substance of the article, rather than the politics of whether or not it's okay to use "he" as a generic gender term. It does get extremely boring to read on every article written by or about a woman someone correcting every c…

It's true, and a bit weird, that this happens even when one's sincere intention is just the opposite. It takes a bit of forethought to realize this in advance and avoid it. That's the skill we're most hoping to see become more widespread here.

Re: I think I found a Mac kernel bug?

#97
post #12

Earlier quoted context omitted.

I'm still not seeing it. Could you quote the relevant part?

I had to add ?33333 to the end of the URL, and reload, to bust the browser cache.

Might not just be the browser cache -- I use Cloudflare on my blog and have a script that uses the Cloudflare API to clear the CDN cache when I update the site, but the Cloudflare API doesn't appear to work 100% reliably and I'm not sure why. sorry about that!

Re: I think I found a Mac kernel bug?

#98

I think High Sierra is the worst Mac OS release yet. I’m sure there’s a cognitive bias partially to blame (since it’s the most recent) but it looks like we are way past that.

10.0 was pretty bad - as in unusably bad. Like everyone I really miss snow leopard.

> 10.0 was pretty bad - as in unusably bad

That's why they gave everyone free CDs with 10.1.

Re: I think I found a Mac kernel bug?

#99
post #88
post #79

Earlier quoted context omitted.

I'm happy to pay a premium to never again have to deal with xorg.conf. All platforms come with a cost.

FWIW, X configures itself nowadays and Wayland also just works. But I know where you are coming from. Everything audio related for example is still in very bad shape when you want more than Intel HDA.

Canonical is not of the same opinion, they just gave up on Wayland for the next LTS release.

Re: I think I found a Mac kernel bug?

#100
post #38

Earlier quoted context omitted.

The mach kernels in general are buggy, regardless of the release. e.g. I'm pretty sure they end up delivering SIGPIPE to the wrong thread in some circumstances on Sierra. There is also a problem with recvmsg not returning control messages some time. Another reason they killed OS X Server maybe.

They killed server because that was a losing battle: Apple was never going to "win" at servers. Despite all their effort they managed to score only a few modest wins, and the intense competition in that space made it a huge distraction. Remember Apple started down the "server" road decades ago with their A/UX UNIX server ( https://en.wikipedia.org/wiki/A/UX ). Throughout the 1990s you could get a high-end Mac spec'd…

Still it did fulfil a market, servers for Apple shops.

Now there is only Mac minis for it.

Post reply on HN