8 ms·
This is so incredibly Apple :) The breakage, I mean. To clarify a bit, for better or for worse, this is what Microsoft does, totally different psychology: http
by oblio 9y ago
This is so incredibly Apple :)
The breakage, I mean. To clarify a bit, for better or for worse, this is what Microsoft does, totally different psychology: https://blogs.msdn.microsoft.com/oldnewthing/20031223-00/?p=41373 https://blogs.msdn.microsoft.com/oldnewthing/20031223-00/?p=...
- mrpippy 9y agoApple isn’t breaking old/existing binaries, the new behavior only applies to binaries compiled against the 10.13 SDK.
- gradstudent 9y agois that so much better? I dread every new release of macos because it always breaks some part of my toolchain (either gcc and friends, or valgrind or whatever). It wasn't so bad when a new os came every few years. now they break stuff every year. six months since I bought a new machine and my gdb still isn't working quite right.
- sigjuice 9y agoApple is not responsible for every piece of third party software, especially niche tools like gcc, gdb and valgrind. It is up to the maintainers of those tools to keep up with new macOS releases. Beta releases of macOS are made available early to developers for exactly this reason.
- familyit 9y agoYou work there for sure
- dang 9y agoThis crosses into personal attack, which is a bannable offense on HN. Would you please read https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html and post only civil, substantive comments from now on?
- realusername 9y agogcc isn't exactly a "niche tool".
- sigjuice 9y agoHow many people who buy an Apple computer need to install and run a C compiler? EDIT: BTW, it is trivial to install clang without Xcode on a pristine Mac. Just typing cc in Terminal will pop up an installer that will download and install clang (and possibly other tools)
- realusername 9y agonot everything needs to be used by the end-user directly. I bet gcc is used a countless amount of times just to build OSX anyway.
- pjmlp 9y agoOS X uses clang.
- 4ad 9y agoClang is used to build macOS and 99% of macOS/iOS applications, not gcc, and Apple maintains clang for you.
- realusername 9y agoAh my bad, I did not know that.
- pjmlp 9y agoIt isn't the official compiler on Apple platforms either, that ship has sailed long time ago. Google has also shown the door to it on their OSes. Lovers of BSD licenses will miss FSF software in a couple of years.
- saurik 9y ago
- josteink 9y ago> It is up to the maintainers of those tools to keep up with new macOS releases. Why should stable tools which has been working for decades constantly have to change their source-code to keep working on Apple's OS, a piece of software whose primary task is running software the user wants to run no less? Apple should make sure the user's software runs on its OS, not the other way around. Stop apologizing for what is essentially the world's wealthiest corporation being lazy and putting the maintenance cost of its own OS on everyone else.
- chii 9y agoWhen shit breaks in the new version, people should stop upgrading to the latest macos! Apple has found that they don't need to put effort into api backwards compatibility because people are still freaking upgrading. It costs money to ensure backwards compatibility, so not doing it is desirable. The end user has to put pressure on Apple to do is.
- coldtea 9y agoYou missed the fact that fixing problems and not stacking technical debt for the sake of "backwards compatibility" is also desirable.
- josteink 9y agoAny particular reason you decided to quote backwards compatibility, as if it's not a real thing?
- coldtea 9y agoQuotes are not only used to denote non-real things -- if anything that's a quite recent (couple decades) trend.
- sillysaurus3 9y ago"recent"
- CJefferson 9y agoWell, it depends on your point of view. Microsoft, and Linux (just the kernel I'm talking about here), have both decided the point of an OS is to run programs, so with each update they both heroic efforts to not break userspace, often adding code just to make sure old programs that did weird things don't break. Apple have decided to go a different route, and leave a trail of programs just a few years old that are forever unrunnable, as they won't even distribute old copies of their OSes. However, it seems many users are willing to take that choice, as we can see from their success.
- dng88 9y agoDepend upon how old. Not sure as I still can download their OSes in App store. Not that I trust Apple to keep there forever and I download them from time to time. But I think I have all since I can get it from App Store. Good to run them in VM as well these days. Strangely you do not have Sierra or High Sierra there. * And keeping old program running as meant all old bugs and old virus run as well. Not sure I live it. * But as long as you have more than one major OS, it is fine to have different approach. Not that you cannot run Sierra now so your program cannot run. Just a deadline instead of we are still using Win 7 after 6 years. Or Win XP per Wanna Cry.
- saagarjha 9y ago> they won't even distribute old copies of their OSes They do, actually; if you bought a copy it should be available in the App Store. They even sell physical installers for old operating systems: https://www.apple.com/shop/product/MC573Z/A/mac-os-x-106-snow-leopard https://www.apple.com/shop/product/MC573Z/A/mac-os-x-106-sno...
- djrogers 9y agoThat was the policy for several years, but this year they changed it - the Sierra installer is no longer in the App Store after you upgrade.
- abritinthebay 9y agoIt is very different but I wouldn’t argue better. It’s lead to a lot of their problems with Windows APIs
- pilif 9y agoI honestly prefer an early crash to random memory corruption
- grandinj 9y agothat is exactly what I dislike about Microsoft. The right answer is to detect those dodgy applications and disable them, and notify the user that the program is "bad", thus providing a severe disincentive to software authors to ever do such things again.
- ygra 9y agoThat mechanism also exists, notably in Vista and 7 there were a number of older applications where Windows would display a warning prior to running it that the application has known incompatibilities and may not run correctly. However, a user who just upgraded Windows and half their programs stop working will simply not upgrade. In many cases such dodgy applications are also never fixed because the vendor doesn't exist anymore, doesn't care, or the flaw is in some library they use and they don't really want to invest that much time to change it. Besides, detecting such behaviour is pretty much the same as fixing it with a compat shim, since you have to do more or less the same work. So from MS's perspective the benefit of working around the buggy behaviour is much more prominent than trying to discipline developers by making users suffer.
- nimish 9y agoWhy should users pay for developers' poor choices? This is a great way to piss off people who would blame Microsoft. There isn't a great answer to this that satisfies everyone.
- grandinj 9y agoHuh? That is kind of the deal isn't it - you pick your developer and if that developer makes bad choices, you get a bad product. If we don't push back against bad practices by developers we never improve the quality of the ecosystem. In this specific instance, the user has a choice - don't upgrade.
- saagarjha 9y ago> the user has a choice - don't upgrade That's how you get everyone stuck on Windows XP. There's no good choice for the user here–either you're on an old OS that's missing features or security updates, or you can't run software that used to work.
- geocar 9y agoSo Unix people had this function called `gets` that was defined like this: char *gets(char *at); In the early days, if someone wanted a string you could do: x = gets(sbrk(0));brk(x + strlen(x) + 1); And this is perfectly safe, but it is perhaps the only safe way to use `gets`. See, most people wanted to write: char buf[99]; x = gets(buf); And is this not safe because `gets` doesn't know that `buf` only has room for 99 bytes. The API has a choice: a) They can make it harder to do the wrong thing; make `gets` generate errors, warnings, crash if you use it, etc. This requires people fix their programs. That's what GNU did for `gets` and it's what Apple is doing here. b) They can change the rules: It's possible to modify the ABI and require markers or a mechanism to detect where the edge of the buffer is. This requires people recompile their programs. I think Zeta-C had "fat pointers" so gets should be safe there[1] c) They can work around: If you have enough resources, you can look at the programs using this API and figure out what their buffer sizes are and hardcode that into the API provider. Microsoft has famously done this for SimCity[2] That's it. They can't really do anything else: The function is difficult to use right and programmers do the easiest most-obvious thing they can. oh i need to get a string, so i'll use gets... but i need two strings so.... Anyway, I'm not aware of any good rules for choosing which way to go: Less total effort seems like a good metric, but this is very hard to estimate when you live on an island and don't know how other people use your software. Memory corruption is serious though: It's often very easy to turn into a security hole, so I generally advocate doing something. All of the people just disabling this security feature make me nervous. I wonder how many of them run websites that I use... [1]: http://www.bitsavers.org/bits/TI/Explorer/zeta-c/ http://www.bitsavers.org/bits/TI/Explorer/zeta-c/ [2]: https://news.ycombinator.com/item?id=2281932 https://news.ycombinator.com/item?id=2281932
- fanf2 9y agoSurely that gets(sbrk(0)) will not work since sbrk(0) returns a pointer to unmapped memory. Maybe you wanted sbrk(BUFSIZ)?
- geocar 9y agoWell, no actually: That still limits you to a gets of BUFSIZ. Just as we often grow the stack with page faults, you could grow the heap with page faults: Modern UNIX doesn't because this is another one of those "almost certainly a mistake", but: signal(SIGSEGV, grow); void grow(int _) { sbrk(PAGESZ); } should work.
- wruza 9y agoIf I ruled MS or was a big boss of Raymond, I would ask him to show a big screen-dimming warning before running these programs, like “This application uses unsafe methods of interacting with your computer and works only because we decided to support it, spending two weeks to make it work. Still no safety guarantees, btw. Please ask Vendor, Inc. to read http://doclink http://doclink on how to do his shit the right way.” [Okay] [Damn, FTS] [Send email for me] No chances I make it to the top of MS though.
- oblio 9y agoAs he nicely explains in some other blog posts, sometimes Vendor, Inc. went out of business in the 80's but the apps are still in use. So you'd just annoy the poor dweeb from Human Resources that has to use the OS and app provided by his employer, the only job he could find in Podunk :)
- valleyer 9y agoApple does this too. Run "strings" on various libraries in Apple's OSes and you will find plenty of instances of bundle identifiers of non-Apple apps.