Flutter Is About To Win Over the Web

Websites today, including the one you are using now, are written in HTML, JavaScript, and CSS. You probably read that and think to yourself well, yeah, that’s patently obvious. If I told you to create a website without using any of these three technologies, you would probably have some questions.
And yet, throughout the course of history, we’ve had many players in this space. We’ve had Flash, we’ve had Silverlight, all competing technologies that have attempted to shave off a slice of the browser market, to let the developer use a different technology to create a website. But none of them have really ever taken off. So how is it possible that I am coming to you, dear reader, and telling you that there could yet again be a competitor in this space? Especially after literally none of the other players in this space have gone anywhere, despite years of effort?

https://encinitaschamber.com/forum/topic/full-watch-servant-season-2-episode-5-online-free-streaming
https://encinitaschamber.com/forum/topic/123movies-servant-season-2-episode-5-hd-online-stream-free-series
https://encinitaschamber.com/forum/topic/full-watch-servant-season-2-episode-5-hd-online-free-123movies/
https://encinitaschamber.com/forum/topic/full-watch-a-discovery-of-witches-season-2-episode-6-online-free
https://encinitaschamber.com/forum/topic/123movies-full-a-discovery-of-witches-season-2-episode-6-hd-watch-online
https://encinitaschamber.com/forum/topic/watch-a-discovery-of-witches-season-2-episode-6-online-full-series
https://paiza.io/projects/iFHlJm8vAzAACaYKEKEvHA?language=php
https://www.onlinegdb.com/fGaH6_9BM
https://caribbeanfever.com/profiles/status/show?id=2663233%3AStatus%3A12583809#comments
http://beterhbo.ning.com/profiles/blogs/flutter-is-about-to-win-over-the-web
http://beterhbo.ning.com/profiles/blogs/cnfgmvf
http://www.shadowville.com/board/general-discussions/flutter-is-about-to-win-over-the-web#p465877
https://blog.goo.ne.jp/saloirkofe/e/f30f5ff964c82f53e5a4ca0f61881551
https://warosu.org/jp/page/S1#p33152746_1
http://paste.jp/44087528/
https://www.hybrid-analysis.com/sample/c3079a81f59cd804945cc8283aeacd77b0b443fc795e56f0c64bea104217250d
http://www.4mark.net/story/3203520/full-watch-servant-season-2-episode-5-online-free-streaming
https://telegra.ph/Flutter-Is-About-To-Win-Over-the-Web-02-12
https://myanimelist.net/blog.php?eid=843217
https://sanaeoi3.cookpad-blog.jp/articles/571223
https://cox.tribe.so/post/https-encinitaschamber-com-forum-topic-full-watch-servant-season-2-episode---6026a5c020e47336320fa1b4
http://officialguccimane.ning.com/photo/albums/cvcxvxcv
https://www.posts123.com/post/1331562/cvbmxcvbdfxzfb
https://ideone.com/NNTwYm
https://jsfiddle.net/q90edpkL/
https://dumpz.org/cxFa5GGqsDws
https://p.teknik.io/z8F0U
https://bpa.st/XROQ
https://paste.in/7tD429
https://pasteio.com/xk9uB5Y45C12
https://paste.ee/p/uo0lP
https://paste.centos.org/view/70d7bdcd
https://slexy.org/view/s20sSkfF24
https://paste.feed-the-beast.com/view/bfcf4038
https://paste.tbee-clan.de/zyLb5#
https://rentry.co/n53as
https://paste.by/yrQFi55Bum
https://pastebin.com/btd5jerT
https://www.heypasteit.com/#
https://justpaste.it/6xoio
https://paste.toolforge.org/view/6c1ea907

Well, let’s take a minute to appreciate the things that these past attempts have had in common, namely:
They needed a browser plugin to run. They normally need a platform-specific browser plugin to run on a targeted platform. Silverlight is a good example of this — at the time, people who use Linux couldn’t watch Netflix, as the site depended on Silverlight (which wasn’t available for Linux). Sure, there were open source alternatives, but nothing first-party.
They introduced security vulnerabilities. Flash was notorious for this (with over 1,000 known vulnerabilities). The browser would have to load a plugin to display the content, and at that point, none of the security safeguards of the browser mattered, as the plugin had complete access to the host computer.
The performance was not as good as pure HTML. In terms of whether it was faster to load a plugin and display some text, it was always faster to just do it in raw HTML and CSS as opposed to trying to load a plugin to display some content for you.
HTML5 came, and CSS improved. Suddenly, creating beautiful, involving experiences wasn’t impossible. Better still, browsers that hated standards, used weird hacks, or used vendor-specific implementations instead of their CSS equivalents (like Internet Explorer) were killed off.
All of these things made the choice to create a new web app in native HTML easy. After all, if the technology that you used to create your web experience got deprecated, and stopped receiving security fixes, then there would be no option but to rewrite your app from scratch in a new, supported language. But how did we get here in the first place? How did HTML become such a mainstay in today's thriving internet?

In order to create a simple website, you need to be across three separate languages, and that’s purely for the website itself. That’s HTML, JavaScript, and CSS. Your website has to look and feel great, and it can’t do that if you don’t know how to write performant JavaScript or if your CSS styling is bad.
If you actually want your website to do anything, then you might use a framework like Angular or React. As you start to bring in packages via npm, the size of your app starts to grow, so you will also use a bundler like webpack to tie all your packages together and minify them appropriately. Webpack is a topic in itself (and a huge one at that) but it’s a worthwhile topic to consider and does form a considerable part of building web apps.

Once you have your website and you have your packages, you need to use a bundler to bundle up your client app and to make sure that it works in their browser. Depending on what browser they are using, you’ll also need to “shim” in certain features so the user’s browser can actually use your website. If you’re using a language like TypeScript, webpack also transpiles from this language into JavaScript. Nothing about this is inherently bad, but it is very complex and has a lot of moving parts. If your website breaks, did you mess up the code, or did the minification break it, or did webpack not include it properly, or did the transpilation process introduce a problem? These complicated pipelines can introduce difficulties in debugging or finding the root cause of issues in your app.

If you’ve heard of Flutter, you’ve likely heard of it in the context of phone app development. So how on earth does it apply to websites? Well, with a normal HTML webpage, you deal with the page as a document. In Flutter though, the “page” (or what the user interacts with) is actually drawn to an HTML canvas. Flutter actually controls every pixel that is drawn to the screen and doesn’t use HTML, JavaScript, or CSS to define any of its look or logic. (Technically speaking, native Dart code is transpiled to JavaScript through dart2js, but no business logic is actually written in JavaScript.)
You’ve likely picked up two things alarming with that sentence. First, no HTML. Second, we’re drawing everything to the canvas. I get it — it sounds weird and, at least in the case of drawing to the canvas directly, not very performant. But let’s dig into this a little bit more.