Science Project Quadruples Surfing Speed - Reportedly

johnp. writes "A computer browser that is said to least quadruple surfing speeds on the Internet has won the top prize at an Irish exhibition for young scientists, it was announced on Saturday. Adnan Osmani, 16, a student at Saint Finian's College in Mullingar, central Ireland spent 18 months writing 780,000 lines of computer code to develop the browser. Known as "XWEBS", the system works with an ordinary Internet connection using a 56K modem on a normal telephone line. " A number of people had submitted this over the weekend - there's absolutely no hard data that I can find to go along with this, so if you find anything more on it, plz. post below - somehow 1500 lines of code per day, "every media player" built in doesn't ring true for me.

Comments

Extraordinary claims require extraordinary proof

[GregWebb]

They've claimed that a 16 year old student has written 780,000 lines of code. That it combines a browser accelerated way beyond what anyone else has ever claimed (and that could potentially run faster, just doesn't yet), multi-format media player (actually, I don't want to watch DVDs in a little side window while browsing the web, thanks...) a meta search engine and an avatar-based help system?

That's massive work _and_ a revolutionary breakthrough. If he's that good - and in a way that others hadn't thought of despite the efforts of several of the world's largest companies going into browser and network research - then this is remarkable. But without hard evidence (or even a mention on the competition's admittedly poor website) this just sounds way too much like a scam.

Pattern matching?

[horza]

I'm surprised that the majority of posters are resorting to unimaginative "what BS" posts instead of thinking up innovative ideas. Ok, here is my idea:

Most web pages have a lot of static content in, especially menus etc. You could start rendering the page immediately from the cache from the last page and rerender afterwards as the new page starts to differ from the cached version.

As the page comes in, keep switching to the page that is closest to same structure in cache (ie predominantly on the HTML tags). Don't render the text until the initial few chars are confirmed by the version downloading, then progressively render that (ie show old version then modify words where they differ).

This would have the effect of progressively rendering the page as a whole much like those progressive GIFs. It would show a large speedup on pages that contain tables, as most browsers these days won't render a table until it has recieved the /table.

This would be a 'faster' browser with no compression or pre-caching.

Phillip.

Re:have you ever been 16

[dubstop]

Yes. For a year during my mid-teens.

I don't deny that it's possible to write 10,000+ lines of code in 5 days but, unless you're some sort of prodigy, I would have serious reservations about the quality of that code.

All of us who chose development as a career because we love to write code, rather than just because it's a well-paid and relatively easy-going job, have at some time cranked out amazing amounts of code in a short time. My doubts are caused by the duration. I don't believe that it's possible to sustain that sort of output for that period of time.

Then why the hell did you post it?

[kramer]

there's absolutely no hard data that I can find to go along with this, so if you find anything more on it, plz. post below - somehow 1500 lines of code per day, "every media player" built in doesn't ring true for me.

Twits who make up bullshit stories like this thrive on attention. By posting it on a major site like slashdot, you give him exactly what he wants. Just use a little restraint, and try not to post the stories that are obvioulsy fake -- like this one, and the one about Masters of Orion 3 beign out soon (grin).

Re:Basic maths.

[Angst Badger]

Still, sustaining 1,500 LOC per day for a year and a half ... that's beyond the productivity level of anyone I've ever seen. I personally have managed 4,500 per day for a period of about a week on occasion ... but I wasn't sleeping much during that period.

I broke 1,000 LOC per day for about a week while working for an unnamed gigantic CPU monopolist. I was behind schedule, over budget, and had a hard deadline, and the code itself was fairly repetitive and not terribly efficient. Ordinarily, I'd figure I produce closer to 250 LOC per day during a normal coding period.

Provided this story isn't complete hogwash, my guess is that the reporter asked the boy about the writing the program and he answered that it consisted of 780,000 LOC and took him a year and a half to build. He probably neglected to mention that 90% of those lines were in libraries written by other people. He may not have even intended to be deceptive in any way, figuring that any fool would know that was the case, but not realizing that the reporter was a fool.