• 2 Posts
  • 37 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle

  • The Internet boom didn’t have the weird you’re-holding-it-wrong vibe too. Legit “It doesn’t help with my use case concerns” seem to all too often get answered with choruses of “but have you tried this week’s model? Have you spent enough time trying to play with it and tweak it to get something more like you want?” Don’t admit limits to the tech, just keep hitting the gacha.

    I’ve had people say I’m not approaching AI in “good faith”. I say that you didn’t need “good faith” to see that Lotus 1-2-3 was more flexible and faster than tallying up inventory on paper, or that AltaVista was faster than browsing a card catalog.


  • I have to think that most people won’t want to do local training.

    It’s like Gentoo Linux. Yeah, you can compile everything with the exact optimal set of options for your kit, but at huge inefficiency when most use cases might be mostly served by two or three pre built options.

    If you’re just running pre-made models, plenty of them will run on a 6900XT or whatever.



  • I believe the huge mistake in HTML wasn’t having some sort of element-level addressability.

    People went insane over “the page flashes for 15ms because we have to reload the header and footer and it doesn’t look NAAATIVE!” and the response was to SPA/AJAX everything, inviting a huge Turing-complete nightmare of possibilities when 95% of what peopleneed would be delivered with < form action=“blah” replace_with_response=“#foo” >

    That and a dearth of native widgets-- a < combobox > and a < menu > that worked like the system menus might have kept JavaScript as the sick oddity it should be.









  • Runit works well enough for me; I’ve only added one nonstandard service (launch a custom tool to drive an external stats display) and it works fine. My ,xsession has to load some polkit and pulseaudio stuff but that could be because I’m not using a full desktop like KDE/GNOME/XFCE that do those things for you.‘’

    I don’t really try to do custom package recipes because I tend to ./configure;make;make install stuff I want at random.

    EFI boot is no problem. I think my root is btrfs, but the /boot/efi is vfat. Refind is pretty first-class, but sometimes it has stupid conditions where it tries to default to the wrong kernel version if you have multiples installed (I think it sorts by timestamps or filenames in a way that sometimes work counterintuitively; discarding old kernels largely fixes it)

    Haven’t really had too many showstopper problems with xbps. I probably sledgehammer it a bit-- occasionally when it says a repo certificate is out of date, I usually end up doing a full update rather than selectively upgrading packages.



  • Yeah, he was one of a long string of lunatic leaders, which evidently “democracy” has done little to temper. The thing I recall about him was a bit in a reference book to coins and currency: at one point in the 1950s, the central bank issued a 500-hwan note that had a large central portrait of him (the overall design looked like a cheap riff on US currency of the time), and rapidly replaced it because he concluded people folding it in half across his face (as people do with banknotes) was some symbol of defiance to him personally.

    They don’t teach that style of crazy in dictator school.

    As for the “Korea is a puppet and exists only as long as the US props it up”, duh, but I figure there’s perhaps some chance to exploit some “we’ve been under the yoke so long we no longer notice it” and “we’re a big strong country that thinks it can actually engage internationally” mentalities to loosen the fixation with copyright and chasing those imagined license revenues that will never materialize.






  • No, this is a general practice-- I see it a lot with third-party vendors who want you to integrate with their services. They’ll expire the documentation portal password after 90 days, but the actual user facing service still accepts the same “password123” that’s been set since 2004.

    I suspect the pattern is to protect the vendors from developer scrutiny: by the time you’ve jumped through enough hoops to read the docs and realize it’s trash, the execs have signed the contracts and the sunk costs are too high to bail out.

    Also add another 6 months to actually get the credentials for the test environment.