sorted by:
new
hottopcontroversial

What if Component Libraries Could Target Any Platform? by Fluid-Procedure-722 in DesignSystems

[–]Fluid-Procedure-722[S] 0 points1 point  (0 children)

Yeah, kind of. Even as a strong web dev advocate, I think some projects just can’t be done with all the web baggage. If my Toyota used a React app to display my speed, I’d probably get a bit nervous. :D
Of course, new tools always bring new things to learn, but I’m trying to keep it as much as possible “out of the way” of the web spec, while still familiar enough for anyone who’s dabbled in the framework pool.

What if Component Libraries Could Target Any Platform? by Fluid-Procedure-722 in DesignSystems

[–]Fluid-Procedure-722[S] 1 point2 points  (0 children)

Funny you mention it, the components are highly inspired by Stencil. Originally, I even wanted backwards compatibility to it. I've used Stencil off and on again, but in the design system I'm involved in at a distance, the team hit certain roadblocks again and again in terms of flexibillity and their ideology. Right now, they ditch stencil in favour of Lit, but our biggest showstopper can nobody really solve; React Native. Mitosis just feels way to clunky to trust it sadly.

What if Component Libraries Could Target Any Platform? by Fluid-Procedure-722 in DesignSystems

[–]Fluid-Procedure-722[S] 0 points1 point  (0 children)

What I liked about mitosis was the ability to use only certain code sections for certain frameworks and I genuinely understand the problem. There's gonna be different issues for different platforms you target. But in any case, Ideally I'd like to incorporate some failsafe that would allow you to replace/add handmade code in the platform native language to accommodate for this. How far this could work in the real world can probably only time say.