Are there serious proposals to just add a wealth tax on top of the existing income tax that would apply to the sort of people who actually pay much in income tax vs capital gains? It's an honest question; I haven't seen proposals of that sort, so I'm skeptical that the arguments are meaningful here. For an individual like Jeff Bezos, he's paying virtually no tax under the normal income tax rates referenced in the article, but rather capital gains tax, which tops out at 20%, not 37%.
Yep, NSIS is awesome and my team is still using it to package Windows builds of at least two apps. I was pleasantly surprised to see Tauri [0] includes NSIS as one of its built-in installer options.
$10/month difference is, to use your phrasing, absolutely nothing. It's not worth anyone's time to make that switch unless it's some toy app paid for out of pocket.
The premium tier is $19/user/m, not $49. Still, I agree that even $19 is high relative to the competition. We're currently on the (soon to disappear) $4/user/m Gitlab plan and now I'm wasting time trying to figure out if we'll lose anything we care about by dropping down to the free tier.
I hope this works out, and I hope it fixes some of the grief that Cordova causes. We've ended up with some legacy apps built with Ionic, and have had so many problems that trace directly back to Cordova that we're looking very seriously at complete rewrites.
Integrating with some third-party like Auth0 goes smoothly for our projects until we get to Cordova, at which point we start chasing absurd bugs and explaining to their support that we do actually need Cordova support. We've been told more than once that Cordova is the "problem child" in terms of supported platforms.
> The hit I see is by providers of 'serverless' computing, since they charge per request and have their margins reduced.
AWS, Azure, and GCP all bill serverless with a combination of per-request fees and compute (GB-seconds), so I'd expect the entire hit to be passed on to the user since this will cause increased compute time for each request. N requests that used to average 300ms each will now be N requests that average, say, 400ms, so the per-request billing remains the same and the compute billing will increase by approximately 30%.