Your second point misses an important fact: the Tesla Model S Plaid set a 7:25 Nurburgring lap time, and the Porsche Taycan did it in 7:07. Both of these lap times are faster than many high-performance ICE cars, and close to GT2/3 times which are just below 7:00.
As you might expect, the technology will continue to evolve, too.
This person is explicitly ignoring that EVs use tire and braking configurations that maximize efficiency over performance in order to make their point. It's like saying ICE cars are inherently bad at performance because of Ferdinand Porsche's VW Beetle design choices or because my 3000lb vehicle (lighter than a modern Porsche) Jeep XJ isn't a sports car ICE vehicles can't be performance vehicles.
True, but you do still feel the weight. Even with good tires, they give up time around the corners and make it back with insane acceleration. That's why you generally see hybrids for the most extreme hypercars, at least over the past decade or two. They have most of the advantage of electric without the weight penalty. (I own and track both ICE and electric cars and find both have advantages and disadvantages.)
To keep the comparisons honest, I honestly couldn't care less about the performances of Taycan. That's not what I drive and that's not what everybody on my roads drive. Yeah maybe I see one hypercar a week but I definitely won't keep that as the bar for driving behaviour. So maybe we should compare between (pick your specific models) Dacia and Toyota?
Mergent (YC S21 - https://mergent.co) might be precisely what you're looking for in terms of a push-over-HTTP model for background jobs and crons.
You simply define a task using our API and we take care of pushing it to any HTTP endpoint, holding the connection open and using the HTTP status code to determine success/failure, whether or not we should retry, etc.
Happy to answer any questions here or over email james@mergent.co
Ok, I'll bite. We (mergent.co) have looked at similar tools before but ended up managing our own infra. This is primarily because the tools we've found focus on recreating Heroku/similar on our AWS, which doesn't suit our needs.
For example, in addition to traditional applications, we run:
- Kubernetes + Knative
- Apache Pulsar
- ScyllaDB
- Elastic
- Clickhouse (soon)
How would Argonaut help us with our (frankly, painful) infra? We're living in YAML hell over here.
This type of use case leverages Argonaut's flexibility maximally. For traditional apps, the push-to-deploy CI/CD can be setup. For Pulsar and ScyllaDB, and Elastic there are helm charts that can be used very easily as a part of our AddOns which we are expanding continuously. For Knative and clickhouse, the best way to run them would be through Kubernetes operators. While this can be setup using Argonaut today, the experience feels janky and we're working on making this a first class entity in the product.
The way Argonaut would help is by managing the configs and deployments in one place for easy collaboration and deployment, across environments and having GitOps with secret management for all the configs.
Mergent (YC S21) https://mergent.co -- our crons & background tasks are free for the first 1k invocations per month and pay-as-you-go after that.
There are two ways to set up a cron job: the dashboard or via the API if you need the flexibility, e.g., dynamically creating/starting/stopping crons.
We use HTTP webhooks to make the outgoing cron requests, which makes it easy to integrate with a wide range of services and platforms, including Vercel, Lambda, etc. We're also working on adding local execution so you can have even more control over how your tasks are run without using webhooks, but that's still being built & tested.
Feel free to reply here or email me directly if you have any questions: james@mergent.co
If you're diving into Postgres and want to better understand how it works under the hood, there is a great talk from PGConf Silicon Valley 2016 titled "How does PostgreSQL actually work" on YouTube: https://www.youtube.com/watch?v=OeKbL55OyL0
The job with the best team. Generally, the job where you have to jump through hoop will have a team who has jumped through those hoops as well. It's all about vetting.
As you might expect, the technology will continue to evolve, too.