Removal of Oddity? #39
Replies: 1 comment 4 replies
-
The main reason was that Oddity was written in Clojurescript. Working on Oddity itself was difficult. Also, all communication between Oddity and DSLabs had to happen in JSON or some other serialized format. One way in which that was annoying was that objects with circular references couldn't be handled without a custom serializer. Now, the visualizer and DSLabs tests are run out of the same JVM, and it's surpassed Oddity in terms of the features provided. My favorite aspect is the event list on the right hand side of the display. It provides a graphical and expandable view of the messages/timers that lead to the current state. When I'm debugging, looking at this is often the fastest way to diagnose problems. It should be easy enough to try it yourself. All the same commands to The one downside of the new visualizer is that running a Java GUI app isn't quite as foolproof as opening up a web browser in terms of cross-platform compatibility, but I've been able to run it on all the major operating systems without issue. |
Beta Was this translation helpful? Give feedback.
-
Hi Ellis, thanks for creating this framework and sharing it - it's been an invaluable learning resource. I noticed that the labs recently removed Oddity and switched to a new visualizer. Can I ask what motivated you to make the switch? I'm interested in what the new visualizer can do, but I'm also curious about what was missing in the Oddity visualizer. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions