Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Announcing .NET Core 1.0

blogs.msdn.microsoft.com

Post reply on HN
Print view View original

91–100 of 327 posts

Re: Announcing .NET Core 1.0

#91

Post by PopsiclePete »

RomanPushkin wrote: post #34

Do we officially have better-than-Java on all platforms now?

Yeah but so what. If the "best" language always won, why isn't the entire world running on Haskell and Rust or whatever? Java's eco-system is ginormous and it's deeply entrenched as the "corporate stack" in non-MS shops, with more than 15 years of history.

I'm afraid this is just too late to make a big dent. C# is nicer than Java, but not that much nicer to warrant switching over or rewriting your stuff in a very immature eco-system.

Maybe they're hoping to capture some of that elusive start-up market- and mind-share? That one is already pretty hostile towards MS...

Either way, this is a good thing, I just wish they had done this in 2005 or so.

Re: Announcing .NET Core 1.0

#92

Post by jsingleton »

computerlab wrote: post #79
jsingleton wrote: post #33

Earlier quoted context omitted.

MVC 6 is the version that works best with Core, although they don't really refer to it directly much any more. Both MVC 6 and Web API 2 are now part of Core. They're just packages like everything else.

Good point, I meant MVC6. I confused the versions of ASP.NET 5 (which is now known as ASP.NET Core) and MVC6.

The naming is really confusing, but then naming things is hard. As Phil Karlton famously said:

  There are only two hard things in Computer Science: cache invalidation and naming things.

Re: Announcing .NET Core 1.0

#93

Post by eropple »

AndreyErmakov wrote: post #50
jsingleton wrote: post #36

Earlier quoted context omitted.

I would be surprised if there wasn't a free (as in beer) Express version for Linux, with a DB size limit like 10GB. Otherwise Entity Framework Core supports PostgreSQL, but there isn't any lazy loading yet.

What I meant was that's just not enough. You can toy with it in a hobby project but in production that will be exhausted pretty soon.

I think that probably depends pretty heavily on what your app is. One of my clients has about 200,000 user accounts (and 40K actives/week) in a database that's well under 4GB, and it's been live for three years now. It's in Postgres, but there's nothing that'd stop them from using a 10GB-capped SQL Server Express until a point where having to pay for SQL Server is a good-problem-to-have.

Re: Announcing .NET Core 1.0

#94

Post by chrshawkes »

jsingleton wrote: post #36
AndreyErmakov wrote: post #19

A bit unrelated, but I'm hoping to hear something soon about the future licensing model for the upcoming SQL Server on Linux. Do we get a free version without DB size / CPU / RAM limitations (but perhaps with some other restrictions) that smaller companies and startups can use in production? I'm planning to run my future ASP.NET MVC projects on Linux and very much would like to know if a better SQL Server Express / C…

I would be surprised if there wasn't a free (as in beer) Express version for Linux, with a DB size limit like 10GB. Otherwise Entity Framework Core supports PostgreSQL, but there isn't any lazy loading yet.

I don't believe it works outside of using EF. Last I checked no database drivers existed for .NET Core for MySQL and PostgreSQL. For that reason I've stuck to Django.

Re: Announcing .NET Core 1.0

#96

Post by triangleman »

knocte wrote: post #82
tacos wrote: post #39

Earlier quoted context omitted.

Way too many compatibility issues unaddressed by that PR to have a hope of getting anything changed there. Also it looks like what you (?) are trying to do could easily be solved with the Path.* and Directory.* path manipulation functions. No need to put a million apps at risk when you can wrap your call to Uri() with a three line helper.

3line helper? facepalm ...

Care to enlighten us?

Re: Announcing .NET Core 1.0

#97

Post by jenscow »

wvenable wrote: post #85
daveguy wrote: post #67

FYI, from the announcement. Probably the most important part at the end, italicized by me. Also note (elsewhere) that licenses are MIT and Apache2: .NET Core Tools Telemetry The .NET Core tools include a telemetry feature so that we can collect usage information about the .NET Core Tools. It’s important that we understand how the tools are being used so that we can improve them. Part of the reason the tools are in Pr…

Microsoft is looking to do more data-driven design; this is the reason for all the telemetry in Windows as well. Raymond Chen pointed out an example where a button was removed File Explorer (prime real-estate) because the telemetry showed that hardly anyone ever pressed it. It's unfortunate they are so tone-deaf about the PR implications in Windows.

Like when they removed Macros from Visual Studio because according to telemetry only 1% of users used them.

Re: Announcing .NET Core 1.0

#98

Post by jsingleton »

chrshawkes wrote: post #94
jsingleton wrote: post #36

Earlier quoted context omitted.

I would be surprised if there wasn't a free (as in beer) Express version for Linux, with a DB size limit like 10GB. Otherwise Entity Framework Core supports PostgreSQL, but there isn't any lazy loading yet.

I don't believe it works outside of using EF. Last I checked no database drivers existed for .NET Core for MySQL and PostgreSQL. For that reason I've stuck to Django.

I believe you can use PostgreSQL with Dapper, as there is an ADO provider for PG, but I haven't tried this.

https://github.com/StackExchange/dapper-dot-net#will-dapper-...

Re: Announcing .NET Core 1.0

#99

Post by manigandham »

chrshawkes wrote: post #94
jsingleton wrote: post #36

Earlier quoted context omitted.

I would be surprised if there wasn't a free (as in beer) Express version for Linux, with a DB size limit like 10GB. Otherwise Entity Framework Core supports PostgreSQL, but there isn't any lazy loading yet.

I don't believe it works outside of using EF. Last I checked no database drivers existed for .NET Core for MySQL and PostgreSQL. For that reason I've stuck to Django.

npgsql is the open-source default driver for PostgreSQL and works with .NET core (netstandard 1.3):

https://github.com/npgsql/npgsql

Re: Announcing .NET Core 1.0

#100

Post by jsingleton »

enricosada wrote: post #75
jsingleton wrote: post #68

Good news! Now time for all the library and framework authors to add support for .NET Core. I know a lot of people were waiting for RTM before starting this, considering the massive changes between RC1 and RC2. I've started a support matrix project at https://anclafs.com . Feel free to file an issue or send a PR on GitHub.

the asp.net core changed a lot between rc1 and rc2 (because moved to .net sdk instead of dnx). The normal libraries or console app not too much

It depends on if you want to run ASP.NET Core on .NET Framework 4.6 or on .NET Core 1.0. It's not just the SDK that is new, Core console apps are pretty recent too, as previously it was mainly for web apps.
Post reply on HN