Seems to be dead? I went to report the misspelling of Columbus, Ohio, and discovered there's been an open ticket for 5 years. https://github.com/stevage/OpenTrees/issues/58

Oh, hi! I was just trying to figure out why there was suddenly a bunch of data source suggestions.

Is it "dead"? Hmm. It's complicated. It's true the data hasn't been updated in a long time. The biggest issue is that most of the data sources that were present on OpenTrees are no longer online.

So if I do a fresh harvest and rebuild, a lot of that data will disappear, which is a bit sad.

I'm in two minds about what to do, and have been for a long time.

So, it's not "dead", it's just very indecisive.

The "75% of Debian archive builds" claim is exactly the same 7 years ago. In fact, look at this slide from the 2019 presentation: https://archive.fosdem.org/2019/schedule/event/roadmap_for_t... (page 8)

It is barely distinguishable from the first slide featured in the Phoronix article from today: https://www.phoronix.net/image.php?id=2026&image=gnu_hurd_1 It seems like there has been progress on other fronts, so I'm not sure why Phoronix ran a headline focused on very old news.

Interestingly, the 2018 version of the slide claims "80% of Debian archive builds"; I wonder what caused the regression. https://archive.fosdem.org/2018/schedule/event/microkernel_h... (page 26)

> so I'm not sure why Phoronix ran a headline focused on very old news.

It's just coverage of FOSDEM 2026 and I guess they assumed that the FOSDEM slides would show notable changes rather than the state of play.

It's just a convenience app, but it's a pretty nice one. When I moved my main PC from Windows to Linux, I was definitely sad to lose the ecosystem of nice launcher apps (GOG Galaxy but also others like Playnite, Launchbox, etc). The dream for me is to have all my games in one cohesive library, and that's what these sorts of apps offer. On Linux I use Lutris for this and it's fine enough, but I'll definitely be taking a look at Galaxy when it comes to Linux.

First, they probably wouldn't win. Oracle lost Google v Oracle. Wine is pretty serious about clean-room principles -- they won't accept a patch from anyone who's ever so much as looked at Microsoft-owned source code.[1] Valve has the means and motive to fight a lawsuit to the bitter end.

Second, it would be a PR disaster. "Microsoft sues to kill the Steam Deck" is an awful look for the company. Their strategy in recent years has been to say "actually we like Linux now" and play friendly to try to win developers; this would run completely counter to that. There may not be much of an immediate consequence to this, but in the long run I think we'd see developers try to reduce their reliance on Microsoft/Windows.

Third, I don't think it would actually stop the tide. Wine and Proton are a big piece of the movement away from Windows, but they're not the only piece. The legal process would take many years to play out; during that time, we'd likely see tons of movement on making it easier for developers to create native Linux builds, and perhaps even new projects that try to find other ways to do Wine-like things without actually reimplementing Win32. Losing Wine would be a huge blow, but I don't think it'd be the end of the story.

[1]: https://gitlab.winehq.org/wine/wine/-/wikis/Submitting-Patch...

Another point that makes everything different is that MS has contributed to the wine project. They've both sent in code changes to wine itself and they donated mono to the wine project.

> Second, it would be a PR disaster. "Microsoft sues to kill the Steam Deck" is an awful look for the company.

If the alternative is losing the entire Xbox market? Money makes people and companies do funny things.

How is the Xbox market related to SteamDeck? SteamDeck plays PC games (which XBox doesn't), and XBox plays its own console games (which PCs and thus the SteamDeck don't)

The Venn diagram of Xbox games and PC games is very close to the Xbox circle just being completely inside the larger PC circle. The number of Series S/X exclusives is literally zero at this point, at least I'm fairly sure, and if there are any, my bets are on them being shovelware. The Xbox One only has one exclusive game of note, which is Halo 5.

I don't think the performance of the Steam Deck is up to play all Xbox games at Series X quality, but that's a nitpick assuming future Steam Decks arrive.

Isn't the xbox market dead after after having to code for the weaker series s lead to the last generation of consoles being outsold massively by the PS5?

They’re killing Xbox themselves already, I doubt they care anymore.

This comment isn't just amazing -- it's my new favorite comment on Hacker News.

I'm Commander Shephard and this is my new favorite comment on the Citadel^WHacker News.

It is so irritating that people now think you've used an LLM just because you use nice typography. I've been using en dashes a ton (and em dashes sporadically) since long before ChatGPT came around. My writing style belonged to me first—why should I have to change?

If you have the Compose key [1] enabled on your computer, the keyboard sequence is pretty easy: `Compose - - -` (and for en dash, it's `Compose - - .`). Those two are probably my most-used Compose combos.

[1]: https://en.wikipedia.org/wiki/Compose_key

Also on phones it is really easy to use em dashes. It's quite out in the open whether I posted from desktop or phone because the use of "---" vs "—" is the dead give-away.

I configured my system to treat caps lock as compose, and also set up a bunch of custom compose sequences that better suit how I think about the fancy characters I most often want to type. My em-dash is `Compose m d`.

And lists! I love to use lists and blather a lot. It was from me that AI learned that:

  * Answers should be really lengthy even if you aren't saying much
  * Lists are the perfect vehicle to layout your ideas
  * Good things come in 3s.

But alas, my wonderful style of internet comments now look tooooo good, like an AI generated them.

I don't use many emoji's though -- that's one way AI has gone wrong.

I've had alt+0150 (–) and alt+0151 (—) memorized for over a decade at this point and frequently use them. It sucks that they're just associated with AI nowadays (along with the poor Oxford comma).

How do you find yourself using en dashes more than em dashes?

I am more likely to separate two thoughts with space-endash-space than with an em dash and no spaces. It just feels weird to not type spaces, and I don't want to do space-emdash-space because that would feel like an enormous gap; if the two clauses need that much distance from each other, why not just split them into two sentences?

I'm sure this goes against many style guides, but for everyday use it's what feels most natural to me.

Not OP, but I find the space-en-space convention easier to read than the nospace-em-nospace convention. American style guides prefer the latter – in my eyes they are wrong about that

They're wrong about preferring the style you find easier to read?

Did you mean American style guides prefer the latter?

brain fart, fixed

For me I use en dashes a lot for ranges like 1–N

Maybe they write out a lot of ranges?

Hot take, but a character that demands zero-space between the letters at the end and the beginning of 2 words - that ISN'T a hyphenated compound - is NOT nice typography. I don't care how prevalent it is, or once was.

I don't know if my language grammar rules (Italian) are different than English, but I've always seen spaces before and after em-dashes. I don't like the em-dash being stuck to two unrelated words.

That's because in Italian, like in many other European languages, you use en-dashes to separate parenthetical clauses. The en-dash is used with space, the em-dash (mostly) without space and that's why it's longer. On old typewriters they were frequently written as "--" and "---" respectively. So yes, it's mostly an English thing. Stick to your trattinos, they're nice!

It's a US thing

That sounds like a strongly held opinion rather than a fact.

I like em-dashes and will continue to use them.

That'll show em'.

>That sounds like a strongly held opinion rather than a fact.

Yes, that is more or less what "hot take" means.

agree. it implies a strong relationship between the two words it is inserted between - not the sentences.

*GNOME features, not Linux features. No such issues over here on KDE.

I have often felt like GNOME is the most Apple-y of desktop environments; they're very form over function. Not surprising to me at all that both would pick a design that seems beautiful until you try to use it.

Indeed, no such "invisible drag areas" here either using just FVWM2.

Instead of saying "don't use libxyz", say "use only native functions". Instead of "don't use recursion", say "only use loops for iteration".

This doesn't really answer my question, which more about specific exclusions.

Both of the answers show the same problem: if you limit your prompts to positive reinforcement, you're only allowed to "include" regions of a "solution space", which can only constrain the LLM to those small regions. With negative reinforcement, you just cut out a bit of the solution space, leaving the rest available. If you don't already know the exact answer, then leaving the LLM free to use solutions that you may not even be aware of seems like it would always be better.

Specifically:

"use only native functions" for "don't use libxyz" isn't really different than "rewrite libxyz since you aren't allowed to use any alternative library". I think this may be a bad example since it massively constrains the llm, preventing it from using alternative library that you're not aware of.

"only use loops for iteration" for "done use recursion" is reasonable, but I think this falls into the category of "you already know the answer". For example, say you just wanted to avoid a single function for whatever reason (maybe it has a known bug or something), the only way to this "positively" would be to already know the function to use, "use function x"!

Maybe I misunderstand.

I 100% stopped telling them what not to do. I think even if “AGI” is reached telling them “don’t” won’t work

I have the most success when I provide good context, as in what I'm trying to achieve, in the most high level way possible, then guide things from there. In other words, avoid XY problems [1].

[1] https://xyproblem.info

The full press conference is worth checking out for more details (or do what I did and read the transcript): https://www.youtube.com/live/ffcV3jCwwPk?t=607s

They won't breach the crewmember's privacy, but they've said the medical issue was not related to any mission operations. There had been some speculation online about it being related to spacewalk prep breathing protocols, but they have confirmed otherwise.

The crewmember is stable and they're not calling it an emergency evacuation. They could potentially evacuate in hours, but they're going to return "in the coming days" instead. They said it's a precautionary measure; they don't have the equipment onboard to do all the checks the doctors want to do.

Apparently they've done statistical models in the past that suggested the ISS ought to have had a precautionary medical evacuation every three years, so the fact that it's taken over 25 years for a single one is pretty incredible. (The NPR article mentions that it's a first in 65 years of NASA spaceflights, but that seems silly to say. Before the ISS, NASA had very few missions long enough for a precautionary medevac to even make sense.)

SponsorBlock is available on just about every type of device these days -- works perfectly on Android with YouTube ReVanced. The options on iOS are naturally a bit more limited, but apparently it's possible on a jailbroken device (or through some other slightly-janky methods on non-jailbroken devices): https://github.com/ajayyy/SponsorBlock/wiki/iOS