On Thu, Dec 15, 2016 at 12:38 AM, Dimitris Chloupis <kilon.al...@gmail.com> wrote:
> > On Wed, Dec 14, 2016 at 5:35 PM Offray Vladimir Luna Cárdenas < > offray.l...@mutabit.com> wrote: > >> This is a good example of the "empowering map" I talk about about >> "Pharo/Smalltalk places for you". What we can look forward in 2017 is >> different for different people, so going beyond the "most exiting >> developments", hype and shiny new things is also a way to show how >> Pharo/Smalltalk are different. We can provide shine and hype, but also >> we're building stuff for different interests and people and that is even >> more worthy to look for the upcoming times (2017 and beyond). >> >> Cheers, >> >> Offray >> > > I think there is big difference between doing something exciting versus > doing something useful. Excitement dies out but usefulness does not. I > don't do it to make Pharo look cool, I do it because I need it. I also do > not like to do something and then abandon it like it happens for 99% of the > open source software. > > Also maintenance becomes a big issue if the scope is wide. Of course you > can also combine excitement with usefulness and still keep the scope > reasonably achievable. > > A thing I love about Pharo is because its so limited third party library > wise it forces me to go do that stuff myself and this definitely builds > confidence in one's coding skills. I really like this DYI approach and I am > definitely moving to the opposite direction of "do not reinvent the wheel". > This would have been unthinkable in communities of very popular languages. > I really like that Pharo forces me to be much less lazy as a coder. > Because reinventing the wheel is a good way to learn about wheels... cheers -ben > > Its also impressive to see the things that other people do by themselves > too and be inspired by it. > > The real problem is that this work is not really visible, I think Pharo > needs something like a magazine and people should be encouraged to share > their work even if it is in early stage because you never know who will > find it useful. I feel the things we see in the mailing list is only the > tip of the iceberg of what people work on and is pity all this code to be > lost in obscurity. >
