4 ms·

Tldr: sbt made it difficult.

pluma 11y ago
The only React-related problems the article describes are API changes (which are generally announced via deprecation messages if you don't skip several releases when upgrading) and invalid DOM nesting (which is just React becoming less messy). Everything else seems to be the result of forcing a square peg in a round hole, i.e. using non-standard tooling. As much as I can understand the desire to have one set of tooling to rule them all, if I were using Ruby/Python/PHP/Java for my backend I wouldn't expect to be able to integrate my backend tooling with the Gulp/Grunt/WebPack I might use to build the frontend. Expecting to be able to do the same the other way around is just as arrogant, especially if you then blame the ecosystem you're trying to avoid for the incompatibilities you're experiencing.
officialchicken 11y ago
Yeah, imagine a problem with the javascript build tool chain. That rarely happens, right? But I was unfamiliar with SBT - it's scala build tools[1]. [1] http://www.scala-sbt.org/ http://www.scala-sbt.org/
- davidjnelson 11y ago
  I think it's the default/recommended build tool for play framework projects.
ed312 11y ago
I wonder why they can't just use node to transpile the react code?
niccaluim 11y ago
Yeah, I stopped reading the second I saw "SBT." I know there are lots of Scala programmers who use it, but none of the ones I know do. (Having worked at Twitter for 4.5 years, that's a not-insignificant value of n.) I've heard nothing but bad things about it.
- estefan 11y ago
  SBT is fine, but using it to build a complex JS project that's using immature dependencies is just asking for trouble. Webpack alone is tricky enough...
draw_down 11y ago
Another version: "Doctor, it hurts when I do this"
AgentME 11y ago
Yeah, if you use a custom/unofficial build tool to compile code, and then the format changes, then your custom build tool is going to require updating. Blaming the React or javascript ecosystem for that seems silly when there are officially endorsed and supported tools that are kept up to date that you specifically aren't using.

pluma 11y ago

The only React-related problems the article describes are API changes (which are generally announced via deprecation messages if you don't skip several releases when upgrading) and invalid DOM nesting (which is just React becoming less messy). Everything else seems to be the result of forcing a square peg in a round hole, i.e. using non-standard tooling. As much as I can understand the desire to have one set of tooling to rule them all, if I were using Ruby/Python/PHP/Java for my backend I wouldn't expect to be able to integrate my backend tooling with the Gulp/Grunt/WebPack I might use to build the frontend. Expecting to be able to do the same the other way around is just as arrogant, especially if you then blame the ecosystem you're trying to avoid for the incompatibilities you're experiencing.

officialchicken 11y ago

Yeah, imagine a problem with the javascript build tool chain. That rarely happens, right? But I was unfamiliar with SBT - it's scala build tools[1]. [1] http://www.scala-sbt.org/ http://www.scala-sbt.org/

davidjnelson 11y ago
I think it's the default/recommended build tool for play framework projects.

ed312 11y ago

I wonder why they can't just use node to transpile the react code?

niccaluim 11y ago

Yeah, I stopped reading the second I saw "SBT." I know there are lots of Scala programmers who use it, but none of the ones I know do. (Having worked at Twitter for 4.5 years, that's a not-insignificant value of n.) I've heard nothing but bad things about it.

estefan 11y ago
SBT is fine, but using it to build a complex JS project that's using immature dependencies is just asking for trouble. Webpack alone is tricky enough...

draw_down 11y ago

Another version: "Doctor, it hurts when I do this"

AgentME 11y ago

Yeah, if you use a custom/unofficial build tool to compile code, and then the format changes, then your custom build tool is going to require updating. Blaming the React or javascript ecosystem for that seems silly when there are officially endorsed and supported tools that are kept up to date that you specifically aren't using.