831 karma · joined June 19, 2012
- Github actions are faster for us (~30% faster)
- Some of our tests failed while waiting for a dockerized server to be up
- It takes several minutes before all jobs are running (I have a pipeline with 6 parallel jobs, a few started with 2 minutes delay).
Another surprise is that Apple’s protobuf generator is able to produce iodiomatic Swift, the same is not true for Kotlin :)
I think that parent probably refers to the lack of something like this:
x := new MyType
Your assumption is wrong, we did not pick a different language just for fun or because we wanted to learn something new :)
Python was just not the language we needed for our APIs, we tried hard to make it work but eventually we looked at alternatives that would allow us to keep things simple and performant. End result was better latencies, a much simpler architecture (less async/MQ work) and processes that would eat a fraction of RAM and CPU compared to Python.
eg. there are no companies that raised an A and have 10+ ARR in EU
This was a huge pain for us. We develop an SDK that needs to work on Node, browsers and React Native.
I am super happy to hear about this :)
So ideally something like:
1. upload to s3
2. manipulate image to a friendly size (ie. 2048x2048)
3. write the image to an LRU cache (ie. memcached)
with steps 2 and 3 on a separate go-routine
Besides that, really cool project :)
> Less than 1% of users may be experiencing trouble connecting to Slack
This is a good example of how to not communicate uptime issues. It clearly shows that Slack is trying to downplay the problem and do damage control. This is not smart and gets customers upset.
Germany in particular made the stupid decision of shutting down nuclear plants (Fukushima overreaction) and it is pushing this narrative of being a green energy country… to me it sounds like an easy problem to solve once there is enough political attention.
Track and trace was introduced and failed in most countries.