News for hackers. Stuff that matters.

A comment on Ionic React. Parent comment

Re:Ionic React by xtracto on Tuesday October 15, 2019 @03:24PM (#21262599)
My main problem with Ionic (having used it for several apps) is that it is very difficult to find answers to question on the web. Reference sites are full of "this is how I fixed it" that work on v1 or v2 or v3 and most of all don't work for v4.

Unfortunately the speed in which they are changing things make community references obsolete quickly.

[ Parent | on HN ]
Re:Ionic React by yesimahuman on Tuesday October 15, 2019 @05:08PM (#21263790)
We hear you. This is why we moved to embracing core framework tooling like in Ionic 4 with Angular, where you don't need to go through our custom Angular build tooling which was a big source of issues and made it hard to get help.
[ Parent | on HN ]
Re:Ionic React by chiefalchemist on Tuesday October 15, 2019 @09:46PM (#21266237)
I found Laravel to be similar. Lots of answers but none for the current version.
[ Parent | on HN ]
Re:Ionic React by tazard on Wednesday October 16, 2019 @12:10AM (#21266969)
Interesting, although true none for the current version, in my case a working solution has nearly always been in the top few results, even if it's originally from an older version
[ Parent | on HN ]
Re:Ionic React by wolco on Wednesday October 16, 2019 @01:13AM (#21267259)
Older solutions still work on laravel for the most part. There are newer cleaner ways to do things but very few breaking changes.
[ Parent | on HN ]