You seem to be saying that having a tax that is refunded gives a different result than not having the tax at all, which sounds like nonsense to me.
585 karma · joined June 7, 2013
You seem to be saying that having a tax that is refunded gives a different result than not having the tax at all, which sounds like nonsense to me.
So in your case the raw material producer would collect €1 of VAT from you, but this is entirely fictional, because you can immediately claim it back. Only when you sell the goods to an end consumer would VAT that cannot be claimed back be due.
I’m sorry, I fail to see the difference. In one case the tax is added during production and then returned when the good is exported, and in the other case it is never added at all. In both cases you end up with zero net VAT/sales tax paid. Where exactly does the difference lie?
VAT countries export VAT free. Sales tax countries export sales tax free.
When you import something to a VAT country, the end consumer has to pay VAT. When you import something to a sales tax country, the end consumer has to pay sales tax.
Maybe we can make some progress if you could explain how these situations are not completely analogous, and what precisely is it that gives VAT countries an unfair advantage?
If a good is exported, no VAT nor sales tax is due in the export country. But because some VAT has already been collected in the earlier production stages, that VAT needs to be returned to the exporter. No sales tax will have been collected at the time a good is exported, hence there is none to return.
In both cases, the end result is that no VAT or sales tax is paid in the export country. Hence the situation is completely the same.
Corporate taxes are orthogonal to this discussion. Both US and EU have them and they apply to corporate profits, independently on if they derive from exports or domestic sales. So no reason to complicate the discussion by bringing them up.
Putting someone else’s name on the deed is a very bad idea for several reasons. I really can’t imagine anyone doing that, unless it’s a trusted family member or something like that.
Regarding class components in general, what is the problem with maintainers choosing to encourage devs to use their new APIs while keeping the old APIs working?
React is stable, upgrading it is painless as long as you don’t ignore deprecation warnings. What can be annoying is other (abandoned) dependencies holding you back from upgrading.
The original motivation was to describe UI as a function of state. It sounds trivial, because it is when server rendering, but once you start sprinkling enough interactivity it can get messy. It's of course not the solution to everything, but above a certain level of complexity I really think you should let someone else handle the problem of syncing state with UI, and JS on its own will never do that for you.
My point is just that the React ecosystem has become surprisingly stable. Of course if you are going to continuously rewrite things into the current flavour of the month framework, you are going to spend a lot of time doing that, but keeping up with upstream changes in dependencies is not something I have found particularly burdensome.
To take the project I mentioned above as an example, currently it’s running on React 18.x, most dependencies are on the latest major version et.c. Still, much of the code is as it was written 8+ years ago, because the core APIs of React have been stable.
I've maintained a sizeable react app for 8 years, and this has not been my experience at all. Maybe 10 years ago things would break monthly but nowadays things are quite stable, with very reasonable deprecation schedules and upgrade paths. I have lots of code running that I haven't touched in 5+ years and it is not causing any problems even when I'm keeping the main parts of the appliaction up to date with modern practices.
Guam and Honolulu both have direct flights to Seoul so it’s not a great example.
Closing online checkin 2 hours before departure and then charging lots for airport checkin is crazy though.