For fixed route transit, speed is latency. The faster the bus can make the average trip, the tighter the timetable can be given the same number of buses. Fewer stops also improves consistency which means you can plan to arrive at the stop closer to the scheduled time, and timetables can be tightened even more by reducing the layover times that keep the bus synchronized with the time table.
Separately, the variability problem can be somewhat solved with the real-time location updates that many agencies provide. You'll still have to wait the same amount of time, but some of it can be done comfortably in your house when the bus is running late.
Sections of lines that already have meaningful congestion at adjacent stops wouldn't be a good target for balancing. WMATA in D.C. recently eliminated about 5% of bus stops as part of their overhauled bus network, this is how they described their strategy[1]: "We thought carefully about each stop, looking at things like how many people use it, how far away it is from the next stops, and whether it's safe to walk there. We also listened to feedback from thousands of bus riders."
Additionally, many stops with a lot of people loading and unloading are hubs which would never be balanced away, and often are designated timing points where the bus will wait to get back on schedule, so loading/unloading time is often irrelevant because predictability is being prioritized over speed. Improving speed and consistency with techniques like removing unnecessary stops increases predictability and allows for tightening up timetables and minimizing average hold times.
Demand-responsive transport (DRT) has been tried a bunch of times in all sorts of different environments and pretty much never lives up to the promise. Predictability is really important and ridership drops as soon as users start having to plan too far ahead, which in the past has been essential to DRT routing.
Autonomy could improve responsiveness to demand but you still run into other issues. DRT usually won't be able to take advantage of things proven to make buses faster and more consistent (bus lanes, reducing stop count, transit priority signals). Futher, consistency and response times gained by dynamic routing can easily be overshadowed by increased variability in trip time as the route adjusts to add new passengers or make out of the way drop-offs.
I've seen it work pretty well in a number of places in the form of privately owned minibuses/vans that can rapidly go where the demand is needed.
As an example, all throughout the Eastern Caribbean this system works really well (in my experience better than most centrally planned bus systems in large cities). On any given island you can go to any main road and within a few minutes a minibus will come along. Most of the time if your aren't familiar with the geography, you just tell the conductor where you are trying to get to, and they will make sure that you get off in the right spot to get where you are going or connect to another minibus. Typical cost was ~$2.
Predictability was pretty low, but because of the small size of busses, there were a lot of them roaming around, I don't think I ever waited more than 15 minutes, and that was in very out of the way places.
It's really not ideal. Similar systems are common in Central Asia. They make it difficult for travelers to predict journey times, it's unfriendly to tourists, and it's much less accessible to other populations (e.g. the disabled). They also don't scale well to large urban environments or out of the way journeys in my experience.
Yes, like all systems, it has tradeoffs. Although I would argue that some of the downsides you highlight are worse with traditional bus systems (e.g. the Caribbean bus conductors will happily guide tourists, and I have seen them go off-route frequently to drop off someone with limited mobility. Large cities in other parts of the world have managed to scale the system out to fill in gaps with other forms of transit like Lima, Peru)
The GP was arguing that it NEVER works out, and I'm just pointing out that it does work in many places.
I would much rather rely on the Caribbean minibus systems than try to rely on transit in cities like Phoenix.
To standardize a journey time in a scheduled system, you subtract the origin scheduled arrival from the destination scheduled arrival. Map apps will even do this for you automatically. If the bus is unreliable, you add error margin. A demand shuttle system usually has a much larger variance, which means you can't predict that the journey time will be acceptable and you'll find some other way to get around.
How do buses fair in this regard?
You look at the route map and the schedule to decide? Again, map apps make this trivial for regularly scheduled services.
> has been tried a bunch of times in all sorts of different environments
Has it? When, where and with what technology?
> Predictability is really important and ridership drops as soon as users start having to plan too far ahead
Uber etc have proven this to be patently false. Existing buses are experiencing dropping ridership - Uber is not.
> won't be able to take advantage of things proven to make buses faster and more consistent
You're replacing buses with auto-shuttles. Just let the shuttles use the bus lanes.
> bus lanes, reducing stop count, transit priority signals
All of these are usable if you widen the scope to include auto-shuttles.
> consistency and response times gained by dynamic routing can easily be overshadowed by increased variability
What is the difference between Busing and Shuttles here? A bus user can keep yanking the stop cord, there can be 1 or 2 disabled passengers who take several minutes to board, there can be 50 children getting on / off. These issues are constants and all are improved with demand based shuttles.
On top of what others have said, the Watchface/App dev experience is pretty great. The OS provides a lot of compositing and animation features that encourage really lively and cute designs, and the Pebble app has a JS runtime that allows apps to do whatever phone-side stuff you need without having to build separate Android and iOS apps (or, as a user, install a ton of companion apps). Spin-up and iteration is really easy because pebble-tool manages building, deploying to QEMU, and running the phone-side code in Node.js so that you can launch and test your app end-to-end with one command.
Having to write C on the watch-side isn't everyone's cup of tea but they are actively working on a replacement for rocky.js so that you can write everything in JS.
Lemonade doesn't support your claim that FSD is a safer driver than you are. It just says that, most charitably, they believe FSD and a human operator are safer than just a human operator (The co-founder said exactly this to Reuters [0]). Further, the program has only been around for a week and their marketing copy specifically cites "Tesla's data" as the source for the 50% reduction rather than any sort of independent analysis.
They are putting their money behind their words, unless there is some backroom deal we don't know about. If a human operator + FSD is twice safer than human operator alone, then FSD is still a large safety improvement. Considering how human operators behave with these systems, I'd also wager having the human operator (many don't even look at the road!) makes only a small difference.
> They are putting their money behind their words, unless there is some backroom deal we don't know about.
Their product is dynamically priced and individualized, and there is no guarantee of what the base rate will be. I don't see any reason they can't keep offering the 50% discount and then adjust the base rates to reverse engineer a sustainable price regardless of FSDs real safety.
> Considering how human operators behave with these systems, I'd also wager having the human operator (many don't even look at the road!) makes only a small difference.
Lemonade will likely be getting driver monitoring telemetry and calculating rates accordingly, but in either case I'm convinced that we are still on the left hand side of the Valley of Degraded Supervision [0]. Operators may not pay full attention at all times but they likely still have pretty good heuristics for what situations are difficult for FSD and adjust their monitoring behavior accordingly.
Tesla could of course release detailed crash and disengagement data to prove FSD safety. That they do not is itself a form of evidence, and in lieu of that we have to rely on crowdsourced data which says FSD 14.x still has a very long way to go to be safer than the average driver [1].
It is in the EU but in the US ADAS won't be mandated until 2029. It would tank your IIHS rating though and all major mfgs have met a voluntary pledge to have >95% light duty vehicles ship with autobraking by 2023: https://www.iihs.org/news/detail/automakers-fulfill-autobrak...
Any time you are reading a law, especially one from another jurisdiction, you have to be very careful to consider that there may be terms with a legal or common law definition that you don't understand. In this case, "reckless" seems to be a well defined term with a fair amount of case law behind it. To my untrained eye it seems like a newspaper would be well within their rights to publish harmful information as long as they avoid "a conscious disregard of a substantial and unjustifiable risk".
It's a fine sentiment but there are a dozen different game theory principles that contribute these investments never getting made when left in the hands of the private sector. If you're upset about not reaping any of the benefits of your tax dollars, just buy the S&P 500. Of course you don't want the government investing in bad ideas but that doesn't seem to be your sticking point.
FWIW I don't think the status quo is ideal, the government should be getting more credit for and more value out of research that results in profit for private companies so it can invest in and lessen the tax burden of future research.
Can you please name/educate us on some of those game theories and how they apply? (Please don't just point me to prisoners dilemma on wikipedia unless it lays out how it applies to research funding)
Free rider problems/tragedy of the anticommons - research that isn't directly patent-able would result in a dearth of private investment because there isn't a comparative advantage in researching it
Tragedy of the Commons - Research into monitoring, maintaining, regulating, and improving resources shared by private companies
Positive externalities - Some research will not pencil out without including return on investment that cannot be captured by a company
Negative externalities - Companies won't invest in research to reduce injury to other parties (could fix with regulation also but depending on specifics this may be very difficult to enforce)
I think the confusion stems from The Register mixing up two different sets of DMA cases against Apple. The March and August EU actions are regarding hardware and software interoperability under DMA Article 6(7). For these cases, the August specification decision has a number of different deadlines specified, and I don't think any of these have passed yet.
The April 2025 non-compliance decision the app devs reference is regarding the DMA anti-steering provisions (Article 5(4)). This decision was that Apple failed to meet their compliance obligations that were specified way back in June 2024, that they would be subject to a fine, and that they would have 60 days to comply before being subject to periodic fines [1].
The Coalition for App Fairness is saying that they don't believe Apple's App Store anti-steering remediation is compliant or timely and that the EU needs to take further action.
Separately, the variability problem can be somewhat solved with the real-time location updates that many agencies provide. You'll still have to wait the same amount of time, but some of it can be done comfortably in your house when the bus is running late.
reply