This seems like a weird argument to make. We either pay collectively more for taxes for the roads we use, or collectively we pay WAY more for food, materials, and basically everything else if we tax trucks proportionally. Large trucks are carrying stuff, and the cost of that stuff is going to be directly associated with the cost of logistics.
Yes, some states haven't figured out what that looks like, but I really don't think the right answer is to dump all that cost on truckers. I would rather pay more for my car's operational tax, increased EV tax or existing gas tax on ICE, than disproportionately affect the price of groceries for someone living paycheck to paycheck.
Doesn’t this assume that the cost will not effect behavior? If trucking logistics becomes more expensive to properly account for the externalities, wouldn’t companies be more motivated to find more cost efficient methods. I’m sure there are plenty of items that could be shipped by rail, but aren’t because trucking is currently cheaper for the individual company, while the cost in road damage, pollution, greenhouse gasses, increased traffic, etc. are paid by everyone else.
As for disproportionately affecting the poor, sales taxes (like on groceries and other goods) and excise taxes (like on gas) are exactly the regressive taxation systems that burden the very people living paycheck to paycheck. Shifting the tax burden from skimming off the top for the people spending all their income on daily necessities, towards companies paying the full cost of their chosen operations, would give the poor more buying power and allow market forces to find and utilize the most effective and efficient means to provide services instead of the cheapest means that are only cheap because they are subsidized by everyone else.
I think you misunderstood my argument. I'm not saying vehicles should be taxed proportionally to road usage, on this I don't have an opinion. I'm saying either you do this for all vehicles or none. You cannot say "EV vehicles pay proportionally but trucks not" without clearly being biased against EV (whatever the reasons).
It's dishonest to leave that conditional off the quote. The work and risk/stress involved in running a supportless shop is quite high. So if they are freeloading by using Rocky then Red Hat is also freeloading.
I do think it's funny that they weren't even number 1 on that list though. Guess they are at least getting a lot of volunteer work from other companies!
I think there's a happy medium, and civilian tourism probably isn't really the place to be pushing the safety envelope.
Science, discovery, boldly going where no one has gone before? Absolutely safety is going to be somewhat compromised. Taking rich people to the gawk at the Titanic? I, personally, think you're a bit of dick for MacGyvering a vessel together and calling it good enough.
If it makes you feel better I had a similar, but not so exciting, situation happen to me in the past. So it's not entirely outside the realm of shit that happens. What does seem super fake is the doubling down, having it an SOP/SSP, and the tripling down without some crazy amount of escalating.
For example my experience went sort of like this:
Low Rent Auditor: Please supply a list of username and passwords for xyz systems.
Me(ccing boss and internal secops): No. Why are you asking me for that? <Links to internal SOPs, guidelines, basic common sense, etc>.
Low Rent Auditor: We need this for x box on y form. <attached>
Me (ccing their Sr. Auditor): That's not what that is asking for. Here's a copy of the PAM config. <attached>
> The first /24 in this range, 233.252.0.0/24, is assigned as "MCAST-
TEST-NET" for use in documentation and example code. 233.252.0.0/24
SHOULD be used in conjunction with the [RFC2606] domain names
example.com or example.net in vendor and protocol documentation.
Addresses within 233.252.0.0/24 MUST NOT appear on the public
Internet.
Well dang I should've thought that through before asking the question. Should've realized up in the 220-230 range was going to be mcast reserved. Can't help but acknowledge the irony in not throughly reading the docs for the documentation reserved range though.
I'll cry if/when Google buys some enterprise software I happen to support one more time. The appeal for a lot of niche enterprise software is responsive/knowledgeable tech support, willingness to implement feaure requests, and their ability to meet SLAs. All of these instantly drop to zero in a google buyout. Also there's no guarantee that the software will even exist in a usable way within a year.
I say this purely anecdotally, though, so take it as such. It has been a point of considerable personal frustration in the past. One instance was particularly painful because we had engaged the particular company looking for several custom features, and were basically buying a sizable percentage of the product they sold, with the promise that they would work with us implementing those features. When google bought them out, not only did the ability to get features implmented vanish, but so did the ones in flight.
Yes, some states haven't figured out what that looks like, but I really don't think the right answer is to dump all that cost on truckers. I would rather pay more for my car's operational tax, increased EV tax or existing gas tax on ICE, than disproportionately affect the price of groceries for someone living paycheck to paycheck.