codebeaker

10 ms·

121.
by codebeaker 10y ago
Don't take my harsh criticism personally. I too enjoy to build things for the joy of building, and I respect your achievement. I just doubt the world really needs what you built, perhaps because I'm not your target audience, and
122.
by codebeaker 10y ago
Did you reply to the wrong parent? I wasn't making any statements about the quality of password generation. I was replying to address two of the three points that these people invested 6 months to build YAPPM (Yet Another Proprietary P
123.
by codebeaker 10y ago
1Password's format is also documented [1], though I'm not aware of any 3rd party clients to parse/work with it. That's actually a thing I was thinking about writing (I commented about trying to write something in C++14 i
124.
by codebeaker 10y ago
Thanks, that page looks like hell, but I recognise a few terms. http://clang.llvm.org/extra/clang-tidy/ is much more approachable, and gives a solid overview. The introductory sentence gave me project-naming cance
125.
by codebeaker 10y ago
I really wish there would be a linter (I realise it's probably a nearly impossible task) which would complain when you use legacy, unsafe language features. As someone who doesn't work in C++ or have the benefit of 10 years experi
126.
by codebeaker 10y ago
Curious too, the phrase is very widely attributed to him, if it's falsely attributed, I've been unknowingly contributing to the misattribution!
127.
by codebeaker 10y ago
somewhat arbitrarily choosing your comment to reply to, I noticed you're picking on the idea of buying a house being an investment, rather than a simple alternative to rent. For me, the motivation for owning a house isn't so much
128.
by codebeaker 10y ago
Project site has some pretty aggressive scroll hijacking, it was basically unusable on my macbook 13" under Chrome... Guys, just drop the scroll hijacking.
129.
by codebeaker 10y ago
I thought the general consensus amongst people, including the general HN crowd was that it was better to allow the w3c to specify a "black box" with well defined inputs and outputs. Allowing vendors to slot in their own (probably
130.
by codebeaker 10y ago
I have a food intolerance based allergy/autoimmune issue which is under a broad headline of "Non IgE mediated autoimmune disorder".. manifestations are depression, fatigue, chronic skin issues (on my face :-(). I've been
131.
by codebeaker 10y ago
Could you share a product link for whatever bluetooth button you were using, that sounds like a product I've wished existed for a long time and failed to find in the market. I remember an old wireless/30-pin connector for my iPod
132.
by codebeaker 10y ago
I've had something on the tip of my tongue since seeing the parent comment last night - I think this is close https://en.wikipedia.org/wiki/Spiral_of_silence but it doesn't seem to say too much about when t
133.
by codebeaker 10y ago
That's pretty much what we did! The fact that the `capistrano-harrow` code is a dependency rather than being embedded into Capistrano itself was supposed to benefit people by allowing us to experiment with tasteful integrations witho
134.
by codebeaker 10y ago
> My understanding of this phenomenon is that only people with extreme views comment. I believe so too, we have much more positive feedback from new customers from the exposure this post has brought than we have negative. In either cas
135.
by codebeaker 10y ago
> If people are concerned about the gem installation (and not the promotion itself), I can suggest that you promote harrow differently. Maybe put it as part of some command's output. Like "Cap by codebreaker (thanks to funding
136.
by codebeaker 10y ago
That's the question we're trying to answer now. We've been maintaining Capistrano with effectively zero data about our users since the project's inception. HN always has very extreme, and usually very negative reactions
137.
by codebeaker 10y ago
> An additional point is - what if I have another CI gem that conflicts with capistrano-harrow but not capistrano? We could find synthetic cases if we looked, Gem conflicts aren't unheard of and everything is name spaced. Fortunatel
138.
by codebeaker 10y ago
> From an engineering point of view it should be a separate gem... Absoluitely, this isn't an engineering decision it's to finally test and see if there's a market for people to support open source now that we've buil
139.
by codebeaker 10y ago
I appreciate your candor educar. I'm also on the fence with some software: - iTerm2 prompted me to opt-in to some pre-beta phase, it was widely discussed on HN and the author was criticized. - Just this week homebrew announced they int
140.
by codebeaker 10y ago
Those are certainly valid points, and they don't fall on deaf ears. Through a mistake when failing to push to the upstream remote this gem caused exactly that problem for someone yesterday[1]. Fortunately I was able to fix it in a few
141.
by codebeaker 10y ago
If you're ever in Hamburg look me up and I'll buy you a beer. I don't hold anything anyone tweets against them, I'm glad you were able to sort the upgrade in spite of my incompetence :)
142.
by codebeaker 10y ago
> I thought your response was fine :-) I see what you are saying now - basically that was part of Capistrano already, so moving it to its own gem is a very good idea. Thanks for the vindication, if it wasn't an external gem, I'
143.
by codebeaker 10y ago
> For example, RSpec 3.4 will use `coderay` for syntax highlighting [1] if it’s available, but doesn’t make `coderay` a dependency of the `rspec` gem. Absolutely true, two observations: - I've often wondered about syntax highlightin
144.
by codebeaker 10y ago
Hey kawsper, good to run into you on HN. Thanks again for reporting that last year. I was afraid people would assume we did it for maximum "reach", honest truth is that I'm just not very good at Javascript and forgot how cook
145.
by codebeaker 10y ago
Right, we'd like to be able to fix bugs in the harrow integration without having to re-release Capistrano. The other gem dependency is a mature, well loved project in it's own right which the maintainer generously offered to main
146.
by codebeaker 10y ago
Capistrano maintainer here, I gave a more comprehensive answer in this thread [1], I hope that answers some of your questions. Specifically to address your point about having "nothing to do with the tool for the vast majority" the
147.
by codebeaker 10y ago
Seven year Capistrano maintainer here. I'm the person who is responsible for Harrow, the gem plugin and the response to the issue linked at GitHub. The point of separating the gem is so that we don't have to bump Capistrano&#x27
148.
by codebeaker 10y ago
BTS = "Base transceiver station", it's not mentioned in the article.
149.
by codebeaker 10y ago
This must be solved with `gulp-plumber` which is actually about a 10 line hack around fixing some underlying bugs with merging streams if memory serves.
150.
by codebeaker 11y ago
Also a big dan of the design but I do find it to be much too dark, I'm in a well lit office, with a calibrated Dell UltraSharp display and the site's color scheme is really quite hard on the eyes, even if the design itself is be

More ›