219 karma · joined July 4, 2010
Is this it for the demo, or do you plan to continue development?
Seated, the monitor is the right height for me, so as to keep my head up and neck straight. When I want to switch to standing, I just move the keyboard to the top level. I make the switch once or twice per day. And I can sit cross legged on the lowest platform (I dont like bucket/office chairs).
That was v0.1 of the desk, constructed in a few hours. the As you can see it is not production ready :p
http://blog.angelinegragasin.com/wp-content/uploads/2011/02/...
"With the help of basic mathematical modeling, you can make an educated guess that the relationship between the optimal line height and line width is exponential. Here’s the simplest equation to express that:"
The author chooses to square height to determine the "optimal" width, as the "simplest equation to express" the exponential.
But obviously the best educated guess would be W = Lh^GOLDEN RATIO
Everything you send up or down is a message, or a packet, and the size of that cannot exceed the size of pipe (with bottlenecks or intermediary restrictions). Call 'em Quantum Packets, or a stream, or a message. The websocket protocol, as imagined by this developer, is meant to allow a continuous lot of Quantum Packs to "flow", without the application level overhead of parsing a bunch of protocol, headers, wackness. I want to get the data into my applications AFAP, cuz I still have to transcode it, analyze it, and all else to make the baby dance.
What we need as developers are minimum-for-reliability standards. No two people in different locations will have the same pipe. As a developer, I consider it my domain to write software on top of, or using, the socket layer to determine the potential through-put of the given socket, and to test such as needed through-out the simulcast. I don't even want the socket-layer-wrapper writers (may God shower them with blessings) intervening at this level, until everybody on Earth has unrestricted 10mbps/s up and down.
If that control is hidden from me, or not an option, or is nullified by protocol, then my app or media could break in ways I could not predict or understand, and so I would have to design my app using the socket layer in a lowest-common-reliability kind of way.
These are not the opinions of a WebSocket RFC acquainted developer.