this post was submitted on 28 Aug 2024
77 points (98.7% liked)

Games

16714 readers
536 users here now

Video game news oriented community. No NanoUFO is not a bot :)

Posts.

  1. News oriented content (general reviews, previews or retrospectives allowed).
  2. Broad discussion posts (preferably not only about a specific game).
  3. No humor/memes etc..
  4. No affiliate links
  5. No advertising.
  6. No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
  7. No self promotion.
  8. No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
  9. No politics.

Comments.

  1. No personal attacks.
  2. Obey instance rules.
  3. No low effort comments(one or two words, emoji etc..)
  4. Please use spoiler tags for spoilers.

My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.

Other communities:

Beehaw.org gaming

Lemmy.ml gaming

lemmy.ca pcgaming

founded 1 year ago
MODERATORS
nanoUFO@sh.itjust.works
77
Microsoft donates the Mono Project to the Wine team (www.gamingonlinux.com)
submitted 2 months ago by nanoUFO@sh.itjust.works to c/games@sh.itjust.works
9 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] trolololol@lemmy.world 1 points 2 months ago (1 children)

Assuming that they will do EEE here once more, can the community fork the latest version of. Net and do with it whatever they want, including maintaining cross platform support if MS decides to abandon that part?

[–] DacoTaco@lemmy.world 1 points 2 months ago* (last edited 2 months ago) (1 children)

The mit license allows forking, merging, modifying and releases of modified code. Yes id assume so yes :)
I have a lot of bad things to say about some microsoft teams and some microsoft managers (cough fluentui webcomponents team cough ), but in general the .net team is a nice one and ive had several nice encounters with few of its devs.
Just dont know what the actual bloody fuck the manager/team was thinking dropping linux when they made maui...

[–] taladar@sh.itjust.works 1 points 2 months ago (1 children)

What I would really like to know is the thought process behind using the oldest dependency version in a version range in .NET instead of the newest like literally every other package or dependency manager ever made. That design couldn't be worse if it was designed to maximize security holes.

[–] DacoTaco@lemmy.world 1 points 2 months ago (1 children)

Care to elaborate? I dont fully follow ^^; Feel free to also dm me or something

[–] taladar@sh.itjust.works 1 points 2 months ago (1 children)

If you specify that e.g. a dependency should be between version >= 4.0 and < 4.1 in dotnet and there are versions 4.0.0 and 4.0.1 available pretty much all other systems choose 4.0.1 based on the idea that that will include a fix while dotnet chooses 4.0.0 based on the idea that that is "more stable".

[–] DacoTaco@lemmy.world 1 points 2 months ago

Ah, thats fair. I think thats fixable using wildcards in the packagereference in the csproj, but id need to check. I too would expect it to choose 4.0.1 unless a patch release needs a big update or something