My favorite Windows drag-and-drop feature is that if ever I drag a file over the left pane of Explorer on its way to another window, the whole thing freezes up for a minute or so. I think it’s polling all the network drives just in case I might decide to drop it there, and since my NAS is turned off (it broke) it just waits until the connection times out. Of course in traditional Microsoft style this locks up the UI thread. I have to remember to drag everything off to the right and then go around.
Naming different things identically is a thing Microsoft loves to do. I still keep opening Teams or Teams instead of Teams. And I think there are at least three things on my PC called Copilot, and they haven’t even released Copilot yet.
Well this one depends on negative mass, which is, as far as I know, no less weird and speculative than dark matter.
It’s important information but not really a very beautiful or useful way of presenting it.
I think the main take on this is to learn the lesson that it is not safe to install random software you come across online. Is this lesson new, though?
I think people often have a vaguely formed assumption that plugins are somehow sandboxed and less dangerous. But that all depends on the software hosting the plugin. There was a recent issue with a KDE theme wiping a user’s files which brought this to light. We can’t assume plugins or themes are any less dangerous than random executables.
You just don’t want to do it regularly. It was an issue for a brief time when SSDs were new, but modern operating systems are smart enough to exclude SSDs from scheduled defrags.
I’ve been programming for almost 25 years and I’d still rather see too many comments than too few. A dogmatic obsession with avoiding comments screams “noob” just as much as crummy “add 1 to x” comments. If something is complex or non-obvious I want a note explaining why it’s there and what it’s supposed to do. This can make all the difference when you’re reviewing code that doesn’t actually do what the comment says it should.
Why not put the “why” in a comment and save people the job of dredging through old commits and tickets to figure out what the code is for? I’d thank someone for saving me the hassle.
All malicious extensions detected by the researchers were responsibly reported to Microsoft for removal. However, as of writing this, the vast majority remains available for download via the VSCode Marketplace.
Ah, the Microsoft tradition of always having the wrong priorities.
On the other hand you can just call wherever you end up the destination, and no one can prove you wrong. 100% success rate.
I’m using GitHub Copilot and haven’t dug into the license. It’s possible I’m technically handing all my code over to Microsoft.
These things cost money to run, so how are they offering it for free? Who’s paying for it? How do they profit from our using it? What’s the catch?
Edit: Someone else here found that the license basically means all the code you write with it becomes theirs. Seems like we found the catch.
It screams made-up internet story.
That’s not so bad. Thank you for the clarification.
You evidently haven’t met my colleagues. There are always people who go for the quickest hack despite the trouble it stores up for later, and they’re usually encouraged by management.
At what point do I get to keep 5.0 instead?
If I subscribe for 10 years then can’t afford it any more I’m rewarded with a 10 year old version of the software? It should be the version that was current when you finished your subscription.
Do people actually copy and paste code with no understanding of how it works, from SO or Copilot? I always thought this was just a joke.
The tricky thing about software development is this balance: you don’t want to hobble your system by designing only for today, because that could waste a whole lot of time later when needs change, but you also mustn’t paralyze the project by designing for all possible tomorrows. Finding a middle path is the art, and the only proof that you got it somewhat right is that things get done with relatively few crises.
Why compromise? Use 1-bit IP addresses.