This doesn't feel like the right way of thinking about it---if you went from 20% of people paying fares to 80%, that's 4x the revenue with the same fixed costs, and farebox recovery goes from 13% to 52%. Now, I don't think compliance is actually that low, but the point is that you shouldn't think of fares as collecting a fixed share of the operating costs.
The costs may be fixed but so is ~87% of the revenue via tax money.
Muni can be 100% free without increasing taxes too. The people using public land to store their private vehicles are not paying their fair share. Proper parking pricing and enforcement could easily pay for Muni’s deficit.
Yes, money is fungible. But why should it be that people who park cars on the street need to pay their fair share but people who ride Muni don't need to pay anything?
It's both. Why should the public 100% subsidize private vehicle storage in vast swaths of the city (And greatly undercharge when it's paid), but not public transit?
SF has some of the most valuable private[1] and public land in the US. Why is it so pressing to charge the last 13¢ on the dollar for a Muni rider, but not for drivers to pay for the public space they're storing their property on?
[1] Private land owners know this, which is why they charge a lot to use their parking garages/parking lots in SF.
The proposal was to charge for public street parking so we can make Muni free. That's not (at least not obviously) a "fair" allocation, it's just a transfer from one group to another. I agree that it's bad for street parking to be free, I just don't think it's necessarily the best use of funds from that to make transit free. If you're spending on transit, why not spend the money on expanding service instead?
> The proposal was to charge for public street parking so we can make Muni free.
My proposal is to make Muni free full stop. Via taxes is fine with me, I provided another way that doesn't necessitate that. We are already paying for the vast majority of each Muni trip from taxes.
>That's not (at least not obviously) a "fair" allocation, it's just a transfer from one group to another.
You're saying we're just transferring from one group to another, well SF was built for people before cars became commonplace, with excellent public transit before it was torn out for cars. I'm arguing that some of that needs to be transferred back to the people for better use (Bigger sidewalks, bike lanes, restaurant parklets etc.)
>If you're spending on transit, why not spend the money on expanding service instead?
Expanding service is great, but you'd be hard pressed to pay for it via parking meters/tickets and it costs even more to run a system on top of that, particularly the metro system.
It is interesting that there's a gap between the "prove N–S existence" conditions, which assume no forcing term, and the "counterexample" conditions, which allow a nonzero forcing term. In theory both (A) and (C) could be true.
Yes, I think the idea is that you start with the individual squares, and you can sew two pieces together at a time. If you come to the point where you need to join two pieces along more than one edge, you have an L-seam.
I don't think unreadable skills implies proper engineering at all. It's just as or more likely that they're the result of a blind iterative process with no clear improvement signal. (And whether iterative RL over a set of evals is actually proper engineering here is another question...)
> And whether iterative RL over a set of evals is actually proper engineering here is another question...
I'd put it like this: regardless of the merit of how they're applied, it would at least demonstrate possession of the advanced skills expected of experienced software engineers.
Due to their essentially cryptographic nature, I don't think SynthID et al are very easy for LLMs to speak natively. They have other ways of doing steganography.
reply