don't you find it a little painful to write code like that? When literate mode was first announced I had a go re-writing some small scripts in that style and for some reason I found it a bit of a chore, especially when commenting on just one or two lines. I've been using
###
comment blocks
###
instead and I find that more readable, especially when dealing with indented code, e.g. a class body.
Edit - here's an example of some coffeescript written in this "illiterate" way, i'm using it with a (work in progress) preprocessor that spits out tests, html, markdown etc - https://gist.github.com/phpnode/2bf86b9633032a51d036
I think it definitely depends on what you're doing. We're by no means deprecating "ordinary" mode, where the code remains primary, and the comments are secondary.
For me, it's most interesting for both exploratory programming -- where you don't quite know how to solve the puzzle yet, but you're in the process of figuring it out, and writing notes to yourself as you do so; as well as for polishing up finished pieces of code -- where you've carefully put a library together in a certain way, and you want to document every significant method with an explanation of why it's written the way it is.
looks nice, but why doesn't it just extend the core array type? (I mean with a "class", not by adding things to Array.prototype). That way things like Array.isArray() still work. Am I missing something?
I wonder how fast a good designer could bang out a favicon (given a source image)? My gut estimate is 30-60 minutes at a bare minimum. If so, they'd probably want to charge more than a few dollars. But that could be a fun side project for a designer. Set up a site and let people queue up requests, then when you get some time, just open up your backlog of favicon requests and churn them out for 10 bucks a pop.
I think it depends how many sites you own, if you only own one then you'll probably be prepared to part with a lot more than someone who manages a load of different sites. Anyone tackling this market should probably set up 2 sites offering the same service branded and priced accordingly.
Sure, my use-case is that I have a few toy side-project apps. Serious enough that I'll drop $15 for a .com domain and could part with $5 for a nice favicon, but not enough that I really care enough to spend $50 (since they don't make revenue).
It's a funny thought experiment. Some people want to only spend a few bucks. But whats the price not for the pixeling, but the time it took to learn color theory, illustration, composition, what makes a bad icon, etc.?
Clearly you have some kind of issue with jQuery but just because you don't like it doesn't make it any less popular, useful or prevalent. Here's a fun drinking game - open up the top 1000 websites and do a shot for each one that uses jQuery. You will be in hospital by about #20 I think.
I disagree with your notion that the top 5 sites are a good sample for development trends, but you did miss some uses of jQuery.
Google uses jQuery (and hosts it for millions of sites), just not on their very optimized homepage. They built a very large framework of their own to power their apps, but a lot of their informational sites use jQuery. Here are some examples:
You ought to read comments before replying to them. I clearly said that only those four are using jQuery, and that the remaining sixteen do not. I checked all of them by hand before stating this, except for Wikipedia because it is common knowledge that MediaWiki uses jQuery.
Also, your idea below about sniffing for $ is a bit embarrassing. Firefox, Chrome, etc. have come with $ for many years as an ID or query selector, and it has nothing to do with jQuery. Prototype and MooTools also provide $, and probably a dozen or more similar libraries you haven't heard of.
People on comp.lang.javascript (which has its problems, and I've been away for a while) have been noting this for a while. jQuery chews far more cycles than comparable libraries with its function overloading, extra $(this) invocations and such.
but still the majority of them do, by a wide margin. I don't even know why you're debating this, it's completely obvious that jQuery has by far the largest mindshare.
edit: ok now I get it, I had a look at your website. You like Closure so jQuery must suck, right? Also I would be in the hospital after 5 shots....
Well, don't provide a test like "you'll be in the hospital by #20" if you haven't vetted the results of it first.
My personal advocacy for the Closure Tools does not discredit my views on other tools, and I'm hoping this ad hominem nonsense doesn't fly in such a forum. Quite a few people come into the IRC channel and are using the Closure Compiler with jQuery and I don't give them shit. I take no issue with you using, liking, preferring jQuery.
You know why I like Closure? Because it makes the hard things possible. When you're talking about JavaScript running the web, it's websites like Gmail that matter the most. And you'd have a hell of a time getting Gmail to run as smoothy as it does using a library like jQuery, or even ExtJS.
you're right in that I should have checked first, and really if you think about it it's no surprise that YouTube, Yahoo, Google etc are using their own tools. That does not detract from the point that jQuery has massive, ridiculous mind share and completely dominates the web though. Your point about it being impossible to build a gmail style app in jQuery is extremely dubious. There are an awful lot of complicated JS apps built on jQuery.
If you check you are right. Amazon, eBay, and MSN all use jQuery. (at least on their homepage).
You can't simply look for the global `$` or a single file named jquery.
I work on large corporate applications and we use jQuery, but we would fail the `$` and jquery file test. We don't expose the global `$` and jquery gets combined and minified with our own code.
You seriously underestimate the complexity of Gmail. It may well be the most complex JavaScript application in existence with an appreciable user base.
You make a fair argument. Google has several state-of-the-art JS applications. I thought of Gmail in particular because it probably sees much higher demand and so matters of optimization are probably a bit more important to it. This makes the amount of network activity, client-side caching, etc. it manages really impressive.
But no doubts that Google Docs is in the same ballpark.
the implementation is the same.if you use jQuery script the jQlite code is disabled in AngularJS. it is only possible if the subset code respect all the behavior or the main code. And Gecko doesnt use Webkit api at all. Chrome just cant swap its webkit code to to Gecko without significant rewrite.
I don't think he's living on his own planet, he's actually right - jQuery runs the client side web. Not for everyone but easily 90% of sites (that actually have javascript functionality at all) will use jQuery
Rather, the practice of providing a DOM API compatibility layer runs the web, jQuery being the most widely used library of this sort. When you step out of the god-object API jQuery provides and look at the internals, jQuery, MooTools, and Closure look surprisingly similar. I find the latter to provide the best compatibility (so does Google), but that is another discussion altogether.
Your opinions on what JavaScript libraries provide "the best compatibility" has little bearing on your original statement, that jQuery is not as popular as it actually is.
did coax ethernet ever work reliably? I remember spending entire days fiddling with cables and terminators trying to get multiplayer quake to work over a network, we almost always had to resort to (very slow) serial ports instead.
Yeah, coax Ethernet did work reliability, or at least enough to get the job done, but none of us missed it when twisted pair became available, it was a major pain when a physical disruption would take out a whole cable segment. Note the original coax for commercial Ethernet was quite a bit narrower and more flexible than that used for the CHAOSnet. From very old memory, something close to maybe 3/4ths? vs. 0.375 of an inch for what came to be named 10BASE5: http://en.wikipedia.org/wiki/10BASE5 Original research Ethernet also used narrower coax.
MIT did use it for some years before commercial Ethernet eventually displaced CHAOSnet (I was gone by then), but, yeah, it was a constant struggle to keep it working reliably. People would work in the cable spaces and ding or crimp the coax outer shield, and we'd have to go find it.