#FiveThings Why JavaScript Developers Should EVEN Care About .NET Core

>>Here we go. It’s like the last actual phone
in the world. I don’t even know what
this is supposed to mean. Hi, I’m Burke Holland.>>I’m Jasmine Greenway.>>This is five reasons that JavaScript developers should
even care about.NET Core. Thing number one,.NET
Core is cross-platform. So, when say.NET
is cross-platform, does that mean that it works
on all versions of Windows? What do we mean by
cross-platform, really?>>Well, not only all
versions of Windows, but also Linux and Mac, and actually, also an IoT
devices believe it or not.>>Really?>>Yeah, absolutely. So, you
could pretty much program your fridge on.NET Core If you have one of
those little Samsung, whatever Tizen things, I
forgot what they’re called.>>Yeah, I think
it’s a Tizen fridge, it’s a screen on
your fridge where you can see the weather,
play video games.>>Yeah.>>Does anybody, I don’t know why anybody would ever do that.>>Right.>>If you have a smart fridge,
what’s wrong with you? But you could run.NET
Core on your fridge.>>Yes, absolutely.>>It’s a nice thing. Nice.
Can I run it on this iPad?>>Not today, but maybe
one day. Who knows?>>Hey, listen
anything is possible.>>Anything is
absolutely possible.>>Wow.>>For sure.>>Thing number two.
When you’re building a single page application it’s easy to use.NET
Core for back-end. So, I think it goes
without saying although a lot of
times we don’t say it, single-page applications can
have to have a back-end. A lot of JavaScript developers do something else
besides JavaScript. A lot of them do Java
or or they do .NET, so.NET Core is a very, very attractive option or it could be an attractive option for building back-ends for
your single-page application.>>Yeah, absolutely. So,
you can use the .NET Core’s Web API and it’s
super easy to get started, there’s so many templates. So, actually in fact there’s
templates on working with the Web API and
with the front end. So, for example,
if you’re a fan of the angular command line
and you want to work with it
independently with Web API, you can absolutely do that and work on your front-end work
on your back-end. In fact.NET or the.NET
teams actually added libraries for to
make it super easy, so you can do things
like hot reloading and or Hot Module Replacement.>>So, you save and it
automatically recompile scene, you have to stop and restart
again to see the changes?>>Exactly. Also as
a last final detail approximately zero
JavaScript developers also write COBOL. I don’t
know if you know that.>>Oh.>>That’s a scientific
statistic I looked it up.>>Oh, really?>>Well, there may be one or two. If you’re out there
and you write COBOL and you also write JavaScript, had deciphered let us know
we’ll send you something.>>Right. Yeah.>>Thing number three. You
can get started with .NET Core with only the command line. Now, I’m going to be honest
that’s a little weird for me. I’ve a history with .NET
and I do believe you also need like 76 gigabytes
of Visual Studio, is that not the case?>>So, number one, Visual Studio is actually not that large.>>Okay, 75 gigabytes. I’m embellishing, I apologize. It’s not. It’s like four, three, four something,
I don’t know. Such a smaller than it was back
in 2015 when I was [inaudible].>>Yeah. It’s much smaller. You don’t need IDE
to get started, or IDE or text editor
to get started, you could literally just
download it and do.NET run, .NET new to create a new project,
.NET star and you have your own .NET project
ready to go [inaudible].>>Just right there
on that terminal.>>Yes.>>What about Visual Studio Code? Some people may know I
love Visual Studio Code. I also love my light editor
theme, don’t add me. Don’t add me. There’s nothing wrong with
a light editor theme.>>No.>>So, for those of us
using Visual Studio Code, which was a lot of
folks, are there any tools or extensions that
would make that easier?>>Yes, OmniSharp. OmniSharp will take care
of any references and things like that you
might be missing in your library and
your syntax issues. OmniSharp is like your one-stop-shop for
all that with.NET.>>So, check out
the OmniSharp extension, will put a link in the show notes to that extension for you. So, go ahead and check that
out if you’re interested in doing .NET Core inside
of Visual Studio Code. Excellent. Thing number
four, .NET Core is fast. I know everybody says that, but I think that maybe we should talk about
just how fast it is. So, can you give us
an example here, so we’re not just
saying it’s fast?>>Yes. So, my favorite
example is Raygun. So Raygun, they are this analytics company
that does a lot of like crash reports and
things like that on mobile and web apps. They did a case study
where they improved, where switching to .NET Core
improved throughput from 1,000 requests per second to
20,000 requests per second.>>20x performance improvement?>>That’s 2,000 percent increase. Triple increase,
which is amazing.>>Increase over what? What
were they using before?>>They were using Known.
Believe it or not. So, we actually have benchmarks that report every month or so about how fast it is. The reason why .NET Core is
so fast is that, in the past, we had, if .NET was as we
know it was only for Windows.>>Right.>>Now that we have, .NET had a library that were
old, Windows specific. Now so, getting rid of all
those libraries and improving these performances and improving performances like on things like collection and things like that, has made .NET Core super fast. Believe it or not, a lot of these improvements came
from outside the community.>>Oh, really? Which brings
us to our next thing.>>Yes.>>Thing number five,
.NET Core is open source. Which, cool story bro, everything is
open source these days. What’s in it for me as a JavaScript developer,
why do I care?>>So, yes, .NET’s Open Source and the nice thing about that is you get full transparency, you get interaction with
the actual team that’s working on.NET Core and you
also get the road maps. So you can see the roadmap,
you can see what’s happening, what’s coming up and
also have input. So, we had a lot of contributors
who come in and just add these new improvements
and updates and ideas and make .NET for them. Because that’s what it
really is. It’s not about reaching out to developers
and open source, it’s just a window to
make this language ours.>>Yeah. I think that’s so great. One of the things that I
love about open source, which I think you hit on
is, the contributions. I remember when someone
from the community added basically Json support
for .NET with Newtonsoft.>>Yeah.>>I remember that. You had
this third party package, which eventually just became,
they were just shipping it.>>Yes.>>So, it’s so cool
that people can now add this stuff directly
to the framework. I also think that it’s been around for so long
that they’ve had so much time to iterate
to make it super fast. Already hit all of
the roadblocks and had all the hard issues and figured out and
gotten around them. There’s a lot of advantage in using something that’s
extremely mature. A very mature framework,
a lot of advantages to that.>>Yes, I agree.>>As a footnote, I used
to be a.NET developer. I was never very good, I only did it for a short
amount of time. But what I noticed was that, C# and JavaScript are
actually quite similar. Now, it’s easy for
me to make the jump. So, if you are
a JavaScript developer, one of the advantages
to looking into C#, is that it’s going to
feel very familiar. So, if you’re thinking,
I can only do Note or I can only do JavaScript, you should look into C# a little bit and see if
it might be for you. We’ll leave some links
for you and the resources below where you can
get started with that. I’m Bart Collins.>>I’m Jasmine Greenway.>>Now you know five reasons why JavaScript developers should
even care about .NET Core.


Add a Comment

Your email address will not be published. Required fields are marked *