eBay was founded with the core belief that we should use technology to empower and connect people globally. In the technology world, we’re a core contributor to and believer in open source technology. Not only does a company culture of open source help us empower our developers, but it also enables our technologists to collaborate both across the organization and with peers throughout the industry.
A key pillar of eBay’s participation in the open source software community is our most popular open source project, Marko. Initially developed by eBay in 2012 to…
The Marko Team has been working on a new rendering engine which is slated to become the core engine for Marko in a similar way Fiber(React), Glimmer(Ember), and Ivy(Angular) have been for their respective libraries. Today I want to give you a first peek into what this is going to look like.
A lot has changed since the release of Marko 4 in 2017. Most of the effort has been managing migrations, and updating tooling (ie.. the move to Babel, Webpack, Rollup). Marko 5 is in alpha and represents the modernization of the toolchain. But what about the architectural considerations?
Two years later I still find myself explaining how Solid has carved out its unique niche in an overcrowded space. After reading Swyx’s Svelte for Sites, React for Apps which again poses the dichotomy for Sites and Apps, I have another take.
The Intel Core Micro-Architecture was not originally designed to be the powerhouse it is today in server and desktop machines. It was for mobile chips.
I have a process. I apply this to almost any sort of problem I face.
Step 1. Define the problem
This for me often takes the longest. It is absolutely critical to understand what you are trying to solve, who stakeholders are, and what's actually important.
Step 2. Propose an idealized solution no matter the cost
No.. “but”s just pure and simple how this should work if everything could go your way.
Step 3. Throw it all away and reframe the original question
I find this absolutely necessary to exhaust the prescribed train of thought so that I break apart…
It’s taken quite a while for me to write my first article of 2020. And in that vein, I wanted to reflect a bit on what has changed over the past 10 years and how that influenced Solid’s design. I’ve always stated that Solid is simply built on the work that has happened in the past (much of…
I’ve recently read a few articles making some pretty outrageous claims, based on little more than anecdotal references to a few conference talks. Part of it is the time of year. As we move from one year to the next it is a good time to look forward to the future. And I don’t even think all the sentiment is misplaced, just that the evidence and justifications are lacking. We might get there one day but that day is not today.
So let’s dig into a few ones that have been floating around the past year.
Web Components are a…
Suspense and Concurrent Mode are being touted as the future of web development by many. This set of features being developed by React is poised to revolutionize how web applications are designed. But these are complicated topics and while Dan Abramov’s series of tweets have helped to promote understanding of React’s intention with these features, I still…
JSX may not be the most obvious choice for templating in a Reactive UI library, but it definitely brings something to the table that should not be overlooked. It allows increased flexibility, better tooling, and unmatched performance. I consider JSX to be a big part of what makes Solid the fastest reactive library out there. …
FrontEnd JS Performance Enthusiast and Long Time Super Fan of Fine Grained Reactive Programming. Member of Marko Core Team. Author of SolidJS UI Library.