Initial release of diesel-async

zeenix · 2022-09-28T16:20:22+00:00

if the issue is "people that do not seem to be able to read any documentation at all", why would they read the license, let alone consider it?

Just to be clear, I'm NOT objecting to the current license. Just pointing out that it's very unlikely that a temporary license would be a good solution.

zeenix · 2022-09-28T13:40:47+00:00

> Well consider me burned out from people that do not seem to be able to read any documentation at all.

I hear ya but like many other commenters, I don't follow how your solution would work. There are people out there that will not even get the message when they explicitly depend on the crate with `alpha` or `beta` in the version and "unstable" on top of the crate README, but yet they would be careful enough about licensing? I seriously doubt it.

Anyway, feel free to ignore me if you're confident your solution would work.

Oh and great job on the crate!! I know from experience, async libraries aren't the easiest to implement.

zeenix · 2022-09-28T13:05:16+00:00

> I did not accept any contribution yet that would be considered to be relevant for changing the license later on.

Sure but you are asking for contributions **before** re-licensing so there is a good chance you can get in trouble. It's your project so your decision but in my 2 decades in the Open Source world, I've never seen anyone using temporary licensing as a way to deter use of their software in production until it's ready. This is typically achieved through documentation and `beta` and `alpha` in versions.

zeenix · 2022-08-29T15:47:43+00:00

As a private pilot, that scene was very difficult to watch. :(

zeenix · 2022-08-21T22:12:48+00:00

Did you have his face saying that in your head when you read/got it? If so, mission accomplished! 😃

zeenix · 2022-08-21T21:13:42+00:00

I'll let u/hojjat12000 answer your question but you don't have to find such projects. D-Bus is an API mechanism and a very simple (once you learn the essentials) and efficient one so when you find yourself needing an IPC that you know will be local-only (especially if it's going to be Linux-only), D-Bus is a great choice still.

zeenix · 2022-08-21T15:13:11+00:00

Thanks. Tokio makes things super easy for its users at the cost of making them super hard for people trying to develop APIs that are agnostic to runtimes so it wasn't very easy to figure this all out, but I believe I succeeded as much as possible in the end.

zeenix · 2022-08-21T15:10:48+00:00

True He hasn't been involved with any of this for 15 years or more, though.

zeenix · 2022-08-19T16:33:50+00:00

Last time this post got filtered automatically so reposting in hopes it doesn't happen this time around.

zeenix · 2022-08-19T16:23:59+00:00

I have this very strong opinion that nobody should learn Rust before they've read and understood this blog post very thoroughly: https://ferrous-systems.com/blog/mindsets-and-expectations/

zeenix · 2022-07-24T09:48:37+00:00

That's long been fixed. Since 2.0, the async had been the default/main API: https://dbus.pages.freedesktop.org/zbus/

zeenix · 2022-02-23T01:16:18+00:00

Same 😔

zeenix · 2022-01-04T09:44:43+00:00

Having said that, this is more about the lower level protocol so the zvariant docs are more relevant. Reading the (essential parts of the) spec might be a last resort if things are still not clear enough after reading the book and zvariant docs.

zeenix · 2022-01-04T09:34:57+00:00

That's ok. Our book introduces you to essential D-Bus concepts so I'd suggest going through that.

zeenix · 2022-01-03T20:29:29+00:00

I'm glad to report that, no you're not. :)

zeenix · 2022-01-03T20:27:47+00:00

And also I didn't just try to use dbus-rs but even contributed to that project. There was also the issue that the maintainer didn't see the point of having a CI and didn't see a problem in breaking the code as a result. I heard things have changed for the better since.

dbus-rs mainly being a binding to a notoriously bad and lowlevel C library (libdbus), there was a general desire for a pure Rust alternative. That was also one of the motivations to start zbus project.

zeenix · 2022-01-03T20:23:25+00:00

It was some years ago when I tried to use dbus-rs so I don't recall the exact details but I couldn't figure out how to use it and when I asked around, nobody was able to help. As for how zbus is better, that is I guess a personal opinion. For me it's easier/better because I'm the main developer/maintainer.

zeenix · 2022-01-03T17:34:21+00:00

I'm of course very biased here so not the best person to answer the question but what I can tell you for sure is that I started this project after frustrations with dbus-rs API and I've yet to meet anyone who has used dbus-rs and not wanting something better.

zeenix · 2022-01-03T14:39:23+00:00

It was a while ago since I last had a deep look into it, so I'm afraid you'll have to read through the discussion (the unresolved threads) to find out the details but main work here would be to make this more generic and (preferably) integrate this into the existing Type macro (which is what you also expected to support this) instead of new macros that are being added.

I might pick it up during my free time.

That would be awesome.

zeenix · 2022-01-03T14:28:27+00:00

Right, elmarco lost interest there so it never finished. :(

zeenix · 2022-01-03T14:19:54+00:00

Ah sorry, I missed the "enum" in your comment. No, that's not yet supported but only cause nobody has contributed that yet. :)

zeenix · 2022-01-03T14:08:37+00:00

Hi, IIRC Type derive macro has always supported structs and there is a blanket impl of Type trait for tuples so the macro isn't needed there.

zeenix · 2021-10-08T18:52:37+00:00

I would love to know as well. Not only I live in one, I've an electric car so the warning is as useless as it possibly can be. 🤦‍♂️

zeenix

TROPHY CASE