> If not what are the reasons for a startup to stay away from .NET CORE? I've been using .Net for over 10 years now, and just launched a new product on Asp.Net Web API + SQL Server + Orleans. Whatever Microsoft says, .Net Core is not at all ready. The tooling and libraries are still undergoing major (and breaking) changes. You'll spend more time debugging it than your own code. I (foolishly) tried to adopt it a year…
Ask HN: Are there any startups willing to use the ASP.NET Core technology?
11–20 of 68 posts
Re: Ask HN: Are there any startups willing to use the ASP.NET Core technology?
#12.NET's text-to-speech isn't available in .NET Core, much less on Linux.
Re: Ask HN: Are there any startups willing to use the ASP.NET Core technology?
#13My startup is based on Windows, the .NET Framework, ASP.NET for Web pages, and ADO.NET for interacting with SQL Server. For the programming language, I'm using Visual Basic .NET -- as Kernighan and Ritchie, IIRC, stated in their C , the lanugage has an idiosyncratic syntax, which it turns ou I don't like. Since C# borrows some of that syntax, I prefer the more traditional (like PL/I, Pascal, Fortran, Algol, etc.) syn…
Re: Ask HN: Are there any startups willing to use the ASP.NET Core technology?
#14The tooling side of things is surely a pain, but it's getting better. I liked the project.json style, so i'm a little disappointed they are moving back to csproj.
Aside from that, it's a great, intuitive, fast framework that we use in production and I love it more every day. I'd chose it again and again.
Watch out for the lack of performance monitoring solutions available so far. Most of them haven't got support for .NET Core yet. New Relic does not.
Re: Ask HN: Are there any startups willing to use the ASP.NET Core technology?
#15StackOverflow.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-...
Re: Ask HN: Are there any startups willing to use the ASP.NET Core technology?
#16> If not what are the reasons for a startup to stay away from .NET CORE? I've been using .Net for over 10 years now, and just launched a new product on Asp.Net Web API + SQL Server + Orleans. Whatever Microsoft says, .Net Core is not at all ready. The tooling and libraries are still undergoing major (and breaking) changes. You'll spend more time debugging it than your own code. I (foolishly) tried to adopt it a year…
I recommend anyone looking at .NET core to use Java for now. The languages are basically mutually intelligible and while java is a bit less syntactically pleasant it gets the job done, and the tools are quite mature. Arguably Java has, and has had, 99% of what .NET core is trying to achieve for many years. Using the right frameworks it's incredibly fast, multiplatform, and even serverless.
The biggest problem that you run into with Java is too much choice, the opposite of the .NET framework. Deciding which tools to use takes a fair amount of research because the ecosystem is so massive. I've been cutting my teeth on it for the past couple months and I would say go with these frameworks:
DropWizard Play Jersey
running on Grizzly, Jetty, or Netty depending on which project supports what.
Database-wise for ORM nothing beats Hibernate. Entity framework is basically a slower more confusing copy of hibernate, coming from someone that's used both. The main advantage of EF is LINQ which Hibernate can't quite match in theory but usually does in practice(the queries generated by HQL tend to be a lot less....stupid)
Re: Ask HN: Are there any startups willing to use the ASP.NET Core technology?
#17> If not what are the reasons for a startup to stay away from .NET CORE? I've been using .Net for over 10 years now, and just launched a new product on Asp.Net Web API + SQL Server + Orleans. Whatever Microsoft says, .Net Core is not at all ready. The tooling and libraries are still undergoing major (and breaking) changes. You'll spend more time debugging it than your own code. I (foolishly) tried to adopt it a year…
Can I ask what you ran into? I'm thinking about starting a side project with .Net Core for my API and React for my front end. I'm wondering if it's even worth it to use Core at this point or switch to Go or Node.
I was always partial to Pythons Flask as well
What did we run into? Tons of brokenness. Inability to use C# libs was the biggest problem, if you're trying to make anything significant you're going to have to roll your own everything. Java is the safest bet for large projects, I've never run into any issues finding a quality library to do anything. This is coming from a guy that's been a career C# dev for years and wishes he could defect to Java.
Re: Ask HN: Are there any startups willing to use the ASP.NET Core technology?
#18I work for a very mature startup, and recently led our first site on ASP.NET Core. The framework itself is very nice and very solid, basically a "do-over" of all the previous ASP.NET frameworks with the benefit of hindsight. Although there's been some new things to learn, I've been very pleased with how consistent and thought out the new ASP.NET Core is. We run the site in production. Having said that, the tooling ar…
They both also need to use project.json for their definition for this to work, otherwise packaging will have to be the solution.
Re: Ask HN: Are there any startups willing to use the ASP.NET Core technology?
#19We have had a pleasant experience so far. Performance is better across the board. Development is as fast or even faster in most cases. Deployment has also been simplified.
We started the port of our code base around October last year and released the update to our product at the end of December. During that time frame, we migrated from 1.0 to 1.1.
We are using some awesome libraries from the community and a few small ones we wrote internally.
Libraries include:
openiddict (for openid connect and oauth 2.0) rawrabbit (simple rabbitmq library) entity framework core with npgsql mailkit for smtp email sending
We wrote these library wrappers around third party services because they did not exist in a stable form: twilio wrapper nexmo wrapper gcm wrapper (now fcm wrapper) bitgo wrapper (hosted bitcoin wallet provider) blocker wrapper (blockchain explorer) openexchangerates wrapper api layer wrapper (mobile number verifications) ip-api wrapper
among others.
A service monitor for monitoring availability of third party services
We have also a spin off from our main product where we are using an private blockchain-like solution(openchain) for a niche market.
We have been very pleased with the overall experience using .NET core so far and we are looking forward to moving to 1.2.0 as soon as it is out.
The only real issue we've had is that the new signalr library does not have a stable release though we are using it in production. We've had to isolate it into a separate project but because of compatibility issues with 1.1 libs. Can't complain about hat though as we knew it is an unreleased pre-beta level library.
To manage the risk of using it, we try to follow the development closely and prepare in advance for any changes we can see coming.
Re: Ask HN: Are there any startups willing to use the ASP.NET Core technology?
#20(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...