ahoyhere

21 ms·

151.
by ahoyhere 14y ago
Yes, the wording is sketchy, but are you aware… * one of the reasons HFCS is so prevalent in the US is because it's effectively government subsidized? * which is also why the worst foods are often the cheapest? * that HFCS is in all kinds o
152.
by ahoyhere 14y ago
It's strange to me that you are comparing HN to traditional media. Mostly* the editors of Hacker News are readers. The readers choose what they want to read. The readers have spoken. It's too bad you disagree with the people who voted it up
153.
by ahoyhere 14y ago
"But what if you end up working on a product for a company that never makes them any money at all?" This isn't something that happens to you, this is something you choose. It's your responsibility as a consultant to pick your clients carefu
154.
by ahoyhere 14y ago
You (and the other commenters with similar strategies) are wasting productive years of your life at jobs like these. You should go on a serious job hunt for a new position, and leave these toxic wastelands before they permanently affect you
155.
by ahoyhere 14y ago
I wouldn't hire a freelance tester, because it's so important, we all do testing in our business. I expect every freelance developer I hire to test everything thoroughly (and I don't just mean unit tests). They're either full-service, or
156.
by ahoyhere 14y ago
Do you really think teens today are power users? Every generation since I was a kid thought their kids were tech geniuses; having interacted with them, I know it wasn't true. So kids today use Facebook and Instagram and Snapchat. And Tumblr
157.
by ahoyhere 14y ago
Americans don't ferment or even soak their grains, which the Weston A Price foundation (and many others) believe is one of the reasons Americans have so much discomfort/illness to do with grains: http://www.westonaprice.org/food-features/l
158.
by ahoyhere 14y ago
No, it's not an American thing, it's an ego thing, and America has lots of great people and also a lot of huge egos and not a lot of cultural taboos to reign them in. Some call this the "rockstar" or "brogrammer" problem, but you'll find it
159.
by ahoyhere 14y ago
Nobody is unique. If you only love her because she's unique, that's a… wait for it… identity problem.
160.
by ahoyhere 14y ago
> Personally, I think the overt bias problem is so bad right now See, that's where we disagree. I have watched many more men get torn down in violent fashion, neglected, and excluded, than women. I think the overall tech culture sucks p
161.
by ahoyhere 14y ago
What we think and what there's evidence for are diff things. Obviously everybody's entitled to their opinions. There is research that suggests, however… * priming people to remind them that they belong to a stereotyped group actually causes
162.
by ahoyhere 14y ago
I very much agree with the premise but she's not a very clear writer. I think she assumes the reader already knows what the problem is. My take is that the more people focus on identity ("female" "founder" "hacker" "HNer" whatever), the les
163.
by ahoyhere 14y ago
That would be a great move. Basic Marketing 101: if you try to attract everyone, you will inevitably get a lot of people for whom the product is not ideal, and then they will be angry. And then there will be backlash. Better to build your f
164.
by ahoyhere 14y ago
If you don't have a system / recipe in place for rolling out new servers, having the newest framework is really not going to help you all that much. That said, we run our current Rails 2.x products on shared servers (Rackspace). Their defau
165.
by ahoyhere 14y ago
OK, Charm was a live interface for handling support threads. New messages would show up when we swept them in from your inbox via POP/IMAP (max lag: 5 min). You'd leave Charm open, messages would appear. If you work in a team, and say your
166.
by ahoyhere 14y ago
> For example, you tend to have a significantly snappier user interface without having to resort to complex and error-prone nested caching schemes. Depends on how you define "snappy"… the ability to use a lot of seemingly live interacti
167.
by ahoyhere 14y ago
In case anyone reading this exchange isn't privy to the facts of the matter: Thomas doesn't "constantly" "attack" libraries "over 2k in size." He's a core team member of Prototype, wrote/"founded" Scriptaculous, scripty2, and Zepto. All sig
168.
by ahoyhere 14y ago
Whoever's down voting me, see Jacques' line about editing his own comment to be less inflammatory. He admitted it. You're not achieving anything here.
169.
by ahoyhere 14y ago
Ember is not marketed as being for a specific type of app, and not for others. The sole hint to kind of app is "ambitious apps." As a reader, that seems like a challenge. Oh, I don't think ember is right for me? Must not be ambitious. Nowhe
170.
by ahoyhere 14y ago
How on earth do you get from "Rails 2.x will be deprecated sometime in the future, they say" to "your server is down 6 hours"? Do you think anyone reading this is coding (and updating libraries) live on the server? This is Rails, not PHP we
171.
by ahoyhere 14y ago
Nope, we aren't - and won't be. Friends don't use ad hominem attacks on friends.
172.
by ahoyhere 14y ago
NB: My husband isn't a native English speaker. His point was that he wrote about our experience with a specific app and that the bulk of jacquesc's argument was "Thomas rails like a zealot" and implies Thomas is an old dead horse (?), and o
173.
by ahoyhere 14y ago
Ah, yes, one word changes characterizations like "railing" and "zealot" into… a slightly (slightly) subtler ad hominem. But still an ad hominem.
174.
by ahoyhere 14y ago
Yes, I believe you just summed up the blog post in question, only without the supportive details. :)
175.
by ahoyhere 14y ago
Rendering anything but the simplest DOM templates from JSON can be extremely slow. We so wrote a book on JavaScript performance -- runtime performance, not simply asset delivery. In that nearly 4yo book, we recommended against templating. A
176.
by ahoyhere 14y ago
How could you know enough to accuse us of being "cowboys"? For the record, we chose carefully… after deciding to build fresh from what we had, to start with a live (client-side MVC) code base instead of shoehorning in AJAX interactivity her
177.
by ahoyhere 14y ago
After years on the bleeding edge, our motto is: "Use what works. Don't faff about with shiny new toys which don't benefit the customer." Ask any of our customers if they care that Freckle is on the simpler Rails 2.x. Or ask patio11's custom
178.
by ahoyhere 14y ago
If your app is heavily interactive, you'll probably find (as it grows) that the initialization of the DOM is the least of your troubles.
179.
by ahoyhere 14y ago
Not when you consider the original blog post, which addressed the question of "Why not let the server be the data store?" Among the other "points"[1] jacquesc raised. [1] anyone who wants to pretend to have a serious, rational discussion --
180.
by ahoyhere 14y ago
We DID build Charm with client-side MVC from the get-go. That's exactly the experience Thomas wrote about as being a problem. Note that Charm was not "read heavy" -- it was totally interactive and doing a lot of real work; we did live (emai

More ›