416 karma · joined November 30, 2012
Well, they know the windows platform and had windows machines lying around. They hooked up PC's to these TV's mounted high up on the wall, either mounted the PC on the TV or put it somewhere that couldn't be seen, and put powerpoint viewer on the PC's.
This might sound like a disaster, but the higher-ups loved it. And it worked quite nicely to my surprise. Windows can easily be configured to start the powerpoint file of your choice in fullscreen mode when the machine starts. Creating the material was as easy making a powerpoint.
So, in the end, the cost of materials and time was minimized because these guys used Windows + Powerpoint for their digital signage. And since they weren't using some buggy piece of custom software, it was fairly stable.
You may not like Windows, but it's a _fine_ computing platform. People get _work done_ with it. Personally, I'll stick with OSX.
You shouldn't have to be a dev to take advantage of the API universe. You'll just need tools that are able to reason about the data available.
Compare mixins.less https://github.com/sapo/Ink/blob/develop/less/modules/mixins... https://github.com/twbs/bootstrap/blob/master/less/mixins.le...
Personally, I like it. It's nice to have competition :)
Thanks, Johnny. This stuff is fun to think about.
One thing bothered me. He said it took a double click and cmd+c to copy? That's not true at all. Single click auto selects. I think the hiding the of the URL is kinda lame because the URL _was the design element_ for "clone" for so long. I see the URL and I know I can click it to select, CMD+C, paste it into my terminal.
Ian certainly has some valid points, but in the end, I think he's not appreciating the full-range of use cases that everyone has. Github has a lot of different kinds of users. Enterprise development flows are a bit different than the open source ones. And those are the flows that bring in the money.
Though, I'm sure they use Github enterprise, so maybe he does appreciate that use case as well.
Thanks for pointing out the error!
Another use-case: We've got hundreds of clients that send health statuses for a ton of different metrics every 10 minutes. Stuff like Wifi strength, exceptions caught/uncaught, various errors and crash reports, blah blah. Anyway, we need a flexible store for all of this stuff because we're always adding more metrics. Whatever the clients send as their request body gets added as a JSON object.
We also want to dynamically display all of these metrics. We can literally grab the data as JSON and make the keys table column headers in an html view. Adding new metrics can automatically be reflected in both the database and in our html views. We can query against new fields without changing schemas or business logic.