3 ms·
Performance isn't really my main concern; I have some projects with configuration web GUIs running on MCUs where it could matter (especially the code size to in
by mort96 1y ago
Performance isn't really my main concern; I have some projects with configuration web GUIs running on MCUs where it could matter (especially the code size to include mbedtls), but most of the stuff I care about is on Linux machines which are powerful enough that it doesn't matter.
See my response to the certificates thing here: https://news.ycombinator.com/item?id=45820782#45956556 https://news.ycombinator.com/item?id=45820782#45956556
- Aurornis 1y ago> I have some projects with configuration web GUIs running on MCUs where it could matter I don’t think these are a fit for an entire HTTP/3 or HTTP/2 stack with WebTransport anyway. WebSockets is fine for these applications and won’t be going away. > See my response to the certificates thing here If you don’t care about validating the certificate you can skip all of the renewals and DNS setup and everything else. The client will complain that it can’t verify the certificate against anything trusted and you tell the client that’s okay, just ignore it and continue. If you don’t care about encryption then you also don’t care about setting up the certificate properly. You put something in there to enable the connection and then have the client ignore the fact that it’s not verified. If your complaint is that browsers show warning signs for certs that can’t be validated and those might scare other users, that’s not going away.
- mort96 1y agoI don't think you understand. I don't want to make services which, by design, show scare screens to people and make it sound like they're being hacked. It's better to use HTTP and restrict myself to features which work in "insecure" contexts.