Live data from Hacker News

A Higgs-Bugson in the Linux Kernel

blog.janestreet.com

11–20 of 58 posts

Re: A Higgs-Bugson in the Linux Kernel

#12
post #7
post #4

> A higgs-bugson is a bug that is reported in practice but difficult to reproduce This was the first time I heard of "higgs-bugson". The term sounded so forced that I had to know how it differed from Heisenbug. In short, it doesn't[1]. Then why did it even exist? The term somehow made it to the "Heisenbug"'s Wikipedia page[1], so I checked the sources. There were two and both end up at the same site: Jeff Atwood's bl…

> because he wanted to remove lighthearted content from the site as he thought it clashed with SO's mission of educating people and advancing their skills[3]. No; he wanted to remove discussion and socialization , because it clashed with SO's mission of presenting useful information without parsing through others' discussion . https://meta.stackexchange.com/questions/2950 https://meta.stackexchange.com/questions/1966…

> why should they be interpreted as representing a "downfall"?

I agree, but also SO has certainly gone through ups and downs. It does feel as though it's now in a terminal "down" having invested its limited resources in things lots of the dedicated members didn't seem to want, instead of basic improvements to moderation and to chat features.

Re: A Higgs-Bugson in the Linux Kernel

#17
post #15

With millions of LoCs, it is no surprise there are bugs. Worse yet, the kernel runs in supervisor mode. This kernel design is bankrupt. There's much better available, such as seL4+Genode.

seL4+Genode is equally as bankrupt. I run my code in the SMM anyway.

Re: A Higgs-Bugson in the Linux Kernel

#18
post #15

With millions of LoCs, it is no surprise there are bugs. Worse yet, the kernel runs in supervisor mode. This kernel design is bankrupt. There's much better available, such as seL4+Genode.

Please try keeping your snide comments to issues they actually apply to. This is a logic bug, with the kernel missing a piece of abnormality handling. You can get the exact same bug in a microkernel (or, FWIW, a memory safe, e.g. Rust) implementation; neither of those concepts help here.
Post reply on HN