61–69 of 69 posts
Awesome job! Can't wait to try it. An aside - over the last few months I began running my containers on two popular CI services and have had some serious pain. I have a slight feeling you will regret the words: "works well with CI as well!"
Maybe I should be more careful with my words in the future...
Dumb question, from someone who doesn't work with Node.js: Why are there 32 versions of it?
Earlier quoted context omitted.
I don't think the issue is that they've released multiple versions, it's more that they've had so many backward-incompatible releases. Python and OCaml have had 3 each. Libc has had 6. 32 for something that's been around less than a decade is a bit excessive. Are all these 32 actually backwards-incompatible?
There have only been 3 major releases with known backwards-incompatible changes. The reason you would want to test your code in so many versions of Node would be to check that you aren't depending on newer features that aren't in older versions that you want to still support. Testing across 32 versions is probably very overkill for most people though.
Earlier quoted context omitted.
That's my plan. But it means I can't use other people's modules anymore.
Why? Put a transpiler inside your build chain.
Most node developers seem to not use a debugger, but I think that's a huge productivity sacrifice.
This is why I hate ES6. JavaScript used to be a write once, run anywhere language. We sacrificed that for syntactic sugar.
JavaScript was never 'write once, run anywhere'. There were quite a few differences between the Netscape and MSIE implementations during the first few years of its existence and things didn't stabilise until the IE5 era.
If a module is heavily using ES6 and you want to run it on an older runtime you're just toast.
As a small update, I've now made autochecker completely language agnostic, so you can test basically anything you can put in a docker container. There is some examples on how to use this here: https://github.com/VictorBjelkholm/autochecker/tree/master/e...
Again, thank you all for taking the time to give feedback, I'm forever grateful to the HN community.