Top all-time · #7683
Bibliographic Wilderness
Personal blog · bibwild.wordpress.comprogrammingweb
Bibliographic Wilderness is a personal blog at bibwild.wordpress.com about programming and web. Since 2010, 10 different Hacker News readers have linked it 13 times, most often “Struggling Towards Reliable Capybara JavaScript Testing”. It is still writing: the last post was on 2026-06-29, and you can follow it by feed.
Too few sampled comments (2) to say how often HN recommends it.?
Why HN links it
One commenter links this blog's long post summarising problems with Rails 5.1, including database use in integration tests, to support a point about the upgrade being difficult for many users.
Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Struggling Towards Reliable Capybara JavaScript Testing2 people · 2 mentions · first linked 2017-02-23
- ActiveRecord Concurrency in Rails4: Avoid leaked connections2 people · 2 mentions · first linked 2014-07-17
What Hacker News says?
If you've had no problems, that's great, but lots and lots and lots of us have. I tried to summarize (well, that's not the right word, it was at length) here: https://bibwild.wordpress.com/2016/02/18/struggling-towards-... While integration tests may ideally not use the database (although I find in practice, I think you often need or want to do some 'manual' setup first. But even if you don't, the _other_ tests do d…
Comment linking /2016/02/18/struggling-towards-reliable-capybara-javascript-testing/
on “Rails 5.1.0 Beta 1”Submitted Hacker News down, unwisely returning HTTP 200 for outage message as a story · 399 points
HN discussion> For a system which establishes and maintains long-running connections, the initial connection overhead becomes a non-factor, regardless of the encryption strength, but there’s still a rather large performance penalty compared to the unencrypted connection. A theoretical performance penalty, which, in practice, you just right there told us was a non-factor, right? If you are connection pooling. Which you should be.…
Comment linking /2012/04/30/ruby-http-performance-shootout-redux/
on “SSL Performance Overhead in MySQL”Submitted Rails threading nightmare as a story · 9 points
HN discussionSubmitted The growing scholarly digital divide: In memoriam Aaron Swartz as a story · 6 points
HN discussionSubmitted Concurrency in Rails 5.0 as a story · 3 points
HN discussionSubmitted State of ActiveRecord and concurrency, another update as a story · 3 points
HN discussionSubmitted Exploring hosting video in a non-profit archival digital collections web app as a story · 2 points
HN discussionSubmitted Rails and concurrent request handling as a story · 2 points
HN discussionSubmitted Struggling Towards Reliable Capybara JavaScript Testing as a story · 1 points
HN discussionSubmitted Benchmarking ruby Unicode normalization alternatives as a story · 1 points
HN discussionSubmitted ActiveRecord Concurrency in Rails4: Avoid leaked connections as a story · 1 points
HN discussionSubmitted ActiveRecord Concurrency in Rails4: Avoid leaked connections as a story · 1 points
HN discussion
