tghw

77 ms·

781.
by tghw 17y ago
Apropos of your comment (and possibly the source): http://stevelosh.com/blog/2010/01/the-real-difference-betwee...
782.
by tghw 17y ago
I'm nowhere near fluent, but I believe "will be awesome" is Jobsean for "will finally be written in Cocoa".
783.
Feature sneak(shipordie.com)
1 points by tghw 17y ago|0 comments
784.
by tghw 17y ago
Isn't this an April Fools post?
785.
by tghw 17y ago
The post is as much a reply to you as it is a reply to your commentors. "Stupid" was used a little more liberally in the comments, and my post just exaggerates that for humor's sake. My main point is that it depends on your audience. For mo
786.
by tghw 17y ago
It's not that they can't , it's that there's a little more friction for them to. (Speaking of my websites, we've actually done the i18n necessary to make it usable from anywhere, but only after we knew we had that international demand.)
787.
by tghw 17y ago
No offense was taken in the reading and writing of these two articles. Just trying (and apparently failing) to humorously point out that if most of my users are based in the US, then I probably have bigger problems to solve than a Polish gu
788.
by tghw 17y ago
That's actually kind of what I was trying to say. Having people put in fake data to satisfy a validator isn't the worst problem in the world. There are probably much better things to be spending your time on. And, yeah, in general, CC valid
789.
by tghw 17y ago
OK, a credit card form is a feature that is very, very rarely used. The features that people will use frequently are still more important. If 5% of users have to lie and put California in as their state and 90210 as their zip...well, it's n
790.
by tghw 17y ago
Yeah, it's long overdue for a redesign. Made a couple changes that should make it a bit more readable. Sorry about that.
791.
by tghw 17y ago
Not to be rude, but I think you're having a bit of a reading comprehension problem. Nowhere did I say to block non-US users, as you've repeatedly asserted I did. What I am saying is don't worry too much about getting it right, especially if
792.
by tghw 17y ago
I didn't have any credit card forms to write, so it's OK, I had the time.
793.
by tghw 17y ago
Where exactly in the article did I mention blocking non-US "citizens"? (I think you mean users; most websites don't require citizenship verification.)
794.
by tghw 17y ago
Of course I exaggerate in the post, you're right that it'll probably take just a week to get coded up. (Which means three weeks, the way development often goes.) The question is whether or not that time is well spent, or if I would be bette
795.
by tghw 17y ago
I gave it a shot of my own. I didn't do all the permutations, and surely left out big swaths that I've never even thought of, but it's a start... http://hicks-wright.net/blog/stupid-american-website-owners/
796.
HFCS makes rats fat? A counterpoint.(foodpolitics.com)
33 points by tghw 17y ago|20 comments
797.
by tghw 17y ago
Take a look at http://www.foodpolitics.com/2010/03/hfcs-makes-rats-fat/ It seems that Princeton's press release greatly overstated the results of the study. It also seems that there are some valid questions about the methodology of the st
798.
by tghw 17y ago
If only Windows users were hardcore UNIX users...everything would be so much easier. No GUI code, no leaking GDI objects, no Java Swing, no WxWidgets, no cross-browser bugs (curl would be the only browser), no DPI scaling issues, no DLL hel
799.
by tghw 17y ago
All of the examples you give are functionality, not how the thing actually looks when it renders on the screen. Is there some way to write a test that determines whether my page renders correctly on Firefox, Chrome, Safari, IE 6, IE 7, IE 8
800.
by tghw 17y ago
For those specs, I'd much rather spend half as much on an Asus UL30Vt ( http://bit.ly/c9AxMn ), though I'm really waiting for the UL30Jt ( http://zedomax.com/blog/2010/01/08/asus-ul30jt-hands-on-revi... ).
801.
by tghw 17y ago
If you're considering cherry-picking, you're still thinking in an SVN mindset. We did the exact same thing for a while before figuring it out, with some help from a few people who had used DVCS longer. You just have to use it for a while an
802.
by tghw 17y ago
That's my point, this "ready" concept is just a holdover from SVN. There's no reason a commit has to be "ready" in any way. You can even say that in the commit message.
803.
by tghw 17y ago
The problem is easily solved with smaller, more frequent commits. In SVN, your changes had to be "ready to check in", which was this big, complicated ritual where you back up your changes, update, merge, check to see if the merge screwed wi
804.
The fighting's been fun and all, but it's time to shut up and get along(blog.bitquabit.com)
90 points by tghw 17y ago|74 comments
805.
by tghw 17y ago
States with applicable statutes (that I know of): * California Cal. Lab. Code 2870-72 - http://www.leginfo.ca.gov/cgi-bin/displaycode?section=lab&group=02001-03000&file=2870-2872 * Delaware Del. Code Ann. tit. 19 805
806.
by tghw 17y ago
I love the idea of the little guy doing it without a big publisher. The problem with that idea is the same problem that any indie artist has had: exposure. Publishers spend between 1 and 3 million dollars on a new book just for production (
807.
by tghw 17y ago
It was just a joke, no offense intended. Apologies to any Rubyist who was offended.
808.
by tghw 17y ago
>>> def print_a(inst): ... print inst.a ... >>> class Foo(object): ... def __init__(self, a): ... self.a = a ... >>> Foo.print_my_a = print_a >>> f = Foo(5) &#6
809.
by tghw 17y ago
The Python community is very vocal and explicit about the conventions developers are expected to follow, more so than any other language I'm aware of: PEP 8, Zen of Python, non-stop critiques about whether some code is "pythonic" enough.
810.
by tghw 17y ago
The "Rube" comment was a joke, not a serious insult. If it genuinely offended you, I apologize. On the other hand, if you're looking to be offended to prove a point about who is "flamier", you've succeeded.

More ›