Would this be like an alternative to Delta? Am I thinking about that right?
Readit NewsDeleted Comment
Deleted Comment
It seemed to me that it was using the dependant variable intentionally so that it could build up to the twist: actually it's all about race.
To be fair, the twist did get me. I thought it was leading up to discussing injury rates, or health in old age. Since I'm not from the US, the pivot to discussing race wasn't very interesting/relevant to me.
Ha, I’ve heard a few Dutch say that American style racism didnt really apply to them, but then later they say that some person isn’t Dutch because they aren’t white. All in the workplace.
I think it’s just not as top of mind in other places, but its there.
kdazzle commented on Oncall shift should be Tuesday to Tuesday arthur-johnston.com/tuesd... · Posted by u/RyeCombinator
> Most places take after hours paging pretty seriously.
LOL i wish
Lol yeah. My old team had oncall pages in the middle of the night pretty often where nothing was actually the matter. My manager was only nominally on call. In the handoff meetings every week he was basically just like “that sucks”.
kdazzle commented on Moving Off Heroku, Slowly jamie.ideasasylum.com/202... · Posted by u/craigkerstiens
kdazzle commented on Moving Off Heroku, Slowly jamie.ideasasylum.com/202... · Posted by u/craigkerstiens
i dunno. moving off heroku to another provider marking up aws or pretending to seems counterproductive.
a go binary in a zip builds and uploads to lambda in 1 second. handle routing and everything else in binary, don’t use aws features. you don’t need em.
lambda, s3, and dynamo all scale to zero with usage based billing.
toss in rds if you really miss sql or dislike scale to zero.
once this is too expensive, move to ovh metal, which sells significantly faster compute, ie epyc 4244p ddr5 5200.
more importantly, they sell bandwidth for $0.50/TB instead of $0.10/GB, which is aws price before paas wrapper markup.
the ovh price is after the 1Gbps unmetered you get for free with any server.
most companies will never even need metal, and between lambda and metal is ec2 spot, which might be of use anyway for elasticity.
ovh metal bills monthly, ec2 spot bills by the second. recently i learned ec2 spot in localzones is x2-3 cheaper than standard spot. i only use r5.xlarge in los angeles these days.
ovh metal has an old fashioned but perfectly workable api. aws has a great api.
spend a few days figuring out a decent sdlc, and then freeze it permanently. it will grow insanely robust over time.
i haven’t published my ovh metal workflows. my aws workflows are here[1].
lower overhead means more interesting products coming to market. lower friction definitely doesn’t hurt. viva le renaissance!
API development on lambda has to be the worst devex I’ve ever had. Not sure if it was cuz we were also using Dynamo, a half-baked JS framework, or cuz we had wacky internal requirements pushed down (one ex: live-live multi-region deployments for our 0 users!)
Maybe you’ve figured it out, but the local dev flow seemed pretty hacky/nonexistent. It also got expensive with real traffic
kdazzle commented on Making the Python back end for my new webapp youtubetranscriptoptimize... · Posted by u/eigenvalue
This post comes at a great time. I've been looking into what the "perfect" stack would be for me (I'm OK with Python but haven't done any frontend work).
Is anyone actually using FastAPI in a commercial, large scale app? Would you prefer using...say Django or Flask + Gevent (since they're more mature) over FastAPI?
I recently found this thread[1] about FastAPI. It's somewhat old now but reviews are mixed. I'm wondering if the landscape has improved now. Additionally, OP is using NextJS for the frontend and even that isn't without complaints[2]. What's odd for me is that the React website also asks you to pick between either Next.js or Remix[3].
[1] https://www.reddit.com/r/Python/comments/y4xuxb/fastapi_stab...
[2] https://www.reddit.com/r/nextjs/comments/1g18xgu/nextjs_is_h...
[3] https://react.dev/learn/start-a-new-react-project#production...
Django with DRF will get you a very maintainable API, and you can have as little or as much boilerplate as you want. For example, you can inherit all of the model’s fields, or you can choose to specify them all, or somewhere in between, add additional fields, etc. You can have it generate pagination or certain filters. It’s got plenty of hooks for overriding functionality.
If you see performance issues or situations where youre hitting the n+1 query issue, you can optimize by using the orm’s prefetch_related, select_related, or just drop into raw sql.
Im obviously a fanperson, but have yet to find a framework combo that I like more than those two. It’s not very fashionable, but you’ll end up with an app thats quick to develop and thats reasonably secure by default.
Deleted Comment
You mention Zuckerberg - even Facebook was made through having experience in the right market and taking an existing product to the next level, and probably a bunch of iteration along the way.