It's a mentality issue, modern programming languages provide the material necessary to create innovative environments but their communities just simply does not care. A language designer may introduce a feature in a language that is super useful. Still people may not use it.
And let's face it even with Pharo nothing beats a personalized environment, of course personalisation is a lot of work. Hence why people avoid it. Essentially boiling down to cooking your own food instead of getting it from a shop. When you begin to learn how to cook , its kinda sucks, but the more you cook the better it tastes. Of course it takes time to get there and hence why so few people cook. Eclispe , which I will disagree with your that is not the worst IDE, started as a smalltalk IDE and then it got Eclipsed. I am sure those people had a "build on" environment , still it got messy. We can blame porting to Java, but can we really blame Java for the mess that is called "Eclipse".... ehhhh.... nope. I once saw a youtube video about a musician using windows sounds (the standard sounds we all know of) to make a very nice music piece. He did all that using multiple instances of windows media player. Just pause reading think about this for a minute. That's the real essence of creativity Use something very limited and come up with something amazing. The software industry is not about creativity for the most part. On the other hand I that work with 3d its amazing how fast super cool new technologies pop around like mushrooms. Every year we have massive improvements in libraries and tools. But the coding for 3d graphics is all about creativity , artists are not very forgiving for ugly GUI, limited features and innovation stagnation. Artists want to be inspired by the tools they use. But then that's the creativity realm. Creativity pays the bills in this case, lack of it , game is not fun, rendering or animation is not fun, you can lose millions. Of course in the creativity realm , there is too much innovation and unless you keep up you are kicked out the door, yesterday. Which brings down to the problem of complexity and how you deal with it. And I don't mean about bad complexity , aka web dev, I am talking about good complexity. Features you cannot ignore because other will use before you and you are left behind etc. On Thu, Oct 12, 2017 at 7:13 PM Peter Fisk <peter.f...@gmail.com> wrote: > Thanks for posting this. > > It is one of the best descriptions of the state of the software industry > that I have seen. > > > On Thu, Oct 12, 2017 at 11:50 AM, Andrew Glynn <aglyn...@gmail.com> wrote: > >> https://medium.com/@dasein42/building-with-versus-building-on-c51aa3034c71 >> >> >> This is an article not *specifically* about Pharo, rather on the state of >> the industry >> in general and how it got that way, but positing Pharo as a way to learn >> building-*on* rather than building-*with*, where in the latter case on >> every project you start at essentially the same place. >> >> >> As a result it does put in front of people a fair amount of info on >> Pharo, and challenges them to try it. >> >> >> cheers >> >> Andrew Glynn >> >> >
