Cool! I can see how optical media could, in theory, be very long-lasting as long as you don't use materials that oxidize or otherwise degrade over time.
tunetardis
Well I guess I'm picturing DNA encoding like a RAID billion in terms of redundancy, so with some checksumming, you ought be able to sort out any mutations? But I'm no geneticist.
That's why I back up my data on stone tablets in Cunieform.
Seriously though, if you wanted data to last for centuries, what would be your best bet? Would it be some sort of 3D-printed mechanical storage? At least plastics are generally not biodegradable, though they are photodegradable, so I guess you'd want to stick your archive in a dry cave somewhere?
Or what about this idea of encoding the data in the DNA of some microbe and cutting it loose? What could possibly go wrong?
You know, I'm not actually quite sure what I'm doing, but I can tell you I am not looking at the keyboard. I suppose it's similar to how I play violin? I don't look at where my hand is but it shifts to different positions depending on what makes the most sense for the pattern I'm trying to play, and yes, a different position does imply a different fingering to reach the same notes.
When learning to program, I initially tried to follow the touch typing guidelines, but they say that you should use the right pinky to reach every key towards the upper right end of the keyboard, which gets old fast given how frequently you need to access them. And just as with music, there are patterns. In programming, you may frequently need to type {}
, :=
, or even something like \{\}
, and flailing around with the pinky is a good way to give yourself carpal tunnel. So your right hand learns to shift to hit those keys using a combination of fingers.
As a Gen X, I think my typing speed peaked around late high school/early university? I tried to teach myself touch typing and got moderately proficient. Then I got into programming where you need to reach all of those punctuation marks. So my right hand has drifted further to the right over the years, which is better for code but suboptimal for regular text.
One thing that's really tanked for me though is writing in cursive. I used to be able to take notes in class as fast as the prof could speak. Now I can scarcely sign my own name.
I suppose it depends on how you look at it. Take solar, for example. On the one hand, you could argue that if your primary goal is to generate heat, you might as well use a solar thermal plant with lots of focusing mirrors over photovoltaics. The conversion to electricity first would inevitably be far less efficient.
On the other hand, if you've got your PV plants for electricity already but they are overproducing at times, there is the question of what to do with the excess power, and using it to run heat pumps may actually be a pretty efficient application at the point?
I paid a visit to Green Bank WV once out of an interest in astronomy. The giant radio telescopes are truly a sight to behold!
Less impressive were the people camped out nearby who saw the place as the promised land where they could cast off their tinfoil hats in the cellular-banned zone surrounding the complex.
There were breaking changes between C and C++ (and some divergent evolution since the initial split) as well as breaking changes between different releases of C++ itself. I am not saying these never happened, but the powers that be controlling the standard have worked hard to minimize these for better or worse.
If I took one of my earliest ANSI C programs from the 80s and ran it through a C++23 compiler, I would probably need to remove a bunch of register
statements and maybe check if an assumption of 16-bit int
is going to land me in some trouble, but otherwise, I think it would build as long as it's not linking in any 3rd party libraries.
I think the thing with C++ is they have tried to maintain backward compatibility from Day 1. You can take a C++ program from the 80s (or heck, even a straight up C program), and there's a good chance it will compile as-is, which is rather astonishing considering modern C++ feels like a different language.
But I think this is what leads to a lot of the complexity as it stands? By contrast, I started Python in the Python 2 era, and when they switched to 3, I was like "Wow, did they just break hello world?" It's a different philosophy and has its trade-offs. By reinventing itself, it can get rid of the legacy cruft that never worked well or required hacky workarounds, but old code will not simply run under the new interpreter. You have to hope your migration tools are up to the task.
Well, I managed to join a hispanic choir at a Portuguese church and I must say we're having a blast, language barriers notwithstanding. I am of neither ethnicity but I just play violin so it doesn't matter. And man, latino hymns rock!
Of course I don't understand a thing the priest is saying. This week I thought hang on, I'll just run Google Translate as he's speaking. But I think there's a problem. It could be he's speaking Spanish with a thick Portuguese accent and it wasn't coming out right? Unless he was actually saying:
…And sushi are big carts of yesterday and today as farms catalyzed for purposes. He is not saying about Jesus…
I didn't even have a color monitor :'( I would've been jealous of yours.
I almost quit programming too when my brother walked in one day as I was feverishly typing. "What? You're programming basic? That's for losers." Then he whips up a ski slalom game in a single incomprehensible line of apl and I was like wtaf?
Today I'm a professional dev and my bro is a perl hacker. I still can't understand a line of his code.
I thought I read somewhere that when they were making one of the Toy Story movies, there was some catastrophic data loss that nearly tanked the whole production. But then one of the animators came back from maternity and said wait, I think I have most of it synced to my home server? And the next thing you know, John Lasseter himself is barrelling down the highway to her place and it turned out yeah, she did have it.