rybosome

48 ms·

481.
by rybosome 13y ago
Reminds me of something a former boss used to say. "Pay me now, or pay me later; either way, there has to be a payment". It sounds like Carmack is saying that brutal purity always forces the "pay me now" approach since i
482.
by rybosome 13y ago
You frequently mention nice things about Go in comparison to Haskell. I'm learning Go at the moment, and must admit that I find myself struggling to stay motivated. Given your background in FP (and apparent enjoyment), what do you find
483.
by rybosome 13y ago
I'm not calling myself a great engineer, but I've actually been hesitant to accept job offers in which I wasn't given a challenging interview. A challenging interview is not always indicative of a good job, of course, but wit
484.
Algorithmic Tradeoffs (examples in Scala)(ryboso.me)
2 points by rybosome 13y ago|0 comments
485.
by rybosome 13y ago
"In all i feel PHP has moved the web forward tremendously." Agreed, wholeheartedly. I truly dislike PHP as a language, but one cannot deny the massive impact it had in making web applications commonplace.
486.
by rybosome 13y ago
Agreed, 100%. I see it as kind of an inevitability.
487.
by rybosome 13y ago
What semantically crazy stuff do you have to rely on? I don't advocate mindlessly buying into the cult of Crockford, but he outlines a pretty reasonable subset of the language in "JavaScript: The Good Parts" The only thing I
488.
by rybosome 13y ago
Any language that emphasizes expressions over statements will have this feature. Off the top of my head, that should include Haskell, Scala, CoffeeScript, Ruby, Elixir, Clojure (hell, anything Lisp really)... The idea is that while you may
489.
by rybosome 13y ago
This is the fundamental point that gets made and debated, again and again. I just don't agree that the stress is the same. Speaking as a person who is very prone to interview nerves, nothing evokes quite the same reaction in me, so it&
490.
by rybosome 13y ago
Maybe.
491.
by rybosome 13y ago
That's an easy solution in any language, frankly; have a shared queue of the requests, and the servers simply pull from the queue whenever they aren't processing a request. I'm sure that this is easier to implement in Go than
492.
by rybosome 13y ago
That's actually a very fair point - when it comes to usability with respect to the functional style, sometimes less is more. I think C# is actually a pretty good example of a pragmatic language that offers FP to make your life easier,
493.
by rybosome 13y ago
Be careful; once you've been working in Scala, going back to Java is unpleasant. =)
494.
by rybosome 13y ago
The danger of that approach is that, in my experience, it's more likely to turn someone away from Scala. At my last job, some of the engineers did write Java in Scala. In what I'm sure is not a coincidence, they were also the ones
495.
Kal Me Maybe - a comparison of Kal to monads in Haskell(ryboso.me)
1 points by rybosome 13y ago|0 comments
496.
by rybosome 13y ago
It's remarkable how similar this code looks to the monadic way of doing it. For this Kal code... task getUserFriends(userName) wait for user from db.users.findOne {name:userName} wait for friends from db.friends.find
497.
by rybosome 13y ago
I'd love to know what James Hague ( http://prog21.dadgum.com/ ) thinks of Elixir. Erlang is one of his stronger languages, and he's written a lot of articles in the past that I really enjoy.
498.
by rybosome 13y ago
This is kind of a strawman, but if you were to use a similar pseudo-API, what would the imperative code look like? Very fair point about efficiency; for all my love of the FP style, I'll never claim it to be faster or leaner w.r.t memo
499.
by rybosome 13y ago
From the article: "For instance, to actually encode a Cap’n Proto message, I couldn’t just allocate a buffer of zeros and then go through each field and set its value. Instead, I had to compute all the field values first, sort them by
500.
by rybosome 13y ago
That's certainly true. Although I'm not an expert on the really advanced type system features, this is an example of convenience without culture, IMO. C# having painless lambdas allows this particular example to exist, but it&#x27
501.
by rybosome 13y ago
The bugs you make may not be related to types because your definition of what a "type" is refers to the very weak guarantees given by C, Java et al. Have you ever had a bug due to something being null/nil when you didn't
502.
by rybosome 13y ago
I would absolutely love to attend this, but I don't think I could justify an international trip right now (getting married in 1.5 months). What are the chances you'll do another one next year?
503.
by rybosome 13y ago
Here's the tail-call optimized version, won't blow the stack. Technically idiomatic, but way too cryptic to be serious code. Clearly I need more outlets for writing Scala. =) @tailrec def getValuesFromNode(node: Node, ac
504.
by rybosome 13y ago
I hope you're right. If I ever get a chance, I'll ask. =)
505.
by rybosome 13y ago
To be honest, I don't remember the technical specifics...too much time has passed. It wasn't so much that a breaking feature change required rewriting code as it was that a single failure propagated. One component written in Scala
506.
by rybosome 13y ago
You make a valid point, but for something as fundamental as nullability, I think that's baked into the core language spec. It's possible that we could see an Option type in the future, but the fact that it's not an integral p
507.
by rybosome 13y ago
If it had been done at the very beginning, I think it would have been wonderful...but given that legal, idiomatic nil is already out in the wild I think it's too late. Such a shame - in the example of error handling, returning an Optio
508.
by rybosome 13y ago
Go occupies an interesting space. In my mind, I see it as competing simultaneously with C and Python. I suppose that the developers didn't see a place for an Optional type within that realm. I have to admit, I think it's a shame;
509.
by rybosome 13y ago
This is why I love pattern matching in languages that support it - typing is just one of the things on which they can switch. As the Scala website puts it (paraphrasing), "Pattern matching is switch on steroids!" Here is how you w
510.
by rybosome 13y ago
We used Scala in production at my previous job. It was great for the most part, but upgrading from 2.9 to 2.10 was a massive, massive pain. I think I spent nearly a week on the refactor. We didn't even have that much code (relatively s

More ›