Threads for oniMaker
-
This sounds interesting, but the link is broken. Is there a backup somewhere?
-
The highlights were that he thinks bitcoins will be worth $1300. Coverage elsewhere:
-
-
-
I’m dismayed by all the people in the comments who didn’t read the article but think that “LOL PHP” is a valuable contribution.
-
-
Having to have a facebook account is a real downer.
-
-
Disregarding the analogy, there are problems with the doctrine itself. For example, here are two that stand out:
“Hell is a place where people are no longer in the presence of God” – how could this be if God is omnipresent?
In a similar vein, if Lucifer rebelled and Adam & Eve chose, and if God is omnipotent/omniscient/omnipresent, then it would mean that God chose to allow both events to occur. If that is the case then God chose to allow his own creation to be corrupted.
-
Jared makes a good point. However, it’s possible to strike a balance between simplicity and capability by making available optional, modular features for a given product; users install modules on request to add capabilities outside the core feature set. A model like this avoids both problems mentioned in the article – keeping the UI/UX approachable, and the code untangled. It does add some complexity though, which is unavoidable. Still, it could be a good way to get new users up and running quickly, then retain them when their requirements grow.
I don’t know, I think this might make me want to kill myself: http://0x0.st/-zeS.png
Don’t worry. Help is near: https://github.com/Annihil/github-spray
From the feedback we got so far, many people seem to have the same problem.
Here are a few reasons:
Thoughts on the above would be appreciated.
I don’t think I’d buy one of these for my own commit history, but others will. Mainly I can see it being marketed to companies & teams, so making it work at the project level should be useful.
If there were repo support, and if you could annotate the history with some text bubbles, then users could mark important milestones, and tell the story of the project. You could make it optional to auto-render things like tags for version numbers. You could make it more personal by adding the avatars & stats of the contributors somewhere in the layout.
Being able to select an arbitrary timescale would enable more use cases. Similar to shopkeepers who frame their first dollar bill earned, a team could enshrine their first week or month of commits. They could show off the crunch time (however long it was) when everyone made tons of commits and everything got finished just before launch.
Thanks for the feedback. That’s all great advice. We also considered prints for teams (with discounts for larger volumes) before and I’m glad others think alike. Support for annotations and custom time-ranges sounds very reasonable.
If you don’t mind me asking, why wouldn’t you order one for yourself? Is it that you don’t like the layout, don’t have many public commits, or you don’t want to make a fuzz around it? I’m asking because we’re always interested in new visualizations for different sorts of users.