Solid's power is that everything is a primitive, right down to the JSX. It evolved to shedding that weight as it came into its own. Solid was modular from the start, built to work with Web Components as a component-agnostic solution. While we could never rewrite what we had we would quickly rip out and replace parts. It was a long lived project that needed to keep on changing and pivoting to find its customer. First created as a side project in 2016 when I was at a startup creating private Social Media. It's an effortless way to get unmatched page load performance without getting away from the simplicity, that in the end we are just making pages in a website. It has the tersest syntax that lets you write the least code of all JavaScript Frameworks. Its Multi-Page forward approach isn't worried about persistent client state or client routing and just works like a website the way you'd expect. Its "Islands" are automatic, and its streaming as easy as adding an tag with a promise. It has all the characteristics people using server templating languages are used to but it is fully isomorphic to become interactive in the browser automatically.Īnd it sends the least JavaScript without thinking. Components are auto discovered and the impact of adding JavaScript feels minimal. marko or using the HTML they copied and pasted from StackOverflow. Marko is a Superset of HTML where the whole world lives in Single File Components and a new user can enter this world simply by changing the extension of the HTML files they got from a designer to. It was very clear from its beginning it was ultimately a language rather than a framework a line of thinking that wasn't really popularized until Svelte did similar half a decade later. Marko also was one of the earliest compiler-based frameworks as its origins were from server side templating languages. A huge emphasis placed on page load, being the first JavaScript framework to introduce both Out of Order Streaming and Partial Hydration right from its inception. It was built for eCommerce and the demanding nature of support global customers where not every device and network is made equal. Marko was created at eBay sometime in the early 2010s and was open sourced in 2014. And the frameworks/libraries I'm talking about today represent both sides to a tee. So it does make sense that maybe there is a way to make this unified even when it hasn't been feasible. We have seemingly two very different use cases trying to leverage the same technology. It even predates Single Page Apps, although that is why it has come into focus so much the past decade. Well, this has been the dichotomy of the web for a long time. Nothing wrong with backing multiple horses. And instead of being focused on the middle and being everything to everyone focus on the more achievable task at being the best version in the places that are divisive. So the task was simple: Don't change the world, change the perspective. But we as developers keep on changing our perspective to pull out these 2D comparisons. It's easiest to explain this as a bunch of independent ranges but the reality is we live in a multi-dimensional world and one solution isn't always fully on one side for all decisions. A pincer movement of sorts for the JavaScript framework world.Įvan You, creator of Vue gave a great talk on tradeoffs of frameworks where he positioned Vue as that middle ground between React and Angular. But the reason this excited me so much was that Solid and Marko represented the most powerful approaches on the axes that matter. Every design decision made with different set of tradeoffs, where the "right" answer for each is allowed to be different. In many ways, they couldn't be more different. Some wondered why I would take on working on a second framework but I never saw a conflict. I would have the opportunity to work on two of the most exemplary approaches to what the future of JavaScript frameworks could look like. When I signed on to join the Marko team back in March 2020 (I know, perfect timing to relocate for work) something was very clear to me. In my heart this was the article I was going to write even before I read quintessential Svelte for Sites, React for Apps. I've been sitting on writing this article for 2 years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |