|
@nelhage | |||||
|
I wrote some thoughts on software performance: blog.nelhage.com/post/reflectio…
|
||||||
|
||||||
|
whitequark
@whitequark
|
10 h |
|
aw. I made Parser about as fast as it was realistic to do in Ruby, but... yeah
|
||
|
|
||
|
@nelhage
@nelhage
|
10 h |
|
Parser is an amazing gem and we got and get a ton of value out of it, I don't want to shit talk it at all. But yeah the comparison is stark :/
|
||
|
|
||
|
ryan
@context_ing
|
3. velj |
|
Wow, going through some of your blog posts now. These are extremely well written and on very useful topics. Thanks!
|
||
|
|
||
|
Buddy Casino
@buddy_casino
|
9 h |
|
> attempts to add performance to a slow system often add complexity
I've seen this first hand, but never heard it mentioned before.
I like this article a lot, its a really well rounded and considerate take on the subject, thanks for taking the time to write it down.
|
||
|
|
||
|
Pascal S. de Kloe
@KloeID
|
22 h |
|
Amen
|
||
|
|
||
|
Ben Plotnick
@benplotnick
|
17 h |
|
Great post. Totally agree that perf can be a feature. But would you have 1) known to value instant response time and 2) been able to convince people its worth the investment if you didn’t have the previous experience of a poorly performing static analysis tool?
|
||
|
|
||