4 ms·

I'm not sure why we need python for the client side web programming, when JS is already used everywhere for that. Does it have to do any issues with JS or it's

I'm not sure why we need python for the client side web programming, when JS is already used everywhere for that. Does it have to do any issues with JS or it's because Python is easy ? Please enlighten me here.

douche 11y ago
Because if Python is a hammer, Javascript is a Fisher-Price toy hammer. It's amazing that such a shit language has become so ubiquitous.
- harel 11y ago
  When used right, even a Fisher-Price hammer can push a nail through wood. And because Python is a hammer, it doesn't mean you can saw with it.
  - eximius 11y ago
    Just because you can use a shit tool doesn't mean you should give up on a better tool
    - douche 11y ago
      http://s265.photobucket.com/user/NarianMar/media/Fry-NailHammer.gif.html http://s265.photobucket.com/user/NarianMar/media/Fry-NailHam...
    - harel 11y ago
      shit to one person is manure to another if we keep on with that line...
- wwweston 11y ago
  I've been using both for a while now -- JS for 15 years, Python for five. I expected some big revelation given the consensus that Python is clearly better. I like working in Python, but I'm still waiting for that revelation. As I can tell, if you can't be as productive in JavaScript as you are in Python, you're either not actually productive in Python, or you never bothered to learn JavaScript. (I appreciate people who are nevertheless insistent about Python's superiority without bothering to provide any kind of supporting argument, though -- it lets me know how safe I am in disregarding an opinion where I used to think I was probably missing something -- so if you want to recapitulate the quality argument I'm responding too, feel free.)
  - douche 11y ago
    Python doesn't have the whole == vs === debacle. Python has a string library that makes some kind of goddamn sense (because it matches the C implementation). When I realized that in JS, foo.replace('bar','fizz'); only replaces one instance of 'bar', my head exploded. Then there is the lack of real integers, and all the bullshit ToStringing() that can happen at runtime if you aren't hyper-vigilant.
  - Retra 11y ago
    If by "learning JavaScript" you mean "getting used to all the awful decisions..."

douche 11y ago

Because if Python is a hammer, Javascript is a Fisher-Price toy hammer. It's amazing that such a shit language has become so ubiquitous.

harel 11y ago
When used right, even a Fisher-Price hammer can push a nail through wood. And because Python is a hammer, it doesn't mean you can saw with it.
- eximius 11y ago
  Just because you can use a shit tool doesn't mean you should give up on a better tool
  - douche 11y ago
    http://s265.photobucket.com/user/NarianMar/media/Fry-NailHammer.gif.html http://s265.photobucket.com/user/NarianMar/media/Fry-NailHam...
  - harel 11y ago
    shit to one person is manure to another if we keep on with that line...
wwweston 11y ago
I've been using both for a while now -- JS for 15 years, Python for five. I expected some big revelation given the consensus that Python is clearly better. I like working in Python, but I'm still waiting for that revelation. As I can tell, if you can't be as productive in JavaScript as you are in Python, you're either not actually productive in Python, or you never bothered to learn JavaScript. (I appreciate people who are nevertheless insistent about Python's superiority without bothering to provide any kind of supporting argument, though -- it lets me know how safe I am in disregarding an opinion where I used to think I was probably missing something -- so if you want to recapitulate the quality argument I'm responding too, feel free.)
- douche 11y ago
  Python doesn't have the whole == vs === debacle. Python has a string library that makes some kind of goddamn sense (because it matches the C implementation). When I realized that in JS, foo.replace('bar','fizz'); only replaces one instance of 'bar', my head exploded. Then there is the lack of real integers, and all the bullshit ToStringing() that can happen at runtime if you aren't hyper-vigilant.
- Retra 11y ago
  If by "learning JavaScript" you mean "getting used to all the awful decisions..."