• 2 Posts
  • 101 Comments
Joined 2 years ago
cake
Cake day: June 7th, 2024

help-circle
    • 1️⃣ Start screen recording yourself 🎦
    • 🦟 Fix the bug and write up the PR, except…
    • Throw in a lot of gratuitous emojis 🎉🏆🤝 – em-dashes – and “On the other hands”
    • 📤 Submit it
    • When they come 😡 screaming at you about no-AI, just show them the video 😎
    • All their outrage will be spent on accusing you of using 🤖AI.
    • Where it all started will be forgotten 🥳
    • Profit 🏆

    Comment written by 💯 human




  • The whole thing about moving from centralized to decentralized had a core glitch. Whatever server you signed on would effectively lock you in. What happened if things didn’t go as planned? LOLA is a good step, but it’s still not enough.

    Long time ago, URNs were designed to handle URLs that moved. These were permanent resource indicators that would allow the underlying data to move but not break the link. The HTTP redirect codes were supposed to help. Idea was, a website could redirect to a new location so clicking on a link would never get you a 404. It assumed both source and target site were still accessible so source could send the 301, 302, 307, or 308 codes. Very genteel. But what if the source site or account were zapped or suddenly blocked?

    Redirect codes work if the owner moved them and has now set up a suggested next location. But it doesn’t handle the negative reasons. Getting forcibly banned, site getting hacked, sites shutting down, owner not paying the bill (for economic, health, or political reasons), anything else that could render the content inaccessible. It’s nice to add constructs to avoid getting account hacked. But what if owner is in jail, muffled, coerced, going through a tough personal stretch, or dead?

    They still need to solve for real life and how shit happens.




  • So many system bugs are because of unclear memory ownership, buffer overflows, and race conditions. C/C++ don’t help you avoid any of these footguns. Any other system that relies on GC is non-deterministic and prone to mystery hiccups, which is why OS and driver tech has been pretty much the same foundation since the 70s.

    Rust lets you avoid 2 of those 3 issues (thread race conditions are still a thing). And being compiled, instead of interpreted bytecode means you can get reasonable performance on smaller machines. No wonder these OS guys are so excited.


  • I’ve got a pretty large Rust/Tauri program going. Breaking things into crates help, but if you touch enough bits of common libraries, everything needs to get rebuilt anyway.

    I use Makefiles for everything. What I found helps is breaking out the parts that don’t change much into separate Make commands (like generating icons, linting, frontend, tests, etc), then leaving “make go” as the simplest inner iteration loop. That way, it’s a lot more bearable.

    There’s also “make build” and “make fullclean.” You start one of those and take a long break.







  • The reason computers originally became popular in cars was to help with fuel efficiency. So it could figure out the proper fuel-to-air mixture and engine timing on-the-fly. Everything else could be done through physical wires, switches, and electric servos.

    The problem is manufacturing and repairing all those wires, switches, and servos becomes cumbersome. So manufacturers moved to modular pods that could be plugged together via bus harnesses. That way, you can pop out a malfunctioning box and be back up, instead of requiring the corner mechanic to become an automotive engineer.

    The problems started when each of those boxes were made to be closed and proprietary, requiring custom integration and tools. The vehicle makers became systems integrators, wanting to lock out competitors by forcing all repairs to go through their dealer network and using their expensive parts.

    If someone figures out how to get all the benefits of modularization without all the negatives of vendor lock-in, and throw out the pointless telemetry collection, that would be a great place to start.






  • They have these on a college campus nearby. I once watched one of these things try to get from a walkway onto a road after a delivery.

    It didn’t just backtrack the way it came. It was looking for a sloping ramp, but the sidewalk ledge was too high for its tiny wheels. It kept going back and forth, retracing the same paths over and over, failing, then returning to the original location, turning around and doing the whole thing again. I stopped paying attention after 15 minutes of this.

    It was like watching a drunk come out of a bar and stumble around trying to find his parked car.