This is a great idea - do you have a more detailed overview of this approach and/or an example? What types of things do you tell it to put into the "artefact"?
The entire "no link" thing truly was outrageous from the start and, speaking as someone who very much admires Apple for many things, hearing that Schiller opposed the crazy 27% rule but was overruled by Cook truly makes me wonder whether Schiller wouldn't be a better CEO for Apple than Cook if these types of decisions are still being made.
To be clear though it is not some backend thing by dang etc. but rather users with enough reputation to get the flag button are flagging your posts just because they don’t like you. That is the likeliest explanation.
But the only post on the recent submissions list that is actually marked "[flagged] is this one. If it's because enough high-karma users are clicking "flag", wouldn't they all show up as "flagged"?
The only explanation I have heard that makes sense is: The [flagged] tag only appears after a certain threshold amount of user-flags, however each user-flag contributes to the down-weight of the story.
So if the [flagged] threshold is 10 user-flags, then 9 people can flag the article, burying it, and then only at the next user-flag, [flagged] shows up in the title.
Of course, nobody but HN staff truly knows if this is how it works.
That may be right. Unfortunately, while I have seen Wikipedia articles on HN, my memory is not sharp enough to recall for how long they stuck around on the front page.
Yes! We, too, happily used Discord for years in our small company - it was absolutely amazing and I also wonder why they don't have a version for companies - in my mind it easily beats Teams in nearly any factor that's important to us - though admittedly we're not a typical Microsoft-using enterprise.
Here's what I find most puzzling about these things: Apple does amazingly helpful WWDC sessions on how to profile and improve your code, how to prioritize performance...but when it comes to their own apps, it's like they forget everything they know?
Messages on Mac is one of my biggest annoyances. How do you make one of the most used messaging tools and have the keyboard lag so badly while typing - sometimes even skipping typed letters? It's a complete mystery to me.
There's always been a lot of room for them to optimise performance on macOS to a level that they do iOS, but modern Apple basically wants macOS to go away and sees it as more of an annoyance, so they don't spend any time tuning it. Then the elephant in the room is SwiftUI itself, there's a performance cliff there, wherein if you've optimised everything else, you might just hit the brick wall that's the layout engine with no recourse or ability to even peak under the hood. We're at a point now where building a fully native macOS app, with the first-party toolchain, will give you far worse performance (in terms of responsiveness not resource usage) than something like Electron. I have a suspicion teams inside of Apple are also running up against these issues as they start to actually adopt the framework.
A modestly sized list of WiFi networks (30-40 items) slows down and stutters while scrolling on a M4 MBP. SwiftUI is a performance disaster, and I refuse to use it outside of toy single screen projects
Yeah it's in a really bad spot on macOS still, iOS performance is a lot better. I'm sure all of this can be overcome but I'm not certain it's a priority for them.
Considering how good the hardware is supposed to be, iOS is not that great actually.
This is why Androids that have benchmarks score way lower than iPhone can actually feel smoother to use.
Apple is brute forcing the thing and making all their customers pay, it's useless to have the most powerful chip if you waste all its power running garbage code.
And this is exactly how macOS and iOS feel nowadays: the hardware is supposed to be great but it doesn't feel that good because the software sucks.
I agree with you, just my obsevations from using SwiftUI "in anger" for the last few years, performance is atrocious on macOS and acceptable on iOS, especially with some tuning.
Oh yes, I agree, it's not as bad on iOS for sure.
But acceptable for a premium device is a very low bar to clear.
It becomes much less acceptable over the years as well, infuriating.
In my country the mainline iPhone start around 1k€ and even the "e" is over 700€.
If I had paid 2-300€ like a low-end android device I would find it acceptable but Apple only sells stuff that is the high end of pricing, therefore it is not acceptable.
They are not just "merging codebases". They are literally letting it stagnate in all the parts that matter, and all the user-facing parts are iOSified, or literally delegated to iOS with "you can run iOS programs directly now".
And yes. Merging codebases is a bad thing when it's done without any care for one of the paradigms. The one that they don't like, don't understand, and want to go away.
What sort of citation would you be looking for here? It's generally accepted that it's not a priority for them, the discrepencies in performance and features between UIKit vs AppKit have always existed and are even more pronounced in SwiftUI. Due to how it's used they can't apply the same business model to the mac as they can iOS and therefore can't extract as much value from it, this is reflected in revenue.
Poke around on jobs.apple.com looking at developer positions and everything will become clear. There seem to be at least an order of magnitude more outsourced software development jobs than jobs within the US/EU.
You don't outsource to India because you want to get better quality products. You do it so you can pay a terrible Indian programmer $30,000/yr instead of hiring a great Indian programmer for $300,000/yr in Cupertino.
As for hardware, I'd recommend at minimum a joystick of some kind if you don't have one.
And finally I'd give you a shameless plug for my app SmoothTrack which lets you fluidly control the game camera with small head movements - https://smoothtrack.app ;-)
Looks like Austin found an editor to clean up his texts which otherwise end up super nerdy and way too long. This is excellent, readable, and punchy. Makes me consider getting X-Plane 12 even though I already have 11 (and MSFS 2020 and 2024).
