insta VS hujson

Ron is quite practical if you are having a serializable interface, and you want to get debug like output from it for snapshotting purposes. I am using this with my insta snapshot testing library (https://insta.rs/) in some projects.

> If a test never fails, is it a good test? If I have to change a test everytime I change the implementation, is it a good test? Writing good tests is really difficult.

If you don't like writing / maintaining tests or don't have the time, let the computer write them for you! [0][1]

[0] https://insta.rs/

So you love to code and write programs and or websites. But that doesn’t show me that you’re doing it with the kind of mindset that you have when writing work code. Some of the basic things that distinguish that mindset is thinking about how to handle errors, how to write idiomatic code (which I would define as code that communicates its purpose clearly using linguistic conventions), how to quickly pick up and put to use the latest and most convenient libraries for testing (check out what (insta, for example, or assert_fs do), and using GitHub to maintain and work on a project using a basic continuous integration process (branch off main, add/fix something, commit changes, merge branch with main, repeat). So if you want to get hired as a self taught programmer, then I suggest you focus on demonstrating these skills in small projects.

That, and comments!

Personally, I really hope Human JSON, https://github.com/tailscale/hujson , will take over!

I also like the approach that the hujson library takes, where everything is a type Literal []byte and you can call (Literal).Bool(), (Literal).String(), (Literal).Int() or (Literal).Float() on it and it gives you the corresponding value out of it (or the zero value). So kinda like dynamic variables that can store anything.

One of the variants that permit comments: https://github.com/tailscale/hujson