mastodon 4.5.19Teilweise, Married with children, Nerd, iOS developer, #Macoun (Speaker 2011, App(s) since 2012), Psychrophile.
“IF THIS IS UNEXPECTED, PLEASE FILE A BUG REPORT.”
If that’s not what a dev screaming for help against management looks like, I don’t know what is.
Yes, that was unexpected.
What was not unexpected is that it deleted the half finished SDK download and that it does not automatically resume it.
No, I will not file a bug report.
I just hope @mjtsai@mastodon.social et al. pick it up and blog about it.
Those blogs are easily worth 10 bug reports.
100× or more if by a major printed publication.
#Apple is all things half finished nowadays.
The Gregorian Calendar skipped Oct 5. – Oct 14. 1582.
Apple did implement this in the month view of the iOS calendar app.
They failed to implement it in the year view.
If you open the day view of Oct 4. 1582, try to add a new event, then tap the start date selector, the calendar app crashes.
iOS 18.7.8 was released.
It’s also available for iPhones/iPads that are supported by iOS 26.
The update is still well hidden but it is available. (For a video see @cosmic040@chaos.social)
Could it be that #Apple accepted that those that remained on iOS 18 are not going to update to iOS 26?
Between 1954 and 1990 (36 years), the number of active nuclear power plant reactors world wide changed from 1 to 416.
Between 1990 and 2026 (36 years), the number of active nuclear power plant reactors world wide changed from 416 to 415.
That’s what “every country but ours uses nuclear power to become carbon neutral” looks like. (If you think the total net electrical capacity changed a lot: Nope. +2% from 2005 to 2024)
https://de.wikipedia.org/wiki/Kernkraftwerk#Anzahl_der_Kernkraftwerke
https://pris.iaea.org/PRIS/WorldStatistics/OperationalReactorsByCountry.aspx
https://pris.iaea.org/PRIS/WorldStatistics/WorldTrendNuclearPowerCapacity.aspx
Bei courtlistener, z.B. https://www.courtlistener.com/docket/67239065/cornet-v-twitter-inc/ Eintrag vom 19. März, steht oft „SO ORDERED AND ~Util“.
Ich wollte wissen, ob meine Interpretation, dass „~Util“ bedeutet, dass die Anordnung sofort in Kraft tritt („direkt angewandt“), korrekt ist. Google siehe Bild.
Können wir das mit den KIs jetzt bitte wieder lassen? Das hat in den 70ern nicht funktioniert, in den 80ern nicht, in den 90ern nicht, und auch die letzten 25 Jahre ist es nicht so zuverlässig geworden, dass man es haben möchte.
Schade, dass das hinter einer Pay-Wall ist.
https://www.sueddeutsche.de/kultur/afd-rechtsradikale-meinungsfreiheit-li.3472726
Aber Aufmacher auf der Startseite ist für sich schon eine Ansage.
Genauso Sätze wie „Natürlich hätte Deutschland die AfD schon vor Jahren verbieten müssen – und müsste es spätestens heute tun.“ oder knapper „Ein Verbot dieser Partei ist zwingend”.
Was mich (wie so oft) stört: Wir können die Partei nicht *verbieten*, aber wir könnten prüfen lassen, ob sie verboten *ist*. Optional ist nur die Prüfung, nicht die Folgen.
@leeloo @Sarnau @mayo @dasdom Do you know the difference between 'const char *andchar * constin C++? I thinkletis a more likechar * constthan likeconst char *`.
The "\("string literal")" case probably gets special treatment when optimizing. I vaguely remember it from when I implemented https://github.com/dhoepfl/DHLocalizedString/ because it was concatenated even when I wanted to get every interpolation but could not.
Not to forget: Interpolation is used for more than just plain old strings.
import Foundation
print("Cannot \("action") because \("reason")")
gets optimized when compiled with swiftc -O as you assumed.
BUT
import Foundation
let action = "action"
let reason = "reason"
print("Cannot \(action) because \(reason)")
is not optimized to "Cannot action because reason".
For localized strings, it cannot be optimized, the key format is documented, it will be “Cannot %@ because %@”.
@leeloo @Sarnau @mayo @dasdom Because of the way string substitutions work in the Swift/Obj-C/SwiftUI/UIKit/AppKit world.
If you write "Cannot \(action) because \(reason)", the compiler generates code similar to StringInterpolation(…).appendLiteral("Cannot ").appendInterpolation(action).appendLiteral(" because ").appendInterpolation(reason). This would show up as "Cannot " and " because " in the binary.
For localizable strings, something like "Cannot %@ because %@" would show up.
@leeloo @Sarnau @mayo @dasdom I don’t know that. All I know is that said someone did add a separate error string for that very case.
I assume that it was not expected that it is possible to even try to delete the installed component but whoever wrote that error message had to implement a protocol where delete() has to be implemented. Instead of going the extra mile to make sure the delete button is disabled, that someone called it a day.
Test von USB-Netzteilen.
Negativer Punkt bei einem: „In vielen Farben erhältlich“.
Dabei hatte ich gar nicht gefragt, ob die Redakteure dumm sind, aber dass der Test nichts taugt, das erkennt man nicht nur an dem Punkt.
@leeloo @Sarnau @mayo @dasdom That’s the search pattern, I should have given the result of the grep, too: It is the exact error message.
I did a different grep to find the location of the string, the grep I gave in the post was just reduced to produce the single one line that matches the error message 1:1.
Initially I used grep -a -r Cannot' dele' /Applications/Xcode.app/ | less but that contains lots of (binary) output and makes it hard to see the interesting part.