Skeletor
2d ago
You possess no knowledge on this subject. That's fine, most people don't. But no one who does has been especially surprised by the actual outcome of any of Jake Paul's fights. He's defeated some over-the-hill MMA guys, the elderly husk of Tyson, and even a couple of random journeyman boxers here and there, but then he fought an actual serious world-tier heavyweight and got crushed.
That said, personally I really don't mind him. Honestly for how late he got started on the sport he's not bad, and the slobs he's fought are the type lots of guys start out fighting, especially guys without amateur experience. He might be some kind of edgelord by YouTube standards but until he rapes someone or gets some mob ties he's still a cuddlebug by boxing standards.
Skeletor
5d ago
In C, you may get away with not checking the return value of a function that could error. In Rust, that is completely unacceptable and will make the compiler cry. The path of least resistance in C is to do nothing, while the path of least resistance in Rust is to handle the error.
This reminds me of learning BASIC on a Timex/Sinclair 1000, AKA the US release of the ZX81. It had this stupid gel-tab keyboard that made real typing impossible, but it would turn single keystrokes into full commands, even multiple commands per key which it would select contextually depending on where you were in the line you were typing. That and it called out syntax errors on the spot and wouldn't accept them until they were fixed.
This is all relevant to nothing, I'm just waxing nostalgic. For a machine with 2k native RAM (expandable to 16) it was an awesome kid's first computer to learn how to program out of a book.
Yeah but him losing a narrow decision to a reasonably okay boxer wasn't the payoff people wanted at all. They wanted to see him get pulverized.
More options
Context Copy link