71–80 of 107 posts
content won't show for me (latest firefox beta, 56b05) : Failed to register/update a ServiceWorker for scope ‘https://stenciljs.com/docs/’: Bad Content-Type of ‘text/html’ received for script ‘https://stenciljs.com/docs/sw.js’. Must be ‘text/javascript’, ‘application/x-javascript’, or ‘application/javascript’. Error DOMException [SecurityError: "The operation is insecure." code: 18 nsresult: 0x80530012] intro:19:41
> 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?
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 time (to 1-2 seconds I hope).
> 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.
Sure looks terrible on Edge, Chrome, and Firefox on Windows 10. Gray on gray makes for terrible contrast.
Hello all! We just deployed a new version of the site that should solve some of these problems, thanks for the feedback.
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…
Earlier quoted context omitted.
basically Chrome (I just saved you a click)
...and Safari? Which is actually a pretty popular browser (with good reason).
Safari 10.0 = 0.64%
Safari 8.0 = 0.33%
Safari 9.1 = 0.27%
===================
Total = 3.88%
For July 2017 according to NetMarketshare.
I wouldn't call a 3.88% install base "pretty popular". It's also offers a terrible developer experience
cf: https://www.netmarketshare.com/browser-market-share.aspx?qpr...
Earlier quoted context omitted.
> WebComponents in general are a solution in search of a problem Maybe they don't solve your problem, but they certainly seem to solve Ionic's or Netflix's problems (or mine for that matter).
"React seems to solve Facebook's problems (or mine for that matter)" "Vue.js seems to solve Gitlab's problems (or mine for that matter)" etc. Throwing big names around amounts to pretty much nothing.