It really is great for fiddling with html,css,and javascript all on the same screen without having to deal with a complicated development environment or separate files. It would be a nice platform for teaching basics, or even introducing something new.
JsFiddle: a REPL for web development
21–25 of 25 posts
Some Stackoverflow members use it to paste solution and prove that it works :)
Re: JsFiddle: a REPL for web development
#22I think Panic should update Coda to allow a similar 4-square split of the window. Currently you can split the window as many times as you want, but they all have to be the same orientation (ie. You could have 4 rows or 4 columns.
But yes jsfiddle is great. Note that you can load more resources into it, like KnockoutJS, and use them to. It also does automatic version control (well, the version number increments when you press save, but the old URL still works). I first discovered it in the Stackoverflow JS chartroom, where everyone was using it. I showed a lecturer at university, and now lots of people there are 'fiddling.'
Re: JsFiddle: a REPL for web development
#23I recently wrote a little throwaway blogpost that used the embed ability of jsFiddle (http://breakfastdinnertea.co.uk/blog/keep-those-rows-line-li... - excuse the pig ugly design et al). I found it an absolute joy to work with. It also provides nice fork abilities for any ensuing discussion / counter arguments on Twitter or wherever.
Re: JsFiddle: a REPL for web development
#24JSFiddle is great for embedding code examples in a library's docs too. Highcharts uses them in the API reference, and it's outstandingly useful.
Re: JsFiddle: a REPL for web development
#25A wonderful project written in MooTools- IMHO, a civilized and superior JS toolkit if your JS environment is homogenous/sane.
surely the stability of your architecture is not dependent on the library you use? unless of course your library defines your architecture- but i wouldn't consider a library of that nature a "toolkit".
It is, to some degree. For one, you buy into certain module management systems when you choose a library like jQuery, Dojo, MooTools. Another example: you buy into unique implementations of promises which are used throughout the library. If you used jQuery before 1.5, you didn't even have them and had to use callbacks -- that definitely impacts your architecture.