enemenemu

joined 1 month ago
[–] [email protected] 6 points 2 weeks ago* (last edited 2 weeks ago)

At least an ai would've adressed the topic but the post didnt

[–] [email protected] 2 points 2 weeks ago

That's smart, thx

[–] [email protected] 21 points 2 weeks ago* (last edited 2 weeks ago) (4 children)

Unfortunately, the article does not write about how people use it.

I use it to skip reading docs. Either it works, or I read the docs, sometimes in parallel, whatever is faster.

Oftentimes I just forgot how some function is called.

I'm still in the testing phase and in more than 50% of the cases its crap. Halizination is a real problem with those models that I've used.

[–] [email protected] 6 points 2 weeks ago

Difficult. Paperwm/ Niri has the best workflow.

I am looking forward to set niri as compositor on cosmic.

[–] [email protected] 19 points 2 weeks ago (2 children)
[–] [email protected] 4 points 2 weeks ago* (last edited 2 weeks ago)

I am no dev of rust.

My guess:

  • they didn't want to scare anyone.
  • They really think that MIT is free and that anyone shall do with it whatever they like. They are not afraid that someone takes the rust code base and produces a proprietary fork and make money from it.
[–] [email protected] 6 points 2 weeks ago

You are allowed to license your code change under gpl, you do not have to use MIT just because the package author uses MIT. You can use GPL.

You can also use MIT or no license at all. it does not force you to use MIT

[–] [email protected] 4 points 2 weeks ago (4 children)

You could say that, yes.

It makes sense to suggest MIT license for a MIT project

MIT is better than proprietary. MIT does not force you to not make your project free.

[–] [email protected] 22 points 2 weeks ago* (last edited 2 weeks ago) (7 children)

It's kind of the default in the docs

https://doc.rust-lang.org/cargo/reference/manifest.html?highlight=License#the-license-and-license-file-fields

SPDX license expressions support AND and OR operators to combine multiple licenses.1

  [package]
   # ...
  license = "MIT OR Apache-2.0"

Using OR indicates the user may choose either license. Using AND indicates the user must comply with both licenses simultaneously. The WITH operator indicates a license with a special exception. Some examples:

MIT OR Apache-2.0
LGPL-2.1-only AND MIT AND BSD-2-Clause
GPL-2.0-or-later WITH Bison-exception-2.2

When I started out (I don't write Rust but other languages), in my first years, I liked gpl and after a couple of years I got to know MIT and I started using that because I thought it is "more free". I wasn't aware of the consequences immediately. Once I read the GNU philosophy and started reading more about free software, I started using gplv3 again

[–] [email protected] 4 points 2 weeks ago (2 children)

Good for you

Poor prof

[–] [email protected] 7 points 2 weeks ago (6 children)

Are you still using matlab? Why? Seriously

view more: ‹ prev next ›