Avoid jobs that require you to be an expert at a particular framework in the door.
Ask HN: Is Rails really dying?
21–24 of 24 posts
Re: Ask HN: Is Rails really dying?
#22Earlier quoted context omitted.
I'm curious why you recommend dart? I definitely wouldn't put that on my list, but everything else seems pretty on point.
Dart is kind of speculative -- but it has the backing to be a big thing in a few years. And since it's the "anti-javascript" I think it adds more to a developers versatility than learning 5 javascript frameworks. Our dev teams that have adopted it like it, and it's been very successful for them.
Re: Ask HN: Is Rails really dying?
#23Earlier quoted context omitted.
I'm curious why you recommend dart? I definitely wouldn't put that on my list, but everything else seems pretty on point.
Dart is kind of speculative -- but it has the backing to be a big thing in a few years. And since it's the "anti-javascript" I think it adds more to a developers versatility than learning 5 javascript frameworks. Our dev teams that have adopted it like it, and it's been very successful for them.
Dart's very similar to JavaScript in a lot of ways, especially most of the syntax. The main difference is that programs have a static shape, which makes tooling and reading a codebase much, much easier.
Re: Ask HN: Is Rails really dying?
#24Earlier quoted context omitted.
Dart is kind of speculative -- but it has the backing to be a big thing in a few years. And since it's the "anti-javascript" I think it adds more to a developers versatility than learning 5 javascript frameworks. Our dev teams that have adopted it like it, and it's been very successful for them.
Yeah but they just announced the removal of the VM from chrome and making it compile into JS, right? Did that change your opinion at all?