React-Native's error messages are getting ridiculous.

Apparently I have to do yoga otherwise it won't compile.

Good Fitness is essential to programming.

You know what doesn’t force you to do yoga? ... native development

@practiseSafeHex That error looks familiar. It comes when I don't wrap a component in a <View/>

@leksyib it comes when you don't write it in Swift in Xcode

Lol. I just feel Building cross platform apps is easier than building for IOS with swift and learning java to build for android.

@practiseSafeHex

@leksyib

*looks at the above picture*

... yeah I can see why.

*Disclaimer spent 2,5 years building apps with hybrid tools. Not enough money in the world to make me go back. Its complete horseshit compared to native

@practiseSafeHex lol

@practiseSafeHex Ionic made you into a bitter person?

@saintograph nope, appcelerators titanium not being able to open a map with a pin on Android 4.1 on a HTC one S

... why so specific? because thats the phone the CEO had at the time and NOTHING I could do would make it work.

Even gave him an app with only a map, a static pin and nothing else and it still crashed.

All of these tools suffer from the same shit, at some point there will be a bug in their implementation of the native code that will fuck you in the ass.

... or you can build native where you have the biggest communities of devs to help, not restricted in the methods / the UI you use and can build an app the way god intended

@practiseSafeHex My story involves a client who heard about Facebook's open-source baby and paid me to build a video editor with it.

Needless to say, I had to write native plugins to speed up hardware processing and ended up with a bloated mess.

I only received up front payment for that job. I'm staying away from hybrid for anything that goes into production.

That error in my attached image is from a news reader I'm building for a non-profit. Hybrid should work just fine for that purpose.