Hacker News new | past | comments | ask | show | jobs | submit | Snild's comments login

As a kid, Krabban Konrad, "Kermit the Hermit" in English (https://en.m.wikipedia.org/wiki/Kermit_the_Hermit), was one of my favorites.

In high school, 1984 hit me hard.

As an adult, I'd pick Pojken som fann en ny färg (literally translated "The boy who found a new color"). I really liked it's ultra-short chapters, making up snapshots of a romance and family being built and falling apart.


> I wonder how they got around this requirement, or if they didn't, did they rewrite everything to be compliant to this rule?

I can't say, but I know that they have made wide-ranging changes to behavior, e.g. the in-kernel locks: https://www.kernel.org/doc/html/latest/locking/locktypes.htm...


That page seems to be describing SCHED_FIFO processes, which are already a thing without PREEMPT_RT. Maybe they weren't back in the pre-2.6 days? Anyway, they are usually limited to 95% of total runtime by the sched_rt_runtime_us tunable, to avoid accidental self-DoSing. Maybe that, too, was later invention -- 2.6 is very very old.

The page goes on:

> A patch does exist to enable process to have real-time process access to any process requesting it.

According to the sched(7) man page, this has never been the case: before 2.6.12, the process had to have CAP_SYS_NICE; after, it was limited by policy through RLIMIT_RTPRIO. I guess it's possible that this was not the case for the original out-of-tree patch set.

But it's been there for many years, well before the 2020 edit that added the bulk of the current text on that wiki page.


Discs are super cheap to press, and word is that Switch games are significantly more expensive to manufacture: https://www.eurogamer.net/why-nintendo-switch-games-are-endi...


I think it was a misunderstanding based on different views of what "the whole repo" means -- all the files or all the history.

It quite nicely demonstrated the difference in philosophies, albeit accidentally. :)


We've had this problem in Malmö, Sweden recently: https://www.svt.se/nyheter/lokalt/skane/nya-hundbullar-hitta...

Bread rolls with bits of glass or metal in them, found in parks or along other pedestrian paths. They caught one woman doing it, but it is believed the news might have inspired other nutjobs.


I agree that it should be standardized, but not with your argument.

Yes, any tablet worked, but it required running an app customized for the hardware. That only proves that we can standardize at the level of Android app APIs.


There are some downsides.

https://github.com/libexpat/libexpat/pull/789/commits is a PR of 16 related commits. Many of them make sense individually, but are depended on by subsequent commits.

Reviewing them separately makes sense. It's easier on the reviewer (and future readers) to handle multiple smaller changes, especially since each is more tightly coupled to a rationale in the commit message. Unfortunately, github's PR-focused UI doesn't really make this per-commit review as convenient as Gerrit does.

Additionally, the last two commits are authored by another contributor. This metadata would be lost in a squash.

Of course, each intermediate commit must build and pass tests. WIP and cleanup commits are squashed locally before final review/merge.

You could argue that all of these could be separate PRs, but I think there's value in grouping them up with that final merge commit, showing what one was trying to do at a larger scale.


I read that part not as "trickle-down", but as "the tax would have to be collected from other sources".


Isn't that just already my linux dist, if I want to?

I can install python-matplotlib from my package manager, and it appears in my python path. I never bother with venvs.

Maybe my needs aren't advanced (or exotic) enough.


Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: