• 0 Posts
  • 928 Comments
Joined 1 year ago
cake
Cake day: January 2nd, 2025

help-circle



  • Insider, there’s been massive change along the way.

    Yea, fundamental paradigm hasn’t changed from a UI perspective, but that’s just to keep people from having to re-learn too much at once.

    Under the hood, the change from NT3.51 to 4 was noticeable from a stability standpoint, then from NT4 to Win2k was massive - true plug-n-play, dynamic event capability, performance and stability were significantly improved. XP was a small increase over that.

    I had to reboot NT4 every day, often multiple times if I changed hardware, like using a vendor dock even.

    Then Win7x64, another massive increase in performance and stability.

    Win8 can die in a fire, because it wasn’t any better than 7, with some dumb stuff in the UI and the beginning of MS really scewing up control panel.

    Win7 is the high water mark to me, though Win10 is virtually identical to server, it even runs exactly the same Hypervisor framework. The differences from 10/11 to server are mostly tuning, how updates are managed, and server lacks some user-focused services.

    I’ve run Server Core and Win10 (for Hyper-V) on the same hardware and the performance difference wasn’t visible. It would take running a large server and heavy VM workloads (eg databases, regular VM migrations, etc), to see the difference.

    I don’t see a major performance increase going to Win10 as a single-user machine, but virtualization is much faster than if I were running even Win10 with VMware workstation (naturally).



  • I’ve never heard “tinhorn” used to refer to an actual object - what an interesting twist language makes through different eras and groups.

    The only definition I’ve known is the “inexperienced gambler”:

    tinhorn gambler

    A cheap, small-stakes gambler who boasts and dresses ostentatiously to seem more successful or skilled than they really are. An allusion to the dice game “chuck-a-luck,” which features a chute, called a “horn,” from which the dice are dispensed. More high-class leather horns were often substituted with makeshift tin ones, and thus cheaper, lower-stakes gamblers were known for their tin horns.He always wears the same three-piece suit and slicks his hair back like he’s the Great Gatsby when he comes in to play, but everyone knows he’s just a tinhorn gambler who taps out after losing a couple hundred bucks.

    https://idioms.thefreedictionary.com/tinhorn

    Not to say you’re using the term incorrectly, at all, just a neat observation about how language drifts.






  • It’s a fantastic app, but doesn’t do sync like SyncThing or Resilio Sync.

    It can do things similarly if you work at configuring it, but it can never monitor a remote and sync based on file changes there. That’s not a criticism, it’s a function of the file system approach it takes - it can sync with many different file systems, but it doesn’t have a client at the other end - it simply interfaces with that file system. Fantastic actually.

    I’ve used it since about 2010, it was my solution for moving files back and forth for a long time. I still use it for specific things, but I’ve put more effort into ST and Resilio Sync config and management because they’re full-on sync suites.






  • Nothng official, sorry, wish I did!

    Mostly personal experience. But that experience is also shared among a group of peers and friends in the SMB space where their clients think they can keep stuff on externals in an office safe only to find they’ve gone tits up nearly every time they pull them out a couple years later. And not the enclosures, the drives themselves - they all have external drive readers for just these kinds of circumstances.

    In the enterprise you’d get laughed out of a datacenter for even suggesting cold drives for anything. Of course that’s based around simple bit rot concerns, and why file systems like ZFS use a methodology to test/verify bits on a regular basis.

    If nothing else, that bit rot should be enough of a reason to not store data on cold drives. It’s not what drives were designed (or tested) to do.

    Edit: Everything I’ve read over the years suggests failures happen as much from things like lubricants hardening from sitting as from bit rot. I’ve experienced both. I’ve seen drives that spin up after ten years but have numerous data errors, and drives that just won’t spin up, while their counterparts that have run nearly continuously are fine (well, their bit-rot was caught by the OS and mitigated). With a running drive you have monitoring, so you know the state.