I have been giving React Native a go over the past month and at first it was pretty exciting and challenging (coming from a more backend .NET development background) but as I started to encountered the multitude of issues from waking up one morning and finding the build that worked last night no longer works and some obscure hack job was required in a node package (really WTF).
All was well until React Navigation decided to break today and this pretty much made me give up on doing anything substantial on React Native for the time being. Due to my experiences I decided to look into the problems further and I am alarmed at how many issues exist and usually are resolved by the 100th poster going "oh yeah you need to add this line in this obscure place" - that rings alarm bells for me sorry.
But this seems to be a common occurrence with these front end libraries - they are great for a while but as you start add other packages things break or you update your node packages and something was updated somewhere in the 50k packages that is causing the issue.
What I keep asking but no one is answering is: how the **** are these issues happening? They shouldn't be and in a production development team this shit can kill productivity dead in the water (and leave people a little burned).
Don't get me wrong when things were moving along it was a great workflow I was getting through my tasks but today has been a total whitewash and to add insult to injury I think I have no choice but to wipe my dev machine completely because pulling previous "working" commits are also broken (how is that even possible).
Sure I could dig into all of it, find the root cause and fix the problem but why the hell should I be doing this?
Novelty has worn off for me - sure was fun firing up console windows feeling like I was on Linux again and I can see the value from an automation perspective but when you have 1000 moving parts and something goes wrong its very very painful.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have been giving React Native a go over the past month and at first it was pretty exciting and challenging (coming from a more backend .NET development background) but as I started to encountered the multitude of issues from waking up one morning and finding the build that worked last night no longer works and some obscure hack job was required in a node package (really WTF).
All was well until React Navigation decided to break today and this pretty much made me give up on doing anything substantial on React Native for the time being. Due to my experiences I decided to look into the problems further and I am alarmed at how many issues exist and usually are resolved by the 100th poster going "oh yeah you need to add this line in this obscure place" - that rings alarm bells for me sorry.
But this seems to be a common occurrence with these front end libraries - they are great for a while but as you start add other packages things break or you update your node packages and something was updated somewhere in the 50k packages that is causing the issue.
What I keep asking but no one is answering is: how the **** are these issues happening? They shouldn't be and in a production development team this shit can kill productivity dead in the water (and leave people a little burned).
Don't get me wrong when things were moving along it was a great workflow I was getting through my tasks but today has been a total whitewash and to add insult to injury I think I have no choice but to wipe my dev machine completely because pulling previous "working" commits are also broken (how is that even possible).
Sure I could dig into all of it, find the root cause and fix the problem but why the hell should I be doing this?
Novelty has worn off for me - sure was fun firing up console windows feeling like I was on Linux again and I can see the value from an automation perspective but when you have 1000 moving parts and something goes wrong its very very painful.