brian-bk

I think it's time that AWS customers hesitate before using any abstract software that AWS has built, as we're about to see the enshittification/profitability squeeze of an incumbent player. I wouldn't trust anything more than the ec2, RDS, S3 layer which are more "completed" products and there's not much to enshitify, only squeeze costs. You can already see that AWS has essentially dropped support of any publicly available software, I can't imagine it's any different internally.

It seems like AWS is replicating GCP's level of customer support, instead of using that as a differentiator (not that AWS' support was ever great, but dang it sure was better than GCP's by comparison). Consider yourself on the own, only trust software built on VM's, not SaaS abandonware.

There are a very light benchmarks in the Readme, or are you looking for more?

I'm convinced nothing solid has come out of AWS in 10 years. The original products (ec2, RDS, s3) are solid either from being created at a time when AWS could write software or just from existing for so long.

Any modern AWS product (mostly SaaS) is just utter dookie, the only reason they continue to sell well is companies already have an accounting relationship with AWS. It's a lot less internal approvals required to start using the AWS SaaS version of whatever, compared to a brand new vendor negotiation contract and security guarantees.

So I guess AWS is just working off of a broken incentive structure designed to churn out SaaS-slop over stuff that actually works great.

flip the direction of time and hawking radiation ""creates"" mass/energy inside a black hole (overall mass/energy is conserved)

I'm pessimistic about Go if they _don't_ change error handling. The handling of nil's and errors (by extension panic's) is purely conventional, and baked in to the language has no protection.

Author asserts that error handling is unsolved and therefor a solution shouldn't be attempted. I disagree, anything is better than Go's error handling now.

Investors love a company spouting AI not because it's actually good at raising efficiency, but because it's a codeword for layoffs.*

* there are certain industries that will see incredible efficiency gains from AI, but I think most will not see the efficiency gains that AI companies tout.

I'm assuming the Texas lawsuit against OnStar contributes here as a software income stream that didn't work out... low level employees always pay for bad decisions from leadership.

Same thing happens in reverse with salaries. Glassdoor isn't your friend, it just helps companies regress to the 50th-percentile.

What are cdk and dms in this context? I'm only familiar with them on AWS

JSON(newline delimited or full file) is significantly larger than csv. With csv the field name is mentioned once in the header row. In JSON every single line repeats the field names. It adds up fast, and is more of a difference than between csv to parquet.

Correct, I've seen advertisements for afrin like crazy the last 6 months. It shouldn't even be OTC given it's potential harm.

I'm more familiar with kubernetes for running production-grade apps and that's what I went with. I run ubuntu's microk8s, and the volume management is in kubernetes-land which I understand well. Finally helmfiles deploys my Postgres and immich helm charts. Perhaps "overkill" to some, but it's tooling I'm very familiar with, and feel comfortable running in "production" for my personal server.

Worth noting that immich itself recommends not using immich for the single source of your images and videos from how active development it is, so I also run nextcloud + crunchydata's postgres also inside microk8s/kubernetes.

Which is less than 2%, so more a showing for investors than a real layoff.

This happened with me -- VP said he wanted feedback but clearly didn't like real critical feedback. Then that VP tried to set up a denied promo, even though I was performing two levels above my then-current level. Finally the company got bought and levels were frozen and he was laid off (as executives are often laid off in an acquisition), so who knows what would happened.