The question is, how do we, from the comfort of our local browser, access this data? With modern security protocols and limitations of the browser, we can’t exactly establish a database connection and query for the data we desire (for good reason). When we build web applications meant to be run in the browser, more often than not, we’ll require some sort of data to display on the page that ultimately is stored in some database on some server, somewhere on continental Earth. With the plethora of SPA frameworks available at our disposal, JavaScript holds the market share by a landslide, and for a good reason. Working on the modern web nowadays, for the most part, requires knowledge in some form of the client-server model, with our specific implementation being communication between the browser and a backend service API. So, without further ado, let’s jump into the first topic in our Blazor series. In the spirit of helping others learn from my trials and tribulations, I wanted to write a series of posts exploring Blazor that will hopefully serve as a reference for you on your own personal journey into Blazor development. NET community as they’ve embraced the framework in its entirety. I’ve been fiddling with Blazor a lot lately, using it for personal projects, and experimenting with the plethora of awesome tools and libraries put together by the. Don’t get me wrong, we’ll dive into some of the details when we start getting our hands dirty with the framework so we have a somewhat fundamental understanding of what exactly is going, but we’ll only be skimming the surface. I won’t go into the details as to how exactly we get native C# code to run in the browser, as there are numerous articles and documentation out there that will do a much better job than I ever could providing technical explanation for the framework, as quite frankly I’d be lying if I said I fully understand how the minds at Microsoft, a.k.a Steve Sanderson and team, built Blazor in the first place. If you have heard of Blazor, or have even used it in a project, you’ll know that it works because of WebAssembly. If you’ve been living under a rock and this is your first time hearing about Microsoft’s new SPA framework, I’d suggest taking an afternoon to read through some of the getting started docs the team has put together, the different hosting models the framework has to offer, and Blazor’s philosophy in general. NET developers, and anyone looking for a JavaScript alternative, to bring their backend skills and knowledge to the browser, all in the same platform. I could go on and on about my personal journey with JS, things I like about the language, things about it that make me want to throw my laptop off a 20-story building, and where I see JavaScript’s place in modern web development evolving over the coming years, but I digress.Įnter Blazor, the new kid on the block from Microsoft that enables. However, despite my personal angst with JavaScript, I can think of quite a few other languages and platforms I’d much rather stay further away from than JS (I’m looking at you, AS/400). If I told you that I’m an advocate for JS, in all honesty, I’d be lying. Heck, I’ve had my fair share of JS development during my professional career, from fixing mid-90’s early JS that will make your eyes bleed, to building large enterprise web applications using Angular with TypeScript for sanity. Listen, I get it: JavaScript leaves a lot to be desired for a Turing-complete language, but nonetheless, it is quite the robust language and is used by companies large and small across their entire stack and there’s nothing we can do to change that. It just so happens that since JavaScript’s rise to power beginning in the mid-to-late 2000’s (some might argue sooner, some later), virtually every modern website on the web nowadays has some sort of JS running to make those fancy page transitions seem like magic to the user. Now just because a language happens to be used en mass across a variety of development specializations does not necessarily mean it is superior to any other language, or framework. JavaScript is used all over the web, across the entire stack, and even leaking into the desktop development space with things like Electron. Two truths and a lie: Nickelback is good, pineapples don’t belong on pizza, and JavaScript is bad.Īll memes aside, JavaScript is not actually bad, despite most of the developer opinions you might see on r/ProgrammerHumor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |