Quoting: Alm888you are outright bashing users of other services and stores

Do you actually see that you are doing exactly this?

I gave you that advice earlier when you were attacking Feral without ever having owned one of their games: "Get a beer and take a deep breath". Same advice here with Valve.

View this comment - View article - View full comments

Quoting: GuestValve only did anything as a backup plan.

Yes, sure, but even just for that they did more than anybody else for Linux gaming recently in that regard. It is the result that matters imho.

View this comment - View article - View full comments

Quoting: Alm888

Quoting: meggermanLinux gamers can't afford to ditch Valve at this point…

I personally have all the rights to ditch Valve however I want. And Valve can not do anything to me. Because I don't even have Steam account and neither is planning to, ever. :D

Why don't you just stay out of this discussion then?

View this comment - View article - View full comments

Quoting: GuestAnd forcing open source I disagree with. I try to use words like encourage, or want, instead of force/must, because ultimately the choice should always be up to the user, and things aren't black & white.

Sorry, this is what I wanted to say. My impression is that you do not force your opinion on others. Thanks for that.

View this comment - View article - View full comments

Quoting: GuestIt restricts the use of my hardware in a technical capacity.

Would you really be able to fully use your hardware if there hadn't been any company with some real resources/money behind it? Hardware was difficult 20 years ago and since then it certainly hasn't been getting easier. Some companies do actively support Linux the way the Linux community prefers it (Intel, recently AMD), others support Linux in a less FOSS compatible way (NVidia). Though it is Nvidia's freedom to do it their way. Being not your best friend doesn't automatically makes you an enemy. (Note: you didn't imply that, that's just a general statement)

Quoting: GuestSo yeah, that's why I want FOSS. Want though, not enforce.

Thanks a lot for coming up for your principles, but not trying to force others do to so.

View this comment - View article - View full comments

Quoting: GuestAll of which just makes me ask: why do you use GNU/Linux?

Linux has more to offer than just the ideals of Open Source. Speaking for myself, I prefer Open Source, but don't mind using the NVidia propriety driver (from the negativo17 repositories for Fedora, works really well), Steam, JetBrains Rider or other closed source applications either. What is important for me is that I have an OS that works and that fits into my workflow. I love how Gnome Shell works, prefer how Linux performs, how it is structured and built as OS (e.g. no file locking compared to Windows) and how package management works. Simply stated: Linux is just the better OS, being Open Source is a nice welcome.

PS: That said, I'm not blind. Linux has its shortcomings and Windows or MacOS have their strengths, but overall Linux is the winner for me.

View this comment - View article - View full comments

Quoting: GuestOh, and medical device development isn't suited to "proper" agile. It needs documentation for every minor detail and change (with good reason really).

Yes, sure, should have added that there are branches that needs a different or adapted treatment. There is no "one size fits all". If someone claims so for whatever, it ain't true.

View this comment - View article - View full comments

Quoting: GuestThat book has the word "agile" in the full title. No way I'm going to read it. I despise that term.

Yeah, shame that this term has been so heavily abused, especially by so-called scrum masters that never really understood what this is about. The original meaning/the statements from their manifesto are still very valid if one reads with care.

View this comment - View article - View full comments

Quoting: tuubiIgnoring the condescending tone of your reply

I guess both our comments have that condescending tone. I apologize if that triggered something inside you, that was not my intention.

Quoting: tuubiis that supposed to be an argument against code comments?

No, as I stated, there are lots of valid comments. Mostly about WHY a certain piece of code has to be there, assumptions, preconditions, external references etc.

I discourage comments about WHAT a certain code is doing, these kind of (simple or ugly) comments should be part of the code itself.

// This is needed due to this and that

var i = 0; // iterates over list Y

// Does something
[a few lines of code]

// Does something else
[a few lines of code]

// Does something different if this is given
if (this == that && that == something)
{
  [a few lines of code]
}
should imho be written as
// This is needed due to this and that
var yIterator = 0;
DoSomething();
DoSomethingElse();

if (ThisIsGiven())
  DoSomethingDifferent();

...

The second version is much more robust against rework and refactoring, don't you think? Note that I was taking about several years, i.e. ten, between Developer/Team A and B, where A and B have never spoken to each other. Development methods (coding styles, review procedures, team organization) were quite different ten years ago and will be again quite different ten years in the future. Code that has to to survive this time span will get messy over time due to different approaches how to solve things, especially because teams doing maintenance later are usually not the strongest ones. Having code as robust as possible, that includes removing ugly comments and replace them with method extraction and better naming, helps to stand the test of time a little bit better.

Edit: Extend sample.

View this comment - View article - View full comments

Quoting: tuubi

Quoting: jensA second developer touches the code (years) later, does some refactoring but leaves the (no longer matching) comments as is, cause it seems nice to have comments and because comments aren't touched if you use some tooling for refactoring (Jetbrains and friends).

And here you see a developer who doesn't do his/her job. If comments are no longer relevant after you've changed the code, it's your job to update or remove them accordingly. Tooling is a bad excuse.

Welcome to the real world ;). Of course this was a bad job, but these things do happen, though usually much more gradually over time thus a lot less obvious.

View this comment - View article - View full comments