Comments on: The Web Stack

By: DaNmarner

DaNmarner — Fri, 05 Nov 2010 04:52:51 +0000

HTML5 + ECMAScript5 + CSS3 = “HEC”

By: Stephen Schneiter

Stephen Schneiter — Tue, 29 Jun 2010 19:24:18 +0000

I have to agree with Nancy, Web Stack does make me think of pancakes! But then again I like cooking, and in cooking there is a phrase called the “Holy Trinity of Cooking” referring, at least in the South more specifically New Orleans, as equal parts of onion, celery, and green peppers.

It would stand to reason then that we could refer to the term of the “Web Trinity”. They go together hand-in-hand. Thoughts?

By: Mark Blackman

Mark Blackman — Mon, 21 Jun 2010 14:25:24 +0000

I favour either ‘browser stack’ or ‘render stack’ or ‘display stack’ or ‘UI stack’ over ‘web stack’ which implies a lot of things way outside the UI to my mind.

By: David Goss

David Goss — Mon, 21 Jun 2010 12:27:38 +0000

You could call these kind of apps “browser-based”. That accounts for the technologies are dealt with by the browser e.g. markup, CSS, JS but excludes server stuff and native applications (although I suppose it includes plugins). Also, I think most regular people would get what “browser-based” means, so it wouldn’t have to be an industry “in-word”.

Does it really need an acronym or a cool name? (not moaning, just saying)

By: David

David — Sat, 19 Jun 2010 21:00:13 +0000

I like BOBAFETT myself.

By: The State of HTML5 Apps

The State of HTML5 Apps — Thu, 17 Jun 2010 17:10:27 +0000

[...] Respected web design consultant and author, Eric Meyer, has started talking about the concept of Web Stacks — and we’re in a situation not unlike the beginnings of Ajax: A few people are already [...]

By: James Sarmiento

James Sarmiento — Mon, 14 Jun 2010 04:11:52 +0000

Within our office, I developed a habit to use the term ‘core front-end languages’ to define HTML, CSS and JS altogether. But after reading this and the rest of the comments I’m liking to form it as ‘core web stack’. What do you think?

By: Michael Lehmkuhl

Michael Lehmkuhl — Mon, 07 Jun 2010 00:52:22 +0000

+1 for “browser stack” or “web client stack” or maybe “client-side stack” (of the three, I prefer “web client stack”)

Reminder that the origin of the term “web” stems from the interconnectedness of the various nodes on the network. I’d suggest that presentation of and interaction with the data and UI of those nodes is a significantly different animal than the network itself.

Sidenote: I prefer one of these terms to “HTML5 apps” because the latter is inherently dated to roughly the present time. When the next big advance in front-end web tech comes along, it will become outmoded.

Sincerely,

An irked server-side developer
;-)

By: Alex Kessinger

Alex Kessinger — Fri, 04 Jun 2010 07:31:32 +0000

PPK is calling them HTML5 Apps. Quick, meeting of the internet-buzz-word society: fight.

By: John Larsen

John Larsen — Wed, 02 Jun 2010 09:42:37 +0000

Web Client Stack

Web Front End Stack gives WebFESt

By: Nancy

Nancy — Sun, 30 May 2010 02:23:28 +0000

Thanks David!!!! I am so glad Eric is busy getting beyond this point….see how long it would take me to get past this point??!

By: David Hucklesby

David Hucklesby — Thu, 27 May 2010 17:40:12 +0000

Just a note to say that I love Nancy’s CJAX idea. Probably too derivative to catch on, but I think it’s pretty inspired…

I love standards–there are so many to choose from.

By: manuel

manuel — Thu, 27 May 2010 17:10:04 +0000

(And it should be noted that HTTP isn’t actually required for what I call the web stack—one can load pages directly from a device with no web server involvement, and still work. Is that the web? Hmmm.)

Eric, I'm surprised you don't consider HTTP to be a core part of what you define as “the web stack”. If you exclude HTTP, it's not the Web. You may as well call it “shiny stuff in a browser”. Some would go as far as saying that your web stack is what's optional, rather than HTTP. I don't agree with that view, but I do think that both are required. In practical terms, HTTP response headers will have a direct, visual impact on how the page is rendered in the browser. So being able to understand and manipulate those headers should be a required skill for a front-end coder. The absence of HTTP as a topic in front-end coding curricula causes many coders to reach dead ends when debugging, not knowing how to make use of Firebug's Net tab. I'm thinking stuff like encoding declaration conflicts, wrong mime types, missing resources, content negotiation, and of course ajax debugging.

By: Hector Hurtado

Hector Hurtado — Wed, 26 May 2010 04:58:39 +0000

Coming back to it…

“the collection of front-end web-standards technologies” = front-end standards.

In the context of web, anyone should understand what this implies.

By: Tami

Tami — Mon, 24 May 2010 22:46:39 +0000

I like the term web stack. The moment I heard it the first time I knew EXACTLY what it was. And it is a much better alternative to incorrectly calling all the new css3 and javascript HTML5 (yer previous post). Like Bob, I too, come from a background that calls upon the network stack term ; but to me that’s just a bonus; it makes the concepts of layering structure, presentation and behavior crystal clear.

So I say go for it, call it “web stack”. I’ve already started to.