Have tried almost every PaaS and same for me, I always come back to CapRover, it's the platform I've had the less issues with, it's simple and yet feature complete enough for me to run almost anything.
I'd love a better alternative if possible.
React in itself isn't that heavy, and things like preact exists if you want an even lighter library, it's mostly other dependencies that are heavy, so the blame is mostly on the side of the devs, not react, for having heavy and clunky software.
Good thing that 99% websites don't need to modify 1k dom elements every seconds then, if you do using a DOM library isn't the right choice.
My comment was about size library, in response to the parent comment about MBs of js.
I'd gladly take a 10ms slower update on 1k rows(that practically never happens, ever heard of virtual lists?) for a maintainable codebase any day.
Any plans to expand further than Hetzner?
They're pretty restrictive on certain usages(e.g VPNs), I'd be really interested in support for Datapacket for example.
Was innitially designed for Hetzner, but they way it has been bult, will allow expanding to any provider.
Especially to providers that offer their own Kubernetes distribution.
Thats such a political argument, this is ecology, your POV on origins isn't correct in this case.
Introducing a new species that has never lived somewhere could maybe introduce really bad side effects?
Imagine a new predator that somehow eats everything and reproduce 10x more than any other species in the introduced ecosystem, causing it to simply be destroyed?
Same goes with plants, why do you think airports prevents you from importing fruits and seeds? Because they could cause irreversible damages.
You can Google tons of cases of invasive insects being mistakenly imported being a bane to farmers and the like.
> Imagine a new predator that somehow eats everything and reproduce 10x more than any other species in the introduced ecosystem, causing it to simply be destroyed?
But chatgpt wasnt the first, openai had coding playground with gpt2, and you could already code even before that, around 2020 already, so I'd say it has been 3-4years
First one maybe but definitely not the second one.
Have you actually thought of it?
How would the platform know who sent what. They can't. So it's definitely not shared on the deposit side. And I doubt they'd move the money around because of fees so I doubt it's shared on the withdrawal side too.
From my experience, of course it depends on the blockchain used, but they all have static addresses per user
I think one of the reasons Google choose UDP is that it's already a popular protocol, on which you can build reliable packets, while also having the base UDP unreliability on the side.
From my perspective, which is a web developer's, having QUIC, allowed the web standards to easily piggy back on top of it for the Webtransport API, which is ways better than the current HTTP stack and WebRTC which is a complete mess.
Basically giving a TCP and UDP implementation for the web.
Knowing this, I feel like it makes more sense to me why Google choose this way of doing, which some people seem to be criticizing.
> I think one of the reasons Google choose UDP is that it's already a popular protocol...
If you want your packets to reliably travel fairly unmolested between you and an effectively-randomly-chosen-peer on The Greater Internet, you have two transport protocol choices: TCP/IP or UDP/IP.
If you don't want the connection-management & etc that TCP/IP does for you, then you have exactly one choice.
> ...which some people seem to be criticizing.
People are criticizing the fact that on LAN link speeds (and fast (for the US) home internet speeds) QUIC is no better than (and sometimes worse than) previous HTTP transport protocols, despite the large amount of effort put into it.
It also seems that some folks are suggesting that Google could have put that time and effort into improving Linux's packet-handling code and (presumably) getting that into both Android and mainline Linux.
