Lesson 3 - How Netlify Blows The Competition Out Of The Water

[00:00 - 00:08] Why should someone choose Netlify? Well, there are a few different reasons you could choose Netlify R, say, "Why do you deploy your product?"

[00:09 - 00:21] First of all, here's some of the organizations that use Netlify other than ourselves. It's Tagoreflow, it's Nike, it's Riot Games, and it's Kubernetes.

[00:22 - 00:38] Now, if someone knows how to properly pronounce Kubernetes, please let me know if it's a huge debate and I can't find a right solution. So, yeah, you are a good company and we're not just speaking around them just to deploy our apps with.

[00:39 - 00:50] So the second reason to choose Netlify as a way to deploy your app. That's because it's built with absolute ease of use in mind.

[00:51 - 01:04] What does this mean? It means that it was made so that it's a great option for everyone from developers to marketers, to anyone, no matter how much you know about code and deploying and development in general.

[01:05 - 01:16] And yeah, this means that you don't have access to a complete controller over everything, but that's exactly the point. You don't need access.

[01:17 - 01:31] And you shouldn't have access to everything if you want speed, because if you want access to everything, it means if you need that stuff, you need to set up everything yourself. And this is what takes a lot of time.

[01:32 - 01:49] So obviously you need to delegate some of these things to Netlify and let it have its basic defaults that help you deploy fast. That being said, you still have access to all of these different options.

[01:50 - 01:55] So it's not like you don't have access to anything at all. It's just basically, think of it more like defaults.

[01:56 - 02:05] You have default that is used and then you can go and change it. But let's see a better example.

[02:06 - 02:10] Let's say that I want to deploy my app. Let's see how you will go on this to the Atlassian versus Netlify.

[02:11 - 02:15] So on this Atlassian, I would need to sign up. I would need to choose my dropnet.

[02:16 - 02:22] I would need to SSH into my dropnet. I would need to SCP into my project.

[02:23 - 02:37] I would need to make sure that I do it at a directory that I will be using for the following setup or else nothing would work basically. Netlify is hard to install engine on my dropnet.

[02:38 - 02:45] I would have to set up engines to serve my project from the directory I-S-speed to. I would need to install it as I said.

[02:46 - 02:56] I would need to edit my engine configuration to use that SSL. I would need to try not to cry, but I will probably end up praying a lot anyway.

[02:57 - 03:05] Now on the other hand, with Netlify, I will have to sign up and I would have to drag and drop my project into Netlify. And that's it.

[03:06 - 03:07] That's all. Nothing else.