HNHacker News
TopNewBestAskShowJobs

gurraman

746 karma · joined October 14, 2008

trell.se
submissionscomments
gurraman··on We know what you're doing
Another interesting column: "Who's out of town?". I wonder how burglers use social networking.
gurraman··on Fish: Finally, a command line shell for the 90s
It gives me great joy every time a new command-line-related project is released (or, as in this case, gets a major update). I will dedicate a few hours of my weekend to take this for a thorough spin!
gurraman··on Cowboy - A small, fast, modular HTTP server and socket acceptor pool
I've been using this wonderful piece of software for a couple of weeks now. It's extremely powerful when you need to implement multiple interfaces (including non-HTTP-based) to the same data-source.

The performance (only done preliminary testing) looks very promising as well.

A huge amount of kudos to the author!

gurraman··on Customizing the Mac to behave like Xmonad
I'm in a similar situation (hooked on Xmonad, but cannot run Linux). I've tried various solutions over the years, but the only one I've found acceptable so far is a full-screen iTerm2 running tmux.

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.

gurraman··on State Machines
They're generally useful when you need to process input and keep track of what to do "next".

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).

gurraman··on Pixel-fitting – how antialiasing can ruin your logos and icons
If you prefer a video:

http://methodandcraft.com/videos/pixel-hinting-vectors-in-ph...

gurraman··on Building a Virtual World on Hydna
I'd say the pricing is about the same. You do, however, get access to a hosted environment with all of Hydna's plans (including the free one). You can use this environment to deploy rules and custom logic, reducing the need to set up a third party server.

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.

gurraman··on Will Apps Kill Websites?
I was thinking something similar when I was browsing the other day. We've made such advancements in technology, but I bet that the average time it takes to load a web page hasn't much improved.

I guess it's natural that we want to push boundaries, but maybe Gopher wasn't such a bad idea? :)

gurraman··on Show HN: Learning to let go - our hosted real-time platform
Thank you for all the kind words and comments!

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.

gurraman··on Show HN: Learning to let go - our hosted real-time platform
Good and valid point. Thanks!

Now we just need to find some voice talent! :)

gurraman··on Show HN: Learning to let go - our hosted real-time platform
That's most unfortunate! Would you mind telling us what browser (including version) and OS (ditto) you're using?

Thanks!

(we did a full test in "all" browsers before posting, but there are always edge-cases and we appreciate your help a lot)

gurraman··on Show HN: Learning to let go - our hosted real-time platform
Ok, quick-fix online. We'll take another look at it in the morning. Thanks for the encouraging words! :)
gurraman··on Show HN: Learning to let go - our hosted real-time platform
You're absolutely right. Will be "fixed" in our next update! :)

Thanks for taking the time to comment!

gurraman··on Show HN: Learning to let go - our hosted real-time platform
Agreed. We will work on that. Thanks a lot for taking the time to comment! :)
gurraman··on Show HN: Learning to let go - our hosted real-time platform
A few days ago an article on "delayed launches"[1] was posted here on HN. We took a step back from our computers, looked at each other, and laughed nervously. The article was about us. The thing is, the author couldn't possibly have known about us as we've been too afraid to leave the comfort of our stealth mode.

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...

gurraman··on PhantomJS 1.5 released (headless WebKit with JavaScript API)
That you can operate the software without the normal i/o devices (monitor/screen, mouse, keyboard etc).

With browsers, it's commonly used to programmatically take screenshots of web sites.

gurraman··on Handbook of Text manipulation on Unix
Sort of related: rpl[1] is an often overlooked tool for replacing text across multiple files. Terser than "perl pie" and a few nice features like simulation mode.

[1] http://www.laffeycomputer.com/rpl.html

gurraman··on The Markdown Mark by Dustin Curtis
I saw this on Dribbble a few weeks ago:

http://dribbble.com/shots/423934-This-Means-Markdown

Another nice one:

http://dribbble.com/shots/424152-Markdown

gurraman··on Responsive Text
In the end, we'll have so much extra markup and scripts to execute that the users get annoyed by slow downloads and choppy performance, instead of having to zoom interfaces :)
gurraman··on Suffering-oriented programming
The key here is "an unfamiliar domain". The "make it possible"-part is empirical research. So, you could make it beautiful and fast the first time around, but some would argue that it'd be better to first make it beautiful and then optimize where necessary.
gurraman··on Vim-powerline: The ultimate vim statusline utility
For various definitions of "instant", I guess.

I move around a lot and I want my editor (and my shell, for that matter) to be ready the instant I hit enter.

gurraman··on Vim-powerline: The ultimate vim statusline utility
I too appreciate "native" plugins. I've even recompiled vim without support for Python, Ruby and Perl in an attempt to speed up startup (it starts a "great deal" faster, if I remember my tests correctly).
gurraman··on Vim-powerline: The ultimate vim statusline utility
Vundle installed. I agree that it is nicer than Pathogen, thanks for the tip.
gurraman··on Convore (YCW11) is reborn as Grove.io, a chat service for businesses
Not to mention any IRC network (EFnet, Freenode etc) with TLS/SSL support. At least if you're not discussing things like missile launch codes.
gurraman··on Don't return null; use a tail call
Common idiom in Erlang. Using message passing (untested code):

    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.
gurraman··on On Erlang's Syntax
I used to dislike the use of different punctuation characters as they make it "difficult" to re-arrange code. I've, however, grown to love them as they are very explicit and gives the reader a good indication on what will happen next (f. ex. an alternate function clause).

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.

gurraman··on The switch: Python to Node.js
Most of our "django projects" are listed as being written in js on GitHub.
gurraman··on Erlang R15B Released
Yes! Although the absence of line numbers forced you to think through (in some cases) related code as well as the code that generated the error :)
gurraman··on Understanding email routing (i.e. MX-records)
Would've been nice with a little more meat .. like convering all the steps performed when detecting the actual SMTP servers (including connection attempts, alternative lookups when no mx records exist etc).
gurraman··on Asynchronous UIs - the future of web user interfaces
Does it also prevent the browser from crashing if there's still something pending? :)
← PreviousPage 2 of 7Next →