Or in the case of Superbad, a film based on Seth Rogen's experiences as a Vancouver teenager in the late 90s, Vancouver is a stand-in for Los Angeles, which is a stand-in for Vancouver.
Just about everything I watch or listen to is served from the same iTunes Library I've had for over 20 years. It's more important to me now than it has ever been.
I would really love to see something like EndBASIC built around a Lisp-family language.
I've recently been playing around with some of the old Logo implementations from the 80s and I've been really charmed by just how powerful and elegant that language can be once you've wrapped your head around it. It makes BASIC look barbaric by comparison.
Let's say that back in 1930s when they were assigning frequencies for the broadcast television channels, they allocated enough extra bandwidth for a future color (chroma) signal, apart from the existing monochrome (luma) signal.
If the bandwidth was available, would it have been possible to include separate chroma and luma components in the broadcast signal without the two interfering with each other, thereby producing a much cleaner color image while maintaining backward compatibility with the original B&W TV sets?
Isn't that essentially what happened? In the 1930s, the channels were allocated at 6 MHz spacing, but only needed about 3 MHz of bandwidth for the luma channel. There might have been some foresight involved, but the gaps between channels also allowed for cheaper, less precise tuners. Then in the 1950s they added a 1 MHz chroma signal on a 3.58 MHz upper sideband, expanding the channel bandwidth to just under 6 MHz.
6 MHz was there from the start. If it wasn't, the CBS field-sequential might have won. Both government (FCC) and industry (RCA) were pushing for a backward compatible system and there was enough bandwidth to pull it off. OP asks what would've happened had chroma been given its own separate, non-overlapping band. That was not possible while maintaining compatibility.
You could argue that if extra bandwidth were available it might be better allocated elsewhere for improved picture quality. But yes. It would've reduced lots of engineering complexity and probably would've looked very much like PALplus.
From my years of iOS development—and based on https://xcodereleases.com typically ships two major Xcode updates each year:
- X.0 (September): bumps Swift, SDK versions, etc. It also tends to have a noticeably longer beta cycle than other releases.
- X.3 or X.4 (around March): bumps Swift again and raises the minimum required macOS version.
Other releases in between are usually smaller updates that add features or fix bugs, but they don’t involve major toolchain-level or fundamental changes.
Today’s release doesn’t bump the Swift version, which suggests the core toolchain is essentially the same as Xcode 26.2—so it makes sense that the minimum macOS version wasn’t raised either.
Agreed - I tried installing Xcode26.3 on my mac running Sequoia and there's no "intelligence" pane in Xcode settings to connect Claude like there is in the docs.
Computer Chronicles and MotorWeek were fixtures of my Saturday afternoons as a young kid in the 80s. 35+ years later both shows became fascinating and priceless time capsules of the era.
For me it was those two, but also Bob Ross (of course!) and Star Gazers (Keep looking up!). I enjoyed drawing and astronomy and the entire reason I got into computers was to program the equations from the astronomy with your pocket calculator book.
That's also why Apple renamed OpenStep to Cocoa. Java was supposed to be the primary development language for Mac OS X (because Java and Cocoa go great together).
For a while you could write OSX stuff in Java. I did. They also had some pretty okay JNI bindings for stuff like quicktime, so I was able to write a java application that used quicktime to load and display videos. I needed to analyze video streams for my dissertation, so I wrote some custom visualization stuff in java that used the quicktime bindings. Good times.
