Include developer ramp up time, enhancing existing JavaScript, and working with JavaScript

[making3]

After writing a decent chunk of an Elm application (in Electron) and toying around with converting a Node.js repository to Typescript, I've found the following as pros of using Typescript:

• Developer ramp up time. I think this is a given, Typescript is extremely similar to JavaScript.
• Enhancing existing JavaScript.
• Working with JavaScript.
  • Using existing libraries. Yes, ports aren't very difficult to use, but it's more involved than just including a file in JavaScript / Typescript.
  • Working with custom DOM events. Elm does have dom, but working with tasks / commands aren't the easiest, compared to calling these things directly in JavaScript / Typescript. I spent a few hours yesterday trying to auto scroll a textarea once Elm updated the values with no luck. I'm sure it's possible, but I assume this would have been much easier in JavaScript.

Most of these are time limitations rather than Typescript being better than Elm.

[absynce]

@making3 thanks for the suggestions.

I haven't put the full outline in yet, but "Learning curve" is one of them. I think there will be a couple surprising points in that conversation.

I spent a few hours yesterday trying to auto scroll a textarea once Elm updated the values with no luck.

I'm not sure I understand what you're trying to accomplish. Do you have a SSCCE in Ellie?

[making3]

@absynce I haven't implemented in hl7-sender yet, but using Task.attempt / Scroll.toBottom works in this tiny Ellie example. I guess what I was trying to point out, this felt like it was more complicated than it would be in straight HTML/JavaScript.

Reference SO answer.