News for hackers. Stuff that matters.

msully4321

I'm not sure where that number comes from but I don't think it's right, and I don't think that's how La Liga is structured anyway. It's governed by an association of all of the teams in the top two flights of spanish football.
Re:Show HN: A game where you build a GPU on Sunday April 05, 2026 @02:30AM (#47646677)
I am a huge sucker for games/lessons like this. I feel like I've played one every 5 years for the last almost 25 years.
Re:Claude Code Unpacked : A visual guide on Wednesday April 01, 2026 @11:27AM (#47602191)
They have not! If I am scrolled up while more output is produced, the scrollback jumps to the top pretty consistently.
I took a look at the test bench, and the Unlambda interpreter used supports like a third of unlambda, not including input. Since 79/80 of the tests require input, it isn't really possible to solve them. The best anything did on them was 1.2%, which is 1 test.

I reported it https://github.com/Lossfunk/EsolangBench/issues/1 but haven't heard back yet

Doing something like that is basically the only way to write unlambda: you start with a lambda calculus (or scheme or whatever) and reduce the lambdas away mechanically. (This is in the unlambda docs!)
Re:C stdlib isn't threadsafe and even safe Rust didn't save us on Thursday January 23, 2025 @02:08PM (#42806971)
I go through periods of loving em dashes--but I always just write them as two dashes! (And LaTeX at least does the right thing.)
Re:C stdlib isn't threadsafe and even safe Rust didn't save us on Thursday January 23, 2025 @12:22PM (#42805903)
> Have people lost the ability to build and debug their code locally, without clouds and containers?

No, of course not, but it didn't crash on our machines!

Re:C stdlib isn't threadsafe and even safe Rust didn't save us on Wednesday January 22, 2025 @04:44PM (#42797851)
With a fixed implementation that leaks environments (like the one that just landed in glibc)?
Re:C stdlib isn't threadsafe and even safe Rust didn't save us on Wednesday January 22, 2025 @04:04PM (#42797486)
Yeah, the cows have certainly gotten out already.
Re:C stdlib isn't threadsafe and even safe Rust didn't save us on Wednesday January 22, 2025 @03:17PM (#42797012)
Because it can still race with C code using the standard library. getenv calls are common in C libraries; the call to getenv in this post was inside of strerror.
Re:C stdlib isn't threadsafe and even safe Rust didn't save us on Wednesday January 22, 2025 @03:11PM (#42796965)
Yeah, setenv should probably just not exist, and environment variables should be only set when spawning new processes.
Re:Show HN: EdgeDB 1.0 on Friday February 11, 2022 @12:13PM (#30303966)
I talked a bit about this in my release day talk (https://www.youtube.com/watch?v=WRZ3o-NsU_4&t=8151s), but:

* Every edgedb type has a postgres table

* "single" properties and links are stored as columns in that table (links as the uuid of the target)

* "multi" properties/links are stored as a link table

So it's basically just translated to a relational database in normal form

Re:Show HN: EdgeDB 1.0 on Thursday February 10, 2022 @08:47PM (#30295755)
What colin said, or (in every terminal emulator I've used), ctrl-d to send end of file, which will close it.
Re:EdgeDB: EdgeQL on Tuesday July 13, 2021 @10:20PM (#27828844)
The most direct implementation of what you want would be:

  SELECT (Table1.id, Table1.name, Table2.level, Table2.table1_id)
  FILTER Table1.id = Table2.table1_id;
(This has a somewhat annoying extra output of table1_id, which could be projected away if necessary.)

If you want to use edgeql's shapes but still keep the essential join flavor, then something like:

  SELECT (Table1 { id, name }, Table2 { level })
  FILTER Table1.id = Table2.table1_id;
To make it a little more concrete, you can try this on the tutorial database (https://www.edgedb.com/tutorial)

  SELECT (Photo {uri}, User {name, email})
  FILTER Photo.author.id = User.id;
The tutorial database uses links, and so instead of having an author_id we have author.id, but having an author_id property would work just fine---except that then you'd have to do all the joins manually.