7 ms·

Even if performance matter Go should be a better choice. Go's performance is very close to rust in Web ecosystem and is very mature.

legulere 6y ago
Or C# with ASP.NET Core which is much closer to rust in performance.
- jeswin 6y ago
  > Or C# with ASP.NET Core which is much closer to rust in performance. I haven't noticed that C# is faster than Go, or that it's as fast as Rust/C++. Except in selected micro-benchmarks, of course. C# is at best in the same bracket as Go: https://www.techempower.com/benchmarks/#section=data-r19&hw=ph&test=query https://www.techempower.com/benchmarks/#section=data-r19&hw=...
  - yread 6y ago
    https://www.techempower.com/benchmarks/#section=data-r19&hw=ph&test=composite https://www.techempower.com/benchmarks/#section=data-r19&hw=...
    - jeswin 6y ago
      The fastest .Net based library scores a 58%, while a framework based on Go scores 52%. The weights are arbitrary, so can't infer a lot from the 6% delta between .Net and Go - except that they compare favorably with each other in terms of performance.
      - apta 6y ago
        The fastest .NET library is ASP.NET Core, which is a standard, mature, off the shelf framework. Compared to the golang version using fasthttp, which is non-standard and makes compromises to achieve speed, and I'd avoid it for production.
  - pythonaut_16 6y ago
    In my experience ASP.NET and its frameworks are potentially much slower than raw C#. As much as C# is supposed to be a fast language, whenever I run into a C# web app it seems to be inexplicably slow.
    - nobleach 6y ago
      I'm not sure why anyone would be downvoting your data point. I am pretty bothered at how much emphasis folks throw behind the TechEmpower benchmarks. If you really dig into the implementations for the top languages, it's easy to see how far from the real world, those apps are. In the case of C#/ASP.NET, as soon as you add EntityFramework (or Dapper, if that's your thing) and some real-world querying of a database. You're looking at a pretty big slow-down. I'm certain things can be done to speed it up though.
- eznzt 6y ago
  Is that free in any way?
  - pbz 6y ago
    It's free in all the ways
  - brixon 6y ago
    C# or ASP.NET Core never costed anything. The cost is in certain versions of Visual Studio, but that is not required. Besides Visual Studio, Visual Studio Code is popular too.
    - iruoy 6y ago
      I can recommend Jetbrains Rider [1] for anything C#. I prefer it over Visual Studio even. [1]: https://www.jetbrains.com/rider/ https://www.jetbrains.com/rider/
    - eznzt 6y ago
      Is it also free to deploy? Can you deploy it on Linux?
      - reese_john 6y ago
        Yes. It is also fairly straightforward to dockerize dotnet core apps[0]. [0] https://docs.docker.com/engine/examples/dotnetcore/ https://docs.docker.com/engine/examples/dotnetcore/
  - legulere 6y ago
    The C# compiler roslyn, the dotnet runtime (Jit compiler, ...), and ASP NET Core are all MIT or Apache licensed and run officially supported on mac os, linux and windows.
felipellrocha 6y ago
That’s just not true. More mature, sure. But the language experience couldn’t be more different between the two, and that counts. I don’t wanna be wasting my time with quirkiness.
- throwaway894345 6y ago
  I like Rust and everything, but pretending it’s going to get the job done faster than Go is just that—pretending. If you don’t like Go’s developer experience, then fine (and understandable when the alternative is Rust), but it’s not wasting time IMO.
  - deleted 6y ago
    [deleted]
  - ffdjjjffjj 6y ago
    It’s not pretending. In fact, web application hosts are a great candidate for replacement with faster languages because it can have an immediate impact on infra costs.
    - throwaway894345 6y ago
      Reducing infra costs are rarely the largest opportunity for an organization, and even then the majority of infra waste is typically unrelated to language. Moreover, trading iteration velocity (and/or rewriting your application) for some marginal infra cost improvement is not a very good approach.
  - couchand 6y ago
    Writing a for loop every time you need to iterate over a collection is wasting time.
    - aaronblohowiak 6y ago
      My ratio of writing to debugging has never been such that the difference between for and forEach ever mattered. That being said, debugging complex go code bases 5 years ago (when I last was doing this daily) was less fun than other languages (their armory stocks a nice assortment of footguns and the debugging support was... minimal. Might have changed since then.)

legulere 6y ago

Or C# with ASP.NET Core which is much closer to rust in performance.

jeswin 6y ago
> Or C# with ASP.NET Core which is much closer to rust in performance. I haven't noticed that C# is faster than Go, or that it's as fast as Rust/C++. Except in selected micro-benchmarks, of course. C# is at best in the same bracket as Go: https://www.techempower.com/benchmarks/#section=data-r19&hw=ph&test=query https://www.techempower.com/benchmarks/#section=data-r19&hw=...
- yread 6y ago
  https://www.techempower.com/benchmarks/#section=data-r19&hw=ph&test=composite https://www.techempower.com/benchmarks/#section=data-r19&hw=...
  - jeswin 6y ago
    The fastest .Net based library scores a 58%, while a framework based on Go scores 52%. The weights are arbitrary, so can't infer a lot from the 6% delta between .Net and Go - except that they compare favorably with each other in terms of performance.
    - apta 6y ago
      The fastest .NET library is ASP.NET Core, which is a standard, mature, off the shelf framework. Compared to the golang version using fasthttp, which is non-standard and makes compromises to achieve speed, and I'd avoid it for production.
- pythonaut_16 6y ago
  In my experience ASP.NET and its frameworks are potentially much slower than raw C#. As much as C# is supposed to be a fast language, whenever I run into a C# web app it seems to be inexplicably slow.
  - nobleach 6y ago
    I'm not sure why anyone would be downvoting your data point. I am pretty bothered at how much emphasis folks throw behind the TechEmpower benchmarks. If you really dig into the implementations for the top languages, it's easy to see how far from the real world, those apps are. In the case of C#/ASP.NET, as soon as you add EntityFramework (or Dapper, if that's your thing) and some real-world querying of a database. You're looking at a pretty big slow-down. I'm certain things can be done to speed it up though.
eznzt 6y ago
Is that free in any way?
- pbz 6y ago
  It's free in all the ways
- brixon 6y ago
  C# or ASP.NET Core never costed anything. The cost is in certain versions of Visual Studio, but that is not required. Besides Visual Studio, Visual Studio Code is popular too.
  - iruoy 6y ago
    I can recommend Jetbrains Rider [1] for anything C#. I prefer it over Visual Studio even. [1]: https://www.jetbrains.com/rider/ https://www.jetbrains.com/rider/
  - eznzt 6y ago
    Is it also free to deploy? Can you deploy it on Linux?
    - reese_john 6y ago
      Yes. It is also fairly straightforward to dockerize dotnet core apps[0]. [0] https://docs.docker.com/engine/examples/dotnetcore/ https://docs.docker.com/engine/examples/dotnetcore/
- legulere 6y ago
  The C# compiler roslyn, the dotnet runtime (Jit compiler, ...), and ASP NET Core are all MIT or Apache licensed and run officially supported on mac os, linux and windows.

felipellrocha 6y ago

That’s just not true. More mature, sure. But the language experience couldn’t be more different between the two, and that counts. I don’t wanna be wasting my time with quirkiness.

throwaway894345 6y ago
I like Rust and everything, but pretending it’s going to get the job done faster than Go is just that—pretending. If you don’t like Go’s developer experience, then fine (and understandable when the alternative is Rust), but it’s not wasting time IMO.
- deleted 6y ago
  [deleted]
- ffdjjjffjj 6y ago
  It’s not pretending. In fact, web application hosts are a great candidate for replacement with faster languages because it can have an immediate impact on infra costs.
  - throwaway894345 6y ago
    Reducing infra costs are rarely the largest opportunity for an organization, and even then the majority of infra waste is typically unrelated to language. Moreover, trading iteration velocity (and/or rewriting your application) for some marginal infra cost improvement is not a very good approach.
- couchand 6y ago
  Writing a for loop every time you need to iterate over a collection is wasting time.
  - aaronblohowiak 6y ago
    My ratio of writing to debugging has never been such that the difference between for and forEach ever mattered. That being said, debugging complex go code bases 5 years ago (when I last was doing this daily) was less fun than other languages (their armory stocks a nice assortment of footguns and the debugging support was... minimal. Might have changed since then.)