- Pharo-users - lists.pharo.org

Modeling Money Units

by Sean P. DeNigris

There are several tools: Aconcagua, Money, Units; and at least two classes to overcome the imprecision of Floats: ScaledDecimal, FixedDecimal... I found one thread where Hernan said they use Aconcagua [1], another from Squeak implying that ScaledDecimal is broken [2]. A third seemed to say that FixedDecimal would be better [3], which I hadn't heard in the handful of times money has been discussed on list (usually ScaledDecimal comes up). For a simple case where someone wanted to write a small personal accounting app, which tool and which type would be the best place to start? Thanks! [1] http://forum.world.st/Money-units-tp68797p68800.html [2] http://forum.world.st/Seaside-Re-Money-ScaledDecimal-is-it-really-appropria… [3] http://forum.world.st/Pharo-dev-Monetary-package-tt4692670.html ----- Cheers, Sean -- View this message in context: http://forum.world.st/Modeling-Money-Units-tp4838614.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 21, 2015

Re: [Pharo-users] Ephemeric Cloud - new platform to publish Pharo web applications

by Andy Burnett

Mike wrote <<< Thanks for pointing this out! When websocket support is ready on the ephemeric gate I'll add a ping to API server so application will work continuously without any effort. I think conceptually it should "just work". Also I plan to have a "sticky-run" option so you can mark some of ephemerics not to go to sleep mode. What do you think? >>> That sounds like a good approach. Just to dig into this a bit more, here is our first use case. We have an iPhone/web app which is a multiuser countdown timer. The data are hosted on Firebase. The iPhone app can set the time, and control start/pause. The web apps count down by themselves, but the start/stop/reset signalling is done in real time by the Firebase server. So, if you imagine a timer that is set to run for 45 minutes, we would need to signal start to the image. That would be reflected to all connected clients via wss, and then, for example, stopped with 5 minutes to go. We would need the app to remain live whilst a timer was running. However, we don't use the timers all the time, so keeping the whole app live might burn up more of the server's resources than necessary. Cheers Andy

July 21, 2015

Re: [Pharo-users] [OT] Bill Gross: The single biggest reason why startups succeed

by Ben Coman

On Tue, Jul 21, 2015 at 12:27 AM, Martin BÃ¤hr <mbaehr(a)email.archlab.tuwien.ac.at> wrote: > Excerpts from S Krish's message of 2015-07-20 17:47:50 +0200: >> Check out this amazing TEDTalk: >> Bill Gross: The single biggest reason why startups succeed >> http://on.ted.com/h15YB > > meh. > read the transcript if you want to save the time, > but to save even more time, here is the summary: > "The number one thing was timing. Timing accounted for 42 percent of the > difference between success and failure. Team and execution came in second, > and the idea, the differentiability of the idea, the uniqueness of the idea, > that actually came in third. ... > The last two, business model and funding" > > he talks about the need to assess timing, but unfortunately doesn't tell much > about how to do it, which is really the crux of the matter. > > in hindsight it is of course easy to see how the timing factor applies. > but before, it's like trying to predict the future. Its like the Weak Anthropic principle explanation for the question of why the cosmological constants of our universe seem so finely tuned to allow our existence... If the universe was not able to produce us, we wouldn't be here to ask such questions. cheers -ben

July 21, 2015

Re: [Pharo-users] XMLRPC?

by Arturo Zambrano

Thanks Luc, that version loaded without problems. cheers. arturo On Mon, Jul 13, 2015 at 6:49 AM, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > Hi Arturo, > > for our PhaROS project, we use XMLRPC. > When I had a look at it, started to clean it up... > So far, the ConfigurationOfPhaROS uses the bleeding edge version of XMLRPC > because it was moving a lot. > Here what I use: > > > Gofer it > url: 'http://ss3.gemstone.com/ss/XMLRPC'; > package: 'ConfigurationOfXMLRPC'; > load. > > (ConfigurationOfXMLRPC project version: #bleedingEdge) > load: #('XMLRPC-Client-Core' 'XMLRPC-Client-Tests' 'XMLRPC-Server-Core' > 'XMLRPC-Server-Tests'). > "1738 run, 1738 passes, 11 skipped, 0 expected failures, 0 failures, 0 > errors, 0 unexpected passes" > > Best, > > #Luc > > 2015-07-12 19:13 GMT+02:00 Stephan Eggermont <stephan(a)stack.nl>: > >> On 12-07-15 00:59, Arturo Zambrano wrote: >> >>> Hi all, >>> I tried this: >>> Gofer it >>> url: 'http://ss3.gemstone.com/ss/XMLRPC'; >>> package: 'ConfigurationOfXMLRPC'; >>> load. >>> ConfigurationOfXMLRPC project latestVersion load: 'All'. >>> >> >> I'm afraid 1.0-alpha4 might be larger than 1.0.2 >> Did you try #stable? >> >> Stephan >> >> >> >> >

July 21, 2015

Re: [Pharo-users] [OT] Bill Gross: The single biggest reason why startups succeed

by Sean P. DeNigris

Jose San Leandro wrote > If an opinion from a newcomer is useful, I'm not so obsessed about how > popular Smalltalk is. Very useful, and not just a newbie opinion. On the Amber list, Richard Eng, who is working to make Smalltalk mainstream, was disappointed by his blog post stats. I responded in agreement with you [2]: > Unix, which Alan Kay describes as "a budget of bad ideas" (and I > agree), took almost 50 years to take over the world [1]. Maybe you're 10 > years too early to make Smalltalk popular ;) But seriously, I think you're > using the wrong metrics. The great majority of people are instrumental > thinkers i.e. they judge every new thing by how useful it is to their > current goals. This is the definition of the Pink Plane. Given that the > real value of Smalltalk is that it's prototype Dynabook software, which is > way into the blue plane of computing, convincing the masses of its value > is extremely unlikely - and not required! If say 10% of programmers are > interested in the inherent value of ideas, and we capture this 10%, that > will be more than enough critical mass. And given your report of relative > popularity of your blog posts, 570/7000 = 8% doesn't sound too far off ;) > > BTW I'm not saying don't try to reach as many people as possible, only to > reframe what failure looks like. > > [1] > http://www.forbes.com/sites/timworstall/2013/05/07/is-unix-now-the-most-suc… [2] http://forum.world.st/A-Gentle-Introduction-to-Amber-tp4831244p4833048.html ----- Cheers, Sean -- View this message in context: http://forum.world.st/Bill-Gross-The-single-biggest-reason-why-startups-suc… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 21, 2015

Re: [Pharo-users] Ephemeric Cloud - new platform to publish Pharo web applications

by mikefilonov

Hi Esteban, Pharocloud runs on OVH infrastructure. However Ephemeric Cloud solution can be ported to some other provider or client's datacenter if there is a strong need. - Mike -- View this message in context: http://forum.world.st/Ephemeric-Cloud-new-platform-to-publish-Pharo-web-app… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 21, 2015

Re: [Pharo-users] Ephemeric Cloud - new platform to publish Pharo web applications

by mikefilonov

Hi Andy, Thanks for pointing this out! When websocket support is ready on the ephemeric gate I'll add a ping to API server so application will work continuously without any effort. I think conceptually it should "just work". Also I plan to have a "sticky-run" option so you can mark some of ephemerics not to go to sleep mode. What do you think? -- View this message in context: http://forum.world.st/Ephemeric-Cloud-new-platform-to-publish-Pharo-web-app… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 21, 2015

[ANN] Pharo Consortium New Academic Partner: RyCh group

by Marcus Denker

The Pharo Consortium is very happy to announce that RyCh has joined the Consortium as an Academic Partner. RyCh (Robotics and Computation in Chile) is a laboratory of the Computer Science Department (DCC) of the Universidad de Chile. RyCh is a new research group, with a focus on the computational aspects of robotics, more specifically machine learning and the software engineering process of robotics. At RyCh, Pharo is the implementation technology for Live Robot Programming. About - RyCh: https://rych.dcc.uchile.cl - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

July 21, 2015

Re: [Pharo-users] [OT] Bill Gross: The single biggest reason why startups succeed

by Sven Van Caekenberghe

Hi Jose, Thank you for your well written feedback. It is very important to hear a voice like yours. It is hard to articulate why we like Pharo/Smalltalk. Like you say, it has to do because it is so different, because we learn from it, because it empowers us, because we feel it is a good way to develop software. Sven PS: I didn't really like the talk either, doing something new, trailblazing is always hard, often fails and sometimes works, afterwards is always seems like 'it was the right time'. > On 21 Jul 2015, at 12:08, Jose San Leandro <jose.sanleandro(a)osoco.es> wrote: > > If an opinion from a newcomer is useful, I'm not so obsessed about how popular Smalltalk is. > > I came to Smalltalk because a friend of mine (Rafa Luque) was enthusiastic about it, and suggested me to try it. > The candy was not to build applications faster, but to think differently, to question what and how we approach problems with mainstream, industry "best practice" technologies and languages. > > I see Smalltalk more like what security researches think of their discipline: it's a process, not a list of tools or recipes. After almost two decades of developing commercial software for others and open-source projects (mainly) for myself, using mostly Java but also Lisp, Smalltalk has blown my mind. That wouldn't have happened if I'd tried Seaside just because I wanted to try a different web framework. > > In my case, to approach Smalltalk I needed a certain state of mind. You have to be aware programming is not memorizing design patterns and pay for an IDE to do most things for you, including to check for non-functional stuff nobody seems to care about. We're in the "i'm proud to be lazy" era. I've seen smart people reject Smalltalk just because they don't seem to care about what they do, or at least they don't want to invest their time and energy. > > Probably there's a way to convert Pharo in node.js or Go, to make people use Seaside instead of ruby on rails. More people potentially means more financial support, and a better, sooner, full-featured, Pharo. > But even then, Smalltalk empowers people to think differently and gives the means to do so, and to promote that has to tackled differently. > I'd focus on how using Smalltalk gradually makes you a better professional, before blaming ourselves for not yet providing sophisticated frameworks anyone can use even if they don't know what they're doing. > > Let's take the Scala or the Git case. What made people invest in learning them was, at least in part, that they felt smarter. We should focus on that: comparing how the same problem is solved in other languages. Showing what live programming is. Don't be humble just to be polite. > > On the other hand, Smalltalk enables us to face problems that are potentially unachievable in other languages / ecosystems. Let's define on a "Pharo way to do X", which inevitably starts building a domain-specific browser, a custom IDE, and recipes for common scenarios. > > In summary, as Martin Bahr says, it's critically important to ensure we can survive indefinitely until the perfect "timing" arrives. But don't punish ourselves too much for not being popular. For me, the greatest value lies elsewhere. > > > 2015-07-21 3:14 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Martin BÃ¤hr wrote > > did smalltalk miss its chance, so we should give up? > > or is it still coming? glass bowl anyone? > > Using Unix - which took 50 years to takeover the world - as a metric, we > should be hitting our stride in about 2030 ;) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Bill-Gross-The-single-biggest-reason-why-startups-suc… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

July 21, 2015

Re: [Pharo-users] [OT] Bill Gross: The single biggest reason why startups succeed

by Jose San Leandro

If an opinion from a newcomer is useful, I'm not so obsessed about how popular Smalltalk is. I came to Smalltalk because a friend of mine (Rafa Luque) was enthusiastic about it, and suggested me to try it. The candy was not to build applications faster, but to think differently, to question what and how we approach problems with mainstream, industry "best practice" technologies and languages. I see Smalltalk more like what security researches think of their discipline: it's a process, not a list of tools or recipes. After almost two decades of developing commercial software for others and open-source projects (mainly) for myself, using mostly Java but also Lisp, Smalltalk has blown my mind. That wouldn't have happened if I'd tried Seaside just because I wanted to try a different web framework. In my case, to approach Smalltalk I needed a certain state of mind. You have to be aware programming is not memorizing design patterns and pay for an IDE to do most things for you, including to check for non-functional stuff nobody seems to care about. We're in the "i'm proud to be lazy" era. I've seen smart people reject Smalltalk just because they don't seem to care about what they do, or at least they don't want to invest their time and energy. Probably there's a way to convert Pharo in node.js or Go, to make people use Seaside instead of ruby on rails. More people potentially means more financial support, and a better, sooner, full-featured, Pharo. But even then, Smalltalk empowers people to think differently and gives the means to do so, and to promote that has to tackled differently. I'd focus on how using Smalltalk gradually makes you a better professional, before blaming ourselves for not yet providing sophisticated frameworks anyone can use even if they don't know what they're doing. Let's take the Scala or the Git case. What made people invest in learning them was, at least in part, that they felt smarter. We should focus on that: comparing how the same problem is solved in other languages. Showing what live programming is. Don't be humble just to be polite. On the other hand, Smalltalk enables us to face problems that are potentially unachievable in other languages / ecosystems. Let's define on a "Pharo way to do X", which inevitably starts building a domain-specific browser, a custom IDE, and recipes for common scenarios. In summary, as Martin Bahr says, it's critically important to ensure we can survive indefinitely until the perfect "timing" arrives. But don't punish ourselves too much for not being popular. For me, the greatest value lies elsewhere. 2015-07-21 3:14 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Martin BÃ¤hr wrote > > did smalltalk miss its chance, so we should give up? > > or is it still coming? glass bowl anyone? > > Using Unix - which took 50 years to takeover the world - as a metric, we > should be hitting our stride in about 2030 ;) > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Bill-Gross-The-single-biggest-reason-why-startups-suc… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

July 21, 2015