• 3 Posts
  • 60 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.


  • What holds me back is that nobody has made a decent MX-mount click-leaf switch. Clickiez are out due to their astronomical price (~4x that of Kailh Box or Matias switches) since my board uses 129 of them.

    Kailh Box Jade/White/Pale Blue feels nice-- super stable-- and has the vast MX keycap ecosystem, but the click is still a bit high pitched. Gateron Melodic is the La Croix of clicky switches. Matias Click sounds great but are a bit sensitive to poor keycap fitment (I have some Alps-compatible relegendables and vintage caps that needed shaving their stems to not bind) plus there’s limited keycap choice and they feel a bit looser.

    The I-rocks “Alps but with a MX stem” design might have worked if it was dold to end users rather than as a preassembled board.


  • 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.









  • This is big “if we break your old toys, you’ll HAVE to play with the new ones” energy.

    Tell me when they port FVWM. Seriously. FvwmButtons-- a pretty trivial dock except it can swallow other windows-- seems like it would be out-of-bounds on Wayland unless it was owned by the compositor itself to access the other windows. I don’t see any of the new taskbar-tools used with Wayland compositors offering similar functionality (I could be wrong) and that seems an amazing loss of feature parity.