Are those downsides still valid today?

[rupert]

I’m wondering, is the debugger problem this one:

Maximum call stack size exceeded when running --debug

RangeError: Maximum call stack size exceeded when decoding a long list

I ran into the error when decoding a json value which contained a list that had over 4000 elements. I found old posts and github issues about similar situations, but none had concrete steps to fix it other than to update to the latest version of elm. I did try running the app without the debugger and it did work then, but that’s not really a solution as the debugger is pretty useful at times. My elm version is 0.19.1-3 from npm. My code is below. import Json.Decode as Decode import Json.Deco…

Not so much when the message gets more complicated, but when your model gets too big?

I’ll create one and a PR for this fix, as its a simple fix, and the code is in that discourse thread already.

I don’t find the time travelling debugger so useful. I used to use it more, so perhaps it serves its purpose as a learning tool? Or I have learned to know when it can be useful, and just Debug.log the rest of the time.