News for hackers. Stuff that matters.
Re:Singularity – Microsoft’s Experimental OS by solarkraft on Sunday October 10, 2021 @07:52AM (#28817682)
Microsoft has such impressive research and such great developers. Makes it all the more frustrating what their products end up like (I’m guessing due to leadership).
Re:Singularity – Microsoft’s Experimental OS by nolok on Sunday October 10, 2021 @08:04AM (#28817747)
> Makes it all the more frustrating what their products end up like (I’m guessing due to leadership).

"Need to make money" is the main reason, actually. Leadership are merely running after that.

Re:Singularity – Microsoft’s Experimental OS by Arisaka1 on Sunday October 10, 2021 @08:57AM (#28818064)
If there's one "conspiracy theory" I'm inclined to believe is that Microsoft deliberately makes every other Windows version subpar to the previous in order to make the market (that has the memory of a goldfish) applaud the follow-up for... going back to what to how things used to be with a few tweaks in between.

It's like they thought that keep improving on the things they work would make them hit a ceiling so instead of steadily climb they take one step back to delay the climb.

And the reason why I think it's deliberate is because none of their other products follows that pattern: Azure faces fierce competition so you cannot afford to stumble, C# is amazing compared to Java at least, Office has alternatives breathing on their back, VS Code... used to have competition but now that it's super popular I'm scared it'll be the next product to follow the "Windows progression pattern".

Re:Singularity – Microsoft’s Experimental OS by hcarvalhoalves on Sunday October 10, 2021 @10:26AM (#28818672)
I think it’s more likely a company that size and the technology as a whole keeps them stuck around a local maxima, only able to iterate around it.
Re:Singularity – Microsoft’s Experimental OS by tenaciousDaniel on Sunday October 10, 2021 @07:56AM (#28817701)
fwiw, VSCode is very impressive. I often forget I'm using an electron app.
Re:Singularity – Microsoft’s Experimental OS by lelandfe on Sunday October 10, 2021 @08:03AM (#28817745)
Which is a big reason why I'm consistently surprised at how terrible Microsoft Teams is, despite also being made with Electron.
Re:Singularity – Microsoft’s Experimental OS by lelandfe on Sunday October 10, 2021 @08:05AM (#28817757)
One of my favorite "just why" moments in Teams: let's say I have an image, `foo.jpg`.

I share it once and it gets uploaded to Sharepoint (as `foo.jpg`). This happens even if you're just sharing a funny image in a private message. It gets uploaded to Sharepoint. Ugh.

Anyway, let's say I share the same image again. Teams says "hey do you want to overwrite `foo.jpg`, or keep the existing one?" I select keep. Teams now creates `foo-1.jpg`.

We're already off to a bad start, but bear with me. Here's where it gets amazing:

1. I share `foo.jpg` a third time.

2. Teams says "Do you want to overwrite or keep?" I select keep.

3. Teams then again asks "Do you want to overwrite or keep?", because `foo-1.jpg` is taken. I select keep.

4. Teams tries to create `foo-2.jpg`. Return to step #2 until an unused integer is found.

That chain of dialogs can continue for a while for common file names on large teams.

Re:Singularity – Microsoft’s Experimental OS by JoiDegn on Sunday October 10, 2021 @08:25AM (#28817853)
One of the biggest reason I find teams not usable for teams. And so easy to fix, just assume when the user does not want to overwrite the first file that they don't want to overwrite consecutive files.
Re:Singularity – Microsoft’s Experimental OS by vidanay on Sunday October 10, 2021 @09:53AM (#28818425)
Aside from the annoyance factor, this is a huge gaping hole allowing information leaks. Let's replace `foo.jpg` with `Annual Review 2021.pdf`. You send employee #1 their review, and then send employee #2 theirs, but forget about this quirk, and instead of keeping, you overwrite. Now employee #1 can open employee #2's confidential info in their link.
Re:Singularity – Microsoft’s Experimental OS by lelandfe on Sunday October 10, 2021 @10:23AM (#28818650)
Thankfully (I guess?) that isn't a problem: the files are uploaded to Sharepoint folders specific to conversations or channels.

So the issue I detailed would only rear it's head in your scenario if you sent employee #1 their review twice.

Humorously, this issue does not occur when uploading files directly in the Sharepoint interface – despite the interface looking like it stepped out of Windows 95.

Re:Singularity – Microsoft’s Experimental OS by vidanay on Sunday October 10, 2021 @10:26AM (#28818669)
I'll have to verify this tomorrow, but I am 99% certain I have seen this message when sharing the same file name between different 1:1 conversations. I guess it's possible that it is a configuration issue since our Teams/SharePoint is self-hosted at my company.
Re:Singularity – Microsoft’s Experimental OS by lelandfe on Sunday October 10, 2021 @10:33AM (#28818723)
Yeah, I am not a licensed Microsoft config guy whatsoever, but do know that Sharepoint can be configured to the moon and back. That was, after all, the reason my old org went with Teams over Slack.

So it's not hard for me to imagine that it could be set up in a way that causes this issue across discussions. Yuck.

Re:Singularity – Microsoft’s Experimental OS by JeffRosenberg on Sunday October 10, 2021 @08:46AM (#28817991)
Man I hate this. I sort of get wanting to support robust file sharing for teams, but let's be honest: 99% of file uploads on teams are going to be silly gifs.
Re:Singularity – Microsoft’s Experimental OS by lelandfe on Sunday October 10, 2021 @10:31AM (#28818714)
It is also SO SLOW. It's so slow. Uploading images takes full seconds before they can be sent because Teams has to put them onto Sharepoint first (which itself is slow).

For those still on Teams, my condolences, here's a workaround: copy the image onto your clipboard and paste it into the textbox. It skips the uploading to Sharepoint, prevents the issue I described, and is sendable in milliseconds. Downsides: a. they're randomly ephemeral and sometimes just permanently disappear, b. no animated images - it'll just send the first frame of a GIF/APNG/etc.

And for those on macOS, that means you can get screenshots sent quickly. Ctrl-Cmd-Shift-3, Cmd-V into the text field. Send.

Re:Singularity – Microsoft’s Experimental OS by _ph_ on Sunday October 10, 2021 @04:51PM (#28821868)
I have stumbled over the same problem and wondered why at minimum it isn't able to recognize that this is the identical file and not ask. Also, it should be able to reshare one file already uploaded.
Re:Singularity – Microsoft’s Experimental OS by sha-3 on Sunday October 10, 2021 @08:07AM (#28817766)
Only until I have to open Task Manager to see what's hogging my memory.
Re:Singularity – Microsoft’s Experimental OS by tenaciousDaniel on Sunday October 10, 2021 @09:06AM (#28818122)
Ha, usually it's a game of "is this vscode, postman, chrome, or all of the above?"
Re:Singularity – Microsoft’s Experimental OS by datavirtue on Sunday October 10, 2021 @10:41AM (#28818791)
Chrome. It's Chrome.
Re:Singularity – Microsoft’s Experimental OS by atatatat on Sunday October 10, 2021 @09:18AM (#28818197)
Many things, including OS, will take as much memory as you allow — this is by design/helpful in some cases.
Re:Singularity – Microsoft’s Experimental OS by monocasa on Sunday October 10, 2021 @12:36PM (#28819735)
Only the OS and applications intending to be the only application ever running on a box should do that. When normal applications do that, they don't have the information to share when their peers need those resources too.
Re:Singularity – Microsoft’s Experimental OS by jbjbjbjb on Sunday October 10, 2021 @09:41AM (#28818330)
Worth noting they didn’t use dotnet to build VSCode (and to a lesser extent Teams) when they could have.
Re:Singularity – Microsoft’s Experimental OS by forgotpwd16 on Sunday October 10, 2021 @08:57AM (#28818067)
Has or had? Singularity's last release was more than 10 years ago predating Windows 7 perhaps the most acclaimed OS release Microsoft had.