puls

It doesn't because it doesn't use any mainline rail track. Imagine if the T-Third went onto the Caltrain tracks at Bayshore and continued down the peninsula instead of terminating at Sunnydale; that would be a tram-train.

It would also be more or less impossible under current US regulations, but there's always hoping that that could be fixed.

I love this footnote so much:

> This feature does enable a neat quine: the Perl program “Illegal division by zero at /tmp/quine.pl line 1.”, when saved in the appropriate location, outputs “Illegal division by zero at /tmp/quine.pl line 1.” The reason for this behavior is left as an exercise for the reader.

This article lost me at "Most homes are not wired to handle 120kW chargers, which are likely not cheap to set up."

If the author had done any research, he'd realize that there's no such thing as a 120 kW home charger. (The weasel word "likely" only confirms the lack of research.)

I have the same machine you do and I ordered the new machine as soon as I could. Two external 5K displays is a huge unlock for more productivity.

What was the downside to doing the same thing as before by default?

Carnegie Mellon is absolutely in the midwest.

Pennsylvania is a big state.

I've been coding full-time in Swift for the last three months and at this point our source base is about 10K lines of code. Given this experience, if I had to do it all over again, I'd probably choose Swift again.

The good:

- Swift is a far better language than Objective-C. It's much safer, the type system is great, and the functional features are a joy to use.

- Everything largely works as advertised; even for a super new language, the amount of total brokenness is minimal.

The bad:

- The current compiler's error messages are frequently bad to the point of being useless. Try to mutate an immutable dictionary? You get a type mismatch when you could get an error about immutability.

- The compiler is a lot slower than I think they mean for it to be.

- The debugger takes several seconds to evaluate an expression compared to almost instantaneous evaluation in Objective-C.

- 8 MB of standard library in your app binary.

The ugly:

- "SourceKitService crashed" messages in Xcode flashing on the screen at 30 hertz.

But at the end of the day, if you're hiring an outside company to do this, why does it matter to you what language it's written in? Shouldn't they be able to use their best tools?