> perhaps he wouldn’t have won if there was some kind of crash.
But there was! That bet started in 2007, and 2008-2009 saw the biggest percentage drop in the S&P 500 in decades with the GFC. We're talking down to levels last seen in 1996, at the worst of it in March 2009.
> While tear sheets date back to the old days when stockbrokers would rip individual pages out of the S&P summary book and send them to current or potential clients, most information is extracted online today. Therefore, any concise representation of a company's business fundamentals could be considered a tear sheet.
Many games of that era have this. Usually the first track was the data, everything after was just normal cd audio data. I noticed it with most of my tg16 cd games and a few ps games. Once ogg and mp3 became a thing that sort of went away. Instead of 10-15 tracks you could have several hundred in the same space with similar quality in audio.
> Once ogg and mp3 became a thing that sort of went away.
I'd assume the issue was rather the game needing the space: the first few CD game generations took 50, 100, 200MB on the disc, so putting the OST in CD format was a nice easter egg. Note that games didn't generally put all sounds as CD tracks, just the actual music.
Once your game starts filling the CD, to say nothing of needing multiple CDs worth of storage, having the OST included is not an option anymore.
>so putting the OST in CD format was a nice easter egg.
It wasn't an easter egg; it was how the games accessed and played the in-game music (and digitized speech when that was a new, exciting thing). There would be one huge data track and then dozens of small audio tracks. If the game did take multiple CDs, then either (a) you installed all the discs but all the audio was on the CD that had to be in the drive for the game to play or (b) each CD had the audio needed for the levels that were on that disc (I think that scenario was more common on PS1 games, but I could be mis-remembering)
> It wasn't an easter egg; it was how the games accessed and played the in-game music
Except they never had to do that, even before the MPs, they could always have stored the audio data as regular files on the disk image. Using CDDA just makes things more complicated as you need to reaccess the raw media instead of just reading the data from the filesystem.
In those days CD drives could output the audio as analog or digital signals separately from the data bus, using a cable that connected directly to the sound card for zero-overhead music. Commodity CD drives on the PC go back to about 1992 and playing CD audio would have been prohibitive overhead for contemporary CPUs
It really wasn't so much ogg and mp3. But the fact that systems got powerful enough to run both games alone rather complex task and also decode the music. We often forget just how slow systems in early nineties were.
Oh, listening to In Sides while shooting strogg? Maybe not a bad match. I don't think I can stomach this album anymore, though. I shouldn't have listened to it as much as I did back then.
Yeah, it had this amazing habit of reaching the transition in "Adnan's' right as you came into a large open space, things like that. Memory is a little rusty from 1997 but I preferred it to the Reznor tracks, despite being a big NIN fan.
I'm 52 years old, and I have diaries stretching back to 1980 (when I was all of 9 years old!). Over the years I gradually worked on transcribing them from handwriting to comupter text, and that's made them much more accessible in the present day. E.g., when my father passed away in 2020, it was so easy to just search for "Dad" and revisit long-ago snippets from the past. (And to sadly realize that I'd taken his presence for granted over the years.)
I still regret my roughly ten-year diary hiatus from 1985-1995, losing the bulk of my formative high school/college years in the process. Because as I've grown older, and those memories become more and more distant, I've lost a lot of the day-to-day detail, trivial though it may have been, of my past.
I've been planning to scan my old journals. Waiting for OCR to comprehend my messy writing. Now I think I will read them out loud, record it, speech to text.
Conversely, I'm 52 years old and I've never experienced living in a housing bubble until this most recent ten-year stretch (the runup in property values prior to the 2008 GFC mostly missed my area (DFW), though we were still adversely affected by the aftermath).
> But are you really going to say they stand up to films made in recent years with a fully mature vocabulary?
Sure! I've seen 19 of the 42 films you counted as being made between 1920-1945, and I'd say the overwhelming majority of those 19 definitely still hold up. Are you seriously telling me Double Indemnity (1944), City Lights (1931), Duck Soup (1933), and Casablanca (1942) are only fit for consumption by film students? If so, I'd say "lucky film students!"
I am telling you that Metropolis for always being cited as one of the greatest films of all time is not actually that good, although very very influential.
Perl is usually installed by default on Linux and Unix systems. Ruby might be there, it depends.
Perl is faster than Ruby. Ruby has been one of the slower scripting languages.
But Ruby has been working on performance improvements in the past few releases. I have not seen any benchmarks of the current Perl versus the current Ruby, so this may have changed.
Perl is more concise than Ruby allowing more functionality for less code.
>> As for speed it's useful to distinguish between startup and runtime.
The JVM would like a word. (It has slow startup, but can be very fast at runtime due to JIT optimization and cacheing.)
Scripts should start and run quickly.
Ruby has historically been fairly slow which is why Ruby 3 focused heavily on performance. It has been improving a lot, but I have not seen any benchmarks against other programming languages.
The thing to remember here is that speed is relative. I haven't checked but Ruby 3 is probably faster than Perl 5.0. For most scripting purposes on modern hardware Ruby is plenty fast enough. Whilst there may may be marginal speed differences between Perl, Ruby and Python the differnce is insignificant.
I used Perl then Ruby as my main language for almost a decade each. These days, I don't really write Ruby anymore; I moved on to Elixir and never looked back. But I still find myself using Perl on the command line, in contexts where Awk or Sed would also make sense. Ruby never optimized for the one-liner case IMO.
I'm 51. If it was me, I'd DCA it monthly into a 60/40 index like VBIAX over the next year or two. If the market drops near-term, you can re-assess your appetite/tolerance for risk. If it doesn't, you're easing your way into what should be a decent long-term position.
I was told that deferred_ptr/deferred_heap was supposed to solve these things for C++, so perhaps that would make Rust the option with worse problems in this department. Not sure where it got by now, though.
While the peak-to-trough drop wasn't as bad as QQQ's, the S&P 500 still managed to fall something like 40% from its dot com peak in 2000 over two years, and didn't fully recover until 2007. (And of course 2008 sent it right back down again for another five-ish years).
But there was! That bet started in 2007, and 2008-2009 saw the biggest percentage drop in the S&P 500 in decades with the GFC. We're talking down to levels last seen in 1996, at the worst of it in March 2009.