19 ms·
Thoughts on Cocoa
- codefreq 7y agoFor me it just redirects to apple.com
- markdown 7y agoIts a thread that starts with this: Subject: Thoughts on Cocoa From: Turtle Creek Software via Cocoa-dev <email@hidden> Date: Wed, 2 Oct 2019 13:14:44 -0400 Sadly, we just decided to abandon the Cocoa update for our app. It's not easy to walk away from 3 years of work, but better 3 years lost than 5. Time will be better spent on our Windows version. TurtleSoft started Mac-only with Excel templates in 1987. The first prototype of our current stand-alone accounting app was in the early 90s. Since then, programming for Mac has gone through four primary programming languages (Pascal, C++, Objective C, Swift). Three, soon to be four chip architectures (680x0, PPC, Intel, ARM). Four frameworks (MacApp or Think Class Library, PowerPlant, Carbon, Cocoa). Microsoft and Adobe are big enough that they've survived the many pivots. They can just throw 100 programmers at it. Intuit has barely kept up. For anyone smaller, it's hard to justify the constant need to rewrite code just to stay in the same place. Return on investment is just not there. Seems like each new update is more difficult. Many good apps for Mac have died in one pivot or another. We managed to lurch through most of the changes, but not this one. Thinking ahead to the consequences of Marzipan was the last straw. Meanwhile, our Windows version hasn't needed any work since 2000. It probably will take less than a year to get it updated to 64-bit and a better interface. Casey McDermott TurtleSoft.com
- sliken 7y agoIt did for me 2-3 times, and I was puzzled. I tried a 3rd time and it worked.
- jimbob45 7y agoIt's not like Microsoft is any better. UWP, WPF, WinForms, and GDI are all in various states of disrepair and neglect.
- ch_123 7y agoI would say that the main difference is that many applications written for Windows 95 will work just fine on a Windows 10 system. The Mac ecosystem has nowhere near the same amount of longevity.
- sebazzz 7y agoAnd even well written games, like Deus Ex. Not it's successor ironically though.
- badsectoracula 7y agoWith some tweaks, Deus Ex Invisible War runs fine here on Windows 10. In general i didn't had any game or program i couldn't get it to run in Windows 10 and i have a lot of older software.
- ahartmetz 7y agoBut you can still use any of them. Especially GDI/Win32 which just won't die.
- c-smile 7y agoGDI. If FillRect(hdc,rect) is the only thing that you need from it then it will work for you, yes. But GDI does not support antialiasing so, let's say, Ellipse(hdc) will just draw an illustration to Brezenham algorithm but not that you would want to present to the user. Same thing about alpha channel - no transparency in GDI. So forget GDI for UI purposes. You may try to use that GDI+ horse... But it is pure CPU rasterizer and so forget it too on modern high-DPI monitors. Yes, GDI is still with us but the chorus is here already to sing "Sic transit gloria mundi".
- carlosrg 7y agoAll of these are still maintained and get new OS features.
- badsectoracula 7y ago
- tonyedgecombe 7y agoApple started selling 64 bit machines in 2005 and supported it in the operating system with Leopard: http://theocacao.com/document.page/343 http://theocacao.com/document.page/343 There weren’t many 32 bit only Intel based Macs. This complaint says far more about the developer than Apple.
- duskwuff 7y agoThe first response sums it up nicely: > The people I hear complaining about this are those who, like you, didn't move to Cocoa. Carbon was a _temporary_ transition API*. It was necessary when Mac OS X shipped in March 2001, but even though it wasn't yet formally deprecated, it was clear it would be. - https://lists.apple.com/archives/cocoa-dev/2019/Oct/msg00021.html https://lists.apple.com/archives/cocoa-dev/2019/Oct/msg00021...
- TBurette 7y agoThe fact that they had a long time to transition doesn't negate the fact that they have to spend the time doing the transition. At market-rate developer salary, it doesn't take a lot of man months for the port not to be worth the investment for small shops.
- qubex 7y agoActually, considering the long-term average growth of “developer market-rate salaries” it makes sense to transition as early as possible (as soon as the new alternative is announced/becomes available) to minimise overall cost and capture the market share of those who shan’t transition when deprecation is announced and cost of developers is too high to make it worthwhile.
- beagle3 7y agoExcept if the new thing flops and the old thing doesn’t die - which is much more common in the Windows world. MFC is mostly dead. So are ATL and WPF. Win32 is still going strong though.
- marcus_holmes 7y agoI'm looking at doing desktop apps for my latest project. It's not simple. It used to be simpler, although fragmented. There wasn't one tech for all targets, but there was at least one tech for each platform that did a good job. How come writing a desktop application is harder now than it was 20 years ago?
- zerr 7y agoCross-platform toolkits have much nicer and sane APIs compared to native SDKs. Even if I wanted to target the single specific platform, I'd still pick wxWidgets or Qt Widgets over Win32 or Cocoa.
- etaioinshrdlu 7y agoI would completely agree. It's a bit like html vs native though, you end up trading flexibility for compatibility and ease of development.
- ahartmetz 7y agoDepends. On Windows and Linux, ~nobody complains about Qt applications. On Mac, users do complain because some details aren't exactly right.
- speedplane 7y ago> On Windows and Linux, ~nobody complains about Qt applications. On Mac, users do complain because some details aren't exactly right. Windows users are used to UIs from the 1990s. Linux users are used to 100 different types of UIs and bask in the glory of diversity. Mac users are trained to care.
- badsectoracula 7y agoFWIW i find Qt applications "off" on Windows too, at least when they try to look native, because there is always some little detail that they get wrong :-P. (also often cross-platform toolkits tend to have weird layouts, like having multiple numeric input fields span an entire dialog box width instead of making a more compact arrangement)
- fit2rule 7y agoI hear and also feel the pain. I've been doing multi-platform app development since the 90's, and keeping up with Apple is starting to feel like a fools game - the work one has to do, just to stay on the platform and current with the vendor changes to the OS is very frustrating. Which is why I'm just going to use an engine-only approach from now on. I can, fortunately, eschew native UI's .. since I work on creative tools and my users prefer to have the same pixel-equivalent interface on each platform rather than shifting paradigms. I think that game engines are the future for all app development. There's not much I can't do in Unreal Engine, for example .. with the benefit that the same app truly runs everywhere. If Apple want to continue to subvert developer minds to keep them on the platform, fine by me. The engines see this as damage and easily allow a lot of us to route around the problem.
- jbverschoor 7y agoGood luck running 20 instances for some productivity apps.
- fit2rule 7y agoWho runs 20 instances of an app? That just sounds like poor design. Anyway, I have no problems running multiple instances of a small and light UE-based app. Most I've had running on one machine is 5 .. but I'm not seeing the limitation you're indicating.
- thrower123 7y agoGood luck running 20 Electron apps...
- deleted 7y ago[deleted]
- enzo1982 7y agoAs an open source developer, I have mixed feelings about this. Yes, Microsoft seems very keen on keeping Windows compatible even with ancient versions of the OS. New stuff usually is optional and APIs that behaved strangely in Windows 95 still behave the same way in Windows 10. In Apple land, APIs may change their behavior whenever Apple deems it necessary. I ran into issues because of this with almost every macOS update since 10.8. And I see that even big players like Adobe keep running into compatibility issues all the time. On the other hand, I'm spending just a few hours per week working on my project [0] and I manage to support an app that now runs on 10.5 through 10.14 and on three different CPU architectures with a single package. So no, I don't think you need to "throw 100 programmers at it" to get a working macOS version. [0] https://github.com/enzo1982/freac https://github.com/enzo1982/freac
- badsectoracula 7y agoNot all applications are the same. Your application may not have the same requirements from the OS than some other application. As an (extreme) example, an application written in C that only needs from the host OS is a top level window and basic events for handling input while doing everything else with custom code will be much more portable and easy to keep up with changes than an application written in a language with its own runtime, creates a native UI for each platform, uses native APIs and tries to integrate with the native OS.
- saagarjha 7y agoAlthough, it seems like you’re reimplementing platform controls? This seems like a mini-Qt: https://github.com/enzo1982/smooth https://github.com/enzo1982/smooth
- enzo1982 7y agoYes, that's my own custom UI framework. Most of the platform dependent stuff is implemented in the smooth library. In hindsight, it would have been easier to just use Qt, GTK or wxWidgets. But I learned a lot by doing this myself and wouldn't want to miss that experience.
- 7y ago
- kalleboo 7y agoThey also have a blog post with more a detailed explanation than the linked mailing list post https://turtlesoft.com/wp/ https://turtlesoft.com/wp/
- saagarjha 7y agoThe version numbers are a bit off in that.
- galad87 7y agoCarbon UI framework has been deprecated for 12 years. Cocoa has been available since the first Mac OS X version, so ~20 years ago, and it's still be main UI framework on macOS, and it will still be for years. You can't come now and whine that Apple changes UI frameworks too often.
- danieldk 7y agoI think another issue is that on Apple's platforms the changes are quite abrupt, whereas most other platforms are gradual. E.g., if you wrote a Qt (the toolkit) application in 1996, you could have slowly transitioned your application to Qt 5 version by version. In the meanwhile, you have gone from non-standardized C++ to C++98, to C++11. So, you would have an application with a modern language and toolkit, which was gradually developed over the last 23 years. The same for Windows applications. For me, the truth is somewhere in the middle. Yes, there is more churn on Apple platforms. On the other hand, it also allows Apple and the ecosystem to move faster. It is amazing what they have been able to achieve with (just naming some random things): wide Touch ID support, Metal, or application sandboxing.
- galad87 7y agoYou could have done the same with Carbon to Cocoa: transition a window/view at a time. You can use Cocoa windows and views in Carbon. Plus you can keep using your C++ core even if the UI is Cocoa. The same applies to Swift, you can write or rewrite parts of the app in Swift and keep part of it in C++/Rust/Objective-C or your preferred language. The same happens in SwiftUI, you can mix it with NSView and UIViews.
- blub 7y agoAFAIK Carbon was a C++ API and Cocoa is Objective C(++). In which case the UI is a rewrite , not a transition.
- lonelappde 7y agoYou rewrite one screen at a time.
- threeseed 7y agoThis is entirely by design. Apple doesn't want you to build an app 20 years ago, make no updates to it and continue to sell it as though nothing has changed in the time since. Their website is compromised of mostly broken links, the design is dated and it is showing reviews and awards from 10 years ago. Clear to me that they couldn't be bothered to put any effort in at any point in the buyer's journey so I say good riddance to them.
- ubercow13 7y agoIs this the reason that everything on iOS app store is transitioning to subscriptions where before an app cost $3 and now it costs $3 a month, because developers worked out that the cost of keeping up with Apples constant platform changes is too much?
- bluk 7y agoI think that’s more that developers want to make a decent living. The vast majority of subscription apps have a server side maintenance cost. As the platform matured and developers realized those users were going to stick to their apps for years without paying another penny, then it becomes untenable.
- blub 7y agoThat's simply not true, many offline apps are transitioning to subscriptions and maybe add some lame cloud sync as an excuse/afterthought. Happened to me recently with an app which is the interactive version of a book. From one day to the other they switched from buying chapters/the book to some stupid subscription. If they can't make a living they need to charge more and if they can't charge more they need to find a real job/business.
- acdha 7y agoThe problem is that so many companies burning VC cash and/or ad dollars have trained customers to think software costs less than a cup of coffee. If you charge what you need for a sustainable business up front, your sales will be enormously less and you’re going to get tons of negative reviews from people who think a $20 app would need to cure cancer to justify that price. (And, of course, even $3 deserves lifetime free updates and new features) It’s especially bizarre that you’re ranting about them needing to find a real business when that is exactly what they’re doing by finding a billing model which is viable long-term.
- Nokinside 7y agoWhen you consider investing into user facing software trough specialized API's and tools, it's safe assume only 5-10 year useful life. The consequence is that investing into user facing apps and developers has limits because ROI is limited by current and near future user base. Separating all the program functionality from all the OS/UI stuff pays off over longer term.
- seanalltogether 7y ago> Meanwhile, our Windows version hasn't needed any work since 2000. I see they haven't updated their website since 2000 as well. It's hard to have sympathy for software companies that don't invest in their business.
- beefhash 7y agoI, for one, rather enjoy the 2000s aesthetic. Different tastes for different folks.
- tannhaeuser 7y agoCome on, there certainly are reasons to complain about Apple deprecating stuff and strongarming developers into their walled garden, such as OpenGL, the fast-move to Swift/Swift versions, SIP/mandatory signed apps, XCode a moving target with OS updates, EFI BIOS updates for eg. booting from afs only downloadable as part of 6GB Mojave and soon Catalina OS updates, deprecation of semi-official Mac OS ports without equivalents on brew, stone-age Unix userland tools (bash, awk from early 2000), Java (and now Python) unbundling, and probably others I'm not aware of since right now I'm not very much into developing on Mac OS and iOS. But Carbon isn't one of them. I knew Carbon was about to be deprecated in 2005 when I was coding a crappy UI for a crappy OCR solution. Carbon was just a forward-compat GUI lib on Mac OS classic (1998?) for apps to run on Mac OS X (2000).
- saagarjha 7y ago> deprecation of semi-official Mac OS ports without equivalents on brew Apple doesn’t deprecate ports, since they don’t run it.
- badsectoracula 7y agoIn other saner platforms (Win32 or even X11, if you ignore Gtk and Qt) you can pretty much assume that if something is deprecated it will still remain around even if it wont get updates as doing otherwise will break all the applications that rely on that tech that people bought and rely on. Especially when that deprecated something is still used by developers despite it being deprecated. But apparently Apple doesn't care about their users and developers. Saying "told you so" doesn't help much, the only thing that helps is keeping things working. Anything else doesn't matter. Though if there is anything that can be "told you so"'d that would be bothering with Apple's platforms when Apple doesn't care about you.
- calcifer 7y ago> X11, if you ignore Gtk and Qt You don't need to ignore those. GTK+2 was released ~17 years ago and Qt4 was ~12 years ago. Apps written with them still run perfectly fine on modern Linux distros.
- protomyth 7y agoI would have much the same sour grapes attitude of many in this thread, except for one point: Apple cannot even keep code examples working. Most of the code samples on Apple's dev site don't even compile a year or two after they are written and Apple doesn't bother keeping them updated. This is a rather large problem and verification of how hard it is to keep up.
- Synaesthesia 7y agoI’d you’re talking about swift yes they changed a lot since the early versions and many code examples are out of date. I believe the language has stabilized now.
- protomyth 7y agoMost, but the Objective-C examples also have breaks.
- saagarjha 7y agoOnly very rarely.
- protomyth 7y agoUhm, the OpenPanel changes basically crapped on a whole group. Apple does not keep its examples updated. Heck, now its hard to find examples at all.
- Klonoar 7y agoI still write ObjC more often than most, and I’m pretty familiar with their stuff - I’m generally the first to claim examples are like a needle in a haystack, but they almost always do work when you find them. They definitely might be outdated, tho.
- quelsolaar 7y agoThis is why unfortunately the Mac is dead to me. I would love to support it, but when OpenGL was deprecated it was just game over for me. A company that forces me to learn a completely different language to access their basic APIs and keeps changing them is just too mush of a hassle. Every hour spent on maintaining a mac port is an hour not serving the 90% of users who aren't on Mac. You can complain about OpenGL all you want, and praise Metal, but it doesn't matter how much better it is. i cant rewrite all my shaders, and do the API integration. The fact that the richest company cant hire 10 engineers to maintain compatibility, and are pushing all this work on to thousands if small independent developers is just rude. With apples history, why spend time embracing, their new tech if you cant count on it sticking around. For developers who write small one-off apps for iOS its fine, but for people who make larger long term applications Apple is very developer hostile.
- wffurr 7y agoUse ANGLE and keep writing OpenGL. It has Metal and Vulkan backends and papers over all the various GL driver bugs.
- quelsolaar 7y agoThere are workarounds for everything. The problem with the Mac is that I have to work around everything. No C API, XCode, lack of extension support, driver bugs, poor documentation, weird manifest files, the OS switching run directory randomly... You cant behave like that when you are a small platform.
- lonelappde 7y agoA trillion dollars says you absolutely can behave like that.
- dansman805 7y agoThe trillion dollars says you can behave like that on a large platform (iOS), but not much of that trillion dollars comes from the Mac, a comparatively small platform, does it?
- mwyah 7y agoSeems like they call themselves "Turtlesoft" for a reason.
- blinkingled 7y agoNot sure if they're complaining about runtime compatibility on macos but does anyone know if I wrote a Cocoa app few years ago on Snow Leopard or whatever would it still run as-is on macos version of today? If not, then I can sympathize with their complaint that keeping up with macos updates will be more effort than Windows. The one time carbon to Cocoa update will be worth doing if my Cocoa app is not broken by next 10 os updates requiring constant code updates.
- badsectoracula 7y agoDepends on what you used, i guess. I bought an iMac in late 2009 which i think came with Snow Leopard and i upgraded to new macOS versions whenever they came out up until El Capitan which was the last version to support it (i've heard that you can run Sierra with an unsupported patch too but didn't try it). I've also got (some bought, others free) a few applications from their developers' sites - that was before the Mac App Store. After every single macOS upgrade some application would stop working. By the time i installed El Capitan, no application that i had installed since the Snow Leopard days worked. Mac App Store didn't help either though. I've only bought a couple of applications from there, but one game - NOVA 3 - broke after an OS upgrade (do not remember which) and then was removed from the store instead of being updated. Of course this is partly the developers' fault, but on Windows this would never have been an issue as i have games and applications more than a decade older than NOVA 3 that still work on the latest Windows 10 with little to no fixes. I also had a similar case with iOS - i got an iPod Touch some time ago, bought a bunch of things, several versions later nothing worked. Eventually the device itself stopped being supported and developers were both forced to not support it and did require later versions of iOS. Typical case of forced obsolescence since otherwise it was a fine device. This experience alongside Apple's attitude towards (ignoring) backwards compatibility is what makes me stay away from their systems.
- mantap 7y agoForget snow leopard, Apple can't even keep compatibility for the version they released 1 year ago. When Apple announces a new OS update at WWDC you have approximately 4 months to install a beta on an external drive and fix any incompatibilities. Oh and it's a moving target, they only freeze it just before release. This process repeats every single year, sometimes they are so excited to break shit that they do it in a patch release but that's much rarer. If there's a silver lining it's that Apple has gotten so bored with the Mac that they don't change as much as they used to, it's certainly not as bad as it used to be, but not because Apple has suddenly started caring about backwards compatibility.
- charlesism 7y agoThe paradigm programmers deal with today is demoralizing: it’s lousy to know your work will disintegrate in five or ten years. For a while Mac OS 10 had support to run Mac OS 9—- via nicely integrated emulation. Then Apple removed it. I’d just love it if the current OS supported all previous versions, via emulation.
- badsectoracula 7y agoEh, it isn't that bad. Apple is such a case, sure, but other platforms are better. Win32 is probably the king of backwards compatibility - software you wrote or bought 25 years ago will work just fine on modern Windows 10 (assuming you didn't do too many mistakes :-P). But Linux in general should have decent backwards compatibility too, at least for stuff not relying on Gtk and Qt (or C++ if you go far back). Some time ago i compiled some examples from a GUI toolkit i was working on on a RedHat from 1998 and they worked on Debian from 2018 just fine. In source code form you may even surpass Win32 as code written for X11/Xlib and Motif (to some extent since that wasn't 100% compatible between different Unices) will still compile with little to no modifications. And of course anything you write to run in a web browser has good chances to work in the future (client side only). Well, assuming Google doesn't completely take over and decide that they know better than anyone else if it is a good idea to remove stuff or not. Also while not exactly OSes, but several platforms exists that provide isolation from the underlying OS madness. E.g. Java/JVM is an example of a platform that almost never breaks stuff. Languages like Smalltalk and Common Lisp also tend to be very stable. Free Pascal and Lazarus developers also try hard to avoid breaking code (there is still breakage but it is very rare and in almost all cases is about bugs in the compiler - personally i had only a couple of cases where i had to fix code over the last 15 years and that took me only a few minutes).
- charlesism 7y agoGreat point. I made some assumptions without taking a mental inventory. The issue is disproportionately an Apple issue (and even then, an issue with programs that rely on Apple APIs).
- matwood 7y ago
- rcarmo 7y agoI coded in Objective-C back in the NeXT days, did various (small) Cocoa and iOS apps and still use Macs daily - but work at Microsoft now. Despite my own personal plights with small desktop utilities I write now and then, I don't think Apple has broken Cocoa _that much_ or that it is untenable for a small company to ship cross-platform desktop apps these days (never mind Electron, I'm talking about toolkits like Qt, Xamarin, etc.). _Especially_ if their core functionality can be cleanly detached from the UI. I poked around a bit to figure out the detail to which the software does estimations, and it does seem like there is a very complex UI: https://www.turtlesoft.com/Images/Goldenseal%201024x768.jpg https://www.turtlesoft.com/Images/Goldenseal%201024x768.jpg ...but I keep wondering how much of it could be abstracted away by a cross-platform toolkit, and what kind of separation there is between the estimation/modeling code and the UI itself. We'll never know without a good overview of the internals, but my guess (based on looking at many internal corporate apps over the years, from the pre-web days) is that this evolved organically over time and built up technical debt by literally following UI abstractions rather that isolating their core code from it.
- dagmx 7y agoWithout using their software, and just going based off of screenshots, I don't see anything that couldn't be ported to Qt fairly easily. Now if there is a lot of intertwined code that makes the UI less portable, that's another issue, but I currently don't see how their UI layer could be so complex as to not be easily shifted to Qt. The cross platform nature alone would be worth the cost in my opinion.
- silvestrov 7y agoOr even electron (gasp). The application looks like simple webpages. It might even work better as a web site, so the customers don't have to worry about backups, sharing data, etc.
- pikuseru 7y agoOr just go the whole way and make a virtual machine http://fabiensanglard.net/anotherWorld_code_review/ http://fabiensanglard.net/anotherWorld_code_review/
- princekolt 7y agoThe only Cocoa API that has been deprecated in recent years is drawers. Apple is not going to suddenly rewrite their entire desktop apps and utilities in UIKit/Marzipan anytime soon (if ever - hell, they won't even rewrite them in Swift anytime soon), so Cocoa is well established and here to stay for a long time. So unless your app is entirely built out of drawers, I don't see how the mere presence of Marzipan can affect your long term business.
- swerner 7y agoQTKit was deprecated, and support for objective-C garbage collection, once praised as the future, was removed altogether.
- vlozko 7y agoTo the best of my knowledge, there wasn’t much of a difference in programming style going from GC to ARC except for a few exceptions like all those pesky CFMakeCollectable calls that ended up being no-ops anyway.
- swerner 7y agoYou have to add all kinds of reference qualifiers (__strong, __weak, ...).
- plorkyeran 7y agoYou don't have to explicitly mark things as strong as it's the default. Having to manually break references cycles with weak pointers does make the migration not as simple as just changing the compiler flags, but I've never heard of it being all that difficult. Apple managed to migrate Xcode in a single version.
- kec 7y agoGarbage collection was deprecated almost immediately after it was released and has never been supported on iOS (which let’s be honest is the target for 95% of all cocoa developers)
- ciconia 7y ago> For anyone smaller, it's hard to justify the constant need to rewrite code just to stay in the same place. This sort of says it all about modern progress, or indeed modern capitalism - you need to run all the time just to stay in place. This is also known as the Red Queen's Race [0]. [0] https://en.wikipedia.org/wiki/Red_Queen%27s_race https://en.wikipedia.org/wiki/Red_Queen%27s_race
- mantap 7y agoFor me the last straw was notarization. I am not going to beg for permission to release software for Apple's platform. Considering the dire state of the Mac software scene Apple should be the ones on their hands and knees begging developers, the arrogance is incredible.
- galad87 7y agoNotarization is an automated process, it's not an app review, there is no "begging". Anyway, you can just run unsigned apps on macOS.
- sjwright 7y agoApps aren't required to be notarized and it trivial for any vaguely competent person to dismiss the one-time warnings about unsigned apps. So it's only a big deal if you choose to make it one. To be perfectly honest, if you can't even jump through that absurdly minimal hoop, I wouldn't want your software running on my mother's computer anyway.
- perspective1 7y agoApple's app stores are stuffed with quality apps. They don't need to give developers a quality experience because the supply is there anyway. So they don't. Small development shops have similar negotiating power and position to struggling unsigned music bands.
- andrew_ 7y ago> my current windows app STILL WORKS ON VISTA, i don't have to do ANYTHING to "stay up to date" with Windows, cuz they support backward compatibility, and don't force changes on developers. > Meanwhile, our Windows version hasn't needed any work since 2000. Microsoft's impressive backcompat is a blessing as much as it is a curse, and is also the cause of the [subjective opinion incoming] awful User Experience and complete lack of UI and UX consistency, and it remains the number one reason I don't wish to go back to Windows.
- badsectoracula 7y agoTheir UI inconsistencies (i find the UX perfectly fine myself) mainly comes from their insistence on creating new toolkits left and right due to their internal power struggles. They have improved existing stuff several times, but they most likely have a Google-like situation where new stuff is rewarded more than keeping old stuff running (though unlike Google they also manage to keep old stuff running, so perhaps things aren't as bad).
- noisem4ker 7y agoWin32, WinForms and WPF desktop applications are all able to follow the OS theme. With Metro there's been a departure to a visually incompatible paradigm. This is to say that the lack of UI consistency is a political problem, not a technical side effect of keeping old UI technologies running.
- stickfigure 7y agoI wouldn't be so sure of this. I made the Windows -> Mac transition in 2008 and recently played around with a modern Windows machine. I was pretty stunned to find the Control Panel experience... not unchanged, but still eerily similar to Windows XP. Windows' Control Panel is a trainwreck of UX compared to OSX System Preferences. Being such a core part of the OS, I really expected to see, well, something new and better. But then I remembered how countless programs embed themselves in the control panel via DLLs, so Microsoft probably can't make major changes to the UX without breaking binary compatibility with ancient software packages.
- GnarfGnarf 7y agoQt seems like a good solution to multi-platform requirements.
- mikece 7y agoI'm not familiar with the architecture of the app in question but are the UI parts and business logic/processing parts not properly separated such that a full app rewrite is needed? Someone referred to the backward compatibility of Windows apps as a curse: this is especially true when companies finally decide to update a VB6 or early 2000s WInForms app to something modern, the first step of which is to extricate all of the business logic in click handlers. By the time Cocoa came out the concept of separating your application into logical layers such that things like the UI could be swapped out with newer tech faster were well known so this shouldn't have been such a big deal if the app was constructed correctly.
- m-p-3 7y agoThe operating system is a foundation all developers needs to upon, and you want this foundation to be solid in many ways. Being secure and offering the latest technologies available to the developers is one aspect, but being stable (in terms of ending support) and supporting those previous technologies for a long amount of time is another. I feel like Apple isn't doing the later.
- sercand 7y agoI guess they don't have the resource to update their homepage last 20 years how they can update the app? Their website still shows how long does it take to download files on the Dial-Up connection.
- c-smile 7y agoThat happens all the time. With any OS. On Windows, if you have an application that draws stuff using GDI+ (20+ years technology) then you will discover that it is not moving today on high-DPI monitors. GDI+ is pure CPU rendering and the Moore's is over. GPU rendering is the only option these days. Yes, GDI+ still works. You see it renders something in your applications on Windows 10. But you cannot use the application on your new cool monitor. Same with CoreGraphics on Mac. CG is GDI+ alike thing by nature - pure CPU rasterizer. Something tells me that it will die pretty soon too. Good abstraction/isolation layer is definitely needed for the applications that want to survive on the long run. As an example, Norton Antivirus started using such UI layer (Sciter Engine - https://sciter.com https://sciter.com) 12 years ago. First versions were using GDI rendering backend. Then we added Direct2D GPU accelerated backend. With the same API. Application code and architecture did not change all these 12 years. Same thing on MacOS. Initially the engine used CoreGraphics. Then OpenGL gfx backend was added. And now we are working on Metal. And Vulkan for these matters. But API of the engine is the same as it was initially. TL;DR: Good application architecture is still the thing.
- abujazar 7y agoThey probably should’ve started porting their app to web tech 10-15 years ago rather than ranting about progress in native frameworks.
- TheOtherHobbes 7y agoNot specifically Cocoa - but audio in Catalina is a city block-sized dumpster fire. A good set of big audio developers - Steinberg, Ableton, Avid, NI, Presonus - and not a few of the smaller developers have had to send out emails saying "Whatever you do, don't upgrade yet!" I'm sure there's a shiny happy Cupertino reason for this, but is it ever an annoying waste of time and resources for everyone involved.
- macintux 7y agoWorth pointing out that Catalina hasn’t been released yet. There’s a good chance the problem(s) won’t be fixed by then, but it’s a little OTT to gripe about beta software.
- pier25 7y agoI started using macOS in 2007 and I've learned the hard way it's not a good idea to update to a major version right away. These days I usually wait about a year before installing a new major version. I barely installed Mojave the other day.
- jmnicolas 7y agoI do the same with Windows. I upgraded to Vista 1.5 years after it's initial release and never had a complaint about the OS which was much better than XP for me.
- FpUser 7y agoI skipped Vista completely (except one machine I used to test my software with) and went to Win 7. Same thing with Win 8.
- blub 7y agoSadly not an option for anything internet-connected. Each macOS version has dozens of critical vulnerabilities.
- KibbutzDalia 7y agoI think the future is game engines. You can write once and run everywhere. As soon as there’s one with first-class support for Rust (as the world is clearly and rapidly moving to Rust) the rest will be moot.
- pier25 7y agoFYI Flutter basically works like a game engine.
- seltzered_ 7y agoContext: The authors software website: https://www.TurtleSoft.com https://www.TurtleSoft.com A screenshot: https://www.turtlesoft.com/Accounting-Software.html#Chart_Of_Accounts https://www.turtlesoft.com/Accounting-Software.html#Chart_Of... I want to be respectful to an indie developer, but think it’s worth considering the kind of niche he works in (guessing windows -centric) and probably does more high touch sales. I want to also guess that many of the people on that thread are from an older generation of developers, might be worth considering what the tradeoffs have been in language improvements that have attracted more people to writing software compared to the authors in that thread saying C++ is all they need.
- lonelappde 7y agoHis users are surely customers from 20years ago who never wanted to switch to anything new.
- blub 7y agoThis is exactly how software should be: it should just work reliably for years and decades on end.
- js2 7y agoSure that's fine. You can stick with your decades old computer running a decades old OS and decades old software. What you can't do is expect the rest of the technology world to standstill or forever maintain backwards compatibility.
- thesquib 7y agoI think it is a shame that longevity of software is a thing of the past.
- acdha 7y agoA myth of the past: the reason why everyone switched to online update cycles was recognizing how common security updates and other bugfixes were, and how much you’d save by planning to do them regularly.
- tolmasky 7y agoI wish they would just open source Cocoa (AppKit) if they're going to just abandon it. There were some really good ideas in there, and I think it could possibly develop an active community to continue experimenting with them. IMO the problem this time around isn't the pivot, but the absolute half-heartedness of the pivot: two half-finished solutions: Swift UI and Catalyst, neither of which works very well yet, and this after about 5 years of pitiful development on Cocoa proper while simultaneously asking people to kind of switch to Swift. So it really feels like 3 half pivots in those 5 years, all to end up with something less polished than Cocoa in its heyday. I really respect anyone who put up with working on Cocoa apps the last 5 years. The documentation has been sparse to non-existent on new features (often times for a year or longer your best bet was to wade through a WWDC video to get any information at all), coupled with a really miserable Mac App Store experience that was forced on you. It's really sad that when you would find some bug in Cocoa, unlike in the past, you could basically determine that this was it, as everything feels end of the line and thus not likely to be fixed.
- xhruso00 7y agoThey can't update their web https://www.turtlesoft.com https://www.turtlesoft.com and they charge $495 for a non-accounting licence. Seriously, the web looks like it was done around year 2000.
- FpUser 7y agoShould they? Maybe it is not that pretty but it is functional. Many modern sites on the other hand show big nothing picture that one has to scroll down and hunt for info. And I love that light grey text on white background which is nigh to impossible to read for many not so young eyes. And since they have pretty specific product I am pretty sure that their customers do not give a flying hoot about how the site looks. They need specific functionality from the product
- thesquib 7y agoThis 100 times. Form over function is apparently more important these days.
- reaperducer 7y agoMeanwhile, our Windows version hasn't needed any work since 2000 While I don't disagree that it's hard to keep up with Apple, if you haven't updated your Windows product in 19 years, then it's probably not a product I would want to use anyway. Imagine if web developers thought the same way. Very few web sites exist today as they did in the year 2000, and those that do are ultra niche, or abandoned.
- ratww 7y agoCuriously, the website of the software in question has been using the same design since at least early 2003 https://www.turtlesoft.com https://www.turtlesoft.com https://web.archive.org/web/20030420115300/http://www.turtlesoft.com/ https://web.archive.org/web/20030420115300/http://www.turtle...
- donatj 7y agoI disagree completely. If software genuinely hasn’t needed to be updated since 2000, it’s solid, dependable. It’s a hammer. I use the same hammer I use today I used 20 years ago. It’s a tool, not a gimmick. Think the UNIX tools used billions of times a day we don’t even think about.
- guitarbill 7y agoHammers don't have security issues, which is where the analogy breaks down. Sometimes, these UNIX tools haven't changed much on the outside, but they are getting updates. If you look closer though, the BSD and GNU variants of common tools have diverged. And while I like BSD's conservative approach, some of the GNU features are damn useful.
- vbezhenar 7y agoHacker News looks like it was from 1995. Works fine for me.
- reaperducer 7y agoBut HN is updated minute-by-minute. It's up to date. The guy moaning in on the Apple listserv said he hasn't touched his Windows app since 2000.
- coldtea 7y agoWell, they'd only have to do one major transition, to Obj-C/Cocoa and for that the writing was on the wall for 20 years (and official for 15 years) and everything would have been much smoother. Had he used Cocoa, the rest, would have been trivial (to x86, to 64 bit, etc). Or he could use whatever they like (C++, Pascal, what have you), and have their own UI/compatibility layer between OSes, like Adobe for example does (and several others, big and small: Sublime Text is an one man shop, and they make their own UI just fine). The first response in the thread is not far off: The people I hear complaining about this are those who, like you, didn't move to Cocoa. Carbon was a _temporary_ transition API*. It was necessary when Mac OS X shipped in March 2001, but even though it wasn't yet formally deprecated, it was clear it would be. The Carbon UI frameworks were deprecated circa, um, 2006(?). QuickTime has been deprecated nearly as long. 64-bit systems shipped in the mid-2000s, even before the x86 transition, and it was obvious then that 32-bit would eventually go away. Eighteen years is _forever_ in the tech industry. At the time Cocoa was introduced, the Mac itself hadn't even been around that long! It sounds like keeping an app limping along on 30-year-old APIs, and then suddenly trying to move it forwards all at once, is a bad idea. By comparison, keeping a Cocoa app up to date isn't that big a deal. I was maintaining Cocoa apps during the 64-bit, x86 and ARC transitions and had to make very few code changes. I've been out of the UI world for about 8 years, and there have definitely been significant changes in areas like view layout and document handling, but adapting to those isn't rocket science. Yes, Microsoft is rather fanatical about compatibility. But that's part of what lost them their lead after the '90s: the amount of development resources needed to keep everything working exactly the same, and the difficulty of making forward progress without breaking any apps. —Jens
- pjmlp 7y agoWhile I agree with you relating to Carbon, Microsoft is pretty much the still only game in town for desktop computing (which also includes laptops and 2-1 hybrids) in worldwide market share.
- coldtea 7y agoYes, but macOS has enough native apps for everything, and the advent of web apps and mobile apps, made the whole point moot. You can do everything and more on a Mac.
- twarge 7y agoThis constant iteration is exactly how software development works now. By contrast to this, Quickbooks for Mac went through a ground-up rewrite in Cocoa about 10 years ago and has been keeping up with the transitions. It's really beautiful software that's a delight to use. They even used an SQLite data format so that you could easily access your own data. Apple's is best at how it gently breaks stuff to move everyone forward.
- FpUser 7y agoI can't even fathom what would poor Quickbooks ever do without Apple "gently breaking stuff".
- thesquib 7y agoDoes anyone know if the current macOS still uses elements of Carbon under the hood? What about Catalina?
- floatingatoll 7y agoI wish this post focused on the core issue: they don’t make enough money from Mac sales to be willing to replace a framework (Carbon) deprecated by Apple 15 years ago, and are instead terminating Mac support. I’m surprised they didn’t do that sooner, but blaming Apple for ending Carbon support is beside the point of “not enough revenue”.
- musicale 7y agoApple makes my preferred platforms, but macOS and iOS have poor backward compatibility, and this is particularly bad for games. Yearly ABI changes and removals impose a recurring maintenance burden on developers to revise their apps just to keep them working. I think it's one of the factors driving the move to subscription pricing.
- cmsj 7y ago“Meanwhile, our Windows version hasn't needed any work since 2000” I honestly don’t see that as a good thing. What are these people doing if they haven’t touched their code in almost 2 decades?