Skip to main content


The hoops you have to jump through in #dotnet to do local package installation that is as simple as 'mvn install' with #java is **astounding**...smh...

André E. Veltstra reshared this.

In defense of #dotnet local tools are brand new, and even global tools are relatively new. I'm sure when more people stay using them, they'll become easier to use with updates to .Net Core

I'm trying to do local library not tools management but I think the thing that was most frustrating is that I have to install a whole mono toolchain just to manually download nuget.exe so I can do a one line command that should probably be in `dotnet nuget` already...

What exactly are you trying to do? In my experience dotnet add package worked for me without mono.

Alternatively, you could try paket as an aforementioned local tool

I'm trying to publish a package for use locally. `dotnet push` as far as I can tell can only work with a properly setup nuget server. I'm writing up a tutorial on how I got my setup working.

Try installing local packages using Gradle for Java. Better yet: have a mix of local packages, packages hosted locally on an Ivy repo, and packages hosted remotely on Maven or Bintray. Because that's where I'm at.

I bet it's equally astounding.

I've never had a problem with that actually. If I recall correctly I used the Maven plugins so it was Maven that was doing the local repo management though. I will say that I'm far more used to Maven than Gradle for larger projects. Those systems aren't perfect either for sure.



Thank you for this post. Researching Spring and Kotlin sent me down a very educational rabbit hole into aspect oriented programming and related sub-topics.

Kotlin is a lovely, modernized language for writing to the JVM. It cleans up most of the complaints people have about Java's verbose syntax and add features that makes code written in Kotlin safer. Were I still cutting code these days (and with the end of my current gig, more code-cutting may be ahead), Kotlin would be the language I'd prefer to use.



Not thrilled to be back to coding #java (I'd rather it be #kotlin) but with Java10 having type inference 'var' it's a lot nicer than before. Hopefully it and #csharp add 'val' eventually #programming

André E. Veltstra reshared this.

The main beef I have with Kotlin is that Google is trying to make it the de-facto language on Android not because it is the best choice, but because it is different enough to safeguard them from another lawsuit from Oracle. Everything in Kotlin syntax screams "we're making it this way because we want to do it differently." But they're still restricted by the JVM...

Why the hell would a multinational software business switch from the most widely used language to one that is used by a few hobbyists and has no resemblance to the old one? We ask this every time someone suggests we should start using Kotlin instead of Java.

Rust on the other hand looks quite promising and interesting.

But then again, Java is constantly evolving into the right direction.

JetBrains is the company behind Kotlin not Google. As someone who likes Kotlin but doesn't get to program in it often enough I was pleased when Google decided to use it instead of Java as it's primary language. I can think of a lot of reasons why I like Kotlin over Java. Kotlin is like a good marriage of the modern syntax and features of C# with even better overlays of functional programming concepts. When I was thinking of leaving Java for C# it was because of how stuck it was compared to when I was using more up to date languages. It's better now but still behind where Kotlin is. I don't like Kotlin because it's new or buzzwordy. I like it because it makes developing easier.



.NET Core 3.0 adds even better native library integration. In case it wasn't far enough ahead of the JVM's! Even more excited if the rumored Java Interop comes to fruition next year as announced! #dotnet #java



Tucked away in the .NET 5.0 (in a bullet no less though) was this awesome tidbit: Java Interoperability. I don't want to get too excited but being able to use my favorite #java libraries in #dotnet would be awesome!