←back to thread

245 points rntn | 2 comments | | HN request time: 0.597s | source
Show context
wkat4242 ◴[] No.45167565[source]
The bigger issue is, if you're refusing to honour a contract as a vendor, not only do you risk a lawsuit like this one. But more importantly, who is ever going to sign up for another contract with you? You just proved it isn't worth the paper it's written on.

Unwritten terms like "valid until I decide to tear it up haha lol" are not generally appreciated by companies that depend on your stuff for their business. Of course you can extort your existing customers until they manage to move away but basically in the longer term you're suiciding your entire business.

replies(11): >>45167604 #>>45167610 #>>45167646 #>>45167690 #>>45167794 #>>45168811 #>>45168947 #>>45169373 #>>45170174 #>>45173303 #>>45173437 #
stego-tech ◴[] No.45167646[source]
This.

I had to tell CurrentCo that I cannot reinstall their vSphere deployment at a client site because they bought a perpetual license, didn’t migrate it to Broadcom before they cut it off, and now we cannot simply go get the latest patch or appliance for that version number without inviting an audit and a sueball from Broadcom.

“Good thing Microsoft would never do that to us.”

Ha. Hahaha.

replies(1): >>45167791 #
ocdtrekkie ◴[] No.45167791[source]
At least VMware isn't user-facing and it can be removed without riots. Imagine trying to tell someone they don't need Excel. I try to maintain at least plausible flexibility to go tell vendors to shove it, but if you have some enthusiastic fans of Microsoft Teams (they exist, who knew?)... Teams is one of those things that is inescapably tied to an incredibly deep well of platform lock-in.
replies(4): >>45167875 #>>45168508 #>>45168872 #>>45169025 #
snapplebobapple ◴[] No.45167875[source]
Really? Teams?? We went teams abd microsoft ecosystem fully because we needed extra windows management stuff as we have grown and users had software that required windows and excel and the biggest pain point has been teams. As near as i can tell it tries to do everythibg wrong and the things that are so blindingly obvious that it can't do them wrong, it finds a way to do them suboptimally
replies(2): >>45167910 #>>45168626 #
gotbeans ◴[] No.45168626[source]
You didn't really say much of what does it do wrong or right, you seem to just try to convey a for-granted idea.

I've been an msft employee for a couple of years and teams... Was ok. I prefer slack, but meetings, video, messaging, formatting, etc. was just fine in teams.

replies(4): >>45169933 #>>45172145 #>>45174053 #>>45176753 #
pohuing ◴[] No.45172145[source]
There's a bunch of annoyances in teams. The text editor is awful if you try to paste/send code for one. The screen sharing is shit by default and only lets one person share at a time for no good reason. It's fairly slow. And it doesn't have a global fucking hot key for push to talk/muting. Despite being integrated with the damn task bar(which is broken if you're on hold in one call and active in another, then it's too stupid to figure out that the mute button is intended to mute my active call, not the one that's on hold...). Also the teams feature gets out of your way, which is an issue if you're trying to use it like you would channels in discord or slack. Would be nice to at least have a notification pip there.
replies(1): >>45178647 #
1. wkat4242 ◴[] No.45178647[source]
> And it doesn't have a global fucking hot key for push to talk/muting.

It's control-space. It is global on Windows as far as I know. Unfortunately you can't change it because I would love to have a single key I don't normally use assigned to it. I use a Mac keyboard with 19 function keys so there's plenty that I would never touch.

I agree with all the other criticism by the way, it's a messy slow clusterf*k.

replies(1): >>45180034 #
2. pohuing ◴[] No.45180034[source]
I hate to be like this, but no it's not(at least not on my windows 10/11 work laptop). It is not active globally, the Teams window containing the call has to be active(on my system).

And it would be a problem if it was, as ctrl shift is the default binding for show suggestions in IntelliJ and Rider.

All of the following you've already mentioned but I forgot you mentioning them in my rage at MS. Figuring out if I'm holding it wrong or not revealed another silly issue however: the push to talk button is hard coded to ctrl space, unlike other keybinds it doesn't show up in the keybinds dialog.