Just version it right as per semver, anything <1.0.0 is in-dev, any any 0.x.* change for x implies backwards incompatible, feel free to always move fast at this point, I do and don’t get any complaints, but the feedback is beyond invaluable! 
OvermindDL1
2
devonestes
In theory this works great. In practice this results in lots of angry people opening issues on GitHub who don’t care that it’s 0.x. They’re just upset cause their production app is broken and they don’t want to do the work to fix it.
I totally support Boyd’s decision (although I can’t wait to see it)!
7
boydm
Creator of Scenic
I’m probably going to first release it at something like 0.7, which will then be in the mode @OvermindDL1 suggests. @devonestes is totally right about the work so far though. Somebody would try to build something “real” on apis that I need to rearrange, rework, or whatever, and they would complain about the churn in the codebase.
I used to describe developing software projects as similar to making Jello. You’ve picked the flavor you want, but at first is all liquid and stirring around. Then it starts to harden, but is still mixable. Then it hardens more, generally keeps its shape, but bounces all over the place. Then the vibrations reduce until is is stable. Note that it never stops moving completely, it just gets very predictable.
To me, calling it 0.7 reflects that there is still room for feedback and possible breaking changes, but that the worst of the bouncing is in the past. Won’t call it 1.0 until it feels nice and presentable as a dessert or maybe in a nice fruit salad or some other analogy that is now past it’s original meaning.
11
NobbZ
To me, this means nothing, as versions have no upper bound. There is still a lot of room for breaking changes until you do the 0.99999 release, of which still a 0.100000 could follow while never reaching 1.0. No part of a version number stops at 9.
1
joeerl
Creator of Erlang - Fondly Remembered
You could use the Knuthian convention (who you recall used the successive digits of Pi to indicate versions) - you could use the digits of Phi (the golden ratio) - this would be appropriate for a graphics program.
Note that TeX is now at version 3.1415926 - Knuth thought that stability and having a version that worked in future exactly the same way as now was more important than introducing new features. He also offered a bounty of $2.56 for each reported error in TeX doubling for each new error.
The digits of Phi are here
There are sufficient digits for many versions
8
lackac
Or go with digits of 1/Phi while you still want to retain the ability to change the API significantly.
2
sherbondy
Boyd has done it! Open source as of this afternoon:
https://github.com/boydm/scenic
Congrats! So excited to see the start of a viable elixir-oriented GUI toolkit. Goodbye Qt!
Can’t wait to contribute some components and supporting libraries.
Some ideas for fun libraries:
- SVG renderer
- Code generation tool that ingests common UI design formats (Sketch, Figma, XD…)
- Grammar of Graphics style or D3-eque data viz primitives.
And of course all of the nitty gritty UI components, e.g. date pickers, scroll views, …
Woohoo!
22
50kudos
Just finished watching the talk, super excited! I’m a little bit wondering about how Scenic ships, is it a release or a mix?
1
Eiji
@sherbondy: OW YEAH !!!
Sorry for caps, but I’m really so excited!
Awesome work @boydm. I will try it as soon as possible!
2