Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror

+ - Is the Web really the best way to build distributed applications?

Submitted by simonstl
simonstl (42816) writes "The Web grew up in a tough neighborhood, popular but infested with feuding constituencies and sprawled across multiple platforms. I argue that those challenges have created a best-of-breed solution, even if it doesn't look like the toolbox developers from more civilized environments expect. It's not just that the Web is what we have to do this work — it's that the Web is what we have to do this work because it learned lessons other platforms haven't yet even noticed."

+ - Has Flow-Based Programming's Time Arrived?

Submitted by Anonymous Coward
An anonymous reader writes "Flow-based programming keeps resurfacing lately. FBP claims to make it easier for non-programmers to build applications by stringing together transformations built by expert programmers. Many projects have already been using similar approaches for a long time, with less (or different?) hype. Is it time to take a closer look at flow-based programming?"

+ - Web founder asks what we should ask for since we're getting DRM

Submitted by simonstl
simonstl (42816) writes "Sir Tim Berners-Lee asks "If we, the programmers who design and build Web systems, are going to consider something [DRM] which could be very onerous in many ways, what can we ask in return?" He doesn't really answer the question, but maybe you can. Based on his story, though, I suspect that we (and the W3C) won't get much."

+ - The W3C Sells Out Users without Seeming to Get Anything in Return

Submitted by Anonymous Coward
An anonymous reader writes "Questioning the W3C's stance on DRM, Simon St. Laurent asks "What do we get for that DRM?" and has a thing or two to say about TBL's cop-out: "I had a hard time finding anything to like in Tim Berners-Lee's meager excuse for the W3C’s new focus on digital rights management (DRM). However, the piece that keeps me shaking my head and wondering is a question he asks but doesn’t answer:

If we, the programmers who design and build Web systems, are going to consider something which could be very onerous in many ways, what can we ask in return?

Yes. What should we ask in return? And what should we expect to get? The W3C appears to have surrendered (or given?) its imprimatur to this work without asking for, well, anything in return. “Considerations to be discussed later” is rarely a powerful diplomatic pose.""

Comment: Re:what are you even saying? (Score 1) 302

by simonstl (#43539197) Attached to: Stop Standardizing HTML

No, it's not new or novel, but it's exactly what I proposed... you can already mix your own tags into HTML and style and process them.

The article certainly made clear that I didn't expect CSS, JavaScript, the DOM, or a variety of other standards to go away. We just don't need to worry about HTML itself so much any more.

Comment: Re:what are you even saying? (Score 1) 302

by simonstl (#43537531) Attached to: Stop Standardizing HTML

Most of what actually mattered when HTML first appeared - presentation, behavior, and semantics - has already been refactored into CSS and JavaScript and WAI-ARIA.

The question today is whether you want to live only inside that hollow shell, or whether you'd like to look into extending it to fit your needs. CSS, JS, and WAI-ARIA will work just as well for your own markup as they work for HTML.

You're right that this shouldn't affect back-end technologies much at all. To them it's all just markup.

Comment: Re:language (Score 1) 302

by simonstl (#43537489) Attached to: Stop Standardizing HTML

Part of the headache is that they're designing during the standardizing process, making their best guesses at what might work.

Part of what I hope might come from this approach is that many people can try a variety things, and then standards can catch up to what actually worked. Browser vendors have sort of done that, but their experiments tend to have much larger consequences.

In seeking the unattainable, simplicity only gets in the way. -- Epigrams in Programming, ACM SIGPLAN Sept. 1982

Working...