orpheansodality
Joined 11 years ago
Joined 11 years ago
Fun fact: the `bell` control character is part of the ascii standard (and before that the baudot telegraph encoding!) and was originally there to ring a literal bell on a recipient's telegraph or teletype machine, presumably to get their attention that they had an incoming message.
To keep backwards compatibility today's terminal emulators trigger the system alert sound instead.
For me personally I tried svelte in the past and bounced off because there was too much implicitly happening that I needed to have a deep understanding of to model correctly. This solves basically all those problems for me.
I thought your video[1] especially did a great job walking through the pros this change brings. Thanks for all your great work on this!
1. Link for the curious: https://www.youtube.com/watch?v=RVnxF3j3N8U&t=6s
Let's compare a few situations. In the baseline you're tailing the car in front of you with a focus on not letting anyone cheat and get in front of you, let's say 50 feet away. Your commute is 30 miles, and in this frictionless sphere of traffic you're going 60mph the whole time. You get to work in 30 minutes flat.
In the second scenario you're following the 3-second rule[0]. This would put you ~285 feet behind the car in front of you. Let's say over the course of your commute 20 cars move in front of you. If the average car length is 15 feet, and they all are 50 feet away from each other, when all 20 cars are in place you're a net -(20 * 65) feet away from the original car, or 1300 feet total. At 60 mph that adds ~15 seconds to your total commute time.
Well worth having an easier time avoiding a potential crash IMO! Also has the benefit of helping prevent traffic to begin with[1]
0: https://driversed.com/trending/what-safe-following-distance.