robdor

Why is that? My daughters play with barbie dolls and I love that they also have an interest in software development.

I haven't looked too deeply into Rust yet, but was able to understand this coming from Elixir. Pattern matching makes for a beautiful solution. This is a similar solution in Elixir:

  fizzbuzz = fn(x) ->
    case {rem(x, 3) == 0, rem(x, 5) == 0} do
      {true, false} -> IO.puts "fizz"
      {false, true} -> IO.puts "buzz"
      {true, true}  -> IO.puts "fizzbuzz"
      _             -> IO.puts x
    end
  end

  Enum.each Range.new(1, num), fizzbuzz

Since functions are also pattern matched in Elixir (and Erlang!) it could also be done without using case and handled purely as functions.

The first line of the documentation says that it uses a "HAPI-REST API". https://github.com/jheising/HAPI

I disagree that a high vit + end build is bulletproof. I'm absolutely certain that most anybody could destroy that build easily in PvP.

One of the great things about the build system in Dark Souls is a build that is great for PvE may not be a great build for PvP.

With Clojure being available for the jvm, the clr through ClojureCLR and javascript through ClojureScript I don't believe that this will be much of an issue.

I have been using node.js for my day-to-day engineering for the past year. It certainly takes a couple of weeks to get a good feel for solving problems without being able to use normal flow control. But once you get it becomes easy. So I wouldn't call in inappropriate, just different. It's much like the feeling of learning your first functional programming language. It's not wrong, just different until you adjust the way you reason about your programs.

In the setup described here (it has changed a bit in the 6 months since this article was written) Varnish was being used primarily for caching and sending needed requests to the single application server. Calling it a load balancer at that point was a simple misnomer.

Today we still have Varnish at the front of our stack for caching and also use it as a load balancer for a handful of application servers.

This is very similar to the arguments in the game dev community defining whether one has ascended from hobbyist to indie status. It's nothing more than an infantile attempt to stroke the egos of the people who consider themselves in the upper-most status.

If somebody misnaming their "waste of server space", "project" or "startup" according to your personal definition offends you then well, that's your problem, not mine. Suck it up and learn to deal with it.

Hacking on a GitHub client for Palm's webOS.

http://robmerrell.github.com/gitopotamus/

Reminds me of this post from 37signals a while back. http://37signals.com/svn/posts/1561-why-you-shouldnt-copy-us...

The definate danger of simply copying an idea is not knowing the motivation, thought processes and discarded tangents that lead to that idea.

I find "reality checks" to be a great benefit of having a co-founder. The best of us spend time pursuing ideas and tangents for our startups that really don't matter. A co-founder can help identify and keep those incidents to a minimum. Of course this works both ways.

Making online customer support easy with Candlelight -- http://www.candlelightapp.com

I've been working on it nights and weekends. Great respite from some of the less than pleasant activities of coding at my day job.

What a great question. I'm particularly interested in the marketing and customer gathering methods of startups who have gone the bootstrap route instead of receiving investor money.

No, php's implementation of anonymous functions is not efficient. When create_function is called it stores that created function globally which doesn't allow garbage collection. Making it pretty much useless to use in callbacks or when defined within a loop. Watch the memory increase for the following test:

while (true) { create_function('', ' return 0; '); }