Hacker Newsnew | past | comments | ask | show | jobs | submit | chotmat's commentslogin

Wait, you guys actually call yourselves MotherDuckers :rofl:. I was thinking before that would be a hilarious name, kind of like how Google has “Googlers.”


I ride a motorcycle (not a big one), and it will slip out of my short's pocket onto the road pavement, every, single, time, without a case.


Motorcycle meant I went with quadlock case.

But am now in the quadlock system of attaching my phone to anything else.... IE car mounts too. SO quadlock got a bunch of my money.

Maybe I'm a buyer trying to justify my sunk costs, but to Quadlock's credit, once all matched, I think it works well.

And for the 3D printerists, there is a bunch of Quadlock 3D models to help out too.


but what did Gruber do?


Had a public argument with some other guys about whose version of markdown could use the name "standard markdown", apparently?


PR work for Apple


I don't think this is fair, as it will likely also affect any editor with Git integration (or not?)


Yes, likely. And git is not going to fix it. So isn't it fair to expect the editor maintainers to do something about it, to protect their users, no?


Tested with zed and vscode. They don't seem to have the issue. Probably due to "Restricted Access" mode when opening new folder?

Edit: yeah pwned when clicking the big green trust button


No


where did you get this 1%?


It's because you was wrong (or at least not correct). The Mpemba Effect wasn't scientifically proven, and can be explained away with error in measurement. https://www.youtube.com/watch?v=SkH2iX0rx8U


That video is also, outdated.

A reliable way of reproducing the effect was found in 2021. [0] Though the precise cause is still unknown.

[0] https://doi.org/10.1038/s42254-021-00349-8


Then I was wrong, at least until further research into the topic. Such is the tale of science.


Palantir only select people that are okay with this, so I doubt they say anything here.


obviously, they and their claude didn't think about that


Even acknowledging this flaw, there's a valid reason (simplicity) to design it this way.

"Be kind. Don't be snarky."


I don't get it, what's the difference between "got or don't" vs "it depends"?


The allocator’s output is only two: either you get memory or you don’t. To quote GP

> Every function with an IO interface cannot be reasoned about locally because of unexpected interactions with the io parameter input

This means with IO interface is not quiet clear what WILL happen so it “depends”


The "metrics" is hilarious. The "before AI" graph looks like those meme about FAANG engineers who sit around and basically do nothing.


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

Search: