Follow Slashdot stories on Twitter


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Re:Whew! (Score 2) 155

by dingen (#47189759) Attached to: Millions of Smart TVs Vulnerable To 'Red Button' Attack

I honestly don't understand why people would buy a "smart" TV instead of a monitor, surround sound speakers, and plug it in to a laptop or computer. How many people really use OTA broadcasts nowadays?

Yeah, because computers aren't susceptible to attacks at all. Everyone knows there's nothing more secure than keeping an internet-connected computer running 24/7 in your house.

Comment: Re:IE's release model is failing (Score 1) 173

That's why the iphone flopped when Apple decided it wouldn't support flash in an era where flash was pretty important.

But you see, it really wasn't that important at all. Flash was mainly used for 3 things: ads, video and games. Video and games the iPhone could do fine and ads nobody wants anyway.

It would be very different for real web stuff, as people can just install another browser on their devices. I think there would be quite a backlash amongst both developers and the general public if a vendor suddenly decides to artificially limit the capabilities of their web browser. In a way, that is what Microsoft is doing by adopting new features so slowly and their market share is but a fraction of what it used to be. People want to be on the platform that works.

But the larger view is its a catch-22; most developers won't use features that aren't widely available cross-platform -- so any major closed platform that sees those features as a threat simply can refuse to implement them, and most developers will in turn avoid using those features.

When I'm developing for the web, I don't even bother to look at what new-fangled nonsense Chrome has just released. My baseline is to only use features that are widely supported.

The difference between what's widely supported and what's new-fangled is fading with IE's decreasing popularity though. The world in which non of the new stuff was actually usable is long gone. Can you release a web app that uses Web Audio right now and you would serve about 80% of the market, including iPhones and iPads.

Comment: Re:IE's release model is failing (Score 1) 173

Your desire that you want the browser to be a 'platform for applications' is fine, but is not related to the release schedule at all. How come your long term desire can't be accomplished in slower bigger steps?

Because that makes it harder to correct mistakes. The current model of releasing small, frequent updates is a really powerful mechanism for developers to explore what works and what doesn't. The things that make it are adopted and become the standard, the rest is discarded. Google and Mozilla are really pushing the web forward doing this, but Microsoft isn't playing ball.

Windows, iOS, Debian Stable, and OS X Mavericks are all "platforms for applications" and none of them need 25 feature updates a year, but fixes yes... but not whole new releases with new features every couple weeks.

Not anymore they don't. But that's because those platforms are actually quite feature complete and have been for a long time, if not from the beginning. The web however is just barely starting to be able to render graphics and play sound. They've got a long way to go, that's why it would be nice if things didn't take another decade to mature.

The 'web' is no more going to bring about that future than Java did. Especially in a world where hardware vendors are actively seeking to prevent it. (ie Expect Apple to limit the functionality of its iOS browser the minute it starts to threaten app store revenue in a credible way.)

I highly doubt that. I think the moment a vendor starts shipping a lesser web experience in a world where the web is increasingly more important, they will see a drop in adoption and sales.

Comment: Re:IE's release model is failing (Score 1) 173

I don't really give a shit about new bleeding edge features though, I just want to see the standards met.

That's well and nice if you just want to make a document available through the web. But I want to web to more than just delivering documents, I want it to be a platform for applications. I want games in my browser, write code in my browser, image editing in my browser, audio processing my browser, everything I do in my browser. Why? Because *every single device out there* has a browser. I want a future where any applications runs on any device, running any operating system, any browser. That's when we can really use the best device for the job, instead of having to resort to the stuff that happens to run the software we need.

Comment: Re: IE's release model is failing (Score 1) 173

The point is that Microsoft doesn't include new features in those patches, they only put new stuff in major releases. There are simply too little of those to keep up with the competition and therefore Microsoft is still stalling the development of the web.

The end of labor is to gain leisure.