81–90 of 107 posts
Does this mean we will be able to use Ionic components with React or Vue in the not too distant future?
> Stencil components are rendered using JSX... What's the point? Why not just use React? Like many others - I dropped Cordova and Ionic in favor of React-Native. So, what is Ionic trying to do here? Are they throwing in the towel and adopting React? Will they end up making a kit that renders native components using JSX just like React-Native?
Hey all, founder of Ionic (team behind Stencil) here. Didn't expect to see this up on HN so soon (released this morning), thanks for understanding there's still rough edges with docs, etc We built Stencil for a selfish reason: we needed more mobile web performance for Ionic apps being deployed as PWAs (in addition to App Store apps) and we were struggling getting that with traditional framework component/bundle appro…
What kind of events are stencil events? In order to respond to an emitted stencil event, do I have to use the stencil listener, or can I use addEventListener?
" Stencil is a new approach to a popular idea: building fast and feature-rich apps in the browser. Taking advantage of new capabilities in the browser, such as Custom Elements V1, Stencil enables developers to write faster and lighter components without the weight of frameworks. The tooling also a solution to teams and library authors building components that support many frameworks. Stencil components work in Angula…
> Stencil components are rendered using JSX... What's the point? Why not just use React? Like many others - I dropped Cordova and Ionic in favor of React-Native. So, what is Ionic trying to do here? Are they throwing in the towel and adopting React? Will they end up making a kit that renders native components using JSX just like React-Native?
> Like many others - I dropped Cordova and Ionic in favor of React-Native. Few years ago PhoneGap apps were really slow and ugly. So I built native Android app. This year I started building hybrid Ionic 3 app because it has to work on Android and iOS. It works good enough on Nexus 5 (Snapdragon 800). The biggest problem is 4-5 seconds startup time. Stencil and component lazy loading should greatly reduce that startup…
Earlier quoted context omitted.
Yes right this second, but next on our list is providing a seamless solution to dependency dedupe. Not yet ready but it's promising.
Okay, that is definitely needed if we want to build serious components. Else it's gonna go crazy heavy!
Here's a new library to solve a problem you don't have yet.
WebComponents in general are a solution in search of a problem. Despite being 6 years in development: - they basically delivered none of the original promises - they are extremely cumbersome to use without a library/framework on top (Polymer is the jQuery of WebComponents) - they are plagued by multiple problems and shifts in the ecosystem (browsers don't want to support `is=`, HTML imports are being dropped in favou…
To me, it doesn't seem like too big of a stretch to think that the popular frameworks of today will move to the custom element spec instead of their own proprietary component model.
Earlier quoted context omitted.
Adding a "Yes, but..." Microsoft's refusal, or inability, to release a version of Edge (or even a port of an earlier IE) for macOS exacerbates this situation. I virtualize Windows on my MacBook for IE/Edge testing of my designs and code, but it requires a workflow and context shifting that I'd perfer I didn't have to do. Edit: s/I.E./IE
Ironically we have the exact same problem, except worse with Safari, since it has (relatively) poor support for some cutting edge APIs, and unlike Edge/IE we can't even legally test it in a VM because Apple doesn't even allow their OS to be put in a virtual machine. At least Microsoft has the good grace to put up free VMs for browser testing - https://developer.microsoft.com/en-us/microsoft-edge/tools/v...