3 ms·

>Launches faster, than Safari. As it should, since one is a clock, the other a web browser. Interesting stuff. Cross platform development is inspiring.

creativenolo 4y ago
> As it should, since one is a clock, the other a web browser Yeah. Surely a better statistic to be had.here. System preferences?
naniwaduni 4y ago
As it should, but not a given now that it's common for apps to bundle a whole browser as a runtime.
- ChrisMarshallNY 4y ago
  Not mine. I write native. I do tend to release apps in UIKit, so I don't quite achieve Buzzword Bingo, but I have always been a fan of native apps, and have watched the various efforts to avoid native, with the kind of sick fascination usually reserved for train wrecks.
  - klabb3 4y ago
    Do you rewrite your apps for other platforms? I don't think anyone avoids native, it's just that cross platform is a much more important goal for many.
    - ChrisMarshallNY 4y ago
      No. I don't write apps for other platforms. I am quite aware that it is not the ideal "business posture," but that's how I roll. I've been writing for Apple platforms, pretty much exclusively, since 1986.
dwighttk 4y ago
Can’t remember the last time I thought about app launch speed outside of network access issues.
- seedie 4y ago
  And instantly GIMP comes to my mind.
mrozbarry 4y ago
I agree that a clock should absolutely open faster than a browser, but it would be good to know what this metric actually represents. I don't know much about this style of universal binaries, so I don't know if the binary being "true 5-arch universal binaries" is the focus of the application start time metric.
- kenferry 4y ago
  Support for different architectures doesn't impact start time much. The code for the different archs is in different chunks of the file. Linking more libraries slows down launch due to initialization that happens to get the libraries ready to use. Besides that it's mostly what the app itself is doing on startup. So yes, beating Safari for a tiny app is… a good thing, but not very impressive.
WesolyKubeczek 4y ago
Safari “getting snappier” with every OS update is a running gag in at least the MacRumors community. Or has been for quite a while. Maybe it’s retired now, much like the old gold “but will it run Crysis?” one. By now, Safari should be so snappy it opens your pages and have their document tree ready two seconds before you think of doing it.
deleted 4y ago
[deleted]
- deleted 4y ago
  [deleted]

creativenolo 4y ago

> As it should, since one is a clock, the other a web browser Yeah. Surely a better statistic to be had.here. System preferences?

naniwaduni 4y ago

As it should, but not a given now that it's common for apps to bundle a whole browser as a runtime.

ChrisMarshallNY 4y ago
Not mine. I write native. I do tend to release apps in UIKit, so I don't quite achieve Buzzword Bingo, but I have always been a fan of native apps, and have watched the various efforts to avoid native, with the kind of sick fascination usually reserved for train wrecks.
- klabb3 4y ago
  Do you rewrite your apps for other platforms? I don't think anyone avoids native, it's just that cross platform is a much more important goal for many.
  - ChrisMarshallNY 4y ago
    No. I don't write apps for other platforms. I am quite aware that it is not the ideal "business posture," but that's how I roll. I've been writing for Apple platforms, pretty much exclusively, since 1986.

dwighttk 4y ago

Can’t remember the last time I thought about app launch speed outside of network access issues.

seedie 4y ago
And instantly GIMP comes to my mind.

mrozbarry 4y ago

I agree that a clock should absolutely open faster than a browser, but it would be good to know what this metric actually represents. I don't know much about this style of universal binaries, so I don't know if the binary being "true 5-arch universal binaries" is the focus of the application start time metric.

kenferry 4y ago
Support for different architectures doesn't impact start time much. The code for the different archs is in different chunks of the file. Linking more libraries slows down launch due to initialization that happens to get the libraries ready to use. Besides that it's mostly what the app itself is doing on startup. So yes, beating Safari for a tiny app is… a good thing, but not very impressive.

WesolyKubeczek 4y ago

Safari “getting snappier” with every OS update is a running gag in at least the MacRumors community. Or has been for quite a while. Maybe it’s retired now, much like the old gold “but will it run Crysis?” one. By now, Safari should be so snappy it opens your pages and have their document tree ready two seconds before you think of doing it.

deleted 4y ago

[deleted]

deleted 4y ago
[deleted]