(Belated) âHi, Folksâ To stress the point: All of the 20-30 in-house apps I would have preferred to develop using Pharo(Squeak before that) were done in something that didnât lack one of the following enablers (if we skip diacritics/fonts/locales): · Drag & Drop (from the outside world) · taskbar/status icons · support for being launched as [Windows] Service · COM They might seem like small / moot points, but each and single one of them can be a show-stopper. Probably couldâve written the support myself in the meantime, but the total lack of interest was what kept me from trying, and even asking for it. I would have even tried to write something like Matrix myself (Fuel seemed promissing fot that use-case), but the rest of the ecosystem ... Cheers and good luck, M.R. From: RauÅ¡ Miloslav Sent: Thursday, February 29, 2024 5:56 PM To: Pharo Development List <pharo-dev@lists.pharo.org> Cc: Any question about pharo is welcome <pharo-users@lists.pharo.org> Subject: RE: [Pharo-dev] Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes Funny how the story changes depending on the point where one stands. OooooHHHHH, WE HAVE _AN_ APP. vs: Oh, they have an app ... OS/Ecosystem Integration is what matters · native integration o Drag & Drop (from the outside world) o taskbar/status icons o support for being launched as [Windows] Service o COM on windows (and I mean propper support, not the Astares placebo) o .NET bridge everywhere o perhaps even @#%$ Java Semblance of multicore support (even faked, as is â was? â the oh-so-great Cincom âMatrixâ) wouldnât hurt (as far as dynamic/scripting languages go, TCL nailed it decades ago). But yeah, progress happens, it just might seem slow to the people who are watching from the side-lines (Since Squeak 3, I think). Keep on pushing forwards!