> I keep hearing the language is going to be stable "soon"
I think you may be referring to the promises of ABI stability? They kept promising that "soon" starting around Swift 3 (IIRC) and kicking the can down the road for a while there, but it is stable now on Apple's OSes. But I don't recall seeing promises of source stability back then; they were pretty open about the fact that the language was still evolving.
Pet grooming has been classified as essential (by California) since late April. Our local groomer reopened quickly after that. There might be some cities that have other restrictions, but grooming is already open in most places.
You can generally only copyright the parts you change. Sort of like how Disney can copyright their version of Rapunzel, but they don’t own the fairy tale.
(Edit: that’s assuming you’re asking about a derivative work, which I may have misunderstood)
I guess my question is more focused on whether a person can copyright something they created that was created by something else previously. So, if a musician creates a melody and then later finds that same melody was previously recorded on an album from the 1990's can they still copyright their melody? Does it matter whether the 1990's recording was machine-generated melodies or human-generated ones?
This is discussed in the video somewhat. Copyright allows parallel invention. E.g. 2 people can copyright the same thing as long as neither one copied the other. In the video, they claim this is usually difficult to prove in court if the first work had at least moderate notoriety before the second was produced.
Back of envelope: With running status, a note on message is two bytes on a 31250 baud connection. That means the latency from transport is on the order of half a millisecond. If you’re feeling latency, it’s in the gear, not the protocol. MIDI implementation quality has long been wildly inconsistent, and I don’t see a reason to believe that will change with MIDI 2.0.
> That means the latency from transport is on the order of half a millisecond. If you’re feeling latency, it’s in the gear, not the protocol.
As long as you don't transmit anything else. When you have 16 channels with many note and controller messages, latency and asynchronicity between channels can become noticeable.
I remember using 8x8 midi interfaces to get around some of that - not just for the additional midi channels, but also to thin out the traffic for each connection. i.e. each midi channel would get it's own cable/connection.
However that approach didn't work when I wanted to send 16 channels to a single (non USB) multi instrument sound device like my trusty JV-1080. It became an excuse to buy more synths! :-)
> it takes 2 to 3 hours to get anywhere useful with it
Everyone's definition of "useful" is different. I personally run into far fewer last-mile issues with Metro Rail than I did with BART when I lived up north. Heck, BART had to run a bus service to OAK until just a few years ago, and they've had a lot more time to sort this out.
> They squandered a huge opportunity to do it right, to dig subways and put the rail on a grade-separated medium. Instead they opt for light-rail that shares the same surface roads as cars, thereby ensuring that the system is a failure.
No, they did dig subways where needed (and where geologically feasible). And they opted to use existing right-of-ways in other areas, so that the thing could actually get built. Look at the Gold Line going through South Pasadena; it cuts diagonally through a fairly dense, wealthy residential area, which it can do because the neighborhood was built up around tracks that were there long ago. Without that existing right-of-way, the whole line would have gone the way of the 710 connector.
In my experience, the connector has never been implicated in a failing Lightning cable; it’s always been the cable itself. By contrast, the average lifespan of a micro USB cable in my household is a couple months, before the connectors themselves get bent beyond repair.
I don't know how much you abuse cables but I never had a USB cable fail. I understand there's a variable quality of cables out there but failing after 2 months sounds exaggerated
I have small kids who are prone to tripping over cables while trying to squeeze into tight spaces. Lightning connectors handle that stress just fine, but micro USB is no match!
I've had exactly one USB cable fail: a cheap Type-C cable that shorted near one of the ends and let out a nice stinky puff of magic smoke. Thankfully my phone survived unharmed.
The last thing I would want is a peripheral whose data connection was on a MagSafe connector. It’s specifically designed to be able to disconnect easily by accident.
I'd like to find out more about what kind of setup Grandma has, in that case. I'm sitting here on an unmodified Safari installation, and the top of the window is obscured by a giant floating banner ad, while the bottom is obscured by a "subscribe" banner, which is _itself_ obscured by an oversized cookie notice. All of which leaves less than 80px of height to read the actual article content. Given the nice large font size, that means I can see three lines of text at any given moment. I didn't have the same issue that GP did, but it's definitely true that Wired has been adopting some awful web development practices for a while now.
(Side note: My kids' grandma is a retired software developer. So I guess maybe it's just that the average grandma is more sophisticated than we are?)
I’ve noticed certain sites, like government websites (my local healthcare.gov site), banking sites, insurance sites, only work if you disable tracking protection entirely in safari/firefox, and one of them (I think the healthcare site) only worked in chrome with no ad blocker.
I think you may be referring to the promises of ABI stability? They kept promising that "soon" starting around Swift 3 (IIRC) and kicking the can down the road for a while there, but it is stable now on Apple's OSes. But I don't recall seeing promises of source stability back then; they were pretty open about the fact that the language was still evolving.