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…
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…
This is so true… it’s so frustrating sometimes…
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.
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.
Exactly what a dev would say… you guys don’t have to deal with that 3rd gen i3 Jenny from accounting is running.
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…
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.
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.
Agreed. I have colleagues that I write scripts for (I don’t do that any more, I stopped and shit stopped working, so they solve things manually now), they don’t know shit about scripting… and still don’t.
On the other hand, I’ve had the pleasure of working with a dev that was just this very positive, very friendly person and was also very knowledgeable when it came to hardware, so we were on the same page most of the time. He also accepted most of my code changes and the ones that he didn’t, gave him an idea of how to solve it more efficiently. We were a great team to be honest. We’re still friends. Don’t see him as frequently, but we keep in touch.
Well, at least you admit it, not everyone does.
I do agree that they’re out of date, but that wasn’t their point, their software somehow doesn’t like the NASes, so they had to look into where the problem was. But, their first thought was “let’s tell them they’re no good and tell them which ones to buy so we wouldn’t have to look at the code”.
Yep, unrealistic expectations.
Or “you need a 12th gen i7 to run this thing”… the thing is a glorified Avidemux.
It was way too early. If that happened after 11, very few would mind. But it happened way too early. 7 had the classic 6.x kernel start menu, and 8 suddenly had… no start menu button at all 😬. That was their mistake, way too much change way too early.
You don’t have to make it a part of the kernel, it could be an external module, like the firmware. I’ve done it before, it’s not as scary at it sounds. Yes, at a certain point, it will stop to work and you’d have to recompile with a new compiler (if that doesn’t work, code changes need to be implemented), but in most cases, you don’t have to change a thing, except download the new source for the driver and build it again.
It usually works for about a year or two, then you have to rebuild, so it’s not that big of an issue.
MiUI is not that bad IMO. The ad services and the integrated apps are horrible (even without the ads), but apart from that, the UI is fairly usable. They really haven’t changed that much from what Android comes with by default.
Meeh, each to his own 🤷.
Simple example, our NASes are EMC2. The devs over at the company that does the software say they’re garbage, we should change them.
Mind you, these things have been running for 10 years straight 24/7, under load most of the time, and we’ve only swapped like 2 drives, total… but no, they’re garbage 🤦…
You’re gonna get downvoted because of 8.1.
But yes, I do agree, 8.1 was great, a lot better than 10. The problem with it was the start menu (easily fixable) and the fact that MS didn’t invest money or time in it after 10 came out, so a lot of bugs went unfixed.
because literally nothing else that ships with KDE supports my machine’s 5G modem…
Why not just take that module, build it yourself, add the firmware package as well, repackage it and install it on whatever distro you like. I know, it sounds like a lot of work, but you only have to do it once… or maybe twice, depending on what is removed/added in future kernels.
Exactly, same as Arch… which is why I used Arch for like 2 weeks and then hopped to Void. Sorry, but it was the same bullshit all over again, services not running properly, slow boot time, services stalling at shutdown… I’m sorry but, with the words of Garry Oldman, I haven’t got time for this Mickey Mouse bullshit!
Runit on the other hand… it just works. Set it and forget it!
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.