tyler

9 ms·

31.
by tyler 16y ago
And of course, you know that users won't see any difference or care, despite never having seen, let alone used it. Just because you think the problem has been solved well enough, doesn't mean everyone does. After all, who needs a refriger
32.
by tyler 16y ago
We create basically the same experience across browsers, but use the latest tech that the browser supports. For instance, things will render much faster in Chrome than in IE6. However, the documents will basically look the same across all
33.
by tyler 16y ago
Most things certainly are simple in principle.
34.
by tyler 16y ago
"Distant features"? It's launching tomorrow.
35.
by tyler 17y ago
Personally, I'm not particularly picky about my forms of immortality.
36.
by tyler 17y ago
Evan Miller's guide (already linked above) is great. But be prepared to dig into the Nginx code. Most things aren't documented, however, at least in my opinion, it has some of the cleanest large scale C code around. So, don't be scared t
37.
by tyler 17y ago
The word "rape" has multiple meanings. At least one of which applies and is not necessarily connected with anything of a sexual nature. http://en.wiktionary.org/wiki/rape
38.
by tyler 17y ago
The part I find particularly silly is where he writes: For example, assume that the hash table implementation shrinks the table if the number of full buckets drops below half, and grows the table if it becomes over full. If the ta
39.
by tyler 17y ago
No insult intended at all. It was just that as I was reading down that list my brain was screaming "CAP! CAP!". I was glad to find that link there. Looks like an awesome project.
40.
by tyler 17y ago
The description given on their Google Code page seems a bit sensationalistic to me. The author has a bit more reasonable look at the features and tradeoffs here: http://sbtourist.blogspot.com/2009/12/terrastore-and-cap-the...
41.
Terrastore - Scalable, elastic, consistent document store(code.google.com)
37 points by tyler 17y ago|14 comments
42.
by tyler 17y ago
In my opinion, that's a problem. If you don't understand what is actually going on under the hood, you're likely to get bitten when things don't go exactly as you expect. ActiveRecord is the most obvious example of this. If you don't know
43.
by tyler 17y ago
Ouch. "filters" wasn't the right word there. Sorry about that.
44.
by tyler 17y ago
I tend to ask, not how you use the framework, but rather how the framework works. How does routing actually work? How do named scopes work? How would you implement the {before|after} filters on models... etc. It's actually somewhat more
45.
by tyler 17y ago
You certainly could argue that, however, if it were true in most cases Google, a highly data-driven company, would be still be working that way.
46.
by tyler 17y ago
What bothers me most is when a candidate gives off a "this is below me vibe". I tend to start with quick, easy questions and work toward much more difficult ones. Candidates often act as if answering these easier questions is below them..
47.
by tyler 17y ago
Right on. My point was simply that the type of Trie you use has an effect on the data's size in memory. A dual-array setup is pretty good at keeping the data small... There's very little pointer overhead and proximity is fairly good as
48.
by tyler 17y ago
I've had the opposite experience with Tries v. Hash tables. Though that could be a result of the Trie implementation. Dual array tries have really impressive lookup times, especially compared to the naive implementation... Insertion is pr
49.
by tyler 17y ago
As a counterpoint, not every Ruby app is a Rails app. I've been using JRuby more and more lately for various text analysis projects. Calculating the mutual information over a huge set of tokens, for instance, was roughly 10 times faster i
50.
by tyler 17y ago
Nonsense. My multitudes of small web services, many of which have been running months without a restart and while taking up no more memory than they did at the start say you're wrong. Even if there are some obscure bugs, and there undoubted
51.
The Thrush Combinator in Scala(debasishg.blogspot.com)
4 points by tyler 17y ago|0 comments
52.
by tyler 17y ago
From the article: "2) reducing the aggressiveness of our SEO, which reduces total traffic in the near term but increases the relevancy of Scribd links in search engine results"
53.
by tyler 17y ago
Wow. Not many people would willingly say "I hope your startup fails and all the employees (fellow HNers) become jobless." Keep it classy, man.
54.
by tyler 17y ago
The question he was asked was actually whether he would want someone to publish TC's documents. The answer is obviously no. However, that's completely separate from whether he would consider it news. It's news whether or not you want it
55.
by tyler 18y ago
They detect when you paste something and use a fixed-width font on it. Also, they truncate it and link to a full version.
56.
by tyler 18y ago
I don't see why that is a problem. While I don't think that this is really the whitehouse taking a side, what if they were taking a side? They should.
57.
by tyler 18y ago
I've been really looking forward to this mostly because of how bad ActiveSupport's implementation of this is. For instance, lookups require a linear scan. Definitely a welcome change.
58.
by tyler 18y ago
That seems like a dangerous and foolish proposition to me. Just because IBM doesn't seem like a patent troll today, doesn't mean they won't tomorrow. Not to mention, just like a real arms race... It's not the government officials who are r
59.
by tyler 18y ago
Yes. That's true. But that's not what is being discussed. What is being discussed is whether or not frameworks and high level languages exist solely to make the bottom 90% more productive. My comment illustrates the fact that criticizing
60.
by tyler 18y ago
Okay great. Well, you go ahead and hack up your project in assembler, making sure to build everything (including the network stack) from scratch. Let's have a race. If only all of our competitors were as misled and arrogant as you. :)

More ›