• 0 Posts
  • 137 Comments
Joined 7 months ago
cake
Cake day: July 5th, 2024

help-circle




  • Nvidia was “forced” to integrate Linux into its ecosystem

    100% bullcrap.

    Nvidia’s servers for data processing have always run Linux. And you know what those servers run? It’s not Windows, that’s for sure. So why would they write multiple versions of a driver for the same hardware interface? Their servers use the same drivers that you would use for gaming on a Linux desktop system.

    In fact, no version of Windows is supported on their DGX servers, and AFAIK you can’t even install Windows on it (even if you managed, it wouldn’t be usable).

    Long story short, a vendor we were working with (about 6 or 7 years ago now), was working on their Linux version of their SDK. We wanted to do some preliminary testing on Nvidia’s new T4s that at this point were only available via Nvidia’s testing datacenter (which we had access to).

    During a call with some of the Nvidia engineers I had to ask the awkward question of “any chance there’s a Windows server we can test on?”. I knew it was a cringe question and I died a little during the 10 second silence until one of the Nvidia guys finally replied with “no one uses Windows for this stuff”. And he said it slowly like the reply to such a question needed to go slow to be understood, because who else would ask that question unless you’re slow in the head?

    Nvidia has always been hostile to the Linux community or negligent to say the least

    People say “hostile”, but I think a better word is arrogant. They wanted to force the industry to use their own implementations they owned or pioneered like egl-stream instead of open standards. But AMD and Intel have proven that open source graphics drivers not only work, but benefit from being open so that the community can scratch their own itches and fix issues faster.


  • there are no major comprehensive studies that definitively show microplastics are a danger to the body

    I’m not sure what your criteria for “major comprehensive study” is, but there are countless studies linking microplastics to all sorts of things. Most arterial plaques are full of microplastics. The massive drop of male fertility rates (50% globally) has been linked to microplastics. Microplastics have been demonstrated to interfere at the cellular level by mimicking hormones.

    The specifics of everything that they’re doing to us is still unknown. But we know many bad things microplastics definitely are doing.

    We’re WELL past “are microplastics bad?”. We’re at the point of figuring out how badly screwed we are.





  • You car, phone, TV, Rumba, washer, security camera, and microwave spy on you. In fact anything that sends anything through to your phone or wifi is spying on you.

    I have only one smart TV, and it’s not connected to any network.

    I used to have an LG “smart” washer, it was also never connected to any network.

    I have a robot vacuum, it’s incapable of connecting to a network.

    I have several IP security cameras, they are all VLANed and blocked from reaching out to the internet. The recording software is self-hosted and only reachable external through Tailscale (WireGuard). The object detection system I personally built.

    My microwave has buttons from 0 through to 9, start, and stop. That’s it.

    My car is a 2013 Jetta.

    The only thing that spies on me is my phone and general online activity.






  • Then half of your job is dealing with a shitty company and not being a developer.

    Partly correct, but yes.

    Half of your job is being wasted on overhead you can’t manage.

    Who said I can’t manage it?

    How else to describe it than you are half the dev you could be while you blame everyone else. Shit as a director I’m not mixing words.

    Director? That actually tracks. Believe it or not, but a good 30% to 40% of a dev’s work is not writing code. You can’t just start screwing 2x4s together and expect a house. There needs to be coordination and collaboration between the devs; and paradoxically, the more devs you have the more time is spent on that collaboration and coordination part. It’s called The Mythical Man Month. Something managers and directors haven’t been able to get into their heads since the 70s.

    If you can’t break the problem down part of is on the team but a lot of it is on you.

    Break what problem down? What are you on about?

    If you want to architect a solution you have to be able to explain it.

    Ya, that’s absolutely right. And I’ve yet to meet a PM that can properly explain what they’re looking for. They explain result A, they get result A, then suddenly they actually meant result §∆. Happens every time.

    It’s pretty bad having to explain this to coddled engineers learning how the other half of the company works.

    I know full well how the other half works. Not a lot of complexity there. 90+% of what’s said in meetings could be an email. I bet you’re one of those directors that insists the devs have daily check-ins (absolute waste of time) and even have some of the other managers and “stakeholders” join to “ask questions”, when anyone who isn’t a dev has zero right and business to be there. Those stand-ups are not for you and you’re just in the way.

    Talking as if everyone else doesn’t get it

    They don’t. It’s that simple.

    why be an asshole about it?

    Did you really just spit in the face of an entire group and then cry about someone being mean when they called you out? If you’re a director, holy crap! I pity and fear for the people who work with you.

    Why do I get more bs from coders than I do contractors working on my roof?

    I have a theory…

    My grandfather worked on the Apollo missions so why is C# black fucking magic and suddenly you’re Gandalf?

    Your grandfather sounds like he was a smart guy.

    It’s not magic. It’s code

    To me it’s code and logic. To you it’s magic.




  • Seriously I am tired of engineers being gate keepers while the other two legs of the stool keep this shit together.

    Seriously engineers get your shit together as we are all making a product together

    Half my job as a programmer is chasing down the non-devs asking them to explain how they imagined the thing they asked for working, and then trying to find the politest words to say their idea is really bad, all the while trying not to insult their intelligence. The other half is putting out fires that come up all the time because the people who “made the product together” made horrendous decisions about the product design without consulting the devs, or even getting their input. So now we’re saddled with mounting technical debt because of a bunch of morons who were convinced they knew more than the people who teach computers to think.

    Seriously, half the things I hear non-devs say make me actually wonder about the “average” level of intelligence of our species.

    You don’t work magic.

    If it wasn’t, then you’d be able to do the job.

    To you, it IS magic.



  • It uses Universal Blue, whereas Kinoite uses rpm-ostree.

    Aurora has a bit of DE customization, which is arguably more polished.

    It also leans heavily on Flatpack/Flathub.

    The other difference that I’m aware of is Aurora handles updates automatically by default, whereas Kinoite is a manual process.

    To be clear, I haven’t used Kinoite at all. But I have Aurora on a gaming system that I use as a kind of TV gaming console, and I’m setting it up for my elderly parents that get upset when an icon on Windows changes (that’s how tech illiterate they are).