I'm also a little bummed that they seem to have dropped the Pro Display XDR. I wanted a 32" display as the main display, and then use my existing two Studio Display vertically as secondary on each side.
I guess we're going to see how the support for DP Alt-Mode will be, as I'm not sure how much bandwidth that can provide, so 120Hz might be out of the question. But for now that has been a simple way to get around the lack of multiple display inputs, you just needed a separate KVM switch for it.
One thing that made Tahoe even worse is that Apple changed what they considered an update or upgrade, so for Tahoe it was suddenly considered as a update and not an upgrade, in all management solutions.
This force-upgraded a lot of Macs at work and we lost days of effective work across many engineers. The machines was practically useless for weeks.
They clearly don't care about power users anymore, and haven't for quite some time. It's so sad.
You should be careful about speaking in absolute terms when talking about copyright.
There is nothing that prevents multiple people from owning copyright to identical works. This is also why copyright infringement is such a mess to litigate.
I'd also be interested in knowing why you think code generated by LLMs can't be copyrighted. That's quite a statement.
There's also the problem with copyright law and different jurisdictions.
I don't understand why that is such a huge problem. The alternatives have much more severe problems, all from reusing a wildcard in many places to running your own PKI.
It depends on your risk profile, but there are definitely people who'd rather run their own PKI than permit threat actor reconnaissance by publishing internal hostnames to CT logs.
When this information is useful you've either got fundamental security related issues that needs to be addressed long before this, or you're dealing with threat actors with significant capabilities. In the latter case you've probably already taking this into account when you're creating your stuff, or you have the capability and technical understanding to know how to properly roll out your own PKI.
The overlap of people that suggest that you either run your own PKI or just distribute a wildcard certificate and have the technical understanding on how to do this in a secure way is minuscule. The rest of those people are probably better off using something like Lets Encrypt.
I'm mostly happy with my Apple Watch, but you better hope that it doesn't calibrate itself poorly. There's no way to force it to recalibrate and it persists through full reset and even full replacement of the Apple Watch itself. I've more or less given up trying to fix it. So according to Apple I've been standing upright all waking hours for the last 3-4 years.
I've heard similar issues for people using crutches. They get like 3-5x the amount of steps, or not steps at all, and you've guessed it, no way to calibrate it.
(I'm sort of posting this in the hope that someone actually know how to force it to recalibrate)
I'm going to chalk this up to the decline in Google search to save my embarrassment, because that was very straight forward, and I don't understand how I didn't find that. Admittedly, it's a couple of years since I looked and it could be a new feature.
Funnily enough one of the demonstrated use-cases of Apple Intelligence was looking up information like this.
I understand this will reset motion calibration data but does anyone know if heart rate measurements also use calibration data? My Ultra 2 always seems to undercount my heart rate compared to my older Series 6. This is especially noticeable during higher intensity workouts.
I get the point you're trying to make here, and the sarcastic undertone, but I'd have issues living with myself if people died because of something that I was able to identify and that was preventable, and I did nothing.
The whole case strikes me as odd. Not only did the higher ups know about the problem, they also left a paper trail about keeping a lid on it and getting rid of the guy. This opens them up to a lot of scenarios, like:
- As demonstrated by this case, the information came out because of the wrongful termination
- If an accident had happened there's a fairly high chance that the investigators would uncover it, either because the engineer in question came forward or because they think they should have known about this, and cracks appear when they start asking questions.
An unspoken rule in a lot of fields is that you make sure that this kind of information never reaches the people that could be held liable for it. The people that are likely to be held responsible at least have to make it appear that they're not trying to suppress information like this. You quickly lose that ability if you actively try to get rid of people that tries to raise an issue. So they surround themselves with middle management that knows to not bring things up to them, without being explicitly told so.
The point is that there are many people sleeping fine or not, that kept their livelihood by not whistleblowing. solely due to the misaligned incentives and lack of accountability
I think that depends a lot on how the data is going to be used. It sounds like you're not really using EBS volumes for what they're great at; Durability.
While instance storage is ephemeral nothing really stop you from using it as a local cache in a clustered filesystem. If you have a somewhat read intensive workload then you might see performance close to matching that of using instance storage directly.
There are some fundamental limits to how fast a clustered filesystem can be, based on things like network latency and block size. Things like locking is an order of magnitude slower on a clustered filesystem compared to locally attached storage.
Having a low child mortality is important, and we've done so many good things in the last couple of decades, but I'm starting to think we're at the point now where the money you have to spend to make a meaningful difference is better spent in other areas of health care.
A classical example of this is in Norway. There's nothing that gives you access to more resources than being pregnant or being in care of a newborn. You can suffer from all kinds of mental health issues for your entire life, struggle to be a productive member of society and be in and out of temporary treatment and be on social benefits. But the moment someone is pregnant they get will be top priority for anything that is even remotely connected with child mortality, almost regardless of how benign something is.
I personally know several people that finally got the help they had been so desperately been begging for, just because they got pregnant. We could have saved them from literal decades of suffering by just providing good treatment early. I'm willing to bet that we'd even be in a position to spend even more money on reducing child mortality, because when you start doing the math of how much they ended up costing society it really adds up.
They don't even seem to specify what kind of charger they've tested. But I wouldn't be surprised if they found that a quarter of public L2-chargers were out of service. They have tons of failure points and usually very little internal logic to self-report.
Some of the early fast chargers (outside of Tesla) were notoriously bad, and a lot of them are still around, for better or worse. Many of the early AC and DC chargers were also without any kind of connectivity, making it hard to properly manage them. In the early days even some of the fast chargers at gas station weren't really network connected, and if they were it was poorly implemented. Not that different from pumps at the forecourt.
Making a wild guess that it was a Circle K-station that you went to? They were quite early to the market with fast chargers, and had a lot of reliability issues with some of the chargers. Like you suggested, it's usually software related, and you can often get them to work by just power-cycling them using the emergency stop button. If you hear the loud click from the metal contacts or the charger latches with the port and it doesn't start charging it's almost always a software glitch that a restart will fix.
For regular AC-charging all the logic is in the car, so the only thing you really need is some safety features on the outside, typically some ground fault protection and so on. But when you use a DC fast charger the charger itself and the cars battery management system has to work together, which I imagine can cause all kinds of edge cases where people have interpreted the standards differently. It didn't help that there were multiple different standards early on.
I guess we're going to see how the support for DP Alt-Mode will be, as I'm not sure how much bandwidth that can provide, so 120Hz might be out of the question. But for now that has been a simple way to get around the lack of multiple display inputs, you just needed a separate KVM switch for it.