5 ms·
Keeping LRU cache that large with these performance requirements is not a "most people's problem". Go is actually great to solve most people's problem with web
by vogre 7y ago
Keeping LRU cache that large with these performance requirements is not a "most people's problem".
Go is actually great to solve most people's problem with web servers, while Rust is better for edge cases.
- kerkeslager 7y ago> Keeping LRU cache that large with these performance requirements is not a "most people's problem". Sure, but that's not what I said. Any program of sufficient complexity will run into at least one critical problem that isn't a "most people's problem". A well-written general-purpose language implementation will have been written in such a way that that problem isn't totally intractable. > Go is actually great to solve most people's problem with web servers, while Rust is better for edge cases. Most people's problem with web servers is writing a CRUD app, which is going to be easiest in something like Python/Django/PostGres/Apache. It's not the new shiny, but it includes all the usual wheels so you don't have to reinvent them in the name of "simple". Similar toolsets exist for Ruby/Java/.NET. Give it a few years and similar toolsets will be invented for Go, I'm sure.
- majewsky 7y ago> Give it a few years and similar toolsets will be invented for Go, I'm sure. Go 1.0 is nearly 8 years old at this point, and these toolsets have existed for years.