0x4E4F

joined 1 year ago
MODERATOR OF
[–] 0x4E4F@sh.itjust.works 2 points 17 hours ago

Meeh, I dual boot.

[–] 0x4E4F@sh.itjust.works 5 points 17 hours ago
[–] 0x4E4F@sh.itjust.works 5 points 17 hours ago* (last edited 17 hours ago) (2 children)

And the people that don't use systemd.

 
 
[–] 0x4E4F@sh.itjust.works 1 points 1 day ago* (last edited 1 day ago)

Yeah, they tried that a few times, the software would glitch and Windows would either BSOD or just freeze (had something to do with how their HASP dongle license communicated with the software and the drivers it used, nothing to do with our issue whatsoever, lol). In the end, they had to come down and debug the issue on a separate rig and install. We just couldn't have those interruptions in production.

[–] 0x4E4F@sh.itjust.works 1 points 2 days ago

Yep, I know the face... made it a few times with colleagues that don't know basic Windows scripting, but somehow got bonuses... but I don't kiss upper management ass, so I never do. That's life I guess...

[–] 0x4E4F@sh.itjust.works 2 points 2 days ago

This is so true... it's so frustrating sometimes...

[–] 0x4E4F@sh.itjust.works 1 points 2 days ago* (last edited 2 days ago) (2 children)

Me too, but apparently, that wasn't the case.

My reasoning was, they'd have to send someone over to do tests and build the project on site, install and test, since we couldn't give any of those NASes to them for them to work on the problem, and they'd rather not do that, since it's a lot more work and it's time consuming.

[–] 0x4E4F@sh.itjust.works 3 points 2 days ago (1 children)

The fact that I tried nearly a dozen distros, and I tinkerer with it for a literal month, I'm not touching shit.

Lol 😂, yeah, I can understand that. You just want things to work, totally understandable.

Now, fuck no, it should "just work".

Agreed. I can understand things not just working 20 years ago, but in this day and age, yes, they should just work.

I think money is the main issue... for most of the devs working on Linux, this is a fun side project, not an actual job. So, they dedicate spare time to this, nothing more. It's the sad truth I'm afraid.

[–] 0x4E4F@sh.itjust.works 16 points 2 days ago (1 children)

Exactly what a dev would say... you guys don't have to deal with that 3rd gen i3 Jenny from accounting is running.

[–] 0x4E4F@sh.itjust.works 1 points 2 days ago* (last edited 2 days ago)

Yeah, one of the reasons why I switched to Linux, I just got fed up of looking for cracks for applications... I usually ran everything first in a VM with no virtual Ethernet adapter at all, so viruses were not usually a problem, but still, it was a hassle, you still have to power it up and install the damn thing, than run the crack...

[–] 0x4E4F@sh.itjust.works 1 points 2 days ago (1 children)

Try LTSC 2019 (there are 2 other releases for 10, LTSC 2021 and LTSB 2016, back in 2016 it was named Long Term Support Branch). It's almost like Win7 regarding speed... almost.

Not saying you should switch, but I dual boot because sometimes I need things that just don't run even in Wine, so if I have to use Windows, I use LTSC. A lot less intrusive, doesn't have the bullshit apps that come with regular Pro and Home, and, on top of that, 2019 has a 10 year support cycle (they changed it to 5 with LTSC 2021). So, basically, I'm covered till 2029.

[–] 0x4E4F@sh.itjust.works 1 points 3 days ago* (last edited 3 days ago) (3 children)

Long Term Support Channel. It's Windows 10/11, but without all of the app crap. It's frozen in time to when it was released, just takes security updates, no feature updates. Same as any Windows before 10.

687
Sometimes, it's backwards (sh.itjust.works)
submitted 3 days ago* (last edited 3 days ago) by 0x4E4F@sh.itjust.works to c/programmer_humor@programming.dev
 
 
 
 
 
 
 
view more: next ›