Amber: Smalltalk for the Web
amber-lang.net
amber-lang.net
Amber Smalltalk - https://news.ycombinator.com/item?id=26128607 - Feb 2021 (12 comments)
Amber – Smalltalk in the Browser - https://news.ycombinator.com/item?id=22425626 - Feb 2020 (1 comment)
Learn Smalltalk with ProfStef - https://news.ycombinator.com/item?id=17940152 - Sept 2018 (6 comments)
Amber Smalltalk - https://news.ycombinator.com/item?id=13112207 - Dec 2016 (48 comments)
Amber: A new language and live environment made for the web - https://news.ycombinator.com/item?id=11299547 - March 2016 (1 comment)
Smalltalk runtime in the browser - https://news.ycombinator.com/item?id=6216539 - Aug 2013 (33 comments)
Amber Smalltalk 0.10 released - https://news.ycombinator.com/item?id=5369682 - March 2013 (15 comments)
Learn Smalltalk in the browser - https://news.ycombinator.com/item?id=2996510 - Sept 2011 (2 comments)
Amber - Smalltalk on JavaScript runtime - https://news.ycombinator.com/item?id=2995689 - Sept 2011 (1 comment)
Even put together flow [1] a stack based on it because the workflow with Pharo and Mapless [2] felt so nice.
And blogged about it:
Flow - A living full-stack framework for the web - https://medium.com/@sebastiansastre/flow-a-living-full-stack...
Improving the Amber Experience - Some small steps to improve the productivity and overall experience of developing with Amber Smalltalk - https://medium.com/@sebastiansastre/improving-the-amber-expe...
Flow demoed at Smalltalks2014 - https://medium.com/@sebastiansastre/flow-demoed-at-smalltalk...
Upgrading to flow 0.2 - https://medium.com/@sebastiansastre/upgrading-to-flow-0-2-d4...
Here is a talk with more spirit than skill back from 2014 trying to promote that mission https://www.youtube.com/watch?v=iumCpezWzkU
At the time I was focused in a Seaside based SaaS that I started in 2009 https://www.youtube.com/watch?v=7Z29q5PUoJs
Although that SaaS had very low churn and very long LTV and low CAC, I failed to raise money to grow it and I've failed to find the right growth guy that could help and shutdown in 2015. My bet was to use that flow stack to make this SaaS next big upgrade to be a Single Page Application done with Amber in the frontend but didn't go well due to these non-technical issues.
Then Angular was eating the web world and the React tsunami was just started.
It's funny to see that now there is a come back to SSR.
existing smalltalk webframeworks are either backend or fullstack, and made no sense for me to use inside amber.
an amber frontend framework would essentially be a GUI toolkit that uses html/css templates to design the UI, then smalltalk to fill in the logic with fetch calls to exchange data with arbitrary backends.
It also shows how to integrate with external JavaScript libraries. The example they use is D3.
Here's part 2 of their article: https://medium.com/@richardeng/you-are-now-an-ambersmith-c25...
There are probably other tutorial that are more extensive.
a tutorial to use amber with react or svelte for example would be great. (i don't work with either, but given that they are a,mong the most popular frameworks for the time being, it has the most likelihood at capturing some interest.)
There are probably other reasons to avoid a full stack framework, but this isn't one—there's nothing to stop you from making the backend just a proxy to the existing API.
Aside from that, Amber is entirely client-side from what I can see. The Amber server is the equivalent of the Webpack or Vite dev servers, just used during the development process. It looks like Amber compiles to plain JS that runs directly in the browser.
there's nothing to stop you from making the backend just a proxy to the existing API
what is stopping me is that this forces me to run two backends and an additional layer of indirection.
Prior discussion: https://news.ycombinator.com/item?id=38820742
to bring it to a point, i'd like to use smalltalk with a web framework the way i use typescript or coffeescript with angular or react
in difference to coffeescript smalltalk at least offers the benefit of a syntax that is also usable elsewhere.
For LittleSmallScript I knew the syntax taste will go to the roof. And you're making a great point, indeed parts of a program written with Smalltalk syntax would have a lot degree of reuse.
Very cool. What if I want to read through printout of your smalltalk program?
There's a tutorial to get the very basics of Smalltalk/Pharo called ProfStef. Here's an online version: https://amber-lang.net/learn.html
It has a built-in version on Pharo images as well.
https://exercism.org/tracks/pharo-smalltalk
And this if you want to feel not alone in the first steps: