- Can you unpack your first bullet point a tad more? Are you saying that because these shops use other technologies (like say, Python, C++, etc...), they will b

- Can you unpack your first bullet point a tad more? Are you saying that because these shops use other technologies (like say, Python, C++, etc...), they will be fine? But this still doesn't refute my point about Drupal in-and-of-itself. Actually, it might even buffer my point, if I understand it correctly. - But isn't this what so many Drupal developers do as well as Drupal shops (especially small to medium sized shops)? And, again, this point might even buffer my point about Drupal along not being advantageous. Plus, I don't think the Drupal community in general thinks this way (they are even cultish about Drupal actually) - True, as of now. This is where Drupal devs will still have work to do. But that sucks professionally speaking - who wants to just do that? How will that kind of work help you develop as a good programmer? But, all of that is not really relevant to my post anyway - I'm more focused on things ahead - far ahead - the future of jobs. In 5 years? 10 years? These jobs will be gone. - Ok. - See my 3rd bullet point response above. - Sure, but the future of Drupal actively works against that. My point is not that all of this is ending tomorrow, but it time Drupal's philosophy (get as much into core as possible) will eventually hurt programmers and their jobs (for those who stick with just Drupal). - I define a "good middle class" job as the following: long-term job security, real opportunities for growth in the company, good pay, healthcare benefits (including dental) and retirement benefits (like 401ks) etc. There are a lot of small to mid-sized Drupal shops who can't come close to this kind of job offer. They always seem stuck in virtual start-up mode. So, serious Drupal devs are forced to work for one of the big Drupal shops (and those kinds of shops are few and far between)