That doesn’t look very realistic. I bet they just punched Godzilla for the take and then reversed the footage.
Beyond enjoying this channel, I’ve recently been thinking more and more about the value of older books. The trend of the modern internet seems to be leaning towards highly accessible but low quality information, and the amazing density of well-researched information in some older books astounds me.
That’s not to say that we haven’t made advancements (the volume of information I could find about Newport on, say, Tripadvisor vastly exceeds single-source publications like that in the video), but the combined influences of advertising, SEO, fake reviews, data collection, etc. has taken something away from this type of resource.
I’ve used this for a while now, and it’s an excellent app. It’s genuinely refreshing to have apps that just do their job without fuss or feature creep.
That’s pretty rough in a lot of ways, but man would that make ASCII box-drawing easier.
I didn’t see the content of the post, but the modlog lists the following:
Removed Post “Unpopular opinion: Wesley Crusher is not the worst TNG character… Alexander is.” reason: Rule 1 + No be cares about your “unpopular opinion” luke warm takes
Loved the Clint Howard cameo! Pretty amazing to still have actors all the way from TOS appearing!
Was anyone saying it was dead? I guess it took a hit when What went down, but I don’t think people are going to stop listening to music…
This is a good reminder I should get back on soulseek, though; I used to use it and it was pretty great.
I don’t know if it’s a canon connection to Star Trek in particular, but I loved the nod to the trope of using Toronto for NYC/Chicago/wherever.
I, the honorable King of the great nation of Recothuami, am certainly not to blame. On an unrelated note, I have an incredible investment opportunity that may be of interest to you.
Why restrict to 54-bit signed integers? Is there some common language I’m not thinking of that has this as its limit?
Edit: Found it myself, it’s the range where you can store an integer in a double precision float without error. I suppose that makes sense for maximum compatibility, but feels gross if we’re already identifying value types. I don’t come from a web-dev/js background, though, so maybe it makes more sense there.