Not to be flippant, but if you host Server Side Rendered react on the public internet and you're just hearing about this now, that's a skill issue.
2,117 karma · joined March 13, 2013
Not to be flippant, but if you host Server Side Rendered react on the public internet and you're just hearing about this now, that's a skill issue.
Personally I think at their scale, self hosting and creating more interoperability between the stacks would have been a better investment but I was not CTO or an SVP so I didn't get to make those decisions.
I didn't even use the word "modern."
I actually agree the traditional cloud providers have lots of issues and aren't always the right choice, but the fact remains that offerings from Red Hat and the like are far more popular with older larger corporations than startups or "household name" tech companies like X, Netflix, etc.
To say nothing of the banks and others still using the IBM big iron.
My 65" Bravia is one of the best TV's in its class and runs Google TV (IMO a major leg up over the junky Tizen/WebOS offerings from competitors).
They make some of the best noise cancelling headphones money can buy. They have the PS5 and own a bunch of game studios to provide exclusive content for it.
They're doing just fine!
But this is definitely neat. I've found Incus quite handy for development environments, and a good compliment to docker.
For some, the Mac hardware or familiarity with the MacOS UI justifies these downsides. Personally, I'll take my Framework 13 with real actual Linux (Fedora workstation) every time :)
Linux has been a great platform for devs for a long time. This is exactly why WSL exists, and why MacOS has a native Linux container[1] tool.. because Linux was eating their lunch in this user segment.
I starred Posting[1] but haven't yet got around to trying it.
[1]: https://news.ycombinator.com/item?id=40926211
Edit: here's another one: https://github.com/LucasPickering/slumber
https://www.androidauthority.com/working-android-16-desktop-...
I'd like to see some evidence for this. Other than simplicity, IMO there's very little reason to use synchronous Python for a web server these days. Streaming files, websockets, etc. are all areas where asyncio is almost a necessity (in the past you might have used twisted), to say nothing of the performance advantage for typical CRUD workloads. The developer ergonomics are also much better if you have to talk to multiple downstream services or perform actions outside of the request context. Needing to manage a thread pool for this or defer to a system like Celery is a ton more code (and infrastructure, typically).
> async i/o solutions are all single threaded
And your typical gunicorn web server is single threaded as well. Yes you can spin up more workers (processes), but you can also do that with an asgi server and get significantly higher performance per process / for the same memory footprint. You can even use uvicorn as a gunicorn worker type and continue to use it as your process supervisor, though if you're using something like Kubernetes that's not really necessary.
pyenv was problematic because you needed the right concoction of system packages to ensure it compiled python with the right features, and we have a mix of MacOS and Linux devs so this was often non-trivial.
uv is much faster than both of these tools, has a more ergonomic CLI, and solves both of the issues I just mentioned.
I'm hoping astral's type checker is suitably good once released, because we're on mypy right now and it's a constant source of frustration (slow and buggy).
Or by asyncio.
Cool app though!
The mobile experience last I tried was pretty rough though. I don't really need my files on my phone and I have a web interface on my home server I can use to grab them in a pinch, but it's something to keep in mind.
Much like how you don't have the C stdlib when writing kernel code, Rust is used with the no_std option. You do not use cargo and do not have access to crates.
You'd likely have to rewrite half of tokio to use kernel level abstractions for things like sockets and everything else that interacts with the OS.
It's messy in something like Python, but mostly transparent in C#. In C# you effectively are using async/await to provide M-N threading ala. GoLang, it's just different syntax.
OP references the C# method Task.WhenAll so they might be assuming other languages are equally capable.
7 and 2008R2 were pretty good too. All downhill from there..