291–300 of 471 posts
Earlier quoted context omitted.
What's brilliant about it? What's the reference, for those of us unfamiliar?
The author's name is tenderlove. He has been a famous contributor to Ruby and Rails for at least 10 years. If this is objectionable to you, it shows your lack of expertise.
Earlier quoted context omitted.
I guess the reason why modern times feel so bland is because we all agree on the lowest common denominator, and then celebrate that as "iNcLuSiViTy". If anything you do has any personality, aka deviates from the standard workflow, it immediately gets a disadvantaged position on the free market. It's like, we collectively prioritize efficiency over fun and then we wonder why life is not fun even though it is efficient…
Dumb frat-boy innuendos count as personality now, huh? Let's just leave aside the fact that the name genuinely made many people uncomfortable and unwelcome there (it did), it was also just teenage and immature. There's ways to inject personality and fun into a social experience without giggling about sex. Talk about lowest common denominator...
There are many personalities. Not everything has to be mature
I’m a fan of the whole Apple ecosystem but I have to say that there’s a pattern here. Apple does a decent job of keeping my data safe from others but a terrible job of keeping it intact. From music libraries with song titles that got switched to long integers to this (and I’m sure more that I’m not remembering atm) they need to do a better job here. Sure security is important but integrity is too.
I am baffled by Apple's incompetence here. In the past years I've seen: * iTunes/Music app randomly reassign my Album artwork, with different (incorrect) art showing up on different devices! * Reminders app: shared reminder lists can end up with the name of a different list * Ghost photos that are deleted from my phone, and come back later. * Maps, when I say "navigate to $friend" set a route that ended in my own dri…
Earlier quoted context omitted.
I got burned by Apple purposely corrupting my music library. I'm still salty about it.
Purposely? Could you elaborate?
Btw, it was fine from withing iTunes, just never stop using iTunes I guess...
I’m a fan of the whole Apple ecosystem but I have to say that there’s a pattern here. Apple does a decent job of keeping my data safe from others but a terrible job of keeping it intact. From music libraries with song titles that got switched to long integers to this (and I’m sure more that I’m not remembering atm) they need to do a better job here. Sure security is important but integrity is too.
Earlier quoted context omitted.
There is a very popular professional audio website called Gearspace that had a much spicier name for a long, long time. https://gearspace.com/ https://www.reddit.com/r/audioengineering/comments/mftc0g/ge...
Modwiggler changed name around the same time.
Earlier quoted context omitted.
Purposely? Could you elaborate?
Still can't get rid of that U2 album I'm guessing
Earlier quoted context omitted.
This is also my guess. It's really a bummer, and I'd report it to Apple but since it's nondeterministic I have no idea how to provide repro steps.
I have had extremely bad luck, reporting bugs to Apple. They constantly ask for an example project, even if it's something that is easily demonstrated, simply by running existing Apple software, and creating a project, would be a huge pain. They also ignore reports. Very rarely, I may get a ping on one of my reports, asking me to verify that it was fixed in some release. Otherwise, there's no sign that they ever even…
Hm. That is more than I ever got, but I also never bothered to report anything to any company after being ignored the first tries.
It seems to be an import pipeline bug. Photos does a lot of extra work on import (merging RAW+JPEG pairs, generating previews, database indexing, optional deletion), so my guess is a concurrency bug where a buffer gets reused or a file handle is closed before the copy finishes. Rare, nondeterministic corruption fits the profile.
This is also my guess. It's really a bummer, and I'd report it to Apple but since it's nondeterministic I have no idea how to provide repro steps.