An Even Faster Browser? 45
octavian755 asks: "Seems that a 16-year-old Irish student has created an Internet browser called XWEB,
which is the fastest browser known to date. This browser is said to be capable of boosting surfing speeds on a dial-up connection by 100 to 500 percent. What I would like to know is something like this even possible?" Update: 01/20 07:30 GMT by C : As folks have pointed out, this story is a duplicate. Also, a minor title gaffe corrected. Sorry about that.
Already Covered on /. (Score:5, Informative)
Damn, even I remember this one and I'm notorious for my short term memory loss. Who was smoking what when this one got posted?
It's so fast... (Score:5, Funny)
Re:Already Covered on /. (Score:5, Funny)
1) This is posted by Cliff, last time it was posted by Hemos. Isn't it a pity when those who blocked Cliff's or Hemos missed this great news? The news will be reposted by Taco very soon, so he majority who blocked both Cliff and Hemos will not miss it
2) Last time we don't have typo in the headline. This is very untolerable for slashdot readers
3) This time we've same article from other source. Slashdot editors must make sure they don't miss any reference to great news like that
4) Last time Hemos said 'Quadruples Surfing Speed', today Cliff found out that it can actually boost the speed up to 500% percent! This is definitely an improvement and should be posted as a follow-up
Re:Already Covered on /. (Score:1)
Scott
Not only.... (Score:1, Redundant)
point 2) Another slashdot duplicate. How fucking pathetic are the editors here??? (there go my moderator points)
point 3) Last time we discussed this, most technical people wrote this off as a joke.. No I don't need to read this article, I need to see proof.
Hey Cliff (Score:5, Funny)
You oughta, like, read Slashdot more often.
Re:Hey Cliff (Score:2)
Man, I wish I had mod points right now because you just made me laugh out loud. So eloquent and so spot on.
How is it possible to be so fast? (Score:5, Informative)
No, I haven't used it. But there are simple facts, like the speed of light. The thing is this: data can only be transferred so fast.
If I have a 56k connection, than the fastest I can transfer is 56k (I know there are other considerations, but that's not important). It's that simple.
There are some things that can be done to speed it up: cache things. Render things faster, but they are all stopgap measures. I don't care what it says, the fact is that you only get so much speed. Any more just is not there.
It's like saying my car gets infinite miles per gallon. I can improve things, but I still need some fuel no matter what I do.
Re:How is it possible to be so fast? (Score:2)
not true, even the speed of light can be broken, i.e.:
Re:How is it possible to be so fast? (Score:2)
Carmen may be an exception worth studying, but wormholes theoretically allow the speed of light to be effectively (but not really) passed by moving through a different kind of space. I don't recall what the currently trendy explanation is (out of universe different dimension, whatever), but it can't be broken.
And besides, if your pipe is a 14.4 modem, it's going to be slow. Like I said, you can cache stuff, look ahead, render quickly, but there's a limit to how fast things can be. It's finite. Sorry.
Re:How is it possible to be so fast? (Score:1)
Scientists have sent light signals at faster-than-light speeds over the distances of a few metres for the last two decades
Just thought I'd add that.
Re:How is it possible to be so fast? (Score:2)
It's called Quantum duality [attbi.com]
It could just be an artifact though.
Re:How is it possible to be so fast? (Score:2)
Darn, I guess I will never see my *infinately fast* browser. I guess I should give up on browsing the web altogether.
So, what you're saying is (Score:1)
Re:How is it possible to be so fast? (Score:1)
Er, compression? My webserver can move a 300K html file to a dialup user in about 3 seconds, because mod_gzip compresses it to 7K.
Re:How is it possible to be so fast? (Score:3, Interesting)
Let's profile this rather than just flame. The article claims a 100% or greater speedup, which is of course twice as fast. If the download time is half of that, and as you say it cannot be shurnk further, then you can still realize a 100% gain by getting the other half of the work to approach zero time.
Very fast rendering (but very broken? I don't see anything saying this browser is actually usable or at all standards compliant...) is pretty much the main way to bring down that chunk of time. Good caching can minimize the amount of data transferred, and as another commenter noted, if the browser can take advantage of mod_gzip they'll get a significant download reduction on many sites.
Stopgaps? Sure, but no one is saying that things will be infinitely fast. Have you actually spent any time profiling what portion of the time is spent on which tasks in getting & displaying a web page? If the average downloading time is 50% or more then okay, your flame scorched the right target. But if other factors can accumulatively account for 50 or 80 percent of the work time, then your objections become just one of several relevant bottlenecks.
The thing is, whether or not you have ever used software profiling tools, I'm sure that the developers of the major browsers all have. That's what makes me skeptical of this. If there are any major gains to be made in download compression, caching, rendering or other areas, I would think that optimizations from each area would have shown up in the mainstream browsers by now (and in fact, all of this does exist in some form). While there is still room for improvement -- as the release of Safari clearly shows to the MSIE team -- extravagant claims are unlikely to be true.
I skipped out this article the last time it was posted, so may be asking what is a FAQ by now, but can anyone provide a better source of material on this browser than Rupert Murdoch's little puff piece? It would be interesting to hear how this browser supposedly works, against which browsers it supposedly does so much better, and whether those gains hold true as you adjust variables like bandwidth (does the gain wash out at DSL or T1 speeds?) and processing power (does the gain get even better on a very fast computer?). It would be interesting to see which browsers it was benchmarked against, and if there was any obvious problems with them when the tests, if any, were conducted ("what, I shouldn't be running against mod_inflate_data on that side?" :).
/. & vacations (Score:4, Funny)
And I bet he did it... (Score:3, Funny)
I'm really impressed here.. (Score:4, Insightful)
The usual excuse; this is such advanced, groundbreaking stuff and he doesn't want anyone to steal his ideas until after he's been given some development capital.
Scam. Scam. Scam...
deja vu (Score:1, Redundant)
Not even any more info either. I'm sure all of us would like to examine this browser just to see if it is true.
More info: http://radio.weblogs.com/0103966/2003/01/14.html/ 2003/01/13/190872
Even has every media player: http://www.taipeitimes.com/News/worldbiz/archives
http://www.esatbtyoungscientist.com/
Re:deja vu (Score:3, Funny)
Not even any more info either. I'm sure all of us would like to examine this browser just to see if it is true.
More info: http://radio.weblogs.com/0103966/2003/01/14.html
http://www.esatbtyoungscientis
Uh-oh. It's deja vu all over again. Someone call Yogi Berra...
It's easy making it faster (Score:4, Funny)
Easy!
Re:It's easy making it faster (Score:1)
Look for google's cache whenever it asks for a page. SpeeeeeeD!
Re:It's easy making it faster (Score:2)
All you'ld need is a broadband connection and a proxy to compress all data with Mod_GZIP...
Lowering slashdot standards (Score:1, Redundant)
Re:Lowering slashdot standards (Score:2)
Why not? [slashdot.org]
The easy explaination... (Score:4, Insightful)
The other explaination is to modify Mod_GZIP or similar on the server side to report as some odd name (Mod_XWEBS might be a nice one)
The other features (Built-In TTS, Access to multiple search engines, etc) are all fairly standard in the browser market now.
Now, I don't think it's been said enough...this kid supposedly did 1.5 million lines of code in 2 years...
Which would be ~2054 lines of code per day... or 85 lines of code an hour...
If we assume that he needs a minimum of 6 hours of sleep per night, that brings it to ~115 lines of code per hour...
This doesn't allow for eating, testing, rewrites, attending classes, reading documentation, etc...
Now, even the best coders only do ~100 lines of code per day...
I refuse to belive that this kid could do the work of 20 coders over a 2 year period...
You'ld think that this kid would release a binary only distribution for testing so that everyone would stop doubting his sincerity.
Re:The easy explaination... (Score:2)
"If we assume that he needs a minimum of 6 hours of sleep per night, that brings it to ~115 lines of code per hour..."
That doesn't even take into accout debugging - that number would have to be doubled at to maintain the same pace. Maybe tripled.
Re:The easy explaination... (Score:5, Insightful)
That's not true; some coders may write 500, some may write 50, and others may write only five.
I'm not even that sure it is worth measuring the lines of code written as a performance indicator either; I've had days at work where I've written only one line of code - but it was the line to solve a random threading deadlock; and so it was the correct line to write.
Re:The easy explaination... (Score:1)
Re:The easy explaination... (Score:2, Insightful)
Creating IDL definitions, and wrappers for libraries is large in terms of LOC even if it's short in complexity - just to give one example. (I once worked on an CORBA based distributed reporting project)
Other projects written in Java or C++ with lots of comments, and interfaces would be doable - it really depends upon the implementation language the level of the coding, and the individual developer.
Re:The easy explaination... (Score:2)
And as you admitted your example is not as complex as a browser...and even assuming this kid wrote a comment for every line of code that means he would have to sustain a rate of 1000 LOC per day for 2 years *straight*...I'm sure even you would admit that this is not a sustainable rate...
And if you factor in things like compile time, debugging, etc this makes it even more unbelivable.
Re:The easy explaination... (Score:1)
Re:The easy explaination... (Score:1)
So have you ever figured out what your sustained rate is? I mean, over like months???
And if you've never ran into problems that took you a day or longer to solve, that's not real programming.
We're not talking about something simple...and at 1.5 million lines of code, some of the more difficult bugs are going to be hard to track down...
karmaho'ing (Score:3, Funny)
"It's just Mozilla; it seems to cache the entire web during the build process."
Me too! (Score:2)
I'll bet you some fool gets parted from his money, though. People have invested in every high tech scam ever tried, especially if the media reports it. Awful.
lord it just kills me .. and maybe slashdot too (Score:1, Offtopic)
Hell, I'm posting. But I'm not subscribing. Ever. And banner ad revenues and a buck will buy you a cup of coffee.