“Falsehood flies, and truth comes limping after it, so that when men come to be undeceived, it is too late; the jest is over, and the tale hath had its effect: […] like a physician, who hath found out an infallible medicine, after the patient is dead.” —Jonathan Swift

  • 15 Posts
  • 216 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2024

help-circle











  • It’s technically more money upfront, but you’re not just buying the printer itself: you’re also buying the starter ink/toner cartridges that come with the device. The starter toner gives you vastly more pages than the starter ink, and it basically never goes bad. According to Brother, the size of a starter toner cartridge is 1000 A4 pages. According to HP, their Deskjet and Envy starter cartridges print about 150 and 250 pages, respectively.

    So that higher upfront cost doesn’t just go into a better, more efficient machine; it also goes into quadruple the starting pages or more. There are people who could seriously never print more than 1000 pages, whereas the starter for a Deskjet is so small that you practically ought to buy a spare cartridge alongside the printer for when it near-immediately runs out.

    Basically, if I’m not flat-ass broke, I’m paying another $63 upfront for an XL ink cartridge from HP for one of these printers. And what’s the page yield? 430. I’m still not even near the starter toner cartridge page capacity after spending an extra $63 on ink. To me, the upfront cost of an inkjet printer is pragmatically higher unless I’m so boots-theory-of-economics broke that all I can afford is the printer unit and only print a few pages a month tops.



  • Uhhh, yeah, I could see why Reddit might ban you for posting artwork by Sally Mann. I 100% take Mann at her word when she says that her work is strictly artistic. That to me is not even remotely in dispute.

    What deeply concerns me now is the combination of you posting Mann’s artwork (I’m assuming you didn’t just get banned for one of her landscapes) and posting sexualized illustrations of fictional children and remarking about licking your cousin’s underwear while she wears it. That’s a really disturbing pattern, and I mean with 100% sincerity that, even just for your own benefit, you should seriously consider seeking professional help.

    Therapists are some of the kindest, most understanding types of people you’ll ever meet, and they can and would want to help you work through whatever you’re going through.


  • Actually, I was curious why someone with a <1-day-old account here was coming in like “We need a community dedicated to Megumin 😣” and posting Asuka ass shots, which was an instant red flag they’d been abruptly banned from Reddit for doing some really gross shit but still needed their fix somewhere else. I forgot that Reddit doesn’t say what a user is banned for anymore, though, so I just clicked the first live link on the Wayback Machine to see if I was right. This process took a cumulative two-ish minutes.

    Lo and behold, they were “joking” about “licking [their] cousin’s underwear while she’s wearing it”, which OP chalks up to having “different tastes”.


  • “Why isn’t there an entire community dedicated to jerking off to softcore imagery of an anime character who’s canonically 14? 😣”

    Please, OP, get help. This isn’t normal, and this isn’t healthy.


    Edit: okay, so you were permanently banned from Reddit (probably for fantastic reason, uncharacteristic of Reddit), while you were there made “jokes” about “licking [your] cousin’s underwear while she’s wearing it” (seek therapy, OP), dumped lengthy LLM slop into comments sections and got defensive when rightfully called out, and showed up here today to start immediately hornyposting about various canonically underage anime characters.

    We’re not Reddit’s backwash, OP, and there’s something seriously wrong with you that being here is not going to help.




  • I’d go even further: the learning curve for Rust is shallower than C/C++.

    • C is obvious: dealing with strings is a goddamn nightmare in pure C, and strings are used all the time in modern programming. Almost no guardrails for memory safety mean that an inexperienced programmer can easily run into undefined, nondeterministic behavior that makes bug hunting difficult.
    • In C++, there’s a trillion ways to do anything (which varies enormously based on C++ version), and when you make mistakes of even moderate complexity (not “missing semicolon on line 174”), compilers like gcc spit out a gargantuan wall of errors that you need to know how to parse through.
    • Rust, in my experience, gives you a much clearer “good” way to do something with some room for expression, and its compiler tells you exactly what you did wrong and even how to resolve it.

    The fact that the compiler actually guides you, to me, made learning it much easier than C/C++.


  • I don’t know how else they could react:

    And the compiler was slow, the code that came out was slow…

    The compiler is slower because it has more to check for, but “the code that came out was slow” seems like nonsense, exaggeration, or PEBCAK. Rust code is highly performant and very close to C code.

    The support mechanism that went with it — this notion of crates and barrels and things like that — was just incomprehensibly big and slow.

    Dude what? C’s build systems like cmake are notoriously unfriendly to users. Crates make building trivial compared to the ridiculous hoops needed for C.

    I have written only one Rust program, so you should take all of this with a giant grain of salt,” he said. “And I found it a — pain… I just couldn’t grok the mechanisms that were required to do memory safety, in a program where memory wasn’t even an issue!

    He doesn’t say what the program was, and the borrow checker operates by a set of just a few extremely simple rules. There’s no idea of what he was trying to accomplish or how the borrow checker impeded that.

    So my reaction as someone who cares deeply about how disastrously unsafe C is and the tangible havoc it creates in modern society:

    • I agree the compiler is slower. Honestly boo hoo. It’s slower for two very good reasons (better static analysis and better feedback).
    • The code being slower is such a minor issue as to effectively not be true. Benchmarks prove this.
    • I’m not going to take “big and slow” as a serious critique of Cargo from someone who idealizes C’s ridiculous, tedious, convoluted build system.
    • The borrow checker is trivial, and unlike C, the compiler actually gives you easy, intuitive feedback for why your code doesn’t build.