21–30 of 68 posts
Yes, we launched our start up on ASP.NET Core - https://www.comparelearning.com.au/ (We're based out of Sydney Australia - not SF). Overall, it was a positive experience and I think even with the current warts (in particular around tooling), it's a nicer stack than MVC5. I blogged about some things we learned here: https://chad.tolkien.id.au/lessons-learnt-going-into-product...
Most startups are not going to be purchasing hardware for a hosted solution but instead will use cloud servers ala azure or aws heck even google cloud. .NET is supported on all of them.
.NET has great tool, is now open source both standard and core, widely supported, and unless you plan on running linux or mobile then why not?
Since it's been an hour and there hasn't been much response, I'll give my two cents. I don't work for a startup. However, I do work in a small team of 3 developers, and have recently been faced with the decision of choosing a technology stack to start from scratch. Before this decision, we were using PHP5; we were constantly putting out fires and couldn't ever get any actual work done because of this awful inherited…
Go is object oriented.
> I hate to say it, but I just don't trust Microsoft.
But you trust Google? well known for discontinuing products or abandoning them ( GWT?,... )
> It's a statically typed language that treats functions as first class citizens
Without some form of generics/type classes you can't fully take advantage of Go first class functions to do classical functional programming.
> It's not object oriented
it's completely object oriented, it has methods on values,composition through struct embedding and implicit interfaces for polymorphism. It ticks every box of a OO language.
> is easy to deploy (compiled & doesn't depend on a runtime like JVM or .NET core)
Go actually has its own runtime, it's just included in the binary resulting from the compilation.
> doesn't have exceptions (yay)
Go has panics which are exceptions.
I personally find Go useful but don't like the limitations of the language. And they are showing already with more and more untyped API ( context.Values(interface{})interface{} ). Go relies way to much on runtime behavior like type assertions for a so called statically typed language. Go basically asks the developer to do the compiler's job. Because the compiler doing its job would make it slow (?!?). So you find yourself doing a lot of copy paste, writing your own parsers, code generators and manifests to use go gen, use tricks that make code ugly, or just say "fuck" to types and use "interface {}" when you are tired of all that.
.net core isn't ready for production, but when it does it will support both F# and C# + a vast ecosystem of libraries useful for web development, gaming (unity), mobile and desktop apps (Xamarin GUI libs ...), while Go users will be stuck with that poor type system writing extremely verbose code because they believe that generic programming is bad.
StackOverflow.com [1] I'm not certain I'd still call them a "startup" but they have been very open about their large use of .NET and the advantages it brings to bear. [1] http://nickcraver.com/blog/2016/02/17/stack-overflow-the-arc... Edit: More .NET information / usage. [2] http://nickcraver.com/blog/2016/03/29/stack-overflow-the-har... [3] http://nickcraver.com/blog/2016/05/03/stack-overflow-how-we-...
That said, we do maintain a number of .net libraries, such as Dapper or miniprofiler and we ported them to .net core (or we are in the process of doing that).
We are also contributing significantly, together with other community leaders, to the design and development of the .net core API.
This said, we have been having some of the pain that is mentioned in other threads. The framework is still incomplete and evolving, although a lot of what's coming out is excellent and very fast/modern.
Since it's been an hour and there hasn't been much response, I'll give my two cents. I don't work for a startup. However, I do work in a small team of 3 developers, and have recently been faced with the decision of choosing a technology stack to start from scratch. Before this decision, we were using PHP5; we were constantly putting out fires and couldn't ever get any actual work done because of this awful inherited…
> Object-Oriented programming doesn't have a place in our hearts, Go is object oriented. > I hate to say it, but I just don't trust Microsoft. But you trust Google? well known for discontinuing products or abandoning them ( GWT?,... ) > It's a statically typed language that treats functions as first class citizens Without some form of generics/type classes you can't fully take advantage of Go first class functions to…
Since it's been an hour and there hasn't been much response, I'll give my two cents. I don't work for a startup. However, I do work in a small team of 3 developers, and have recently been faced with the decision of choosing a technology stack to start from scratch. Before this decision, we were using PHP5; we were constantly putting out fires and couldn't ever get any actual work done because of this awful inherited…
.net core is exactly the same as go, it can be compiled to an exe that includes the runtime.
I love it.
Feel free to PM for more info.
I just view .net as the staple of commoditized programming language. Go to Asia, Europe, they are always there. The "Java" of Microsoft and it's powering lot of stuff out there.
Since it's been an hour and there hasn't been much response, I'll give my two cents. I don't work for a startup. However, I do work in a small team of 3 developers, and have recently been faced with the decision of choosing a technology stack to start from scratch. Before this decision, we were using PHP5; we were constantly putting out fires and couldn't ever get any actual work done because of this awful inherited…
> Object-Oriented programming doesn't have a place in our hearts, Go is object oriented. > I hate to say it, but I just don't trust Microsoft. But you trust Google? well known for discontinuing products or abandoning them ( GWT?,... ) > It's a statically typed language that treats functions as first class citizens Without some form of generics/type classes you can't fully take advantage of Go first class functions to…
My advice would be to only use it now if you are starting from scratch and you have no business goals in the next 6 months (you are building an MVP and can take the hit of some random bugs in production). I know that at least one startup is using it for critical services, but they are also committed to fixing the dotnet core source code when they run into a problem and I believe are part of the reason for the good pref of kestrel (new web server), I think unless you are willing to do that you should wait a bit longer.