upvote

points

by kevin_thibedeau7 hours ago |
comments
upvoteby gerdesj5 hours ago|
[-]
Quite. I was a VMware fanboi (25+ years, man and boy)

I still look after a few VMware estates and a lot of Proxmox ones (that used to run VMware).

Hilariously, VMware is described as "enterprise class", which I can only conclude means MVP and a bit wanky.

Today I repaired a Proxmox HA + Ceph node using boring old normal Linux skills and as it turns out I have 30 years of those. Part way through a remote v8 to 9 upgrade I think I lost comms due to using OpenvSwitch for networking and despite using tmux for the upgrade session. Anyway, the Proxmox ISO was useless for rescue but the classic systemrescuecd worked nicely and I could run dpkg in a chroot.

VMware "used" Linux and never really gave back. I don't miss fixing vCentres and all the other nonsense that "Enterprise" wankery has foisted on me over the years.

reply
upvoteby taneq5 hours ago|
parent|
[-]
When I was first getting into software dev, I thought 'enterprise' meant 'industrial grade', 'powerful', 'high-performing'.

Then I actually met some enterprise software, and realised that it means 'expensive', 'bespoke', 'one-off', and usually 'janky'.

reply
upvoteby phoghed5 hours ago|
parent|
next
[-]
Enterprise means it has SSO and a support contract
reply
upvoteby jacquesm2 hours ago|
parent|
next
[-]
It means you are paying for a support contract. Whether you actually have one time will tell.
reply
upvoteby esseph4 hours ago|
parent|
prev|
[-]
Lol, so true
reply
upvoteby bigbuppo4 hours ago|
parent|
prev|
next
[-]
Enterprise quality software is a just a DOS application, probably written for dBase III, that has been rolled forward to the present day.
reply
upvoteby elcritch55 minutes ago|
parent|
[-]
Those old school systems are often much more stable than any newer systems. Autozone looks to use something like that and I’ve never seen them have issues as a customer.
reply
upvoteby Nursie1 hours ago|
parent|
prev|
[-]
To me it always meant needlessly complex and overspecced for what's needed. I think probably due to Java's enterprise years.

Why solve the problem directly when you can abstract everything away into FactoryFactoryImplementationInterfaceFactorys, and have something that is both a memory-hog and completely unassailable to any normal programmer seeking to understand it or make changes?

reply