Zip drives arrived at exactly the same time as digital art, the web, and most importantly Macromedia Flash. Maybe the CS people with a few source code files didn’t fully use the space, but the art kids certainly did.
There simply was no other option at the time than Zip drives. Others did not strike the right balance of price, capacity, responsiveness, etc. Maybe Iomega paid to get them installed, I don’t know, but there really was no other option so I can easily see schools buying them just because they needed a solution.
USB thumb drives started appearing not long after, and they didn’t suffer from the click of death, so those became the preferred media by the time those people graduated school.
Sounds like you’re overdoing it when you do exercise. Focus on just getting some kind of motion, not pushing yourself until your muscles or heart feel like they’re working hard.
Even if you feel like it’s not really doing anything, something is better than nothing. The rule of thumb for a lot of basic cardio is that you should be able to hold a conversation while doing it without pausing because you’re out of breath.
The idea that it’s just “more bits” it’s wrong, so I’m not sure your assessment is valid. Maybe at the packet level it’s just “more bits”, but at the network level a lot of processes changed. IP assignment, router discovery, etc. are different.
What you seem to be misunderstanding is that your whole process of nuking IPv6 is more work than studying the issue for a few minutes and then listening on both protocols. Setting a service to listen on a port will use both IPv4 and IPv6 by default, and if yours isn’t means you’re probably already doing something wrong or also have other bugs.
If the app was written using the S3 API, it would be much faster/cheaper to migrate to a local system the provides the same API. Switching to local IO would mean (probably) rewriting a lot of code.
Surely "read object" and "write object" are not hard to migrate to local file system. You can also use Apache OpenDAL which provide the same interface to both.
Yeah, unless you have the raw S3 API throughout your codebase you should be able to write a couple dozen lines of code (maximum) to introduce a shim that's trivial to replace with local file access. In fact, I've done this in most projects that work with S3 or similar APIs so I can test them locally without needing real S3!
Ferrite chokes easily fix this problem. Very useful to have a box of them in an office full of people.
It’s pretty clear that most modern standards (HDMI, DisplayPort, thunderbolt, etc) are so close to their physical limits that there’s no more room for errors.
Ferrite beads are awesome, and I agree that everyone involved with computing and electronical things should have an assortment of them nearby. They can fix problems.
And yeah, we're pretty close to the limits. We always have been, though: At all points on the timeline of digital electronics, we've been pushing speeds to be as fast as we can manage today. But tomorrow (and the next day, and the day after that), we'll solve more of the problems and yet-again make it even faster.
Which brings us back to...ferrite beads, and problems.
I got introduced to Monoprice back when HDMI was still new and somewhat finicky, when stores like Best Buy were fond of selling $180 HDMI cables (and even Wal-Mart wanted something like $60). In that crazy world, Monoprice was the place to buy inexpensive cables that worked.
And it was clear that HDMI was the future, so I placed an order for a half-dozen or so different-colored HDMI cables with ferrites pre-installed near each end.
They showed up, and... they barely worked. They were glitchy, touchy, and intermittent. I was frustrated, and I felt like I'd made a poor decision that cost me money instead of saved me money. In fact, I was rather pissed off by all of this.
With nothing to lose, I used a knife to cut away the plastic overmolding on the ferrites on one of the cables that was being particularly problematic. And then I smashed those ferrites with a hammer.
With the ferrites thus-removed, the cable immediately began working perfectly. It was glitch-free. I couldn't get it to misbehave even if I tried. I repeated this with all of the other cables from that order and they all started working perfectly, too.
---
So, ferrites. Their presence adds a little bit of series-mode inductance. And that's something that can be useful. It slows down the edge of things like transient voltage spikes. And since the spikes are transient, slowing their rise-time in this way reduces their bandwidth and peak amplitude. Adding a snap-on ferrite bead can be enough to turn a problematic data bus into a well-behaved data bus.
But! They're just dumb hunks of minerals. They're indiscriminate. They can't distinguish betwixt the bad signals and the good signals -- everything is affected. So while ferrites can be useful in a fight against unwanted noise, they can also be destructive of the signals that we're trying to use.
They're good to have available, but they're also not necessarily something that someone should go forth and attach to every cable they find. If there's no problem that needs solved, then there's no solving to be done.
(These I days I make it a point to actively avoid buying cables that have ferrites pre-installed, both professionally and at home. But I've got a stash of snap-on ferrites in the top drawer of the toolbox just in case; it's good to have options.)
When commas are used as part of a list of items, I treat them as if they’re bullet points written on a single line. For example, if you have items in a bullet list, but don’t want to use up all that vertical space, join the list into a single line and replace the bullets with commas. Or if the items are more complex, use a semicolon as the separator.
Corpos definitely run Windows. There are many highly technical people and advanced software that need Windows. Not every company employee is just a pencil pusher or bean counter.
This myopia in tech is so baffling to me. Windows has been around over 40 years and tech people still act like it will go away “any day now” just because they don’t like it.
Corporations will continue using Windows the same way they'll continue using mainframes (at least mainframes are interesting machines). If Dell, HP and Lenovo decide tomorrow to ship all laptops with Fedora by default, very few people will install Windows. Or notice it's a different OS. They'll just think that Windows 12 no longer has ads.
Corporations will continue to corporate. Active Directory is a powerful thing. SharePoint is another dependency that's hard to get rid of, even more so when it becomes the file server where all Office content is stored.
I have been waiting for this day since the move to SFF and thin clients. They've been threatening to do all compute in the cloud... at which point the OS, local or otherwise becomes irrelevant.
In fact, the thin client that drives my desk at [company] runs Linux with the Citrix client to connect to a VDI that exists somewhere in a datacenter we own, because regulations.
For solar panels, many people might be interested but also concerned how they look. When another neighbor gets them, people will get used to how they look, realize it’s not so bad, then be more likely to get them.
I don’t think the final conclusion necessarily follows, not with this example. Solar panels are big and obvious on top of the house. It’s not the same thing as other types of values spreading through a community. The house of a healthy person isn’t any different than that of an unhealthy one.
It could be simply that the door to door solar panel salesperson was covering that 1 km area.
There simply was no other option at the time than Zip drives. Others did not strike the right balance of price, capacity, responsiveness, etc. Maybe Iomega paid to get them installed, I don’t know, but there really was no other option so I can easily see schools buying them just because they needed a solution.
USB thumb drives started appearing not long after, and they didn’t suffer from the click of death, so those became the preferred media by the time those people graduated school.
reply