7 ms·

>Problem was, MS was churning out the "next great thing" >faster than I could learn the last great thing. Same here. I design databases, and MS kept bringing n

>Problem was, MS was churning out the "next great thing" >faster than I could learn the last great thing. Same here. I design databases, and MS kept bringing new data access methods every three years; I never could wrap my head around the ADO/DAO difference, but that did not matter for long because both were replaced by .Net I sincerely wondered if this was not a deliberate tactic by Microsoft : while developpers are busy learning their newest "next great thing", they can't invest time in anything else. Meanwhile I learned how to use an OSS lamp stack and have been happily using it for the last 10 years. Very stable and reliable, I could not be happier.

xradionut 13y ago
"I sincerely wondered if this was not a deliberate tactic by Microsoft : while developers are busy learning their newest "next great thing", they can't invest time in anything else." Bingo!
- im3w1l 13y ago
  On what grounds do you confirm his speculation?
  - xradionut 13y ago
    Occam's razor. Either Microsoft is incompetent or promoting/retirement of APIs is more profitable.
    - im3w1l 13y ago
      A, in my opinion, simpler explanation is that they change their product to try to make it better.
      - petit_robert 13y ago
        >A, in my opinion mmmh... I thought about this too. However, MS is anything but stupid marketing wise, I find. So I dismissed incompetence.
EdwardDiego 13y ago
> Meanwhile I learned how to use an OSS lamp stack and have been happily using it for the last 10 years. Very stable and reliable, I could not be happier. I find that Java's biggest problem (stability/stagnation depending on who you ask) is also the JVM development ecosystem's benefit. There's not one body driving adoption of technologies by deciding what's supported and what's not, so technology choice is less dictated by economic imperatives.
- petit_robert 13y ago
  Not sure what you mean exactly, but in any case I know nothing about Java; my LAMP stack is : Linux, Apache, Mod_perl, Postgresql All very pleasant to work with (1) and stable; mod_perl has a rather steep learning curve, but worth it for web work. Very powerful _and_ low cost. ( 1 : if you like Perl, obviously ) [Edit] asterik in note caused weird formatting; replaced with 1

xradionut 13y ago

"I sincerely wondered if this was not a deliberate tactic by Microsoft : while developers are busy learning their newest "next great thing", they can't invest time in anything else." Bingo!

im3w1l 13y ago
On what grounds do you confirm his speculation?
- xradionut 13y ago
  Occam's razor. Either Microsoft is incompetent or promoting/retirement of APIs is more profitable.
  - im3w1l 13y ago
    A, in my opinion, simpler explanation is that they change their product to try to make it better.
    - petit_robert 13y ago
      >A, in my opinion mmmh... I thought about this too. However, MS is anything but stupid marketing wise, I find. So I dismissed incompetence.

EdwardDiego 13y ago

> Meanwhile I learned how to use an OSS lamp stack and have been happily using it for the last 10 years. Very stable and reliable, I could not be happier. I find that Java's biggest problem (stability/stagnation depending on who you ask) is also the JVM development ecosystem's benefit. There's not one body driving adoption of technologies by deciding what's supported and what's not, so technology choice is less dictated by economic imperatives.

petit_robert 13y ago
Not sure what you mean exactly, but in any case I know nothing about Java; my LAMP stack is : Linux, Apache, Mod_perl, Postgresql All very pleasant to work with (1) and stable; mod_perl has a rather steep learning curve, but worth it for web work. Very powerful _and_ low cost. ( 1 : if you like Perl, obviously ) [Edit] asterik in note caused weird formatting; replaced with 1