A more important question for me is what server/framework has the best developer experience and can be maintained easily in the long run. Despite Express.js being rock bottom, I still prefer it as one of the easiest, well known HTTP servers. Of course it all depends on your use case. If you have to extract a penny out of every 1 million http request, performance becomes paramount.
Congrats on the v2 launch, I'm sure it comes in handy in constrained environments like serverless.
I (as a self hoster) much rather write my own PostgreSQL background job queue and not be subject to v2 and v3 upgrades to keep my dependencies in check.
The consequences of a type unsoundness in TypeScript are typically much more benign (an exception typically) than in C (a buffer overflow, arbitrary code execution, etc.). Also the application logic is more visible in TypeScript just due to it being higher-level - there isn't so much low-level detail (ever done JSON in C?) so less chance for a mistake.
This has worked really well for me.
For instance, I deliberately work standing up in the garden with some fitness gear around. Every time I need to wait for something, like a build process or before the next email to write, I do a few bench presses, or push ups. Almost automatically. When I'm seated at a regular office desk, I tend to distract myself with some mindless internet browsing instead. Just creating the right environment can be enough to alter behavior.
I'm currently doing this with Next.js with a "custom server". Allows for sharing TypeScript interfaces/types and the express instance quite easily. It's just one big vscode project. But custom servers are frowned upon and will probably disappear in future versions which will make things slightly more complicated.
Maybe a bit convoluted, but you could create a Prisma adapter in front of your sqlite db and use Prisma Studio to access your data. You can use database introspection to generate a schema file.
https://www.prisma.io/docs/getting-started/setup-prisma/add-...
I think a large part of this is due to API suspensions. I got the infamous "This is a notice that your app - "your bot" - has been suspended from accessing the Twitter API. However, you can self-serve reactivate your app for free"
With a final: "Your application has been reviewed.
Thank you for your interest. Unfortunately, we're unable to approve your application."
This for a small bot that followed a couple of weather gurus to be notified on Telegram on a new tweet. They killed a huge ecosystem in the hope to stimulate direct site engagement.
Do you think they're delusional enough to think everyone would start paying huge amounts of money instead and keep the API? But then again no wonder someone who paid 44 billion for Twitter might think tweets are worth a lot of money.
I agree and think this is a good thing. Building bots good enough to fool humans has become so trivial a high schooler could do it. Something has to be done unless we want to give up on real human interaction on the internet.
Keep in mind, this was a read only bot. But anyways, I was also following bot driven accounts like earthquake notifications. A bot does not equal spam.
Spain has seen massive unregulated expansion of subtropical fruits like mango and avocado, irrigated by illegal wells [0]. This has been long in the making and warned about [1]
