746 karma · joined October 14, 2008
The performance (only done preliminary testing) looks very promising as well.
A huge amount of kudos to the author!
I use `bind t split-window \; select-layout main-vertical` to emulate Xmonads default layout behaviour.
It works because I spend most of my time in the terminal anyway. I miss having the browser - and the video player when doing repetitive or otherwise boring tasks! - in a pane, but keeping other apps out of the tile-management is fine as I'm, more often than not, switching context anyway.
Here's an example where the author manages comet connections using gen_fsm in Erlang:
http://www.letsyouandhimfight.com/2010/01/31/comet-in-erlang...
The FSM starts in state "waiting" (waiting for a connection/request). When a request arrives, the state is transitioned to "have_request". When/if a packet arrives when there's a request connected (packet -> have_request), the data is sent to the client (that then disconnects; the nature of this comet implementation) and the next state is set to "waiting". When a packet arrives when the current state is "waiting", it's added to a buffer and the next state is set to "have_packet". When a request is made and the state is "have_packet" - as opposed to when it was in "waiting" - the packet is immediately sent to the client, and the next state is set to "waiting". There are many other states and "events" in the code, but I think this illustrates how easy FSMs make it to reason about these kind of implementations (protocols).
http://methodandcraft.com/videos/pixel-hinting-vectors-in-ph...
Most applications during the beta so far have consisted of static files deployed to a CDN, running server-side logic in aforementioned environments. We'll be working a lot towards this workflow in hopes to make it as simple as possible for you guys to build and scale real-time-enabled applications.
I guess it's natural that we want to push boundaries, but maybe Gopher wasn't such a bad idea? :)
We'll be working hard with explaining the product better and add lots of tutorials and more detailed examples to the documentation!
UPDATE: You can submit a token when using the Push API as well. We'll be covering benchmarks in a blog post in the not so distant future.
Now we just need to find some voice talent! :)
Thanks!
(we did a full test in "all" browsers before posting, but there are always edge-cases and we appreciate your help a lot)
Thanks for taking the time to comment!
We've wasted so much time tweaking our concept in utter fear of how the community would receive us. Mantras about releasing early and often, or letting our users shape the product, to no avail; we subconsciously wanted our entire (ever-changing) vision to be implemented to perfection before showing you anything.
A lot is happening in the "real-time" business at the moment and now we're asking ourselves: "why the hell didn't we launch a year ago?".
So, as an exercise in letting things go, we're throwing our little project to the wolves. Despite our wishes to have implemented X, Y, and Z before doing so.
[1] http://viniciusvacanti.com/2012/04/02/how-we-fooled-ourselve...
With browsers, it's commonly used to programmatically take screenshots of web sites.
http://dribbble.com/shots/423934-This-Means-Markdown
Another nice one:
I move around a lot and I want my editor (and my shell, for that matter) to be ready the instant I hit enter.
do_something(N) ->
Pid = self(),
spawn(fun() -> find_x(Pid, N) end),
receive
{found, Item} -> ...;
not_found -> ...
end.
find_x(Pid, N) -> find_x (Pid, N, [1, 3, 5]).
find_x(Pid, _N, []) -> Pid ! not_found;
find_x(Pid, N, [N|_T]) -> Pid ! {found, N};
find_x(Pid, N, [_H|T]) -> find_x(Pid, N, T).
You can also handle timeouts and stuff.All in all, I pretty much love Erlang's syntax. It's the perfect mix of readability, terseness and structure; and it has that cozy nerd-air about it, the one that makes you want to sit up all night dishing out code.