News for hackers. Stuff that matters.
Re:The End of IKVM.NET by tracker1 on Tuesday April 25, 2017 @04:38PM (#14197738)
I've done some relatively large projects in Node... though I tend to break things down into discrete components either based on deployable assets, or reusable assets.

Node pipelines are pretty nice, not quite as nice as go's channels, but nice none the less. There are different options depending on libraries. I don't find it to be significantly more cumbersome than C#/.Net (which I have more experience than with Java). Also, your "example" has a LOT of assumed knowledge, more than a relatively simple express app, that's for certain.

It really depends on the approach.

Re:The End of IKVM.NET by kuschku on Tuesday April 25, 2017 @06:25PM (#14198703)
Well, I don’t think so.

I had never worked with Spring or Java Enterprise, and could write the example after 1 hour of reading docs.

After years of working with vanilla JS, and weeks of reading docs, I still can’t get a typescript compilation and CSS/SCSS compilation and minification pipeline right. Seriously, I still can’t get it working.

Re:The End of IKVM.NET by tracker1 on Wednesday April 26, 2017 @03:24AM (#14201116)
I've had better luck with flow over typescript, though frankly, I don't use either... I used flow instead of typescript for an angular 2 project a while ago. Not sure if the webpack story for typescript has improved.

I've managed to get webpack + babel + sass working pretty readily, in about the same time you mention above.