@draft13 In my opinion, as a long-time #smalltalk programmer and fan, it's still one of the most productive environments. #pharo continues to innovate, and #GlamorousToolkit pushes the envelope even further.
Learning any new programming language is a chance to see things differently. Learn Smalltalk and you may never look back.
Note to my future self, never try to read #pharo#spec documentation, it seems to be forever targeting a version behind whatever I'm running. Always check the demos instead.
#Pharo#smalltalk geeks. I've seen a few things lately which refer to "pharo language"
Have the Pharo people actually changed / added to the Smalltalk language, or are people just conflating the pharo environment with the language that powers it?
I would love to start developing for smartphones, creating a proper #emacs client totally reimagined for the smartphone is long overdue and a project I could really sink my teeth into. You know the popup keyboard on your phone? You think Steve Jobs invented that? No he didnt, Richard Stallman did, it's called a minibuffer. Emacs was doing all this stuff in the 80s, and way better, even.
But I can't help but hate all the frameworks surrounding mobile development, ie React Native, Swift, Flutter etc, but also from my experience as a user, the apps I've tried that were made with alternative #fp frameworks like #LambdaNative, which had to downsample and skew the resolution to fit my phone's screen, so it didn't seem to even feature responsive design; maybe ok for the hospital software they designed it for but not something for creating applications that the people will use out of their own volition.
I'm pessimistic that "there is no alternative" but seeing how nicely #FDroid is coming along, I'm hoping that I may be wrong. Is there anything promising out there in the #mobile#gui#foss space?
@acousticmirror@daviwil I do think #MaxMSP really takes the visual aspect to another level though. being able to develop custom interface components using the tools offered by the programming enviroment itself, not to mention with all the low and high level tools offered by #jitter and gen, and the ability for it to instantly snap together to create a proper front end using presentation-mode, is totally game changer. its worth noting most of Max's interface was written in Max, and everything can be hacked apart live like with smalltalk. the talks I used to give with the presentation systems I would create for each talk were some of the coolest things I've ever done, and I don't have that power any more, or know where I could find it except perhaps #squeak and #pharo.
I still think if you implemented something like #Smalltalk with the code browser, debugger and all of that using modern UI, which could allow you to package a project into a native looking app, you would really be onto something.
I also think you would probably be better off having it use #Ruby or #Python. I’m honestly not sure how to even start doing some thing like that in a way which wouldn’t take years, but if I did I might try.
@collin If you're running Windows, Dolphin Smalltalk allows you to package your #smalltalk application as a stand-alone executable. I haven't tried it yet, but I believe a package like Cruiser lets you create native Linux or Windows executables using #pharo.
If you want a Ruby-like experience that compiles to an executable on Linux or Windows, have you looked at Crystal? (https://crystal-lang.org/). I haven't taken it for a test-drive in a while, but it's very interesting.
I’ve wanted to get into #Smalltalk for many years, but every time I try I bounce off of the whole Morphic thing.
I really want to be able to develop my GUI project in a more “traditional” way like classic Smalltalk appears to have had and this just doesn’t seem like an improvement and not some thing I have any interest investing in.
@collin I think they might have considered it a failure if it is true that users didn't get into modifying the software they were running. Devs not getting it might not have bothered them as much.
@rahoulb well, you tried 👍🏼
Taking the liberty of including @drgeo , who was bringing his software to #Smalltalk (tried #Pharo, switched to #CuisSmall). i.e. knows a thing or two about developing in Smalltalk.
@collin I think they might have considered it a failure if it is true that users didn't get into modifying the software they were running. Devs not getting it might not have bothered them as much.
@rahoulb well, you tried 👍🏼
Taking the liberty of including @drgeo , who was bringing his software to #Smalltalk (tried #Pharo, switched to #CuisSmalltalk). i.e. knows a thing or two about developing in Smalltalk.