• 4 Posts
  • 345 Comments
Joined 2 years ago
cake
Cake day: July 14th, 2023

help-circle
  • kibiz0r@midwest.socialtoFuck AI@lemmy.worldCritical thinking
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    2 days ago

    And when they got out into the field with their dubious degrees, they had daddy’s connections to land a gig where they never needed to actually use the knowledge they pretended to have.

    Not sure what we’re gonna do now that problem-solving positions are about to be filled by people whose only training is to produce incremental remixes of old solutions to well-documented problems.

    Particularly with climate change promising to invalidate some fundamental assumptions baked into the literature of a significant chunk of our most important professions.

    If understanding first principles means you move slower, look less polished, and are at odds with the majority of the paid staff in the field, then you’re not gonna make it.

    And there’s a feedback loop, too. If it’s easiest to produce stuff that agrees with everything that came before, then that’s all we’ll make, and that’s all we’ll train new AIs on, so that’s what will continue to be easiest to produce.


  • kibiz0r@midwest.socialto196@lemmy.blahaj.zoneRule
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    3
    ·
    edit-2
    4 days ago

    Welllll… everything in software development is trade-offs.

    It’s honestly pretty rare that one solution is unequivocally “better” than another, across every dimension you might care about (which includes non-technical things).

    The kinds of egregious defects you might think of as brazen incompetence or laziness are more often the result of everyone (technical and non-technical alike) refusing the actively pursue one side of a trade-off and hoping that the devs can just “nerd harder”.

    Technical constraints as in the case of the N64 example can actually help avoid the “just nerd harder” fallacy, because they prompt serious discussions about what you can and can’t compromise on.

    Ironically, when we sit here as users and complain about games not being optimized in this way or that, we’re also refusing to engage in a conversation about trade-offs and insisting that devs just “nerd harder”.

    Edit: That’s not to provide any excuses for the blatant financialization of the industry which prompts the whole “don’t trade off anything, just have them nerd harder” mindset… but to warn yall that even if the market wasn’t ruled by greedy suits, we would probably still be feeling like old games managed to do more with less, cuz well… trading away 500MB of bundle size so you can get better logging of resource management in production wasn’t really an option.




  • Basically:

    Intel, AMD, and Microsoft are all going down a dead-end road called x86_64, especially on portable devices.

    Apple and Google took a turn ages ago, towards an alternative called aarch64. Originally just for phones, but now for everything.

    VR headsets, Raspberry Pis, IoT devices, etc. also tend to run aarch or aarch64.

    Microsoft has been trying to follow suit, but it hasn’t gone well so far. Windows for ARM (the aarch64 version of Windows) is supremely unpopular, for a lot of (mostly good) reasons.

    So people avoid the devices or ditch them because none of their apps run natively. But Microsoft basically has no choice but to keep pushing.

    So the end result is, Microsoft is subsidizing tons of excellent hardware that will never be used for Windows cuz it’s just not ready yet.

    But Linux is!

    Edit:

    Funny thing is, ARM (company behind aarch64) keeps shooting themselves in the foot, to the point where lots of companies are hedging their bets with a dark horse called RISC-V that never had a snowball’s chance in Hell before, but now could possibly win.

    And if Microsoft still hasn’t built a new home on aarch64 by the time that happens, they may accidentally be in the best position to capitalize on it.




  • Someone named Tran? If so, disregard the following:

    I assumed you were talking about “the rights of trans folks”, which is usually “trans rights”. In that case, “trans” is an adjective. Like “human” in “human rights”.

    If you did want it to be possessive for trans folks, similar to if you said “humans’ rights”, you’d say “trans folks’ rights”.

    Because while “human” can be an adjective or a noun, “trans” is only an adjective. So you can call someone “a human”, but not “a trans”.





    1. Fuck AI
    2. This judge’s point is absolutely true:

    “You have companies using copyright-protected material to create a product that is capable of producing an infinite number of competing products,” Chhabria said. “You are dramatically changing, you might even say obliterating, the market for that person’s work, and you’re saying that you don’t even have to pay a license to that person.”

    1. AI apologists’ response to that will invariably be “but it’s sampling from millions of people at once, not just that one person”, which always sounds like the fractions-of-a-penny scene
    2. Fuck copyright
    3. A ruling against fair use for AI will almost certainly deal collateral damage to perfectly innocuous scraping projects like linguistic analysis. Even despite their acknowledgement of the issue:

    To prevent both harms, the Copyright Office expects that some AI training will be deemed fair use, such as training viewed as transformative, because resulting models don’t compete with creative works. Those uses threaten no market harm but rather solve a societal need, such as language models translating texts, moderating content, or correcting grammar. Or in the case of audio models, technology that helps producers clean up unwanted distortion might be fair use, where models that generate songs in the style of popular artists might not, the office opined.

    1. We really need to regulate against AI — right now — but doing it through copyright might be worse than not doing it at all





  • It’s the #1 thing that drives me crazy about Linux.

    It seems obvious. You’ve got a Windows/Apple/Super key and a Control key. So you’d think Control would be for control characters and Windows/Apple/Super would be for application things.

    I can understand Windows fucking this up, cuz the terminal experience is such a low priority. But Linux?

    There’s some projects like Kinto and Toshy which try to fix it, but neither work on NixOS quite yet.






  • kibiz0r@midwest.socialtoFuck AI@lemmy.worldskills for rent
    link
    fedilink
    English
    arrow-up
    53
    ·
    edit-2
    16 days ago

    It’s worse than that.

    The goal isn’t to sell coding superpowers to programmers. It’s to drive a wedge between employer and employee. Make both of them dependent on an intermediary instead of each other.

    Think DoorDash but for coding gigs. You don’t have a job, but a series of push notifications offering a chance to review an 18-line PR for $3.81.

    Remember to respond within the next 90 seconds to maintain your priority status, and don’t decline too many offers.

    Edit: See also, chickenized reverse-centaurs.