Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think this would only be worthwhile if you could do this:

  <script src="http://jquery.js"></script>


The WHATWG should just introduce a new <jquery> element that automatically pulls the latest version.


Not unless jquery is going to be absorbed into ECMAscript it shouldn't.


<joke/>


Ah. My bad.


You could quite easily make the index page the latest jquery minified version, so yes.


I have a revolutionary idea: <script src="http://somedomainyoumanage/jquery.js></script>; + git and save the 100K


<script src="/jquery.js></script>


I'd much prefer this, much the same way http://to/ used to operate:

    <script src="//cdn/jquery"></script>



Very cool. You could also do:

    <script src="http://jquery.js/latest"></script>
And keep / as an informative website.


I can't tell if your you're joking or not. Linking to the latest version is a very nice way to break your app automatically.


You can even drop the http: part, like this:

    <script src="//jquery.js/latest"></script>


Or use Content-Type negotiation. (please note, I do understand that this proposal is basically DOA)


Nah, too much typing. Maybe if you got rid of jquery.com. It's not even a company!


What would the source at js.js/js.js be?


JS.js(js)


js.js/js.js?js=js.js

Just because...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: