News for hackers. Stuff that matters.
Re:The old guard of Mac indy apps has thrived for more than ... by Wowfunhappy on Tuesday January 01, 2019 @05:50PM (#18802921)
Apple really needs to stop removing documented APIs. If they want to announce that some APIs have been moved to "maintenance mode", that's fine—just make some effort to ensure said APIs keep working.

Apple is the world's most valuable company, and an independent Mac division would still likely rank in the fortune 500. They are much too eager to effectively offload maintenance burdens to much smaller, individual developers.

I'm not even an app developer—just a power user who wants his wonderful mac apps to keep working! Apple seems to think they're protecting users by forcing developers to update their apps, but they're also pushing developers to non-native technologies like Electron, and I'm quite worried about what their iOS portability initiative is going to do to the landscape.

(I will note that legacy compatibility with precompiled binaries seems to be significantly better than with code; I use some apps that haven't been updated in more than a decade.)

Re:The old guard of Mac indy apps has thrived for more than ... by scarface74 on Tuesday January 01, 2019 @09:20PM (#18803755)
Apple really needs to stop removing documented APIs. If they want to announce that some APIs have been moved to "maintenance mode", that's fine—just make some effort to ensure said APIs keep working.

When I was deep into Windows development, I remember how crazy it was that MS refused to deprecate APIs.

Just the concept of a “string” when programming on Windows could be different depending on the API Microsoft had:

- standard C strings: a null terminated character array

- the standard 16 bit wide character string that was null terminated.

- a BSTR - a double byte character array where the first byte is the length.

- the C++ STL string class.

- a CString - not to be confused with the C style string. This was part of the Active Template Library

- CStringT - it’s been awhile. I have forgotten what this is.

Keeping APIs forever leads to bloat, is a maintenance nightmare, and increases the surface area for security vulnerabilities.

One of the earliest security vulnerabilities that I remember was that it was easy to run shell commands on a remote computer just by escaping the command in IE if the site was running IIS because MS overlooked a type of string encoding.

https://flylib.com/books/en/2.819.1.43/1/

Re:The old guard of Mac indy apps has thrived for more than ... by barrkel on Tuesday January 01, 2019 @09:38PM (#18803827)
As a user, however, I think MS has it right.
Re:The old guard of Mac indy apps has thrived for more than ... by pcwalton on Tuesday January 01, 2019 @10:53PM (#18804057)
The worst is COM's apartment threading model, which is still in your face to this day despite being pretty much nothing more than an extremely elaborate workaround for the fact that Visual Basic 6 didn't support threads. (VB6 was released in 1998; it became old enough to drink this year.)
Re:The old guard of Mac indy apps has thrived for more than ... by mwcampbell on Sunday January 06, 2019 @05:28PM (#18841151)
I doubt that VB6 is actually the only justification for COM's apartment threading model. If that were the case, then I don't think WinRT would still have ASTA (application single-threaded apartments). I think the real rationale is that making sure certain code runs on the UI thread is something that applications have to do all the time, even today, even on non-Windows platforms.
Re:The old guard of Mac indy apps has thrived for more than ... by colatkinson on Tuesday January 01, 2019 @11:11PM (#18804125)
If I'm not mistaken, CStringT is just the template class for CString, CStringW, and CStringA. Makes perfect sense :)

My personal favorite is the PCZZWSTR type, which I've only ever seen used by SHFILEOPSTRUCT. Basically it's a null-terminated collection of null-terminated strings. And of course, there's a corresponding PCZZSTR for narrow-char paths.

VC++ is... interesting.

Re:The old guard of Mac indy apps has thrived for more than ... by Wowfunhappy on Wednesday January 02, 2019 @01:10PM (#18808435)
Random thought, could the attack surface be reduced by limiting old APIs to programs running in compatibility mode?

This would basically be a modification of the "least permissions" principle—only expose old APIs to programs old enough to need them.

Re:The old guard of Mac indy apps has thrived for more than ... by scarface74 on Wednesday January 02, 2019 @03:15PM (#18809734)
It’s almost impossible to get developers to move to newer APIs as long as you allow them to use old APIs. Fortunately (?) only two third party developers really matter on Macs - Adobe and Microsoft. The rest either have to come along for the ride or get left behind.

iOS on the other hand is ubiquitous enough and there is no one killer app that people can’t live without, Apple can deprecate and then abandon APIs and pull developers forward.

Re:The old guard of Mac indy apps has thrived for more than ... by Wowfunhappy on Wednesday January 02, 2019 @03:44PM (#18810006)
> It’s almost impossible to get developers to move to newer APIs as long as you allow them to use old APIs.

Even if the old APIs requires the user to manually right click the executable, go into properties, and enable compatibility mode? It's not hard for the user to do, but I wouldn't want it to be my users's first experience with something I made.

Re:The old guard of Mac indy apps has thrived for more than ... by asveikau on Tuesday January 01, 2019 @11:40PM (#18804224)
When the super-geniuses of Redmond devised WinRT which was supposed to be the savior of it all, they tried to fix this problem with a new string type, HSTRING. It had some additional quirks around NULL that the other types didn't have.
Re:The old guard of Mac indy apps has thrived for more than ... by Wowfunhappy on Wednesday January 02, 2019 @09:24AM (#18806294)
I'd like to think that there's a balance between Apple and Microsoft in this area.
Re:The old guard of Mac indy apps has thrived for more than ... by michaelcampbell on Wednesday January 02, 2019 @09:07AM (#18806207)
> Apple is the world's most valuable company,

Just a nit; Microsoft is currently $30 billion over Apple in market cap.

It goes back and forth here of course.

Re:The old guard of Mac indy apps has thrived for more than ... by justadudeama on Tuesday January 01, 2019 @07:50PM (#18803406)
I think this is a delicate balance as a user.

On one hand, I understand the commenters frustration over constantly changing API's. I understand that it is difficult and not fun and a lot of work.

On the other hand, as a user, I appreciate the fact that Apple forces people to update their code. I don't know how true it is, but there are roomers that Microsoft didn't release Windows 9 in fear of code that checked to see if the Windows version started with "9". Look at Windows first party apps, you have things like control panel and settings, two apps that have no excuse for being duplicates besides the fact that Microsoft refuses to stop supporting legacy code.

In my opinion, software is something to be maintained. Maintenance is ugly and isn't glamorous (won't see BBEdit on product hunt anytime soon), but is necessary. I think the user and developer experience would be worth is software written 25 years ago ran perfectly on my computer, I don't want that.

Re:The old guard of Mac indy apps has thrived for more than ... by Wowfunhappy on Wednesday January 02, 2019 @09:26AM (#18806313)
Again, I'm actually a user, not a developer.

When developers update their apps, that's great! But for every developer Apple "forces" to make updates, there's a developer who decides to just target Electron instead, or an old app that simply breaks.

Re:The old guard of Mac indy apps has thrived for more than ... by x0x0 on Sunday January 06, 2019 @09:48PM (#18842355)
Makechecks comment reads like an psa for just use electron. Which sucks cause electron is a pig but damn. Code shouldn't bitrot this fast.

Also, re Adobe: idiots at the genius bar basically said it's fine and good that using Photoshop cores a brand new mbp on the latest os, and that's not apple's problem because Adobe hasn't certified the new os. We're getting close to buying this employee a windos laptop that is both cheaper and actually runs Photoshop