• 1 Post
  • 30 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle


  • I didn’t. It just looks like the fair number of Cisco (and the occasional Dell) 10/100/sometimes Gigabit switches I’ve seen in junk shops.

    I bought a nifty blue Netgear 24-port one mostly because I’m more willing to buy junk from the Humane Society shop, but then decided it was too loud (40mm fans) and went to 2.5G (with smaller fanless switches) instead.




  • I guess the assumption is more that for me, a fresh install is often about decluttering as much as anything-- the five Wayland compositors, three music players, and six pseudo-IDEs I tried and didn’t like don’t need to follow me to the next build.

    In a conventional install, that just means “don’t check the checkbox in the installer next time”. In a Nix-style system, this is a conscious process of actively deciding to remove things from the stored configuration, no?

    I suppose the closest I’ve gotten was recently migrating my setup from a desktop to a new laptop. Mostly copying over some config from my home directory, but even then, I wanted enough different stuff-- removing tools I don’t use on the laptop, adding things like battery monitoring and Wi-Fi control-- that it involved some reconfiguration.


  • I suspect the tooling isn’t quite there yet for desktop use cases.

    If I were to try to replicate my current desktop in an immutable model, it would involve a lot of manual labour in scripting or checkpointing every time I installed or configured something, to save a few hours of labour in 2 years time when I get a new drive or do a full install.

    The case is easier for defined workload servers and dev environments that are regularly spun up fresh.



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








  • I think there would be more sympathy if Cloudflare pointed to a specific limit breached and proposed ways to get into compliance at their current price plan.

    “Service XYZ is now consuming 500% of expected quota. Shut it down or we need to get you on a bigger plan.” is actionable and meaningful, and feels a little less like a shakedown.

    I’m sick of “unlimited” services that really mean “there’s a limit but we aren’t going to say what it is.” By that standard, freaking mobile telecoms are far more transparent and good-faith players!

    Perhaps this also represents a failing in Cloudflare’s product matrix. Everyone loves the “contact sales for a bespoke enterprise plan” model, but you should be creating a clear road to it, and faux-unlimited isn’t it. Not everyone needs $random_enterprise_feature, so there’s value in a disclosed quota and pay-as-you-scale approach: the customer should be eager to reach out to your sales team because the enterprise plan should offer better value than off-the-rack options at high scale.





  • I’d love to know what the domestic spin is on this.

    What specifics is he promising this will deliver domestically? I can’t imagine Buenos Aires is on Putin’s shortlist even without the threst of NATO, and it’s not like Americans are goung to start beating the doors down for Argentine imports.

    There’s tactful good relations, and then there’s “sempai notice me”. Although, the Cosplay Crusader may well be familiar with that trope.