I think it really takes truck-loads of courage in going back, taking that massive salary-cut. But if one's a family-oriented person, then it makes sense.
Thanks for sharing your experience! A couple of questions:
1. What was the reason for leaving US? I'm guessing you must be on EB1/EB2 track to the Green Card?
2. How was the process like for the Canadian PR? Had you already secured a job in Canada before leaving US and then applied for the PR from India (Express-entry program)?
1. I had the urge and wanted to experience how life in India would be. I applied for Canadian PR as a back up. Also, i have i-140 so i can go back to US.
2. I am in canada just to try it out and see how it goes. I did not have a job but got a job immediately. For process go online. If you are a software engineer you will get a job.
I don't endlessly do pro and cons. I just try things out.
“For all of the most important things, the timing always sucks. Waiting for a good time to quit your job? The stars will never align and the traffic lights of life will never all be green at the same time. The universe doesn't conspire against you, but it doesn't go out of its way to line up the pins either. Conditions are never perfect. "Someday" is a disease that will take your dreams to the grave with you. Pro and con lists are just as bad. If it's important to you and you want to do it "eventually," just do it and correct course along the way.”
― Timothy Ferriss, The 4-Hour Workweek
Is it popular to hate on JS these days? Kudos to the author for creating the stuff but would you build the next Amazon.com avoiding JS? More often than not, I see Backend developers taking pride on not using JS rather than vice versa. Also, FB and GOOG aren't naive to spend enormous capital and manpower on React and Angular projects.
Probably will get downvoted but just because someone writes pure C does not make him/her a better developer than someone who just writes Javascript.
I'm still trying to grasp why these discussions so quickly spin into extremes. The author clearly states her intent in the first paragraph:
> With the new version I wanted to prove that it was possible to deliver an amazing user experience with a great design while drastically reducing the complexity of the code, maximizing reliability, and minimizing the cost to the end user.
She goes on to show us what she did, where it worked and where it didn't. The most important points I take away from her article are:
1. It's quite possible to build nice-feeling (YMMV), non-single-page web-apps without (a ton of) JavaScript
2. Critically evaluate if you need the complexity that an enormous JS framework brings
> You probably don't need a "Progressive Web App." Seriously evaluate if your app needs such complexity.
This has nothing to do with FAANG. Nobody disputes that there are use cases where it's a really good idea to use React+Redux+Jest+Enzyme+XYZ et al. But _maybe_ (and in my personal experience, in projects significantly smaller than Amazon.com, often) you simply do not need that amount of additional complexity and challenges.
It'd be so nice to just accept that the author provides an interesting data point (it can work without JS) in a community strongly biased towards starting projects by importing ~1000 node modules.
It is somewhat popular to hate on useless dung heaps of pointless Javascript, not because it's Javascript (writing complex code in a mediocre language with mediocre libraries is a separate concern), nor because backend developers have good reasons to do things in the backend, but because it's overcomplicated and so bloated that it causes performance problems, just like nested table layouts a few years ago.
