5 ms·
"We’ll be making sure we get performance of Active Record back to at least 2.3 levels before release." Why call it a Release Candidate if you still plan on twea
by dirtyhand 16y ago
"We’ll be making sure we get performance of Active Record back to at least 2.3 levels before release." Why call it a Release Candidate if you still plan on tweak more stuff?
- sigzero 16y agoI don't think you are supposed to question DHH or what his name is.
- sigzero 16y agoWow, ok. It was an attempt at humor. So now my question is is HN not the place for that? Or do HN folks generally get behind RoR? Or...do I just need to be more thoughtful and not thoughtless in my postings? Help me be a better HN commentator, please.
- deleted 16y ago[deleted]
- JangoSteve 16y agoIf you get down-modded to 0, then you know you did something wrong. Humor is typically hit or miss, sometimes it kills, sometimes it doesn't. That being said, it is an online community and standard mob-rule still applies. I wouldn't dwell on a -4 too much (especially if no one will even comment to tell you why they down-modded). It happens, and no you're not a bad person ;-)
- ramchip 16y agoYes, and it is my impression that the downmodding has become very aggressive recently. It's not for rude posts only anymore. Just looking at the above poster: he adds a polite request for explanations to improve his posting, and yet his reply gets brought down.
- jawngee 16y agoAgreed * 100
- detst 16y agoHumor is often OK. I suspect the problem here is that your comment can be taken in an antagonistic tone that many people have in regards to DHH and the 37signals philosophy. That sort of tone is generally not accepted here, especially as a one-liner without substance.
- blantonl 16y agoI read that as "that sort of tone is generally not accepted here in regards to the 37signals philosophy."
- detst 16y agoIt was meant as that sort of tone is generally not accepted toward anyone/anything, especially as a one-liner because it doesn't add anything to the discussion. It was probably perceived that way because there are many people that have that sort of attitude toward DHH and 37signals. So any intent of humor was lost. It has nothing to do with agreement or disagreement with their philosophy.
- sigzero 16y agoOkay, I get that. It really didn't bring anything to the table. I will remember that. It wasn't meant to be antagonistic though. Just for the record.
- bbwharris 16y agoIn other words, this isn't reddit.
- bbwharris 16y agoMy point goes deeper - reddit hates RoR. Mention ruby and you will be trampled. The OP is seemingly negative on Ruby (which is cleared up through subsequent comments) and he gets trampled. When I say "this isn't reddit" I mean, there isn't the same RoR hatred here that one notices there. That's all.
- jawngee 16y agoAbout a year ago, yes, that would have been good, but HN has sort of been overrun by a gang of douche bags since then, so no, try not to be funny.
- dhh 16y agoBecause we're not going to change the interface to make the internals faster. And we might as well spend the time that the RC is out there looking for bugs to make things faster as well.
- sandofsky 16y agoThis may be a source of confusion. In most circles, release candidate signifies that this should be the final release, and will only be changed if new bugs emerge.
- avar 16y agos/Most/All/. I've never heard of a release candidate meaning anything else, it's something you'll release as-is with a non-rc version unless critical bugs emerge. This is a beta, not a RC.
- jolan 16y agoThink of it as a Rework Candidate then.
- bobbyi 16y agoThe exact meaning of terms like "beta" is subjective, but "release candidate" has the it right there in the name. It's not a release candidate if you literally state that it is not a candidate for release.
- blaix 16y agoExactly. Not to mention if you know you're going to be working on it, there's always the chance new bugs can emerge as a result. If I install the final version I'd expect that means it's the exact same version as the most recent release candidate and no critical bugs were found during that period. Not the most recent release candidate, plus a bunch of tweaks that were made while everyone was testing. And if you're already assuming there will be another release candidate before a final, then this isn't a release candidate.
- rufugee 16y agoI suspect this release is in response to some of the uproar (http://news.ycombinator.com/item?id=1545773 http://news.ycombinator.com/item?id=1545773, albeit dead) on the Rails list about the lack of a release and general lack of communication between the core team and the community regarding when a release might be expected.
- dhh 16y agoHeh, if only it was that easy to get a release of Rails to happen! I'd use that more often myself. This release happened because we have a candidate that's close enough to release that we wanted to get it out.