Hacker News new | past | comments | ask | show | jobs | submit login

Because old solutions are so old and boring. I've built programs with J2EE, I wrote those XML files. Nothing wrong with that, this stuff works. But it's so much better to write 2 lines of Kotlin code running a top of Netty instead. Yes, it's very immature and new. But having fun is essential in my work. If I'm getting bored, I won't work, simple as that. I could be a uber driver, if I wanted boring work. Some people are just boring money makers without any passion. Nothing wrong with that, but not everyone is like this.



> If I'm getting bored, I won't work, simple as that. I could be a uber driver, if I wanted boring work.

This is big problem in the "new economy" of automation. Some people want "boring" jobs and those are disappearing, some people want "stimulating" jobs and there's not enough of them or at least the threshold is too high to get such jobs.


Are you trying to say that Kotlin is better than J2EE & XML? Why not comparing apples to apples?


I think all he's saying is that there are jobs that you can solve either with JEE & XML or with Kotlin, and that for those choosing Kotlin is often the more efficient thing to do.


I'm more in the Spring camp, but most of JEE is annotations based. You can put a Betty backing under it without much problem. Spring Boot does it even more readily.

I'm not saying that Kotlin is bad, but most things are now pretty equal. Java 8 has functional/OO hybrid. It has annotations. It has modern tooling that converts the boiler plat into a few keystrokes.


Fair enough. I've been absent from the Java ecosystem for quite a while, so have no opinion or anecdata to share. It's good to hear though that there are multiple, sane options available to get stuff done.




Applications are open for YC Winter 2020

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: