skysight-inc/HackerNews huggingface dataset:
I honestly don’t remember ever using open protocols to chat, sorry.

Born in ‘97, I was too young for IRC’s height, and although I flirted with XMPP, none of my friends were there so it was just me and a handful of like-minded people I’ve met on the Internet. I think XMPP’s peak was when Facebook and Google supported it for a while, before erecting the walls.

Now there is Matrix which serves a similar niche (albeit more successfully) but doesn’t seem that interested in being a WhatsApp/iMessage replacement for casual day-to-day use. Discord and Telegram have a huge social network element to them but in my limited experience, the performance issues in the very protocol itself and/or with Element (the de-facto Matrix client) hinder its adoption.
I didn't get the impression that the math around it is that simplistic. The first obvious reason I can think of now is the attention mechanism being used. Both GQA and MQA demand less compute and therefore less bandwidth than MHA.
> Systemd is the last init linux will have

I'm fine with that.

> and increases the barrier to port software to other unix-likes.

Don't care about "other Unix-likes", and in fact I wish they didn't exist.

> The non-optional/default features have been buggy and difficult to replace.

Let's not pretend as if the pre-systemd crap wasn't even more buggy.

> The overreliance on dbus turns the “the unix philosophy” ;) away. Text as a universal communication medium, everything is a file, etc.

Dbus is a text-based protocol based on files though. What a silly complaint.

P.S. Dbus sucks, but thankfully it would be pretty easy to replace in systemd if somebody got sick enough of dbus.
"Conclusion

The release of DeepSeek R1 and its research paper might be breakpoint for the open-science and open-source development. Just a week after DeepSeek release, we've been able to reproduce a simple version of R1 learned "reasoning" using GRPO and the Countdown Game. While our implementation focuses on a specific task rather than general reasoning and convergence into a very specific "reasoning" format, it shows that the method is working.

In our mini R1 experiment we used GRPO, with two rule-based reward but already required significant compute: 4 H100 GPUs running for 6 hours to complete just 450 training steps on a 3B parameter model."
You are absolutely right, sadly i can't edit my original comment anymore. Also that's the exact documentary i got it from, thanks for posting it.
Ah, joy of kernel debugging. Even with knowledge of C measured in years it could take weeks to debug trivial mistakes. Been there and seen others (with long careers in kernels) being there.
'White colonizers': Pro-Israel AI account turns against Zionism
As far as I can tell, this is just another rumour :)
In a somewhat similar but frequently more deranged aesthetic vein, I am a huge fan of Defense Charts on Xitter.

https://x.com/DefenseCharts
Streaming data, there was no error but also no new data available.
Hacker News for Gamedev
Just get less email messages
Nice try, Zuck
I used to love Go and its simplicity. It's still my least disliked backend language. But after more than a decade of using it nearly full time (but not exclusively), I've fallen out of love with it.

I want sum types. I want non-nullable types. I want enums (preferably, based on sum types).

I'm okay with the explicit error handling, but would be fine with Rust style error handling too.

Having these features would change the language so much that you'd probably want to re-implement the stdlib, so it probably won't happen.

Surprisingly though, while I absolutely love Go's concurrency model, being able to kick off new goroutines with a dedicated "go" keyword and special channel operators have not been a big deal at all. It's usually abstracted away by some library, or you set it up once in your application and never touch it again.
How long before these are inside laptops
That is insane (not your comment, the fact that the sensors are that small)!

Here [1] is the first result when I searched, it's the powerfully-named Omnivision "OVB0B" sensor.

It has a resolution of 16384x12288 pixels (=201,326,592 pixels in total) meaning individual pixels are 0.61 µm. Visible light is generally around 0.4 µm to 0.7 µm so the sensor is definitely in that size region with its pixels. Wow. Thanks for pointing this out.

[1]: https://www.ovt.com/products/ovb0b/
There was a second American Airlirns flight only a couple miles and a thousand feet higher in altitude in the same approach course. You can actually see it in the video that’s circulating.
As it should be! Shame they didn't make the error type a sum type that forced you to check it isn't an error. I prefer that to exceptions. But the product type that Go uses is ok.
Was just showing my appreciation in a fun way, dude. No need to be such a dick about it.
It has been years ago now, but when I did it this was partly true. Yes it showed up as income, but it also showed up as deductible expense.
"despite" "AI"
Agree that the language has to be analyzed under the original design goals to be fair. Disagree that Go is definitely well-designed in that circumstance, however. A major weakness of this essay is that all perceived issues with Go have to be irrelevant to the original design goals, quite absurd if you think about that.

I would instead say that Go had big things right, while smaller things might be not as right---but not exactly "incorrect". For example explicit error handling is the big idea that Go got right, but both Rust and Zig did a lot to refine error handling experiences; comparing them with Go is just a non-starter.
Does it make sense for every function to have those four cases, though?
> Imagine I have a chicken and an egg. Chicken goes in the animal package and egg goes in the food package. It is now fundamentally impossible to make a chicken lay an egg and an egg hatch a chicken at the same time.

I am familiar with people eating unfertilized eggs. I am even familiar with balut. But I am not familiar with the delicacy of eating an egg as it hatches. If you eat an egg as it hatches, wouldn't that actually be eating a chick (the chicken) rather than an egg?

I suspect the real problem here is that your domain model is ill-conceived. In fact, while Go has no lack of faults, I suspect the vast majority of the complaints directed towards it come down to the limited feature set not enabling papering over bad design decisions.
I’m just going by the article, which describes it as a “surprise update” that “came out of nowhere”. Am I missing something?
I tried. Wasn't even doing that much AI stuff. I spent 9 months building a product that is dead on arrival because they refuse to approve it.

I moved on to other things.
This is just BS.

If you follow their paper, their "inductive" argument can also prove that the result is optimal (the sqrt(2) constant is taken from thin air and may also be replaced by 1 without changing the proof).

My guess is that they tested some graphs, and "empirically" saw a bound of sqrt(2), and then came up with a proof to self-fulfill the profecy. They even mention that "for very small graphs, the approximation ratio may briefly exceed sqrt(2)", which is just nuts, given that they have a formal proof that it should never happen.

In case anyone read the paper and can't figure out the mistake in the proof, they assume that OPT_T + OPT_R = OPT, which is obviously false.
Well Haskell was mentioned many times in presentation, sixos is “Gentoo with Haskell instead of Python”
https://cfp.cccv.de/media/38c3-community-stages/submissions/...

But thank you for insights, I have learned Haskell basics and in awe already. Maybe "functional code is going to fix the world" not the full truth when I get more experienced ;-)
You're right. The slides about infusions and the discussion at the end about them were unexpectedly the most interesting part of the talk.
> Also, was the original article focused on gamedev? I don't see any mention of it. For us normie programmers working on CRUD apps, we don't need bump/arena allocators. Ctor->new, RAII/Dtor->delete is just fine for us.

Yes arena allocators is the word I couldn't remember, a bump allocator is a way to implement an arena allocator and probably the most popular.

Also I 100%, in general you shouldn't need an arena allocator, but if you are building a library you should be aware of allocators and make however you are allocating memory configurable so that if you do need to some day change it it doesn't involve a complete rewrite.
Those things sound great for anyone trying to impose Treacherous Computing on other people, and worthless to everyone else.
package main

import "fmt"

// Define an enumeration for status
type Status int

const (
Pending Status = iota
InProgress
Completed
Failed
)

func (s Status) String() string {
return [...]string{"Pending", "InProgress", "Completed", "Failed"}[s]
}

func main() {
var s Status = InProgress
fmt.Println(s) // Output: InProgress
}
What if you print a page with a slightly yellow background? Would it know to use a different color for the tracking dots?
On this topic, highly recommend this book, which provides a rather different perspective:

https://www.goodreads.com/en/book/show/50403455-metazoa

Breaking it down - what we think of as pain perception is not one thing but several, as you'd expect for one of the major functions in a ninety-giganeuron brain.

There's something not much more than a low-level reflex response - "Ouch" - and most animals have that.

There's wound-grooming behaviour, which is mostly linked to capacity to heal, and shows up in perception as the longer-lasting (minutes to days/weeks) pain from an injury. A lot of animals with exoskeletons have very limited healing capacity, so there's no point in attempting to heal. This is thought to be why, for example, a severely and probably fatally damaged ant will just keep on trucking, whereas even the simplest mammals and reptiles will attempt to rest and heal.

Then there's awareness of mortality. Simply, an animal that doesn't know it's alive can't connect pain to the concept of death. To what extent this exists across the animal kingdom is one of the great unknowns.

And then finally there's placing a value on one's life (and so negative value on harm to it), and the way in which we humans understand that is intimately bound up with concepts like love, grief, friendship, family and so on - these likely exist for animals that care for their young.

Those are traits mostly limited to higher vertebrates, and it's not entirely clear to what extent birds and mammals have a common ancestor with that capability (therefore some commonality in "experience") or whether that's convergent evolution. It's pretty clear that it exists across all mammals, but has independently developed to much higher levels in the most intelligent ones (cetaceans, elephants, apes), despite these groups being very far apart on the mammal tree of life, having diverged almost at the origin of placental mammals (which makes more sense when you consider what a placenta is for).

So what the pain experience is "like" for a hive-society animal like Hymenoptera (bees, wasps, ants), where caste roles are biologically determined, is impossible to say, if indeed there is any experience there. The skin (or exoskeleton) they have in the game is so different to ours that it's hard to reason about it.
They fired the zuck? that was his idea behind the fb in the first place ..
But not every situation. Make illegal state unreprestable is a good ideal.
Asynchronous vs. Synchronous Programming
Not loving the guy, his sentence was perhaps a bit performance art?
This era is so full of paradoxical forces, I'm struggling to follow.
This is excellent. Since reading https://books.google.de/books/about/Models_of_the_Mind.html?... I've been expecting someone to start looking back into biology to try to move forward. I guess the poster is one of the authors. Kudos!
No rebuttal, that's what I thought.
Does this include keyboard inputs from outside the browser window?!

If not it seems like openAi and others also collect how you interact with their models, and the claims of the privacy nightmares of the chinese tech seems a bit stark, while the US doesn't seem to be doing a lot better.
Yes that is why I mentioned it was nearly impossible to replicate. The final optimized method involved a lot of social engineering, which required to have very high standing in the casinos. She had to request, under the guise of superstition, a specific setup with a specific style of dealer, who never changed decks, and to be authorized to call out certain cards as "lucky" which the dealer would flip themselves.

It also required deep pockets, as just playing the shoe enough to sort it could take a few hours of regular gambling. That's the crazy thing, this elaborate setup just got them a few % edge on the house which they milked relentlessly.
> Also, literally whole communist block the whole time and also long after the communism felt.

Yeah, right. They were living in trees and eating fruits. /s
I've been writing Go for about 5 years now and can confirm cicular dependency issues were typically handled buy a small refactor or considering where the borders of the domain should _really_ be
Can anybody explain to me again why systemd is so bad ? Genuinely I'm not sure anymore: It is chock full of features and it gets the job done. Since it is used in a lot of big distributions it gets a lot of fixes, updates, testing and feature improvements regularly.

Yes, it is maybe monolithic (but so is the Linux kernel). Its philosophy may differ from unix's "get one thing done well" too but integration of various functionalities comes with its benefits.

Some people say it is bloated. The substitutes to systemd are lightweight but less featureful. Maybe some of them will get bloated as they achieve feature parity.

People have a right to build substitutes and replacements -- I believe in the "Let a hundred flowers bloom" philosopy. However I can't understand why systemd is the point of so much disagreement.
Ah yes, one of "the funniest" problems. They teach you a lot or drive you insane. Have you ever wrote about this adventure in some form of an article or narrative story? Would be a great read, I'm sure.
Exactly. One can think of examples where these cases make sense, but there are many more examples where there are more cases (e.g. there many be multiple kinds of partial successes) or fewer (most functions, which either succeed or fail.)

Also, the design requires null values. A point which the replies have ignored.
Some fraction of young minds, not all. I was happy to work at a small aerospace company with extreme concentration of brightest minds. Only because they loved the domain, and didn't mind a salary cut. What a joy and relief it was for me after FAANG!
Yes, I know they've said that. I don't believe them. Or rather even if they do sell them I think it will be at a point where their robo taxi's are complete ubiquitous already.
New for 2025 – more local models in Pieces, including Qwen Coder and Phi-4
Not a serious project, but I use their stdlib for my personal static site generator. I think it has much better API compared to the standard stdlib.
I wish more people thought this way. Why does the language you choose have to be your religion and lifestyle, when it’s just a tool? They all have flaws and areas they are useful in.
I enjoy writing Java and C# so much more than Go.
OK, but I can set s to 1000, and it still compiles.
In my opinion your comments on Go concurrency misses a point, the fact that you do it once "and never touch it again" is a very very strong selling point, it probably means it was very well designed; not a weakness but a strength.
> 5%. Incidentally, freshly baked bread is also often around 0.5% depending on the type of bread, as are very ripe bananas.

I’ve heard this before, but how can it be true?
Bread is baked at a high temperature, I do it as 250C, but would go higher if I could. My father bakes at 500-600 degrees. How would alcohol stay in the bread? Or is the measure taken pre baking?
This bothers me from time to time. When I first started using Go, I think I complained to the Go team about it. They told me to think more carefully about where package boundaries are. Having the smallest package possible doesn't necessarily mean the design is good.

I inherited an app from a coworker, and he just put every file in the main package. This was actually fine and caused no problems.

These days, I still have an addiction to making tiny packages, which the Go team would likely not approve. But I'm a big girl and I do what I want! The workarounds I use are:

1) A `types` package. type Chicken struct { Children []Egg }; type Egg struct { Mom, Dad Chicken }.

2) A `utils` package. Let me explain. I would never name a package `utils`. That's illegal and I'm told that the compiler will explode into a thousand pieces if you try. All the king's horses and all the king's men wouldn't be able to put it back together again. So don't test it. Just trust me. But, you can definitely have something like `package hatchery` with a functions related to collecting eggs from chickens. Or you can have `package eggutil` for packing eggs, frying eggs, and shipping eggs.

I would say that I typically have a `types` package (called `types` if I'm hand-writing the code, or myapppb if it's protobufs like at Google), and then structure the rest of my app as model/view/controller. The model puts these types into the database. (Call it `eggdb`.) The controller does whatever business logic you care about (getting chickens together to fertilize eggs, call it `husbandry`). The view calls into the controller to implement your API / gRPC endpoint / beautiful Gtk+ GUI / whatever.

And then you don't really have problems with circular dependencies.

Having said all that if someone puts it all in main.go I'd probably approve the PR. The Go team let my coworker do it in 2014 and nobody died.
Here is another series of two men building an organ into the back of a truck

https://www.youtube.com/playlist?list=PLNE6DEIclzg3WYK2Sqz2x...
I say greed with absolutely no moral implications here ! But when you watch the doco it is pretty apparent that this kind of hunger is compulsive.
In the case of Wata the dude scamming now (Jim Halperin and Heritage Auctions) scammed in the eighties in exact same way and got fined peanut sum by FTC for it https://www.latimes.com/archives/la-xpm-1989-08-10-vw-88-sto...

"Heritage Capital Corp. and Numismatic Certification Institute. Also named in the action were Steve Ivy and James Halperin, prominent numismatic figures. A consent order was signed agreeing to establish a $1.2-million fund for collectors who purchase the NCI-graded coins from Coin Galleries Inc. of Miami."
Nah. Hickey say stuff that sounds profound but doesn't actually help you get better at writing software or even at talking about it.
Most "Investing" Is Just Speculation
Except for the fact that chromium is a feeder project for a proprietary closed source work and so often bends to the will of that project.

Morally there's no equivalence here.
So are you saying you would take on the initial cognitive load of Rust vs. Go for _every_ project?
Probably wildest story involving loading/unloading libraries I have ever read about. How you noticed that? Had to resolve to memory debugging?
This feels like SAT/ACT reading comprehension question! I think that "But it never makes me lolsob minus the lol" means he meant he doesn't like the changes Swift 6 made.
> There being word for a midwife in that language does not imply practicing midwifes

Of course not, they called them this way just to joke.
Thanks to "democracy", eastern europe discovered equality between sexes and finaly the women were able to go to school. /s
Still better than putting porn site address on children’s product (wicked). And they were able to buy the redirect. They should feel very lucky indeed.
It's 2025, I've used PHP professionally maybe for a few months out of the last 20 years, the languages I use mostly don't have `::` as a token, and still, I find it really hard to refer to it as anything other than Paamayim Nekudotayim :-)

Old habits die hard I guess...
Email is one of the few protocols that was designed out of the box to be decentralized, that in the mean time is implemented by a lot of big tech players and that has stayed compatible for communication between accounts at one of those big tech players. And that is also the reason it won't disappear soon.

And aside from that, what the article mentioned is human error. And honestly, I do not think that other online communication protocols will eliminate human errors.
The 16 Pro has a fantastic hand feel with the titanium body, the stainless steel from previous models and combined with their sharp edges feel barbaric by comparison.
You can point out flaws so it's not well designed? By this logic nothing is.

And pointing out missing features in a programming language is just about the weakest criticism possible.

Piling on lots of features is easy and fun. That's why almost all language designers do it. Most popular languages destroy themselves with features.

Rust is in the process of gaining every single feature anyone can imagine. Following C++ right off the complexity cliff.

Go is one of the very few languages to show incredible restraint in adding features because its designers understood the combinatorial complexity problem, among other things.

Not having unnecessary features is one of the best features of Go.
24M, don't want kids. not going to marry (if no kids, why fuck yourself?). sex is fun but not fun enough to make me consider any of the previous things

A bunch of our social activities center around families or dating (and dating culture is just a precursor for marriage for most people)

I'm genuinely convinced (as a young man) that the reason why people are "upset" about us being alone is because they'd rather screw us into arrangements that benefit them. It's just manipulation disguised as concern
Your joking. I have a hundred food items and a hundred animal items. Cows produce milk. Chickens produce eggs. Eggs produce chickens.

It makes 100 percent sense to make two folders. Food and animals.

‘I suspect your “domain model” is ill conceived’??? You buy into that? Don’t follow what those idiots tell you.

You realize that we use these actual separations between food and animals in the real world? And now because of some design philosophy the domain model is ill conceived? The result is a more convoluted domain model to make things flow.

Actually I think this is an easier way to explain it to you. The “domain model” or aka categorization of food and animals works in reality and every other language because it’s not a bad design decision. The reason why it doesn’t work in go is because go is the bad design decision.