marizmelo

I just cited markdown as complement to git. Git is a command line tool as is SSH (don't talk about GUIS for Git, that is not the case). I never said Unix is used exclusively by extraordinary people only (Ubuntu and others are an example), but the majority of people still use Windows.

Have an Unix/Linux background makes it easier to get started because you already know what they are talking about.

My personal opinion? Windows sucks (just to be clear, that is me).

I don't know who copied who: http://color.aurlien.net/

Sounds like a well elaborated excuse to me.

It was about time. Webkit is becoming the de facto browser engine. People will say that this kills competition, but competition is just good when brings better alternatives, Opera is not the case.

GitHub is fantastic if you have an UNIX/Linux background. I can understand the scary felling of someone that uses Windows on daily bases (for example) and suddenly have to work with SSH, GIT, Markdown, etc. I love GitHub but I don't think it is made for ordinary people. One day maybe it will be.

Sorry about what happened with you. The only why you could get the money is to had the PayPal account linked with one account in Venezuela instead of US. According with your F1 status (and mine) you cannot earn any money in US while studying, unless you get authorization from school to work out of campus (CPT), or after conclude your studies (OPT). Even under CPT/OPT you cannot earn money other from other place than the place you work on. Sorry, I wish you the best luck.

Well.. didn't Apple got some money from Samsung recently over design rip off?

The same can be applied over web design.

If you don't believe me go ahead, make an exactly copy of Apple.com, put your logo on it, and advertise as your website.

I did one with a friend while in DeAnza College, it was made for that specific college. But as people pointed out, its seasonal. http://zepply.com

Here in Mountain View

Ratchet powered site fetching HN rss feed: http://jsbin.com/atuzes/1/

Java is an excellent language, it has a elegant syntax, but... it's not made for web development. JSP/Servlets development is a joke.

+1 for this, I thought the comments were actual comments about the book. Usually comments are placed on the bottom of the page.

Since kindle fire, the books can be posted in colors :)

why not make available on Amazon as kindle version? I always think twice before share my card info on random websites.

Epic game. I remembered the discussion about ban the game or replace the humans with zombies or something on version 2.

Great idea, it does look like the Tron bikes. I think putting the front and rear lights will attract more pledges.

such a shame... politics in my country sucks :(

300+ comments... seriously?

PHP is a language with problems like all others (c, java, python, etc). It can be used for good or for bad like any other programing language. All the problems on the article are well known by decent programmers.

PHP is out there, use if you want.

Go write decent code... stop nagging.

yawho?

Creating confusion among developers just because you want to release "fancy HTML5 stuff" doesn't seem to me as a good idea.

Why not first implement these new features on your own browser as "developer version only", and prove that they work and do benefit users and the web in general? I believe that is the way you establish credibility and acceptance of a particular feature.

I am not against the release of all these amazing things, but I am against the way they are currently doing it.

If the proposed features do not have defined and W3C-agreed set of names and properties associated with those features, they should not be released to end users.

I don't want to see something like "only for IE" in applications and websites anymore. The problem is still small for now, but it can become huge if this bad practice doesn't stop.

Why do we have those prefixes in the first place? Ok, ok, test new functionalities is a good thing, but create bad practices among developers it is not.

All the problems with IE began when they (M word) started their with own implementation of javascript, CSS, and even HTML (automatic close for tags is not ok people, developers need to learn).

It is not your (browser vendors) responsibility to define your own interpretation of the standards. We have organizations that take care of this for you. All the problems involving incompatibilities began with browser vendors trying to "simplify" developers life giving their own version of the "standard".

If a new functionality is not part of the standards yet it must be a reason. Why not respect that and avoid all sort of complications?

Why the rush?

Force organizations to release early pieces of work will generate bad industry standards.

Do not like the way how one standard is defined?

You will have to swallow. - by brazilian team couch Zagallo