1,926 karma · joined June 11, 2008
I don’t think the average American is having this drilled into them as you suggest, but there are certainly military planners in the USA whose job it is to think about such things.
China works the same way.
What took over 5 weeks of back and forth was resolved in 2 hours. Airbnb even gave me $100 credit for my trouble...
Our company’s interpretation is that we will need EU based teams (that we will have to hire for) to help debug production issues and to help customers because if I look at the data to triage I’ve transferred it out of the EU.
It's not really a red herring when Lambda mostly forces communication between different application layers to be over the network. You suddenly have to deal with rate limiting, retries, bulkheading, etc. in a lot more places than you would even with even a SOA.
> you actually have to write unit tests
I'm not really sure unit tests are a differing factor in testing functions as a service and other software. The real issue with testing is that it's very difficult if not impossible to do more than unit testing locally. You're often using docker containers or mock services to try and simulate what is going on in production which is insufficient. Things like CloudFormation can't be done locally (and this can be where a lot of gross complexity lies), so ultimately you have to set up an identical-to-prod testing environment and do the bulk of your testing there (which you probably should have anyway, but that's besides the point). Things like localstack HAVING to exist but not being supplied by AWS is a symptom of something gone wrong.
> Would it be simpler to write a full-blown service that polls events and listens to message queues and launches background tasks? Obviously, no.
Why is this obviously no? It isn't to me. You likely need a lot less these type of things if you're running a monolith.
> In terms of complexity, they pale in comparison with even the tiniest hello world windows GUI app, or even Qt.
It seems to me you're ignoring all the extra stuff you HAVE to have to deploy, secure, and maintain serverless. There is a lot more than the code for the function themselves.
In my own work with serverless I think about this a lot. In my day job, we built a new service and we pay AWS a few dollars per month to run. It would have cost us around $100 a month in AWS costs. However, the operational complexity is extremely high and we are also coupled to another service via Kinesis. For a billion dollar business, the trade off doesn't seem worth it.
I wonder how much of serverless is just AWS firing at Google (and Heroku, DO, etc) and other competitors. It certainly hasn't made my life as a developer easier. It's certainly much cheaper for some use cases but the complexity of the system goes up very quickly, and you're end up having to manage a lot of that complexity using an inferior tool like Cloud Formation (or Terraform).
- Test runner
- visual diff tool (gitlens isn't quite good enough)
I've been thinking about what I'd miss from VSCode if I switched back and I cant' really come up with anything other than I really love https://shadesofpurple.pro/.
So why did I switch? Basically everybody is using VSCode on screencasts, at work, etc. for TypeScript and JavaScript and I wanted to see what the fuss was about. It's not better, and I don't really understand why it's popularity.
- We never fight about money because we have already planned for the next month together.
- We each get equal amount of no questions asked personal money that the other person cannot criticize how it’s spent.
- When we first started using YNAB we realized we were living off credit card float, and spending money we didn’t have until we got the months paycheck. We thought we were doing great just because we would pay our credit card off each month. But we were actually 100% relying on our future paychecks to survive.
- My wife lost her job 2 years ago and was out of work for a month due to COVID. The budget gave us an objective view rather than an emotional one. In both cases, we didn’t need to even rely on our emergency fund because of flexible budgeting.
- We are able to maximize credit card rewards without being concerned with spending too much.
- We are able to easily track our cash equivalent net worth.
Most of these things are not YNAB specific, but the software makes things so much easier.
If you're looking for a job, AWS has the largest market share (33%), followed by Azure (19%), and GCP (9%).
If you're looking for a place to host your product, you probably can't go wrong with either of the three, but there are some minor considerations...
Personally, I would consider GCP a little more risky long term. There was a report last year about Google considering existing the cloud business and setting a goal to be a top two player by 2023. Since this seems unlikely, what then? Google has some anti-trust concerns, but the bigger anti-trust concern is probably Amazon. There is a non-zero chance that AWS gets split out from Amazon at some point.
Finally, I don't really know GCP that well, but it's my understanding it's a little easier to manage for smaller teams. I believe AWS is considered IAAS while GCP is more PAAS (although the lines get blurred depending on product). In my experience, for companies using AWS... having a DevOps team that smooths over the rough edges of AWS and provides tooling on top of AWS warts has been a requirement.
I have no experience with Azure, but I can't see Google out performing Microsoft in any world as long as MSFT has .NET stack.
Electron 11 was released today and supports AS, but it is listed as experimental.
Would love to see an experimental docker for mac soon.
airbnb sides too much with the host in my experience.
When a host left me and my family in an unsafe environment due to a gas leak, airbnb was impossible to work with. It took months of escalation with airbnb to get things fixed, despite providing all the documentation required the same day that I didn't stay at the property and had to book a last minute hotel at increased cost.
:)