You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMO jsbin is better for polished concrete examples and jsfiddle is better for, well, fiddling. If ever I throw something together on the fly to demonstrate something for a user on a question/in chat then I use jsfiddle, but if you have a static example of some specific technique that won't change and all you want is a link to throw at people who ask "how do I do X" then I would say jsbin is more suited.
@WesNetmo and me discussed that in chat. His concerns were about having access to GitHub's cookies which has been addressed by GH by moving their GH pages service to a .io domain. So GH cookies won't be accessible form GH pages.
Activity
mainerror commentedon May 6, 2013
I don't mind, whatever you are more comfortable with.
DaveRandom commentedon May 7, 2013
IMO jsbin is better for polished concrete examples and jsfiddle is better for, well, fiddling. If ever I throw something together on the fly to demonstrate something for a user on a question/in chat then I use jsfiddle, but if you have a static example of some specific technique that won't change and all you want is a link to throw at people who ask "how do I do X" then I would say jsbin is more suited.
Just my $0.02
Wes1262 commentedon May 7, 2013
do you mean your ₤ 0.02 ? :-P
i don't know jsbin much, i only know that jsfiddle is very annoying, that's why i'm asking
Wes1262 commentedon May 7, 2013
@kyRAD are you sure examples will not be limited somehow?
mainerror commentedon May 7, 2013
@WesNetmo In what way?
Wes1262 commentedon May 7, 2013
well for example, unless pages are stored on a third level domain seems difficult that javascript would be enabled on them
mainerror commentedon May 7, 2013
@WesNetmo and me discussed that in chat. His concerns were about having access to GitHub's cookies which has been addressed by GH by moving their GH pages service to a
.iodomain. So GH cookies won't be accessible form GH pages.