News for hackers. Stuff that matters.

A comment on Java 12. Parent comment

Re:Java 12 by pjmlp on Tuesday March 19, 2019 @06:47PM (#19436914)
As someone that works with both stacks since their inception, there are tons of platforms with Java compilers, where .NET Core isn't even a thing today, and there are tons of .NET libraries that will never leave .NET Framework.

So it isn't like just exchanging one for the other like that.

[ Parent | on HN ]
Re:Java 12 by james_s_tayler on Wednesday March 20, 2019 @01:56AM (#19439416)
I'm finding library support quite good for .NET Core tbh. Not perfect, but it's not at all a barrier to adoption.
[ Parent | on HN ]
Re:Java 12 by pjmlp on Wednesday March 20, 2019 @03:33AM (#19439799)
Try to port any commercial component library to it like Telerik and friends, ODP.NET, WCF, EF 6, Forms, WPF.

.NET Core 3.0 will fix some of the compatibility issues but not all of them, for example EF 6 will only be partially supported (VS DB tooling is not being updated for Core).

[ Parent | on HN ]
Re:Java 12 by james_s_tayler on Wednesday March 20, 2019 @04:52AM (#19440174)
Yeah .NET Core 3.0 will address some of that, not all. I suppose for any brownfield development looking at switching across those things are the potential blockers at the moment. Especially things running EF where EF Core doesn't have a particular feature just yet. But EF Core development is cracking on at a good pace.

Telerik and the likes I'm not so fussed about personally. I suppose DevExpress is another one on that list. I think front end component libraries like Prime-ng/PrimeReact are probably the way to go for the future of UI development for Line of Business applications.

Overall I reckon in a couple of years there won't be much of those blockers left at all.

[ Parent | on HN ]