Hacker News new | comments | show | ask | jobs | submit login

current apple engineer... the sprint (milestone) development system is still in place... it's not the problem though, it's the problem is the focus on new useless [imo] features at the expense of core functionality and quality

hope marco, geoff and others keep writing these articles so that eventually tim or someone sees one and shakes things up. pressure from the bottom has not worked so far




In case you know someone in charge : the wifi performances issues on yosemite are still not completely solved. This is my only gripe with this version so far, but having to turn off bluetooth to get a good connexion from time to time really feels like working on broken software.


Exactly my experience. There's so many hypothetical fixes on the Internet, some seems to improve intermittently and temporarily, some seems to not work at all. But toggling Bluetooth seems be able to get a reaction from the OS at times. It felt like a ritual and I'm praying to the OS god.

Then one day a fortnight ago, I chanced upon another solution. Some people are speculating that because the WiFi signals is clashing with Bluetooth signals as they are both in 2.4 GHz, its affecting the WiFi. I was using Apple Wireless Keyboard & Touchpad. I have friend who had similar setup who seems to have the same issue.

So the next day, I spent 464 USD just to upgrade my router, get a wired Keyboard and a wired Mouse.

I have definitely splurged on these hardwares but at this point I am so frustrated and desperate that I need to make sure any hardware issue is out of the question. These are the only variables I can control, anything else felt hopeless.

I then jumped on 5 GHz WiFi and stop using bluetooth. My WiFi situation have improved a lot since then. Not perfect, but not un-usable.

The point is that I could have saved those money. To spend so as to fix a bug felt so Window'ish. It use to just work, and glitch are bearable, now I always worry of upgrading.

Anyway, those money could have went into buying Apple stuff.


I've heard the same thing, and my setup indeed includes a wireless keyboard and touchpad. But the weirhd thing is that i don't think i experienced thoses issues with the previous os version.

I also read somewhere it was related to Handover protocol using the same bandwidth as wifi. This sounds more plausible. Then having bluetooth + regular wifi + Handover wifi is too much and the connexion suffers. I which case there's not much Apple can do unfortunately, except rethink the whole stuff.

I'd say in any case the future in that matter doesn't look bright.


in fact, it got worse. now it won't auto connect to my networks. I have to manually connect, every single time


would be interesting to hear what the distinction is between useless and core features.

Maybe I'm just not hitting core features with OSX 10.10, but the features I'm using seem fine. And not seeing stability issues with third-party software.


Useless feature: Tagging files 'Home' or 'Work' in Finder Core feature: A filesystem that doesn't get so easily corrupted and need constant Disk Utility scans to stay healthy

Now, I know some people will really want tags and I remember them spending a bunch of time in the keynote talking about them but I'm pretty sure I've never used them. It's not a bad featureā€¦ I guess it's nice and I bet a lot of people use it, but I would prefer if it was built on top of a more solid foundation.


It was my impression that Tags were just Apple's last attempt to avoid having "Folders" in iCloud. Wisdom on the internet is that the file system is bad and must be hidden from users. But if you add folders to iCloud, then what is it, if not a file system? Then iCloud Drive introduced Folders one version later, and now Tags is kind of a legacy feature.

I don't think anyone but management ever really wanted tags.


Folders and tags shouldn't be mutually exclusive.

Folders allow for a simple hierarchical navigation option and allow you to preserve "structure" when round-tripping resources the rely on nested folders in and out of a cloud service. It allows for strong naming and namespaces.

Tags can be user-supplied, crowd-supplied, or even through AI/expert system, and allow for cross-cutting exploration when involving stuff that can't be indexed like text. (Although even documents benefit from tags to ease finding them again when there's a haystack)

Tags require more effort to maintain but are essential when you are dealing with a complex collection.


Yes, I agree, I like tags in theory.

But there is no way to implement user-supplied or crowd-supplied tags when you are practically limited to the seven colours used for tagging, and it only works if you can even remember which colour is used for which tag.


Not to mention that the colors change if you move the disk to another mac.


The issue of HFS+ bit rot is a good example for caring about long-term core features. IIRC we almost got ZFS per default sometime around 2007?

https://news.ycombinator.com/item?id=7876217


Fwiw I can crash the entire OS by abusing tabs in Chrome. Too many tabs open => System freeze, hard reboot required. OS X Mavericks on MBPr 15".

That shouldn't be possible. Crash the browser yes, not the whole OS.


I was also experiencing something like this. I would open lots of tabs, and at some point the machine would freeze and I would need to do a hard reboot. This got worse after installing Yosemite, where I could rarely go a day without having to reboot my system.

I was about to take my laptop in to see if it was a hardware issue when a coworker pointed me to a forum where someone suggested turning off automatic graphics switching. I did that about two weeks ago, and since then I haven't had a single occurrence of the issue. You may want to try the same thing to see if it helps.


Interesting! Wonder if it's a quality control issue with the code handling the graphics switching. Afaik, Apple engineers write custom video drivers for every supported hardware device. Wonder if Intel is now contributing more to the graphics driver updates and maintenance.


Interesting! Wonder if it's a quality control issue with the code handling the graphics switching. Afaik, Apple engineers write custom video drivers for every supported hardware device. Wonder if Intel is now contributing more to the graphics device efforts.


Interesting! Wonder if it's a quality control issue with the code handling the graphics switching. Afaik, Apple engineers write custom video drivers for every supported hardware device. Wonder if Intel is now contributing more to the graphics driver updates and maintenance.


Interesting! Wonder if it's a quality control issue with the code handling the graphics switching. Afaik, Apple engineers write custom video drivers for every supported hardware device. Wonder if Intel is now contributing more to the graphics driver updates and maintenance.


Interesting! Wonder if it's a quality control issue with the code handling the graphics switching. Afaik, Apple engineers write custom video drivers for every supported hardware device. Wonder if Intel is now contributing more to the graphics driver updates and maintenance.


Interesting! Wonder if it's a quality control issue with the code handling the graphics switching. Afaik, Apple engineers write custom video drivers for every supported hardware device. Wonder if Intel is now contributing more to the graphics driver updates and maintenance.


Interesting! Wonder if it's a quality control issue with the code handling the graphics switching. Afaik, Apple engineers write custom video drivers for every supported hardware device. Wonder if Intel is now contributing more to the graphics driver updates and maintenance.


Interesting! Wonder if it's a quality control issue with the code handling the graphics switching. Afaik, Apple engineers write custom video drivers for every supported hardware device. Wonder if Intel is now contributing more to the graphics driver updates and maintenance.


Sounds like you have a hardware problem, actually. Faulty GPU or RAM, quite likely.


No, you can't single him out like this: Since Mavericks, OS crashes are very often reported, and Chrome tabs seem to be often reported as a cause. I myself have never had crashes with Snow Leopard and I see them often in Yosemite. That's exactly why we see articles reporting the Apple has lost the Quality ground.


I have exactly the same problem on multiple machines.

Plus, the wifi fiasco, over which more than one person should have been fired.

I am barely sticking with Apple for now, mostly because in startups it is the default, but I don't plan to replace my apple equipment with more apple products.


Same deal for me with Safari. No, it's not acceptable for an entire system to lockup, and no this is not hardware related.


It's just brutal in Yosemite. This is the first release to which I regret upgrading. I've never had so many issues on my laptop, and it has never been so slow. My FileVault encryption has been stuck at 99% since I upgraded and enabled, and Apple marked my radar report as a duplicate. They can't/won't tell me if I'm forever hooped or if it will ever be fixed. At this point, I'm looking to spend a day rebuilding my whole system.


I was running the beta and it was pretty rough but that's what happens when you run betas. But then for over a month after gold-master it was STILL really problematic.


Yikes. Whats you're telling us is bug fixing and the incurring of the deep, deep, technical debt isn't seen as a problem. Unfortunately this debt is also being shackled to the 3rd party developers since we have to compensate for Apple's bugs. Not fun.


> pressure from the bottom has not worked so far

wait, this is causing friction? they fired forstall to get total gleichschaltung and now ppl elsewhere are revolting? i hope this'll come to fruits. this whole cozy-collaboration-and-nobody-saying-no thing has to stop.


But how did things like NSURL defaultCache and other base-components get broken in iOS8? There seemed to be work on the fundamentals that broke them right? It's not just that the new flashy stuff stuttered or crashed...


I still can't understand how it got through any sort of automated testing. Which they have to be using, right?


Keyboard input language switching between apps has been broken for 10 years now. Yosemite broke it further.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: