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.
Interesting, the use of grammar production rules reminds me of Grammatical Evolution[0], which has shown some promise in constraining the search space when using EAs for e.g. symbolic regression.
Lots of reasons. My company started using AWS (and specifically S3) something like 9 years ago; R2 wasn't even on the radar back then. If I were starting from scratch today, I'd be looking seriously at Cloudflare as a platform, but it's only in the last year or two that they've offered these services that would make it possible to build substantial applications.
Jeff Barr posted that AWS is actively working on a resolution for this: https://twitter.com/jeffbarr/status/1785386554372042890 . Given who he is, I take this as a strong indication that there will be a reasonable fix in the near future.
I use Authy on my phone and watch, but not Authy on the desktop for exactly this reason; if my computer is compromised and 1password is accessible, they still don't have access to my TOTP codes. Having it on both my watch and phone means I can break a device and not lose access.
This is very disappointing. I'm kind of amazed that they think this is a good business decision when there are massive numbers of paying customers with mountains of python code using boto3. I imagine much of that code uses the resource interfaces since they're easier to use.
This isn't some fringe feature they're deprecating; the official documentation uses these interfaces in its examples; they're literally telling you that's the correct way to use the library and then the next moment they're telling you it's not.
This is interesting. I've just started having video meetings with a colleague (not Japanese) who aggressively interjects these words when I'm speaking, to the point that I find it distracting. I'm simply not accustomed to having someone say "mmm hmm" several times during a single sentence, and I find I start to lose my train of thought.
While you _can_ tack all of those things on to your API, many people (myself included) prefer to separate those concerns. A dedicated API Gateway can prevent a lot of additional load from hitting the backend services. A gateway can also be a nice abstraction of the public interface from the underlying service(s).
It's worth noting that AWS's free tier has absolutely no safety net and you can easily end up with an unexpected bill, sometimes a very large one. The single best thing AWS could do to encourage people to learn about its services by trying them out would be to have a safe-by-default billing configuration. A user should have to flip a switch in their account to allow any usage over a given dollar amount, with services being halted in the event they would breach this limit without having flipped that switch.
This whole time I've been seeing intermittent timeouts when checking a UDP service via NLB; I've been wondering if it's general networking trouble or something specifically with the NLB. EC2 hosts are all fine, as far as I can tell.