Jesse James Garrett Quotes

Ajax is an important development for Web applications, and its importance is only going to grow.

IT professionals have a responsibility to understand the use of standards and the importance of making Web applications that work with any kind of device.

Google is making a huge investment in developing the Ajax approach.

Because the competitive landscape of the web is such that the site which looks and works best gets the most traffic, developers and designers put a premium on the presentation of that content and let structural markup take a back seat.

Technically, web browsers can control what users see, and sites using Javascript can overwrite anything coming from the original authors. Browsers heavily utilize Javascript to create an interactive Internet; sites like YouTube, Facebook, and Gmail could be crippled without it.

Everybody who runs a Web site knows we're not assured of compatibility, and we could end up with a split.

We're actually helping advance HTML5 in some very concrete ways, such as Edge, which is in beta.

We at The Web Standards Project turned everything on its head. We said browsers should support the same standards instead of competing to invent new tags and scripting languages. We said designers, developers, and content folks should create one site that was accessible to everyone.

Many thought it was a fool's errand - that the browser companies were never going to listen to us. Others argued that, 'Users don't care if you use Web standards.' Well, of course they don't. They just know that your site works better.

It's not about HTML 5 vs Flash. They're mutually beneficial. The more important question is the freedom of choice on the web.

Even if it's not always the best markup, what are Facebook and Twitter? They're web standards with some scripts. They may not validate, but they're still CSS layouts and simple markup, and that's great!

Flash and HTML have co-existed, and they're going to continue to co-exist.

Validation is easy - you run your site through a validator, and it's either valid or it isn't. The rest of the stuff, such as whether my logo or the biggest headline should be the h1 in my HTML, isn't so easy and is subject to interpretation.

Ajax isn't a technology. It's really several technologies, each flourishing in its own right, coming together in powerful new ways.

Writing old school HTML code was never very much fun but now it's getting downright tedious for most people.

I'm not against Flash, and I love the work that people such as Joshua Davis do.

The Internet didn't become usable until Netscape because that gave the average person a user interface that was intuitive, simple, friendly - this made it accessible.

I knew a bit about the capabilities of HTML5 and have always had a preoccupation with technology. I wanted to delve deeper, to see what else it could do. The technology becomes the palette that you make the artwork with, your palette and your paint.

Real web designers write code. Always have, always will.

I have my team focused on the front end, working on the user experience, and making sure we have all the wiki-like tools people need to work on the site. We're just cranking away.

I did an early version of my site where it was virtually impossible to get through it, just as a statement about the web. But after a few laughs and some angry e-mails, I realized it wasn't doing me much good. I think the web has become more about the final product, not what it takes to get to it.

I think we're proving ourselves as we go along. The past several months our strategy has been evolutionary - making maximum advantage of our client browser, as well as our enterprise software for people who want to build Web sites.

I would have volunteered to work at Netscape. It was the center node of this new technology and the commercial ecosystem of the Internet.

I taught myself HTML.

Some things like the layout of the early VKontakte was very influenced by Facebook. Otherwise it could take ages for me to build, and I was not a professional designer.