721–730 of 840 posts
Earlier quoted context omitted.
Allow install of Windows onto a partition and not overwrite the MBR
I've hated that behavior for years, and am appalled to learn this it still works that way.
It looks okay if you only have one Windows in your boot options but once you have two you realize you have two bootloaders.
In MS shops no one really wants to use TFS, so most turn to Gitlab and Bitbucket.
I'm excited by this. I feel trapped between Google who will give everything away in exchange for spying on me, and Apple who will respect my privacy but shake me upside down with the most ridiculous vendor lock-in tactics. I'm glad someone as powerful as Microsoft can play the underdog role and provide a viable third alternative. Windows laptops that run Linux well enough for development. VS Code. I now develop on my…
> I have a lot of faith in this acquisition. My software team is growing fast and we have so many little problems that feel like they should be solved at the GitHub layer but the solutions aren't there. Microsoft will fix that. I'm pretty strongly opposed to the petty naysayers and partisan Microsoft bashing, and I'm definitely firmly embedded in the Microsoft camp from a toolset perspective, but I'm very, very far a…
People used to think that Apple did, and now there's a post every four weeks about how bad Apple's QA is because there's a bug if you post an obscure character in a language used by Google's customer support is famously useless, and Microsoft has a ton of bugs.
At some point someone will find a mythical company which cares about the little things that bother us, but that will probably happen shortly after the AI singularity shows up.
Earlier quoted context omitted.
> Apparently people didn't like having fully locked down computers and they discontinued the product, shocker. They do, it just can't pretend to be a full on computer, see the iPad.
It doesn't have to pretend, it is a full computer that is intentionally crippled by the vendor. Apple doing it to doesn't make it any less despicable. These stupid strategies turn perfectly good computers into landfill.
Not affiliated with the team, but I feel compelled to plug https://gitea.io/en-US/ here ... such a lean alternative to GitLab, I was really happy to find it. Runs just fine for a couple of dozen users on a rather whimpy virtual server.
This is a wake up call. Too many things are relying on Github right now. Microsoft was part of the PRISM program. If Microsoft shares SSL certs with NSA they could do MITM attacks. What if in some very specific cases you download dependencies from GitHub and they give you a different version with malicious code? It's the NSA. They could be smart enough to only deploy those attacks on production servers were nobody is…
They could also do it regardless of whether or not Microsoft owns them or whatever favorite acronym authorizes them, or whatever. I've never understood why people love freaking out about this stuff. If the NSA felt like spying on you, pro tip, they're gonna be able to do it. If you care about keeping your shit secure, it shouldn't be on the internet at all.
Earlier quoted context omitted.
>they still refuse to publish the complete list of what is collected They give you the option to fully inspect all the telemetry data your computer is sending, categorized by use. https://docs.microsoft.com/en-gb/windows/configuration/diagn...
incorrect. That page tells you about diagnostic telemetry, but there can be other kinds of telemetry.
Earlier quoted context omitted.
> If Microsoft shares SSL certs with NSA they could do MITM attacks. There is zero reason to believe they do.
Your intention is correct, but your details are not (as are the OPs). Microsoft share's it's SSL certs with the entire planet. Microsoft protects it's private keys and does not share them with the NSA. The NSA forges Microsoft's SSL keys, they do not need to ask for them. https://en.wikipedia.org/wiki/Flame_(malware) Even with the mitigations provided by moving away from MD5, simple integration with a CA would be muc…
> Even with the mitigations provided by moving away from MD5, simple integration with a CA would be much more strategically beneficial.
Returning to the point, this attack would be unaffected by Microsoft purchasing anything.