Hacker Newsnew | past | comments | ask | show | jobs | submit | robdor's commentslogin

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.


Yeah, it's also fun that you can do it in a multiple function head pattern matchy way

  defmodule FizzBuzz do
    def fizzbuzz(x),          do: fizzbuzz(x, {rem(x, 3), rem(x, 5)})
    def fizzbuzz(_x, {0, 0}), do: IO.puts "fizzbuzz"
    def fizzbuzz(_x, {0, _}), do: IO.puts "fizz"
    def fizzbuzz(_x, {_, 0}), do: IO.puts "buzz"
    def fizzbuzz(x,  {_, _}), do: IO.puts x
  end

  Enum.each Range.new(1, 100), &FizzBuzz.fizzbuzz/1

or in a more ruby-esque fashion

  (1..100) |> Enum.each fn(x) ->
    cond do
      rem(x, 3) == 0 and rem(x, 5) == 0 ->
        IO.puts "fizzbuzz"
      rem(x,5) == 0 ->
        IO.puts "buzz"
      rem(x,3) == 0 ->
        IO.puts "fizz"
      true ->
        IO.puts x
    end
  end


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


Correct, it's not RESTifarian. It's HAPIfarian! :)

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.


Okay, so it's bulletproof for PvE.


It's really not though. At least for me, I find that there's a balance between giving and receiving damage in the boss fights. While having higher vitality (more HP) lets you survive longer, unless you can also dish out a lot of damage the fights can become incredibly difficult.

Basically, the question is how many times you can hit the boss by taking advantage of their timing versus how many times you screw up trying to take advantage of their timing.

If you have more HP you can screw up a few more times but if you're not dealing much damage you end up having to avoid screw ups for a long time in some boss fights.

Then there are the fights like the Four Kings where you really want to be doing higher DPS or else things get really messy.

Personally, I found the easiest build for PvE to be a sorcery build focused on high DPS. With a high enough intelligence you can deal a lot of ranged damage, which makes avoiding being hit that much easier.


A Fire Uchigatna+6 or +7 makes Four Kings easy if you have 20 estus flasks and plenty of vitality. Since this weapon doesn't scale with stats you barely have to alter your build to use it. I'm not saying it's the only viable build, nor the only fun one. I'm saying that the builds aren't exactly a work of genius, which is I suppose unavoidable when on your first run there are basically zero clues as to what's to come. For example, how are you supposed to know that Four Kings will need high DPS? A better way to do all this would be to foreshadow every boss in some way. For example, NG being a very cut-down version of the game with simplified, shorter areas and weaker bosses, with NG+ being the real deal deal. This is basically how everyone who really loves the game plays it anyway: bumble around through your first play-through, then on the second and third goes you can start making more conscious choices, since you have some idea of what's to come.


Elemental Weapons are okay, but not really very viable. If you want a weapon without scaling, chaos is your best bet, if you're => 10 humanity. The way to play is break points though. Most stats fall off at 40, then 45, then 50 points. Meaning that You should at most invest 50 points into one stat. So pump up VIT/END to 40/45 and then your primary attributes. For a generic melee characters a mix of STR/DEX works really well, since a lot of weapons scale with both stats.

Just in case someone was wondering about builds...


This is basically how everyone who really loves the game plays it anyway

No, it's not - NG+ is much easier than NG, because you start decked with all your previous equipment. People who really love the game do NG runs staying at level 1.

I've put in lots of hours, and NG+ is dull because you already have anything and can go anywhere. The challenge is gone.


I too quit in NG+, but mostly because I was tired of pulling my hair out. I've heard lots of people say that NG+ is easier... until four kings.


Do you bother trying to understand what was meant before replying? How, after reading my post, was your take away "everyone plays NG+" (something anyone who plays the game knows is false)? The point is that people replay the game knowing what is to come, with everything already foreshadowed, and consequently being able to make much more informed choices. Whether you happen to be on NG+ or not is completely independent of this statement, and wasn't intended to be implied, which is why I said "second third playthroughs" in that sentence not "NG+". It's like you read just one phrase out of my post and responded to it out of context to prove some kind of point.


Yeah, silly me, interpreting a direct follow-on sentence as referencing the sentence before it. I like how you call me lazy for this breakdown in communication; it apparently never occurring to you that perhaps there was actually a connection there, intentional or not. Did you bother to even consider that you had written ambiguously?

I mean seriously, your criticisms of the game are just generic whines because you've encountered a hard one. Finding a boss hard? Go do something else in the game, because there's plenty else to do. There's only a couple of points where the gameplay bottlenecks, and even then you have to try hard to get it to the point where there's 'only one boss/area to do'.


>Did you bother to even consider that you had written ambiguously?

All speech is ambiguous. You're expected as an adult to try to understand other people. You failed to understand me, and looking back at my post it ought to be obvious that you didn't read it carefully at all. The connection with the preceding sentence (a given in any paragraph you dunderhead) does not amount to "everyone does NG+ on their second play through". Nowhere is this written or implied. It's simply pure lazy reading on your part, eager as you are to take issue with what I said. And if you're going to come back with me with this sort of bullshit, maybe you should have some kind of real issue with what you now realise I actually said. But no, we get...

>I mean seriously, your criticisms of the game are just generic whines because you've encountered a hard one.

I've played through both games 3 times each. I didn't find them overly hard. Dark Souls is harder, and some bits were tough. I like that. And alternating bosses is exactly how I dealt with the harder bosses. None of this conflicts with my criticisms at all. Do you have some kind of argument to make? Or are you just upset that in your rush to piss on my post you grossly misinterpreted it? The point stands: the first play through is largely about bumbling around wasting your time. It is disorganized. It lacks clues. Do you have an answer to this, the thing I actually said? It seems it's very hard for you to change your P.O.V. to a superior one, one that can actually be defended with an argument, rather than garbage attacks like accusing me of "whining" because the game is "too hard". In fact, I don't think it's all that hard at all! Which is why in this very thread I spoke about how easy it is to beat the game with vitality builds, which is what I did on my first play through. The only "whining" here is that you didn't read my post, were butthurt by my retort, and without responding with an argument - one that contradicts something I actually said.


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.


Except that ClojureScript is dependent on JVM Clojure, and if ClojureCLR were to take advantage of the CLR's capabilities (TCO and stack allocation, for example) it also wouldn't be Clojure.

So we're really talking about dialects of Clojure (and perhaps might as well be talking about dialects of Lisp in general).


We're not that far from officially having a boostrappable ClojureScript compiler. And some people have already done it - http://github.com/kanaka/clojurescript


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.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: