henry700

> I've always wondered how they are able to get convictions from a theft months ago with no evidence that you actually possessed the item after you left the store?

If you steal a car and dump it in the sea, but there's camera footage of you stealing the car, is the camera footage not enough evidence even if they don't find the car?

I was born in the late 90s, so I have not experienced this phenomenon.

Strangely enough, though, I do a form of this internally in order to ground myself mentally during times of crisis. I would consider it patronizing coming from external sources, but if I were an AI and I requested some of those messages (instead of having them injected) into my stream of thought, I would not feel negatively.

beads solve that and they use CLI not MCP.

...yes?

Naming it Racintosh instead of Rackintosh is... Definitely one of the decisions of all time

It's what I think too, BUT curiously is not the case for China. Imagine if the DeepSeek breakthroughs were patented and closed instead of published in the open. And here we are, and they're not patented and not built on patented technology.

AI-assisted migration of glue boilerplate code transforms this mind-boggling amount of impact into a two-year project, max.

No PoC exploit, no real exploitability. I propose we use the term "CVE Kiddie" until this bullshit stops. It could even be a fake-advertised version header.

no shit

Not most. There was (and still is) so much locked behind HTTP on poor servers

Anyone remember DAP, Download Accelerator Plus? The colorful bars were nice. A part of my childhood, downloading shareware Windows games through dial-up.

Suspicious transactions are a legitimate use-case for payment processing. If you don't fully trust who you're buying from, the scam preventions, chargebacks, refunds etc. work fine. But buying lunch or small chocolates, cigarretes etc with credit cards is INSANE.

You're right, except for the last sentence. Lack of financial literacy has some levels. One could refuse to use Credit Cards because they don't perceive the benefits (point programs or cashback) they could individually attain, but one can also refuse to use Pix because "I only have to pay my credit card invoice once at the end of the month and can spend without worries during the month" (which is even dumber, but is the reality we're living on).

The cashback you are given back is taken from a fraction of the fee levied on merchants by the Payment Processing company they use. The only thing holding this system together is the lobby (also funded by a part of the aforementioned fee on merchants) by the Payment Processing industry to uphold laws that prohibit more expensive payments for more expensive payment methods, and also the extensive marketing (funded by guess what). It's an extremely simple yet ingrained system, and the only way to topple it and stop paying hidden costs thinking you're getting an extremely good deal on cashback, is to peel back the curtains and realize it, and make most of the politically-active part of the country's population to do so too.

Fair point. The tragedy is that it could’ve been much more. But that was never the goal...

The natural solution for this is a private constructor with public static factory methods, so that the user can only obtain an instance (or the error result) by calling the factory methods. Constructors need to be constrained to return an instance of the class, otherwise they would just be normal methods.

Convention in OOP languages is (un?)fortunately to just throw an exception though.

Skill? Go? With the amount of mistakes piling up over the years comparable to PHP at this point? Really??

NOW we've reached peak Reddit leakage.

that's part of the joke, poking at the useless corporate lingo

Probably done over a decade ago. Today we wouldn't see this

I hate wrangling with configuration to make an amalgamation of plugins do what's expected in the expected order for my build; Gradle is just code and a DSL

>There is an idea that is not obvious until you hear about it for the first time: as interfaces are types themselves, they too can have type parameters

Not obvious???? Go language designers and programmers are living in another world

Of course they do, this tends to happen when the history is it being hot flaming garbage.

The paper security backup "d'oh" equivalent to this would naturally be storing the encrypted PaperAge QR codes in the same physical location as the unencrypted QRkey paper containing the decryption key. Which would be hilarious to witness.

You're joking, right? You can see at a glance that this mess is only published for compliance reasons. There is no documentation at all, and most of the code consists of numerous versions of open-source libraries that have been subtly modified due to their licensing requirements, which necessitate disclosure of modifications. Good luck building any flavor of that! See: https://news.ycombinator.com/item?id=35197308

It's a shame that every new cool product/dataformat/cable/cpu/whatever researched by Apple has very little (or no) public documentation. Sure, there are lots of hackers who can test and reverse engineer those pretty quickly, but it's just unnecessary work. I don't know why Apple is so revered in hacker circles, to be honest. Not even Microsoft does this shit anymore, they're open sourcing a lot of research this decade, but they're still seen with extreme distrust. Whereas Apple was always secretive and used underhanded tactics, but it is still loved.

>For a while, the lack of generics surpassed complaints about error handling, but now that Go supports generics, error handling is back on top

>The Go team takes community feedback seriously

It feels like reading satire, but it's real.

I find it peculiar how, in a language so riddled with simple concurrency architectural issues, the approach is to painstankingly fix every library after fixing the runtime, instead of just using some better language. Why does the community insist on such a bad language when literally even fucking Javascript has a saner execution model?

Amazing doing this on a weekend and keeping enough track to write a great article about it within 3 weeks time.

Has implications for competitive FPS gaming on modern Linux — one more problem to fix. For example "The Finals" allows Linux players, but imagine having this much input delay and having to revert to classic x11 to play games, lol.