Lenovo is really crap
-
@Douglasac Dell Backup and Recovery (rebadged from something else), Dell SupportAssist (rebadged pcCillin), Dell Update, Dell Power Manager, Dell Digital Delivery (for if you ordered any non-mandatory crapware), McAfee, Rivet Networks, PowerDVD, the Dropbox shortcut, and one other thing...
@levicki said in Lenovo is really crap:
What's wrong with systemd?
Its invasion and mandatory integration of so many areas that used to have a diverse software offering. Its creators' sheer arrogance and asshattery. Its upcoming loss of support in favor of "SystemKit", like PolicyKit and all the other crap its creators made.
-
@TwelveBaud said in Lenovo is really crap:
Its creators' sheer arrogance and asshattery.
Systemd is the
of the system services world.
-
@dkf It works amazingly well but due to who-moved-my-cheese-ism a small group of people hate it?
-
@loopback0 said in Lenovo is really crap:
@TimeBandit said in Lenovo is really crap:
@sockpuppet7 said in Lenovo is really crap:
4GB RAM
And you're trying to run Windows on that?
I'd be more concerned about trying to run Chrome or the new Chromium-powered Edge on that. 4GB is like a couple of tabs.
Or plenty enough to run Crysis on Windows 7. Maybe Crysis 2. Probably Far Cry 2, even if it were 2GB, depending on the updates installed on that Win7; the "compatibility monitoring (cough spying cough) task" kills performance on spinning-rust systems until terminated. I have to always remember to kill it before I start gaming.
-
@pie_flavor said in Lenovo is really crap:
@dkf It works amazingly well but due to who-moved-my-cheese-ism a small group of people hate it?
No, that's totally wrong. It doesn't work amazingly well at all. It's had a mountain of CVEs because that's what happens if you reimpliment complex systems from scratch and your testing isn't rock solid. It was blindingly obvious it would be a disaster because that's a well-trod road.
Poettering suffers from a ego problem like Linus, unfortunately he isn't a 1/5 the programmer Linus is.
-
@Cursorkeys said in Lenovo is really crap:
Poettering suffers from a ego problem like Linus, unfortunately he isn't a 1/5 the programmer Linus is.
Linus appears to at least take the position that the desired goal is for the software to be fault-free, even if that's exceptionally difficult to achieve. That means he tends to take seriously those people who report that problems exist, and gets upset with people who put faults in through sloppiness (this where his epic rants tend to come from). High egotists like Poettering (and
) instead assume by default that they're doing the right thing and that other people are just being a bit stupid for not seeing it at first glance.
-
@levicki said in Lenovo is really crap:
And that's OK, because sometimes you cannot advance without breaking up with your past. Also no matter how good your testing is, nothing can replace actual use.
In my view it isn't an advance, it's a solution for the sake of a solution. The init system was just fine before systemd. It doesn't solve anything pressing, it just re-implements things, poorly.
Edit: Ok, having a unified init system across distros is handy, granted. I just don't think it was that big of a deal.
-
@Cursorkeys said in Lenovo is really crap:
No, that's totally wrong. It doesn't work amazingly well at all.
Maybe it does on Earth-73!
-
@Zerosquare said in Lenovo is really crap:
@Cursorkeys said in Lenovo is really crap:
No, that's totally wrong. It doesn't work amazingly well at all.
Maybe it does on Earth-73!
It's all a question of perspective.
It works amazing well just like Windows Update and
works amazing well.IOW, it's a fuckin piece of shit.
-
@TwelveBaud said in Lenovo is really crap:
Dell Backup and Recovery (rebadged from something else), Dell SupportAssist (rebadged pcCillin), Dell Update, Dell Power Manager, Dell Digital Delivery (for if you ordered any non-mandatory crapware), McAfee, Rivet Networks, PowerDVD, the Dropbox shortcut
This is the incomplete list of software from an HP Elitebook I set up last week: Bonjour, HP Client Seucrity Manager, HP Collaboration Keyboard, HP Connection Optimizer, HP Device Access Manager, HP Documentation, HP ePrint, HP Jumpstart Bridge, HP Jumpstart Launch, HP MAC Address Manager, HP Notifications, HP Phonewise Drivers, HP Support Assistant, HP Support Solutions Framework, HP Sureclick, HP Sure Recover and HP Sure Run.
Also included are assorted HP UWP apps that I simply delete in audit mode for all users, along with the fun new Office UWP\desktop hybrid thing that, among other things, breaks the Outlook signature window if you use Office 2016.
Preinstalled crap aside though, the current Elitebooks are actually quite nice laptops. As I said before, when they put their mind to it, they can actually design something decent. They just then proceed to ruin it with software.
-
-
@HardwareGeek said in Lenovo is really crap:
Two idiots; one keyboard?
It has Special Buttons(TM) for Skype for Business and such.
-
@levicki said in Lenovo is really crap:
"what is wrong with systemd from a political point of view"
SystemD managed to unify all distros on a single init system, making things more compatible.
Clearly Poettering is the hero we need, just not the hero we deserve, or something like that.
-
@levicki said in Lenovo is really crap:
@TwelveBaud said in Lenovo is really crap:
Its invasion and mandatory integration of so many areas that used to have a diverse software offering. Its creators' sheer arrogance and asshattery. Its upcoming loss of support in favor of "SystemKit", like PolicyKit and all the other crap its creators made.
When I asked what is wrong with systemd I meant "what is wrong with systemd from the technical/architectural point of view" not "what is wrong with systemd from a political point of view".
So, either debate technical merits (pros and cons), or just outright say "I am an old geezer and I hate change" and be done with it.
@Cursorkeys said in Lenovo is really crap:
No, that's totally wrong. It doesn't work amazingly well at all. It's had a mountain of CVEs because that's what happens if you reimpliment complex systems from scratch and your testing isn't rock solid. It was blindingly obvious it would be a disaster because that's a well-trod road.
And that's OK, because sometimes you cannot advance without breaking up with your past. Also no matter how good your testing is, nothing can replace actual use.
Having high cohesion and low coupling is not just for OOP, it's also good for init systems (and whatever systemd is). SystemD is the other way around, it's leaking it's shit all over the place, creating the perfect environment for leaky systems and that is a perfect place for CVEs to happen, and you most definitely do not want CVEs in the parts of the operating system that SystemD has taken over.
The reason for the never ending stream of CVEs for SystemD is not that it's new, it's that its base design is flawed, and the lead developer is shit at his job.
Init was old and crusty and in need of replacing, but systemd is worse.
-
@Carnage said in Lenovo is really crap:
systemd is worse
There are two key problems: one is that it is not written in such a way as to be naturally resistant to faults, and the other is that it is not written in such a way as to be highly compatible with other existing OS components. Both stem from a common source, that the lead author is a egotistical jerkwad.
