not possible:
- workloads over 15m for lambda last time I checked, unsure on other providers
- if you are looking to do anything stateful
possible but not ideal/inconveniences:
- cold starts can hamper latency sensitive apps (language dependant + there are things you can do)
- if you have consistent traffic its not very good value for money
- if you value local debugging
I think a lot of people in office jobs day dream about this sort of thing. My father-in-law is a third generation farmer producing ultra fine wool. I am a source of free labour at shearing time and I will tell you that when I treat myself to a sleep in on Monday morning and roll out of bed for standup at 9:30 I sit there with the biggest shit-eating grin on my face meanwhile my father in law is already 4 hours in to his 12+ hour day.
Also if I was to go into farming I'd have to do something with crops/fruits/vegetables. I am a bit of a softie but the realities of livestock husbandry when met with the economics of farming can be quite confronting.
I didn't mind prisma for managing the schema etc but also seen your linked github issue. I found other people recommend combining Prisma with Kysley. I have only used this in toy projects so take this with a grain of salt.
Just in the interest of balance I am very happy with Starlink, I usually range between 90-120Mbps and 30-60ms latency. It can be a little patchy to play latency sensitive games on (guessing these are the sub seconds timeouts you mention), I swap to tethering my phone for that but day to day (zoom meetings, etc) I have found starlink to be a massive upgrade on the alternatives available in Australia. In 12~ months as a customer I think I've tethered my phone for a zoom call once.
I have a few questions about this approach, cards on the table I mainly deal in C# where DI (through the framework) is the default. How do you manage the initialization of all of the dependencies? Do you need some sort of "root" where everything is initialized and passed in? That was all I could come up with while keeping it testable and that doesn't sound maintainable once you build up the number of dependencies.
I have been interested in web scraping lately but never really dived too deep. Did anyone have more indepth resources (github projects, blogs, forums, etc) than the tutorials that are basically install beautiful soup and get data from a tag?
I have often thought about this, especially in penalty shoot outs where there are 4 people who aren't the "best" penalty taker that have to take one.
As has been mentioned there are penalties that are just unsaveable and against an elite penalty taker maybe a goalie is better off just picking a side and taking a chance against them but against the rest of the takers I'd be thinking eliminate the chance they get a freebie by diving too early or just picking a side and force them to score the hardest penalty possible
the ideas aren't bad though, you just don't agree with them.
Banning meat isn't something I would get on board with but it would probably be effective.
There's been a lot of discussion lately on HN about nuclear and I can actually see both sides of the debate.
Plastic straws I think you have actually just strawmanned environmentalists here as I've never seen plastic straws mentioned as a solution or contributor to global warming.
The way I've seen it work is with having short lived access tokens and a refresh token, with the refresh token being saved to a database so it can be revoked. I think the benefit over an opaque token is that you have data that can be verified to be true and then passed on to multiple places. E.g passed between microservices
sorry, could you dumb this down a little? how does this affect the price/GW? (I'm not questioning it does, I'm saying I don't understand the rest of what you said)
possible but not ideal/inconveniences: - cold starts can hamper latency sensitive apps (language dependant + there are things you can do) - if you have consistent traffic its not very good value for money - if you value local debugging