Indeed, this also gives me some confidence that there are still a few people around at Apple who don't like walls around their gardens :)
700 karma · joined August 8, 2010
As a small side effect I got a 3x speed increase.
JS Engines are good at optimizing, but having a senseless 256 copy loop in every call doesn't really work out that well if you can have a memcpy with Array.slice().
Best Ivo
We're living in a world where digital technology more and more becomes the dominant driving force of our society. We already lost the ability to change hardware to a - relatively small - group of people (yes, considering the amount of people using the stuff, the group is tiny).
So what now? Make sure there's only an elitist circle of high paid, influential "technology gods" left? While I definitely consider my self as a geek, I would not like such a society at all. It can be the target of humanity that ordinary people get even "dumber" than they're now.
Sorry, but I think people should strife for new knowledge, they should keep their spirit of discovery. By simplyfing the whole world around them, at least in my eyes, it becomes harder and harder for kids to figure out all these things on their own. And once all the knowledge is locked away from them, the elitist will choose who gets insight into the then "magical" workings of the world.
Yeah, maybe my picture of the future has a little bit of a dark taint, but well that's what you get when even your colleagues, which are the same age as yourself, are light years behind in terms of thirst for knowledge.
Also, my guide isn't even need the controversity of some of the statements that Crockford has made ;) In the end it's all advice, I'm not forcing you to write code this way.
In fact, I like it when people question the stuff I write, the worst thing that can happen is that people pick one book/guide whatever and just follow it 100% without ever thinking on their own.
But w3schools is read by beginners, they don't have any clue about web security whatsoever, if you don't tell them everything they will just go with the few things that you've told them.
> JavaScript can be used to validate data - A JavaScript can be used to validate form data before it is submitted to a server. This saves the server from extra processing
Sure! Always trust the client :)
Yep a great resource, for wasting a ton of precious time in which they could have learned how to do things right instead of using techniques from ca. 2000.
> ...interested in the actual tutorials.
Which are still the worst part of the site.
Example (just clicked on one of their JS tutorials):
> JavaScript statements can be grouped together in blocks. > Blocks start with a left curly bracket {, and ends with a right curly bracket }. > The purpose of a block is to make the sequence of statements execute together.
Pure BS. JavaScript has no block scope. {} aren't needed for "executing stuff together".
Another thing they tell people is that "var foo = 2;" and "foo = 2;", are equal, more BS.
> If table based layout invalidates a site...
There is a difference in using a table layout because it's a good choice (Google doesn't validate in any way, the just want to cut down traffic, which makes sense for them) and just using it because, well... because one has no better idea.
The site is horrible. Period.
> Completely irrelevant. Don't shoot the messenger.
Aha. Well, if they can't even get their own site right, why should I listen to them in the first place?
Sorry, but that's like hiring a Web Design whose own Web Site consists of nothing more than yellow 20px Comic Sans text on a blue background that uses a million blink tags.
Anyways, I'd rather spent a lot of time improving the JITs instead of writing "optimized" low level code myself these days.
Those should not run in a Browser, they should on a real OS (or Emacs).
What's next VMWare inside your Browser? Then it's OS -> Browser -> VM -> OS -> Browser...
Sorry but just because things are possible, doesn't mean that they should be done...
To get out of the sandbox and wreak havoc? No really, NativeClient is the __last__ thing the Web needs. In the end people will either port their old, bug ridden and insecure C++ code to that thing or they will write new platform dependent code... or both at the same time. That's completely against the OpenWeb.
http://krakenbenchmark.mozilla.org/kraken-1.0/results.html?%...
Chromium 10.0.605.0 (68575) with Crankshaft: http://krakenbenchmark.mozilla.org/kraken-1.0/results.html?%...
Overall Crankshaft is 2.13x FASTER.
Ubuntu 10.04, old Core 2 Duo.