I like Amber, SproutCore was always hard to pronounce (I'm foreign) or to talk about.
Poll: Should we rename Amber.js?
21–30 of 67 posts
Re: Poll: Should we rename Amber.js?
#22ambert.js
amberlite.js
amberlin.js
amberjack.js
ambers.js
embers.js
Re: Poll: Should we rename Amber.js?
#23Call it Milamber.js
Points for guessing the reference.
Re: Poll: Should we rename Amber.js?
#24Call it Milamber.js Points for guessing the reference.
Re: Poll: Should we rename Amber.js?
#25Lager.js
Re: Poll: Should we rename Amber.js?
#26Name it something related to its core vision/goal/function. Anything to make products self-explanatory is always an advantage.
Re: Poll: Should we rename Amber.js?
#27How about Spore.js? It's a nice contraction of SproutCore, and doesn't sound as silly as the spoonerism KrautSpore :)
Re: Poll: Should we rename Amber.js?
#28Here are 2 naming suggestions following the cabbage theme for your inspiration: ;)
Brocco.js
Brussels.js
Re: Poll: Should we rename Amber.js?
#29SproutCore was a nice name, Amber doesn't have the same ring to it. Maybe Sprouts? SproutFrame?
Re: Poll: Should we rename Amber.js?
#30If you rename amber, please, do not rename it brite or bright, as I have already a project with solving the same problematic (with a different approach). https://github.com/jeremychone/brite
I am going to push brite quite a bit next year.