4 ms·

Right, you ever track all the changes in Php or Java? The idea that something being open source means that there aren't changes is just nonsense. Change happen

Right, you ever track all the changes in Php or Java? The idea that something being open source means that there aren't changes is just nonsense. Change happens. It's life. I guess you just pick your poison.

mercurial 13y ago
Forget about PHP. Java's development pace has been glacial the last few years (though Oracle seems determined to do something about it), but when introducing new features, it's rare that backward compatibility breaks (even when it would be desirable).
deleted 13y ago
[deleted]
eropple 13y ago
Explain to me exactly when the core Java stack has massively deprecated something as core as database access in favor of a marginally-redesigned but API-incompatible New Hotness. Thanks.
roel_v 13y ago
"Change happens. It's life. I guess you just pick your poison." What? No, it doesn't have to, or at least not at the pace of once a year. It's not because everybody else does it, it's OK all of a sudden. I like php exactly because it's relatively stable (I'm not talking about the frameworks here, let's not go there). But fuck all those others - that wasn't my point. The win platform could have been so much better for pragmatic developers who just want their foundation to be stable to just get shit done. Why abandon C++ in the way they did? Why the 4-5 different paradigms for UI development? Not incremental changes, or libraries, but completely incompatible new ways of doing things, and if you don't follow the trend, you'll be left out. If the dev tools group had known their place, they would have served developers as customers, instead of the situation we have now. Of course the vocal minority of chase-the-next-thing developers brought this on us as well, it's similar to the 'disregard everything from the past and reinvent everything because I'm so much much than everybody else' often displayed on sites like here and reddit programming - 6 years ago Python was the hot thing, 4 years ago Rails, 2 years ago Node and I'm not even sure what it is now. Anyway, my point is that it's innate in inexperienced software people to want to dive into tech for the sake of it and forgetting the business case behind it. And that is what holds back the industry as a whole, reinventing and re-implementing everything every few years under the guise of 'innovation' or 'we'll do it right this time', but it's really just NIHS. And that goes for the Windows ecosystem, the OS ecosystem, others as well I guess but I don't know them well enough, or they're not old enough yet for this pattern to unfold).

mercurial 13y ago

Forget about PHP. Java's development pace has been glacial the last few years (though Oracle seems determined to do something about it), but when introducing new features, it's rare that backward compatibility breaks (even when it would be desirable).

deleted 13y ago

[deleted]

eropple 13y ago

Explain to me exactly when the core Java stack has massively deprecated something as core as database access in favor of a marginally-redesigned but API-incompatible New Hotness. Thanks.

roel_v 13y ago

"Change happens. It's life. I guess you just pick your poison." What? No, it doesn't have to, or at least not at the pace of once a year. It's not because everybody else does it, it's OK all of a sudden. I like php exactly because it's relatively stable (I'm not talking about the frameworks here, let's not go there). But fuck all those others - that wasn't my point. The win platform could have been so much better for pragmatic developers who just want their foundation to be stable to just get shit done. Why abandon C++ in the way they did? Why the 4-5 different paradigms for UI development? Not incremental changes, or libraries, but completely incompatible new ways of doing things, and if you don't follow the trend, you'll be left out. If the dev tools group had known their place, they would have served developers as customers, instead of the situation we have now. Of course the vocal minority of chase-the-next-thing developers brought this on us as well, it's similar to the 'disregard everything from the past and reinvent everything because I'm so much much than everybody else' often displayed on sites like here and reddit programming - 6 years ago Python was the hot thing, 4 years ago Rails, 2 years ago Node and I'm not even sure what it is now. Anyway, my point is that it's innate in inexperienced software people to want to dive into tech for the sake of it and forgetting the business case behind it. And that is what holds back the industry as a whole, reinventing and re-implementing everything every few years under the guise of 'innovation' or 'we'll do it right this time', but it's really just NIHS. And that goes for the Windows ecosystem, the OS ecosystem, others as well I guess but I don't know them well enough, or they're not old enough yet for this pattern to unfold).