71–80 of 85 posts
The line at the top of the page, for me, says "Undefined". Firefox 10.0.7, Windows 7. I debugged it for you - the outerHTML property isn't supported in Firefox function outerHTML(node){ return node.outerHTML || ( function(n){ var div = document.createElement('div'), h; div.appendChild( n.cloneNode(true) ); h = div.innerHTML; div = null; return h; })(node); }
would be nice to have a "none of the above" option for people who A) Do not use those languages or B) are not programmers who would like to help Every project can do with documentation help etc.
Earlier quoted context omitted.
Notice that selecting any language gives you a dismissive remark, not just PHP. But you're right in that it's probably not the best way to cast a wide net (unless they're intentionally selecting for contributors with a good sense of humor).
Except for Rust which takes you directly to rust-lang.org. I actually like the idea though. No language is perfect and people do seem to be a bit too sensitive of their favourite languages.
Earlier quoted context omitted.
Can somebody tell me reasons why UI designers or UX specialists are more difficult to outsource? I know that many open source projects have difficulties attracting them, but I really don't know the reasons (any reason designers working in this field gave me also should apply to programmers - thus they also couldn't answer this question).
I started writing a response about my experience as a designer at Mozilla and it got really long and I turned it into a blog post called "Code talks and designers don't speak the language." Thanks for inspiring me to come out of blog hibernation. http://skinnywhitegirl.com/blog/code-talks-and-designers-don...
One of the challenges of design education for developers is that developers are naturally geared toward rule sets, which becomes a problem when the designer decides to break the rules for a justifiable reason. Just like devs couldn't teach a designer to code in a day, a designer can't really provide all of the ins-and-outs of good design to devs. Perhaps education needs to be introduced to devs as to the value of UI/UX, rather than the specifics.
If you select PHP, you get "So you like your variable names to include dollar signs? That's cool, everyone misses Perl once in a while." Making smartass remarks about their language of choice is not a great way to initiate a relationship with a developer.
The remaining quotes: C++: "So you like long compile times and incomprehensible error messages? That's cool, we do too" Java: "So you're a believer in AbstractMethodFactoryBeans? That's cool, we all have our vices" Python: "So you enjoy the paradigm of backtrace-driven development? That's cool, everyone gets a bit tired of static typing once in a while" C: "So you think OOP is for hipsters? That's cool, we all get no…
Criticizing languages/paradigms is fine (the resulting flame-wars add a great deal of humour and interest to the world of programming) - but to caricaturize users of different languages as people suffering from certain negative traits is just ugly and leaves me with a bad taste in my mouth reading this.
I for one would not want anything further to do with this author or site.
Download Chrome. Make Mozilla as fast as Chrome.
they don't mention NSPR. is it dead? http://www.mozilla.org/projects/nspr/
Also, it's shared with other projects (Google uses it).
Earlier quoted context omitted.
Can somebody tell me reasons why UI designers or UX specialists are more difficult to outsource? I know that many open source projects have difficulties attracting them, but I really don't know the reasons (any reason designers working in this field gave me also should apply to programmers - thus they also couldn't answer this question).
I started writing a response about my experience as a designer at Mozilla and it got really long and I turned it into a blog post called "Code talks and designers don't speak the language." Thanks for inspiring me to come out of blog hibernation. http://skinnywhitegirl.com/blog/code-talks-and-designers-don...
Concerning point 3:
"Probably the most daunting question for projects without any design lead that has the trust of the team is, how do the devs know if the proposed design is correct? Without that trust, bugs quickly devolve into nasty arguments. How you build that trust has been the subject of entire books. But the question remains, who and how do you approve a mockup? The code review process works great for just that… code."
Developers also have nasty arguments about what code is correct/the better one etc. ;-)
So this argument also should in principle apply to developers - but developers don't seem to have any problem about that point. I don't know whether the reason is simply that developers have less a problem with conflicts?
But nevertheless: there are well-established principles to judge which code/software architecture is better (elegance, smallness, extendability etc. (all of these can be judged rather objectively) - which role these play, depends on the project). I think it would help project leaders if you suggested a similar process for judging design decisions. Just an idea. If this is a bad idea of me, suggest a better one.
Earlier quoted context omitted.
The remaining quotes: C++: "So you like long compile times and incomprehensible error messages? That's cool, we do too" Java: "So you're a believer in AbstractMethodFactoryBeans? That's cool, we all have our vices" Python: "So you enjoy the paradigm of backtrace-driven development? That's cool, everyone gets a bit tired of static typing once in a while" C: "So you think OOP is for hipsters? That's cool, we all get no…
While this is obviously intended to be humorous, I don't really care for the way it attacks the users of the language in such a mocking, patronising manner. Criticizing languages/paradigms is fine (the resulting flame-wars add a great deal of humour and interest to the world of programming) - but to caricaturize users of different languages as people suffering from certain negative traits is just ugly and leaves me w…