The final quoted portion doesn't seem to agree with your final statement though?
> Those price increases are estimated to fully offset the 30 percent of price increases absorbed by U.S. businesses that import goods, so the net effect of tariffs is to raise U.S. consumer prices by the full portion of the cost of the tariffs borne domestically (95 percent)."
The idea expressed previously in your excerpts is that domestically-produced US goods do increase their revenues by the amount that their produced-abroad competitors. So things are okay from that perspective.
But what that final quotation says is that those increased revenues are 95% paid for by US consumers. In other words, they "effectively pay the tax."
I’ve got the uhk60v2. Absolutely love it. Agree with sibling commenter about its high build quality. Really great stuff.
The macro language has really developed nicely too. When I bought the uhk ~5 years ago, I didn’t plan on really using any advanced features. But things change :) I’ve got numerous little QoL things configured now. As well as this fancy flourish (which, admittedly, is a little “extra”): https://www.cgl.sh/blog/posts/wnl.html
It kinda mystifies me that they’re not more popular. Sure, expensive. But so is the ZSA Voyager, and you see tons of those! Although maybe it’s because ZSA was already known for the Ergo Dox.
Most systemd components do rely on some core systemd components like systemd (the service manager) and journald. I would say that a core thesis of systemd is that Linux needs/needed a set of higher-level abstractions, and that systemd-the-service-manager has provided those abstractions. The fact that other parts of systemd-the-project rely on those abstractions does not imply that the project is monolithic.
That's totally orthogonal to Tailwind though; there's nothing that precludes you from combining semantic elements with it. The only thing that would make a dev reach for <div class="m-2"> instead of <article class="m-2"> is the dev's own (lack of) taste. It's no different than writing out separate CSS or using inline styles.
Agreed, but I don't think that has to do with either it's "vanillaness" or the 6 month release schedule. Fedora does a lot of compatibility work behind the scenes that distros not backed by a large company more than likely couldn't afford.
> ...every package having several dozen patches trying to make a brand-new application release work with a decade-old release of libfoobar.
Applying non-vanilla flavor (patches) to libraries in able to make new packages work with old packages. (It's not just a library thing of course--I've run into packages on Debian where some component gets shimmed out by some script that calls out to some script to dynamically build or download a component. But I digress.)
Maybe I'm just out of the loop here, but I'm not aware of this being a general practice in Fedora. Yes, Fedora does a lot of compatibility work of course, but afaik the general practice isn't to add Fedora-flavored patches.
But QUIC doesn’t use 443/TCP; it uses 443/UDP. So it’s unsurprising that middleboxes that care about 443/TCP would ignore it. That doesn’t support your claim that “non-TLS 1.2 traffic to 443 is OK.”
The point I was trying to make, probably badly, was that there was no need to make TLS 1.3 pretend to be TLS 1.2 going to TCP/443. They could have picked some new port, called it TLS 2.0 (which is what it actually is), and run with that. If QUIC can pick its own port and, by the looks of it, not run into massive problems, there's no reason why TLS 2.0 can't do so too.
Throughout history, the hedonic treadmill has always triumphed. Competition and envy conjure their own objects.
Even if you want to allege that the proverbial pie will become infinitely large, any one person’s slice is finite. However big my neighbor’s slice might be, I can strive to make mine even bigger.
However, I understood GP's mention of "embarrassment" to speak more to their own feelings of responsibility. Which would be more or less decoupled from the pressure that a particular client exerts.
> Those price increases are estimated to fully offset the 30 percent of price increases absorbed by U.S. businesses that import goods, so the net effect of tariffs is to raise U.S. consumer prices by the full portion of the cost of the tariffs borne domestically (95 percent)."
The idea expressed previously in your excerpts is that domestically-produced US goods do increase their revenues by the amount that their produced-abroad competitors. So things are okay from that perspective.
But what that final quotation says is that those increased revenues are 95% paid for by US consumers. In other words, they "effectively pay the tax."
reply