3 ms·

What would you develop on then?

• KirinDave 11y ago
  Backend services, maybe micro maybe not. The CLR has really great support for a hybrid async/threadpool model and C# has direct language support. There's a framework called "ServiceStack" which tastes a lot like Jetty that you can use to avoid the ASP.NET-influenced technologies and approach things in a lightweight way. There is also a developer preview of actual native compilation, which means your deploy story in a container is competitive with Go and startup times for a statically linked binary are great. This means it's actually outperforming Java for containerized deploys (in this specific facet). Azure and GCE are both really, really good compared to EC2. Hell, GCE is shipping actual Kubernetes support and I want to migrate our entire tech stack to that. Already we've migrated our growing website to it, and as soon as they fix some network performance issues (already fixed in master, but we don't use beta orchestration software in production), we'll flip the switch on that as it elegantly solves some really shitty problems you hit in AWS VPCs. I like F# a lot, by the way. I can't wait to use it more. It's like OCaml but with a lot of the amenities you expect from the JVM ecosystem (like, for example, the ever-required but poorly supported datetime libraries) and LINQ support, which is pervasive, user-extensible object comprehensions with compiler support. C# doesn't excite me so much, but it has a REPL and it's certainly a more advanced language than Java.