zedpm

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.

0 - https://tauri.app/ 1 - https://tauri.app/distribute/windows-installer/

$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.

[0]: https://en.wikipedia.org/wiki/Grammatical_evolution

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.

Somewhere, Edward Tufte[0] is weeping.

[0]: https://en.wikipedia.org/wiki/Edward_Tufte

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.

I'm glad to see they didn't forget about HTTP 418[0] in their response code docs[1].

[0]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/418

[1]: https://developer.tesla.com/docs/fleet-api#response-codes

Factotum and South of No North are two of my favorites.

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.

I’m still using a 2015 MacBook Pro, and it doesn’t feel slow. I’ve done no repairs or maintenance on it in all that time.

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.

Right, that's my point in responding to the parent comment about fitting 5 people in a Camry; it's not so simple when 3 of them require car seats.

Have you ever tried installing 3 car seats into a compact car?

Wow, yeah, us-west-1 AND us-west-2 are reporting connectivity issues. I'm guessing this is related to the Auth0 outage that's currently going on too.

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.

I'm having CLI issues as well, they're using the same APIs under the hood. For example, I'm getting 503 errors for cloudwatch DescribeLogGroups.

Yep, PHD isn't loading, Cloudwatch is reporting SQS errors, metrics aren't loading, can't pull logs. This is in US-East-1.

Yep, PHD isn't loading, Cloudwatch is reporting SQS errors, metrics aren't loading, can't pull logs. This is in US-East-1.

Evergreen comment:

Don't forget to request your credit per their SLA[0]. You have 10 days to request your credit, which by my calculations should be 10% of this months' charge. Not a fair trade for leaving us dead in the water, but SLAs in general are worthless.

[0]: https://auth0.com/docs/support/services-level-descriptions

The AWS issue in US-West-2 is only affecting a single AZ, according to them. A single AZ should never take down a production service.

Oh no, it's not down, it's just "experiencing elevated error rates" /s. After the appalling outage they had last spring, it's too soon to be dealing with this again. And there have been a couple of small outages in between then and now.

Don't forget to request your credit per their SLA[0]. You have 10 days to request your credit, which by my calculations should be 10% of this months' charge. Not a fair trade for leaving us dead in the water for 4 hours, but SLAs in general are worthless.

[0]: https://auth0.com/docs/support/services-level-descriptions

Every year or so I check back in to see if Cognito has gotten any better. I hasn't. I'd love to use it, but some very basic things are just not done correctly. Yan Cui has a nice writeup on Cognito [0] that touches on some of its shortcomings.

[0]: https://theburningmonk.com/2021/03/the-case-for-and-against-...

> $49/user/m...

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.