3 ms·

> - they interact poorly with requirejs and amd in general. > - the tooling in general is currently rubbish; no way to easily combine sass + jade + coffee into

by DCKing 12y ago

> - they interact poorly with requirejs and amd in general. > - the tooling in general is currently rubbish; no way to easily combine sass + jade + coffee into a web component (eg. with gulp, no the dart bindings don't count as tooling). no way to have external resource files. If you use Dart and its Polymer libraries, these two things should not be a problem. Why does that not count? He didn't say he wants to use Sass, Jade or CoffeeScript. IMO, Dart is becoming much more interesting to me as it seems it is the best way to work with Polymer.

rektide 12y ago
Most javascript developers want to use Javascript and want to use what's available in the defacto javascript package manager (npm) and want to use the build tool that works with the javascript packages (browserify). Suggesting using something other than Javascript, it's packages, and it's preeminent packager to get started with Polymer is exactly the problem parent was highlighting, and your suggestion is bloody not well helping.
- DCKing 12y ago
  Why the hostile reaction? Expanding your horizons is not a bad thing. > Most javascript developers want to use Javascript OP mentions nothing, parent mentions CoffeeScript. Dart also has packages and an official package manager. It also has a dogfooded official Polymer library. Setting up a modular toy project with packages was easier to understand in Dart than JS for me. I don't see how I'm "bloody well not helping".
  - deleted 12y ago
    [deleted]
  - rektide 12y ago
    "polymer has these integration pain points" "you should try dart! it integrates well" you definitely told shadowmint to go fuck himself.
- Cthulhu_ 12y ago
  IMHO, if you (nonpersonal you) identify as a Javascript developer instead of a web developer, you're a very limited and narrow-minded developer. Learning a new language is easy, and installing some new tooling shouldn't take more than a minute nowadays. Looks like Polymer is installed using Bower anyway, which is pretty standard.
  - rektide 12y ago
    If you are a webdeveloepr that builds non-Javascript tools that don't integrate with the rest of Javascript tooling, you will have a very isolated, limited, unadopted and narrow-minded niche you carve for yourself.

by DCKing 12y ago

rektide 12y ago

Most javascript developers want to use Javascript and want to use what's available in the defacto javascript package manager (npm) and want to use the build tool that works with the javascript packages (browserify). Suggesting using something other than Javascript, it's packages, and it's preeminent packager to get started with Polymer is exactly the problem parent was highlighting, and your suggestion is bloody not well helping.

DCKing 12y ago
Why the hostile reaction? Expanding your horizons is not a bad thing. > Most javascript developers want to use Javascript OP mentions nothing, parent mentions CoffeeScript. Dart also has packages and an official package manager. It also has a dogfooded official Polymer library. Setting up a modular toy project with packages was easier to understand in Dart than JS for me. I don't see how I'm "bloody well not helping".
- deleted 12y ago
  [deleted]
- rektide 12y ago
  "polymer has these integration pain points" "you should try dart! it integrates well" you definitely told shadowmint to go fuck himself.
Cthulhu_ 12y ago
IMHO, if you (nonpersonal you) identify as a Javascript developer instead of a web developer, you're a very limited and narrow-minded developer. Learning a new language is easy, and installing some new tooling shouldn't take more than a minute nowadays. Looks like Polymer is installed using Bower anyway, which is pretty standard.
- rektide 12y ago
  If you are a webdeveloepr that builds non-Javascript tools that don't integrate with the rest of Javascript tooling, you will have a very isolated, limited, unadopted and narrow-minded niche you carve for yourself.