Yep; and all Apple fans ever say is "report feedback!!!" but what is the point when seemingly Apple never gets to their backlog of bugs/broken features? I mean, sure, some big stuff gets fixed, but there is a lot of stuff broken going on years they haven't even touched.
Feedback is more or less a black hole, for the most part. It's rarely paid attention to by a human, and is treated like telemetry. If you want something fixed, it needs to get into the press or go viral.
I’m sure there are countless examples to the contrary, but I recently submitted feedback regarding an issue that I was experiencing in Final Cut Pro. Within a week, a member of the Final Cut Pro team contacted me and asked for a copy of my video editing files so they could replicate the issue. I sent them the files, they confirmed the issue, and the issue was fixed in the next release.
> Yep; and all Apple fans ever say is "report feedback!!!"
I'm trying not fall into "No True Scotsman" but... It should be common knowledge at this point that Apple Feedback is a blackhole of despair. "Please attach a sample project" seems to be the go-to, even for things were that makes no sense. Same with attaching debug/diagnostic logs. I understand the value of all of those things but even people who have jumped through all the hoops get ghosted and/or their issue is never addressed.
Currently I would not waste my time on Feedback and it's sad because even if Apple reverses course it will take a lot to get the people who they should most want creating Feedbacks to create them.
Those are probably anonymous employee accounts not fans. I don't know if anyone would be enough of a power user fan to tell someone to file a bug report.
I care more about numerous bugs than I do about performance, to be honest. I'm starting to to regret not switching to Android last time I was upgrading my phone. Even if it is the same bugfest, at least I wouldn't have paid premium for the priveledge of using a device that "just doesn't work"
I need three new phones in close future for the family and I think I will go with Google Pixels and GrapheneOS. There is foldable phone available! It’s cheaper, I can deduct phones in full in the same year since the phones are <800€ before taxes (relevant probably only in Germany). And imho Apple’s premium promise is gone with glass design. Too many small errors.
100% this. I honestly can’t remember the last major feature of MacOS / iOS that didn’t feel like a solution searching for a problem, while I was bombarded by weird little bugs and semi-fail states in core functionality. At this point I experience daily at least once:
- iOS keyboard doesn’t appear when it should
- iOS keyboard button press detection and autocorrect have degraded badly
- UI Layers are missing, misaligned, or stacked in such a way that I can’t actually interact with the element I need to proceed
- mystery Internet slowdowns that resolve only after a restart
- security misbehavior such as refusing to allow a usb device I’ve already approved (MacOS resets approval of my main USB hub every update for some reason)
Snow Leopard was incredibly buggy on release. Spending time on "tech debt and software performance" adds more bugs because all aggressive changes cause regressions.
The reason it worked is that it was a long release cycle with a lot of minor updates.
It presents the main concepts like a good lecture and a more modern take than the blue book. Then you can read the blue book.
But DDD should be taken as a philosophy rather than a pattern. Trying to follow it religiously tends to results in good software, but it’s very hard to nail the domain well. If refactoring is no longer an option, you will be stuck with a non optimal system. It’s more something you want to converge to in the long term rather than getting it right early. Always start with a simpler design.
Oh absolutely. It feels like a worthwhile architectural framing to understand and draw from as appropriate. To me I think - my end goal is being able to think more deeply about my domains and how to model them.
I was going to ask the same thing. I'm self taught but I've mainly gone the other way, more interested in learning about lower level things. Bang for buck I think I might have been better reading DDD type books.
I completely agree. I do everything I can to avoid leaded ammunition. I do not want lead touching the meat I harvest. It can be really tricky to find lead-free ammo of certain sizes. I mostly use waterfowl ammo for upland bird and rabbit - and it works fine. But even ordering ammo online it is quite hard to get .270 solid copper. And in a store? Forget about it
I love `—-dry-run` flags for CLI tooling I build. If you plan your applications around this kind of functionality upfront - then I find it doesn’t have to pollute your code too much. In a language like Go or Rust - I’ll use a option/builder design pattern and whatever I’m ultimately writing to (remote file system, database, pubsub, etc) will instead write to a logger. I find this incredibly helpful in local dev - but it’s also useful in production. Even with high test coverage - it can be a bit spooky to turn on a new, consequential feature. Especially one that mutates data. I like to use dry run and enable this in our production envs just to ensure that things meet the functional and performance qualities we expect before actually enabling. This has definitely saved our bacon before (so many edge cases with prod data and request traffic).
You don't have to spend long looking at Tesla's investors to realize they are exactly the kind of investors you want. You don't have to do anything but make promises, and when those promises fall through, just promise you'll deliver even more in the future.
The scary people who lent the money to silence Twitter actually need paying one day. Lord knows you aren't doing that with any other product in the portfolio.
FWIW my 4070 Ti Super has had zero headaches in Linux. It’s only older Nvidia cards I’ve had issues with. Seems like there was a major driver change starting with the RTX 20xx series.
Up until last week I was running a 960 on mint and had absolutely no problems, nor did I even have to think about drivers. I also have a server running Tesla M10s and they're great too, little more fiddly getting the right driver, but that's moreso on the cards being weird.
Post last week I put in an Arc B580 and I had some issues at the start, but that's more to do with the fact that my workstation has a Haswell Xeon v3... Otherwise it was just turning CSM off.
Linux probably became first-class for them because a lot of ML workflows rely on NVidia in the cloud, and I don't think anyone really uses Windows for that.
Even PVP is starting to “just work” via Proton. Arc Raiders runs just fine on Linux and is a strictly PvP game. Over time I think this will be less and less of a problem.
Still has an anti-cheat, they just bothered to allow Linux support.
Companies don't do this out of laziness/incompetence, but even some large anti-cheats work on Linux and some games simply choose to not enable it (cough, Tarkov, cough). Their problem, I'm no longer gonna play games that don't work on Linux.
Funnily enough the best FPS game ever (Counter-Strike) runs absolutely fine on Linux. Thanks Valve!
As far as I know, all the anti-cheat options for Linux are not kernel-level, which means that they are drastically less effective at their intended purpose. That's why so many competitive multiplayer games choose to not enable it.
Been following this for a little bit and am extremely excited for this. I think the final big hurdle for adoption (for those of use in the MapLibre stack at least) will be getting an equivalent As_MLT() function added to PostGIS.
reply