• 0 Posts
  • 65 Comments
Joined 2 years ago
cake
Cake day: June 18th, 2023

help-circle



  • I have one of these, but only use it for SteamVR. Does this mean I can’t update either?

    AFAIK, the drivers come from Windows.

    Edit:

    From the article:

    Existing Windows Mixed Reality devices will continue to work with Steam through November 2026, if users remain on their current released version of Windows 11 (version 23H2) and do not upgrade to this year’s annual feature update for Windows 11 (version 24H2). This deprecation does not impact HoloLens.

    Well fuck. This headset is the only reason I keep a Windows PC around at all.



  • wim@lemmy.sdf.orgtoLinux@lemmy.mlLinux Boomers
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    To quote the author himself:

    Great, do whatever you want. Just shut the fuck up about it, nobody cares.

    But then he proceeds to do the exact opposite and posts a vitriolic rant about how everyone who doesn’t use what they use is, in their words, and idiot.



  • I’m not trying to be defeatist. I’m just advocating for unions to stop focusing on the local aspect. Transnational cooperation is what is needed in unions today.

    Something which larger unions, such as the steel and car industry unions in Europe have been trying (and mostly failing) to do for almost two decades.

    Companies, by and large, have used the globalized economy to sidestep local action for almost 30 years now.

    Ignoring this is simply a recepy for repeating the mistakes of the past. Especially in software, where there is no physical production equipment at all, and in games, where talent and labour is plentiful.

    Unless you have an organization that reaches as far as the companies you’re trying to bring to the table, you will simply be outmanœuvred.

    You also overestimate the level of union participation if you think they would need to lay off everyone to break a union strike.

    Feel free to tell me I’m wrong, but I’ve been through the proces twice, both involving union action, both in the software industry. Once as part of the workers delegation to the negotiating table. Dismiss a company’s ruthlessness or resourcefulness at your own peril.

    Local unions can only hope to hold off the axe until current projects where the required know how can not be rebuilt or transfered in time are done.




  • I don’t understand what you mean. Why does ARM hardware become obsolete after a few years? Lacking ongoing software support and no mainline Linux?

    What does that have to do with the instruction set license? If you think RISC-V implementors who actually make the damn chips won’t ship locked hardware that only run signed and encrypted binary blobs, you are in for a disappointing ride.

    Major adopters, like WD and Nvidia didn’t pick RISC-V over arm for our freedoms. They were testing the waters to see if they could stop paying the ARM tax. All the other stuff will stay the same.





  • This used to be me but mostly because I would experiment a little too much, never without reason.

    Except a few Arch updates over a decade ago when they changed the default from hal to udev, or a Gentoo setup with WAY too specific USE flags, I don’t think I can remember any failure like this ever. I’ve honestly had more issues with Windows nuking itself on a major update.

    Mostly using Debian and Fedora these days, and it’s been smooth sailing for quite some time.




  • While C is certainly better for some problems in my experience, it too is very hard to use in large projects with a mix of developers, and it is unsuitable for most higher level applications in most companies.

    I think C has its place in the world still, which is mostly confined low level embedded, kernel space and malware. I do believe that the market segment that used to rely on C++ is today better served by either Go or Rust, depending on the project.

    That said, while I LOVE working with Rust, it suffers from many of the same issues I mentioned for C++ in my comment above when working in a mixed skillset team.


  • wim@lemmy.sdf.orgtoProgrammer Humor@lemmy.mlDepression Is No More
    link
    fedilink
    arrow-up
    38
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Everything is fine within the scope of a college course or project.

    Where C++ breaks down is large, complicated projects where you colaborate with other developers over multiple years.

    I worked in C++ for almost a decade, and while there were a few good projects I encountered, most suffered from one or more of the following problems:

    • C++ has so many parts, everyone picks a subset they think is “good”, but noone seems to fully agree on what that subset is.
    • A side effect of the many possibilities C++ offers to compose or abstract your project is that it allows for developers to be “clever”. However, this often results in code that is hard to maintain or understand, especially for other developers.
    • Good C++ is very hard. Not everyone is a C++ veteran that read dozens of books or has a robust body of knowledge on all its quirks and pitfalls, and those people are also often assigned to your project and contribute to it. I was certainly never an expert, despite a lot of time and effort spent learning and using C++.