MQTTnet VS NodaTime

MQTT https://github.com/dotnet/MQTTnet

MQTTNet - High perf IOT comms for .NET - https://github.com/dotnet/MQTTnet

I'm trying to use MQTT.Net and so far everything works.. except for event handling.

Like the other guy said it depends on the requirements, but you could implement your own mqtt server with MQTTnet with a few lines of code

For the server we used mosquitto because we already used it in the past (and it's relatively simple), for the client MQTTnet because it's .net and it seemed good enough (mosquitto has a client library too but it's C so I'd have to write some interop). It's a simple protocol so it shouldn't really matter which implementation you use.

We are going to use MQTTNet as the foundation for this article, although the same concepts can be applied with any other MQTT client.

[2] https://github.com/dotnet/MQTTnet

For example, I used MQTTnet which is a very nice (high performance & extensible) library. And it's free/open source. If you're not writing your server code in .NET, then look for whatever broker libraries are available on your server platform.

Surprised no one mentioned https://github.com/nodatime/nodatime

What does moment.net do better then a combination of (Humanizer)[https://github.com/Humanizr/Humanizer#humanize-datetime] and (NodaTime)[https://nodatime.org/]

.NET's DateTime isn't amazing, it's true, but I think there's been some small improvements in that area recently. If you need something more robust, you can always reach for Noda Time.

Do you .NET programmers have a moment to talk about my personal Lord and Savior NodaTime? https://nodatime.org/ There is one datetime library, and Jon Skeet is His messenger.

Timezone and language support are two different subjects. For time-related issues, Nodatime can help.

it's already been said... https://nodatime.org/

Noda time is very clean/well written IMO -> https://github.com/nodatime/nodatime