dev_tty01

Do you have a reference for this?

At the Facetime announcement, Jobs said that would be an open protocol. Then they ended up in a big patent suit over Facetime and it didn't happen. Not sure how much the suit influenced the decision, but for whatever reason the Facetime protocol was never opened up. I don't remember a similar announcement about iMessage.

As far as abuse, how so? They provide a messaging app. That app is compatible with SMS. There are several alternative messaging apps. Where is the abuse?

Lots of great ideas, especially the format affinity indication/control. Is that just arrow key or arrow with cmd key? If it is only the arrow key, how do you distinguish user intent to actually move the cursor vs change the affinity?

As a long time Mac user, I think a little movement in the other direction is only fair. :-)

If these templates are as common as you suggest, it seems learning from your personal codebase should get the job done.

True enough, but the point of this type of lawsuit is to define the legal framework within which the tech can operate. The law could end up saying that AI generated code from public, but license constrained code, must abide by the license of the original code. Or maybe there are rulings that help to better define "fair use" within this context. There is clearly significant legal ambiguity so this and other suits will help to clarify things.

Of course those laws can't constrain someone from using the tech on their own computer how they want, but most public companies will create policies to keep their workforce within the lines of the defined legal framework.

Sadly, it is a common practice. Humans are really good at rationalizing their way down the slippery slope. "I'll just use this clever way to loop over that structure. Well, actually, the whole function pretty much does what I need, I'll just drop that function in. Hmm, I could just change the API of this module a bit and that will work nicely..." It doesn't take long for learning to turn into copyright violation. I've seen this repeatedly while reviewing code of junior engineers. The engineers aren't malicious. They just sort of slide into it over time.

As Copilot gets better and better, I just don't see how it doesn't end up violating license terms, at least occasionally. Even if much of its output is fair use, as long as some of it is violating licenses, MS has a problem.

I suppose it is good that they finally noticed.

I saw the arc once with a cheap no-name cable. I'm guessing the cable tolerances on the conductor placements was off a little bit.

How do you define "better?"

For charging its fine, as long as you aren't going for high power levels. In terms of data transfer, it simply can't support the data rates that usb-c can. If you want a simple, robust connector for moderate charging loads with moderate data transfer needs it is a great connector.

That's not opinion, just simple physics. Lightning has a lot fewer wires. Apple has managed to get base USB3 rates with a couple of devices, but nowhere close to the thunderbolt rates you can get with USB-C.

Having said that, for the vast majority of use cases, it is a great connector. Simple, idiot proof, and robust.

A Spotlight search never starts a scan of your disk. The disk is always fully indexed and returns results out of the index very fast. The only exception is typically when the system is updated (or some other big event) and it reindexes everything.

That being said, as others have pointed out, there is a setting to make a Finder window search apply only to the directory in the current window.

Geez. One visit and you are an expert. Totally off base. California is ranked 29th in drug use and Alabama is 41st out of 50 states.

https://wallethub.com/edu/drug-use-by-state/35150

https://news.ycombinator.com/item?id=33144632

https://en.wikipedia.org/wiki/Humbucker

Are you sure?

---- "Larry started to explain about some of the places where he thought that he could improve things, but Steve wasn't interested. He continued, "You know, I've been thinking about it. How many people are going to be using the Macintosh? A million? No, more than that. In a few years, I bet five million people will be booting up their Macintoshes at least once a day."

"Well, let's say you can shave 10 seconds off of the boot time. Multiply that by five million users and thats 50 million seconds, every single day. Over a year, that's probably dozens of lifetimes. So if you make it boot ten seconds faster, you've saved a dozen lives. That's really worth it, don't you think?" --- https://www.folklore.org/StoryView.py?project=Macintosh&stor...

Regardless, this isn't about Casey. This is about MS releasing crap software. Text editors from 30 years ago were faster than WT. Something is horribly broken about the programmer's approach to writing code, or they are being horribly managed, or all of the above.

On the surface, it often feels like there is just an extreme lack of pride in workmanship. In code from lots of vendors I am constantly seeing interfaces with strange glaring issues, with bizarrely convoluted UI paths, with odd render bugs, etc... It feels like there is something unfortunate happening across the industry. Maybe I'm just a cranky older engineer, but seeing so many visual and functional failures being shipped makes me think the issue is far deeper than that.