I was certainly never confused--but Shmessy was right, I didn't frame the proposition very well--which is better for Massachusetts: BLX or NSRL?
Again...two projects about as similar as apples and pork sirloin being mashed by incredible feats of arbitrariness into a binary question. There is no fruitful inquiry here. The mental gymnastics required to make an either/or question out of that are full-on invented make-believe. Maybe if you're really bored there's a daydream make-believe discussion to have there...but what problem actually gets a posited solve wasting time hashing that out? It's not real. It's game night playing round of "Would You Rather?"
Now please re-read the previous post where I describe--once again--what's wrong with the puzzle pieces fitting in Lynn Terminal's transpo portfolio, the only conditions that fix it, and what the stakes are. RUR-via-NSRL has one hand tied behind its back for North Shore commutes if you don't build BLX. The frequencies aren't high enough and transfers aren't convenient enough
solely via that mode to trim the bus re-route waste and reinvest the savings in last-mile frequencies (the BIGGEST source of potential RUR ridership growth across the North Shore). And the incredible overload swells hitting South Station for the Red Line transfer greatly destabilize the CBD if you don't have a complete augmenting Lynn-Charles/MGH Blue corridor diverting the loads. There's no either/or...and not even a half-assed RUR+NSRL-only approximate that mathematically addresses enough of the bus hackery to heal that wound. The threshold for the fix is so very specific and measurable, it doesn't leave loads to the imagination on hand-waving at anti-specific substitutes or binary-choice diversion games. There's a nail that has to be driven head-on >>
RIGHT HERE<< for hitting the threshold for the bus perma-fix, or North Shore doesn't have a load-bearing wall to support its transit shares. So...of course, let's get lost in a talk about paint swatches and matching curtains for the finished room instead of measuring up what nail size to drive and getting our matching hammer.
Every attempt to keep pounding at these wholly fake/arbitrary binary-choice daydreams has to reckon with ^those^ facts...that only implanting rapid-transit level service and transferrability solves the bus terminal breakage enough to trim the bus waste and reinvest it as functional doubling of last-mile frequencies. Anything even 10% shy of that target functionally accomplishes 0% of the goal, because it won't be enough improvement to terminate/recirculate the buses at Lynn Terminal sans all the service-punitive routing waste.
This is screamingly obvious...and yet every "Yeah, but..." offered up just buries its head in the sand with ever more fantastic arbitrariness in pants-shitting terror of looking those terms of a perma-fix in the face and making an honest attempt to address them. Why is that? The issues--the breakage and the threshold for a fix--are so goddamn
specific here they aren't dekeable. So I find it very hard to take seriously these invented counterarguments when they are based 100% on deking those specifics. As tall an order as true non-BLX alternatives would be, it
is still possible to come up with a testable-theory project alternative, which would indeed be a pretty fascinating discussion to real-world hash out.
"All Massholes are crammed into one restaurant with a menu of only 2 items: apples and pork sirloin. Which do they eat?"...is not one of those discussions. It's a make-believe time-waster that isn't even asking a question in the general direction of the specific problem here.
If all it comes down to is $ invested in the project (including inflation-adjusting on the bonds 30 years out when they're theoretically retired blah blah blah) vs. a reasonable projection for increase in state GDP generated by the enhanced infrastructure/connectivity, jobs generated, multiplier effect/increased velocity of money, then perhaps it is a simple question.
No...it doesn't come down to $ invested in project. That's all based on a make-believe assumption that the projects are remotely comparable in what they do, and/or magically interchangeable at addressing the extremely specific transportation problem holding Lynn Terminal + greater North Shore transit shares back. This is another example of begging every question EXCEPT the one that's at-stake.
And, how do you know it's a question that will never be asked by anyone, ever? I just did, after all. Resources are limited, decisions must be made, priorities must be established, then rationalized, justified. If one gets built but not the other, then, it seems to me the question will have been asked--and answered.
As explained all above...no, you didn't. You threw out still a few more arbitrary binary-alt choices that aren't anchored to any reality grounded in the actual mobility problem that's here to solve, just posed some brain-teasers about as far-removed as possible from how a reality-based inquiry would approach an ID'd problem and scoring of solution Alternatives. That's the stuff of idle time-wasters, not furthering discussion of relevant solves to a real-world problem. If it makes no attempt at reference, much less addressing, the conditions that shape the problem...it's not even talking in the general direction of a solution.
If the prevailing sentiment is "big problems needing big solves are hard to muster, and I don't wanna think about that so let's have an escapist 'Hot Or Not' contest to amuse ourselves"...fine, whatever floats people's boats. But stop spinning with a straight face that that's the one and the same with an issues discussion. If it won't so much as feign eye-contact with the issues at hand that are so clearly and specifically spelled out, it's not an issues discussion and isn't going to fake that smell test.