Hacker Newsnew | past | comments | ask | show | jobs | submit | 1-more's commentslogin

Best I can do is that the middleman took the sweetheart deal conviction for solicitation at face value, and did not know it was a plea down from crimes against children? IDK

They also declared that a shoelace is a machine gun until they declared that it's not

https://www.reddit.com/r/guns/comments/ctdm3/oldie_but_goody...

https://imgur.com/7N6zc


All we need to do is create Kalshi contracts! Users bet that a fix won't be created for Issue 123 by date XYZ, developers take the other side of the contract and then do the best kind of insider trading: changing the facts on the ground. We did it!


And a few weeks into that arbitrage traders will catch wind and start betting on the more likely bug closures and then the devs that fix the bug will end up owing money!


Then, the people who actually want the fix will bet it back up so the dev is incentivized to fix it!


People who work on making money, tend to have more money and leverage. It’s not an even playing field.


There are bribing and HFT opportunities here too. The fix developer is incentivized to wait until the last possible moment to take the position "the PR addressing the bug will be merged by the date" so that the contract will be the cheapest for them to buy and represent the greatest profit when the PR is opened or merged. What's a savvy speculator on the sidelines to do? After the PR is opened, bribe the project maintainer not to accept the PR by that date so they can turn a sure-thing "Yes" into a huge upset "No." Or watch the developer's github for green shower tiles to see activity in private repos. But the developer can throw up chaff that by scripting bunches of commits in other private repos, or changing the commit dates for the bug fixes to be a year ago. The speculator can monitor the developer's posts in language/topic forums or on social media to get a feel for their progress. If they're really connected, maybe they can see their AI agent/chatbot logs through an insider in one of those companies.

This idea rocks because eventually someone is going to get blackmailed with their affair history over, like, adding native XLSX support to FFMPEG. Can't wait. Financialize everything.


I wonder if Candide is the prototype of this.


Interesting. You have me thinking of Candide as an answer to Quixote.

In very broad strokes, Quixote says my perceptions and ideals are true and apparent evidence to the contrary must be a misunderstanding/ chance/ magic. His agency is to frame the world’s meaning in his own terms. Until finally he gives it up.

Candide accepts societal moral framings (i.e. rationalizations for wrongdoing) naively, but is slowly worn down by the evidence that they’re a sham. But in facing the seemingly intractable harshness of reality, he doesn’t become so cynical as to cede his own agency entirely—“Il faut cultiver notre jardin.”

To me that feels like a wiser response than absurdity or despondency.


Apparently the "lost in the Treaty of Versailles" explanation is a bit of a just-so story: https://history.stackexchange.com/questions/55729/why-did-ba...


4 modifier keys vs 3. Can't go back. Maybe you can get your whole Linux env using 4 modifiers one application at a time, but my god would that be another thing that takes forever on top of everything else you need to configure. No ty.


This was such a big pain for me when switching back to windows / Linux. I’m not sure why it’s not talked about more. 4 modifiers is much better if you are a keyboard “power user” but don’t want to spend days crafting and maintaining a bespoke input system.

A more general point: you can be a “power user” and not have the time to learn about the absurd stack of technologies that is a Linux DE. You may even be a “power user” and not have a job / education related to computers! Shocking!


I'm a dad, I'm doing home improvement stuff, I have cat litter to scoop, I have a day job. I have like 15 minutes at a time to power use my personal computer. I spend it programming. Everything I need to do between opening the lid and typing programs is an affront.


I had a long boring meeting. I decided it was time to grow up and learn a little Lean. Let's do formal methods. Let's be serious, you know? It's pretty cool!


Usually lumped in with labor aristocracy along with lawyers and doctors. Can go either way when it pops off.


Adafruit is maybe an all time amazing success story built on giving more of a shit than anyone else. There is a direct through line from reading MAKE in high school through programming the 8 LED POV thing through the rest of my career. Limor doesn't answer a forum question on a Sunday morning in like 2008 and I don't make my mortgage payment this month and my son gets store brand formula. I wish you every success professionally and in this new chapter with your tiny miracle, and I hope for an amicable resolution to this whole Sparkfun thing.


Sorbet is a decent one. I don't think it ever solved "jump to definition" though. I would just `rg def (self\.)?function_name` or I eventually developed a vibe for where things were, which is sort of the Ruby excuse for the ungreppability of everything. Sorbet did allow us to generate front end types in Elm and also allowed for type safe Haskell FFI. Past tense because it's an old job; as far as I know it's still happening.


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

Search: