It seems some lessons learned in the past have been simply forgotten. After several companies crashed in the 80´th being not able to handle the complexity of their products, software development was all about reducing complexity. One of the targets was to build platforms, where distributed teams where able to work together, even if they used different programming languages.
When people started to write code for their websites, some lines of code often have been enough. Javascript started as a scripting language and was initially not meant to be a full featured programming environment. I suppose, the same is true for PHP. So, tools we are using today are not comparable to the tools we had before. Things are still a bit hacky and full of compromise to be backwards compatible.
If you start to use something completely new and different, you will see, that nobody cares for it. They all are so used to do things the way they are used to, that you will hardly find any good response, even if you build something that could radically change the world. There are so many people that still think, HTML is a programming language. No way to change their minds.
It's indeed interesting how something PHP evolved over time... I was baffled when they dropped goto in there (and given the XKCD on the documentation page I think so was everyone else...). Begs the question: why do we need all that? What's next? OOP in bash?
I do think new environments have the potential to be adopted (e.g. Go, Rust) but they're still quite close to what we're used to. I vividly remember a UX discussion on hamburger menu where the UX designer said: we can't move away from it too far or people won't get it, it'll need to evolve over time... I guess the same holds true for coding.
Still would like to know what the ideal environment is tho... there are a whole bunch of good things to be found in any language/environment that we should definitely keep around but how do we distil all that to its essence and make something new out of that?
yeah we can't sit still can we? as an engineer we can always see ways to improve it further... and as a PO we always want another feature... the fluidity is very much self-imposed 😃
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It seems some lessons learned in the past have been simply forgotten. After several companies crashed in the 80´th being not able to handle the complexity of their products, software development was all about reducing complexity. One of the targets was to build platforms, where distributed teams where able to work together, even if they used different programming languages.
When people started to write code for their websites, some lines of code often have been enough. Javascript started as a scripting language and was initially not meant to be a full featured programming environment. I suppose, the same is true for PHP. So, tools we are using today are not comparable to the tools we had before. Things are still a bit hacky and full of compromise to be backwards compatible.
If you start to use something completely new and different, you will see, that nobody cares for it. They all are so used to do things the way they are used to, that you will hardly find any good response, even if you build something that could radically change the world. There are so many people that still think, HTML is a programming language. No way to change their minds.
It's indeed interesting how something PHP evolved over time... I was baffled when they dropped goto in there (and given the XKCD on the documentation page I think so was everyone else...). Begs the question: why do we need all that? What's next? OOP in bash?
I do think new environments have the potential to be adopted (e.g. Go, Rust) but they're still quite close to what we're used to. I vividly remember a UX discussion on hamburger menu where the UX designer said: we can't move away from it too far or people won't get it, it'll need to evolve over time... I guess the same holds true for coding.
Still would like to know what the ideal environment is tho... there are a whole bunch of good things to be found in any language/environment that we should definitely keep around but how do we distil all that to its essence and make something new out of that?
Maybe things would simply take more time to grow...
yeah we can't sit still can we? as an engineer we can always see ways to improve it further... and as a PO we always want another feature... the fluidity is very much self-imposed 😃