3 ms·
As of 1.0 Kotlin has solid Java compatibility, @Transactional definitely shouldn't be an issue. What features are compelling for you in 1.1? They are nice, but
by vbezhenar 10y ago
As of 1.0 Kotlin has solid Java compatibility, @Transactional definitely shouldn't be an issue. What features are compelling for you in 1.1? They are nice, but generally just a nice sugar. I don't really miss any of those. I suggest you to try it now, if you have a chance.
- jsmith0295 10y agoThe @Transactional problem was fixed, I shouldn't have left that out. I had first tried to do this pretty much immediately after the 1.0 release. Async/await is cool, but it's really the idea of adding channels and coroutines that I'm a fan of. We've also generally stopped using that library that didn't work with Kotlin controllers for any new projects, so Kotlin is definitely something I look forward to using again.