News for hackers. Stuff that matters.
Re:Splash screens == sloth by Maro on Monday February 20, 2012 @09:51AM (#3612529)
This weekend the 3G mysteriously stopped working on my iPhone, so after months of use, I rebooted it. Rebooting the iPhone takes 1+ minute, and there _is_ a kind of splash screen shown during that time. The reason it appears instantenous during normal use is that it doesn't actually boot or load, it just turns the display back on. Also, many iOS apps actually have splash screens, you just don't see them very often as they're usually already running in the background (big apps like Facebook, and even small ones like PCalc Lite or Quotes).

You can kind of achieve this with Windows + Adobe stuff too. Just don't quit Photoshop when you're done using it, and don't turn the computer off, put it to sleep. If you have an SSD (like your iPhone), then swapping Photoshop back into main memory will also be much faster.

Of course the OP is right, Adobe stuff is bloatware and sucks. Fortunately for non-pro designers, there are alternatives like Pixelmator and Paint.NET.

Re:Splash screens == sloth by roadnottaken on Monday February 20, 2012 @11:08AM (#3612778)
I guess this is sort-of the idea behind OSX behavior where an App is running with no open windows. They WANT you to leave everything running in the background. As a longtime Windows user, I still find this confusing, but I think they're trying to make everything appear to "load" instantly because it's just always running... sort of like on a phone.
Re:Splash screens == sloth by jlarocco on Monday February 20, 2012 @12:38PM (#3613097)
At first I didn't like it, but I've eventually started to really like this in OSX. Having a ridiculous amount of RAM to "waste" may have helped change my mind. My only gripe is that I wish it were a per application setting.

Some apps, like my browser, mail program, the terminal, Emacs, ... I love having start quickly, even if it's because they were just in the background before.

Other stuff, like Preview, I don't use often enough to care about the load time, and I would probably configure it to exit when the last window closed.

Re:Splash screens == sloth by openbear on Monday February 20, 2012 @01:09PM (#3613222)
>> Other stuff, like Preview, I don't use often enough to care about the load time, and I would probably configure it to exit when the last window closed.

Under Lion, that is (sort of) what Preview and TextExit do. When you close all open documents in Preview and then switch away from the app, the app will terminate.

Re:Splash screens == sloth by tikhonj on Monday February 20, 2012 @02:53PM (#3613615)
For Emacs, you should consider using Emacsclient and server. That way it's always on in the background, takes a fraction of a second to open a new window and shares state between all the different windows. Additionally, it lets you configure programs that use an external editor, like Git, to just open a new buffer in your current Emacs session, which is very convenient.
Re:Splash screens == sloth by why-el on Monday February 20, 2012 @11:26AM (#3612829)
+1. I find that extremely annoying. Some times I reopen a window of preview let's say just to close the whole program.
Re:Splash screens == sloth by msbarnett on Monday February 20, 2012 @01:59PM (#3613396)
Why not just switch to it and quit it without opening a new Window?

That's the whole paradigm. Windows belong to applications, but applications aren't windows. That's one reason the menu bar is divorced from any window (along with Fitt's law): so that you can interact with an app even when it currently has no windows open.

Re:Splash screens == sloth by pavel_lishin on Monday February 20, 2012 @01:13PM (#3613241)
> Some times I reopen a window of preview let's say just to close the whole program.

I do not understand what you are saying. Can you elaborate?

Re:Splash screens == sloth by why-el on Monday February 20, 2012 @08:47PM (#3614826)
Here is a scenario, and my mac is a month old, so maybe I am borrowing heavily from Ubuntu and MS experiences. When I am reading two pdfs, and then close one, it makes sense for the preview menu to stay on because I am reading the second pdf, but when I close the second, what reason is there for preview menu to stay up?

Edit: As to my original comment, when I switch to another app, preview stays open, but up to now I don't know how to close it because I can't get the menu to appear without a pdf or something using it, that's why I reopen a document, forcing the menu to show up, then close the app.

Re:Splash screens == sloth by pavel_lishin on Tuesday February 21, 2012 @02:34PM (#3617734)
There's lots of reasons for the menu to stay open; the simplest example is clicking File, then Open, to open a new file.

As far as the menu disappearing when you close both documents, that's confusing and directly contradicts what you typed earlier. I can open Preview.app, and it'll just show me the menu. I can close it by alt-tabbing to it and hitting Cmd-Q - no windows required.

Re:Splash screens == sloth by chc on Monday February 20, 2012 @12:55PM (#3613170)
You know you could just close it from the Dock or application switcher, right?
Re:Splash screens == sloth by kylebrown on Monday February 20, 2012 @06:03PM (#3614350)
Yes but that requires a click-and-hold, causing the whole dock to resize for the pop-up menu, which is quite slow on my 32-bit MBP maxed out at 2GB RAM. I find it quicker to just click the Preview icon (causing a new window to open as the focus switches), and command+q.
Re:Splash screens == sloth by msbarnett on Monday February 20, 2012 @07:02PM (#3614502)
You might want to try command-tabbing and quitting.

Basically with command held down the entire time, hit tab until Preview is framed, and instead of releasing command (which would pull Preview to the foreground), hit Q, which will send Preview the command-q event and cause it to quit.

Re:Splash screens == sloth by masklinn on Monday February 20, 2012 @04:03PM (#3613915)
> Some times I reopen a window of preview let's say just to close the whole program.

You could just close it from the dock you know. Or switch to it and command-Q immediately.

In fact, I don't even understand how you'd go around to "reopening a window" of preview, preview will not open any window without a document in it, do you open a document just to close preview or something?

Re:Splash screens == sloth by daed on Monday February 20, 2012 @12:46PM (#3613128)
If you don't have any windows open in the app, doesn't Lion quit it for you?
Re:Splash screens == sloth by wmf on Monday February 20, 2012 @03:34PM (#3613781)
Only apps that are written that way.
Re:Splash screens == sloth by darxius on Monday February 20, 2012 @10:19AM (#3612623)
> If you have an SSD (like your iPhone), then swapping Photoshop back into main memory will also be much faster.

I think the point the author is trying to make is that it shouldn't be up to the consumer to spend more money to make their programs run faster. Software reform is what's needed and "just buy an ssd" is a very strong argument.

Re:Splash screens == sloth by CodeMage on Monday February 20, 2012 @10:29AM (#3612656)
Whenever you can run the same software on a variety of hardware with different specs and capabilities, it's always up to the consumer to spend more money to make that software run faster.

Having said that, I agree with the idea of making software less monolithic and making it start up as fast as possible, as long as it is possible. However, when I say that I want a program to start up fast, I mean that I want it to start being useful fast. Quite a few of author's ideas are not about bootstrapping gradually, they're about faking it. It's like going to a place that used to have a "closed for lunch" sign and discovering that it's now open, but populated by robots whose personality is an Eliza-like AI.

Re:Splash screens == sloth by darxius on Monday February 20, 2012 @10:36AM (#3612675)
I might have misstated. I mean that consumers shouldn't have to compensate for poorly written (in terms of efficiency and speed) software. Sure buying an SSD would increase the write speed, which is usually the bottleneck for a system, but the consumer can save a couple hundred bucks if the developing company focused on speed instead of bloat.

And I agreed about the "faking" issue. Just like how Windows will silently keep loading tons of services in the background after a reboot, but shows you a desktop and makes you think you are free to click and launch stuff.

Re:Splash screens == sloth by sciurus on Monday February 20, 2012 @01:53PM (#3613379)
It's probably the random read speed that matters for starting apps.
Re:Splash screens == sloth by tripzilch on Monday February 20, 2012 @02:43PM (#3613573)
> However, when I say that I want a program to start up fast, I mean that I want it to start being useful fast. Quite a few of author's ideas are not about bootstrapping gradually, they're about faking it.

But quite a few of those ideas are useful.

The only ones I thought were a bit out-there were the ones about "just processing it in the cloud" while the local copy is still loading. But other HNers are probably more qualified to judge how realistic this is.

What is a possibility, however, during loading a lot of time is spent on loading all sorts of modules, ones that might not even be used that session, and most definitely not in the first few minutes. Because what is the user going to do first? Most likely it'll be `File > Open ...` and browsing through the filesystem looking for whatever project they intend to open.

You don't need any plugins for that. And it's exactly the type of task that spends relatively a lot of time waiting for user input and not so much time computing or loading things. During this task the app can continue loading modules and plugins and the user doesn't have to wait because they're selecting a file.

You probably need to disable (most of) the instant preview in the file open dialog until it's done loading, but that's a minor trade-off.

Of course you're loading the modules necessary for opening files first (most recently used filetypes first). When that's done the dialog can start showing previews. If the user happens to have found and selected their file before it's done, then, only then they'll have to wait.

Now you're loading the file and it's showing on the screen, the user can browse the layers a bit and ponder where exactly they left off last time. A wonderful time to load the rest of the modules! Of course the features used in this project will be loaded first. If there's no text layers, we can put off loading font-rendering support in favour of other modules.

It's not all load-on-demand, but a lot of user tasks are not as processor- or data-intensive as you'd think, because the user is busy thinking and as long as the UI is responsive enough they're happy.

Re:Splash screens == sloth by saturdaysaint on Monday February 20, 2012 @10:00AM (#3612552)
He's talking about smartphone app behavior, not the OS. A lot of good apps (with notable exceptions like Facebook and Kindle) work to minimize the "splash" by throwing up a graphic that looks like the UI, even while the app is loading and the UI (briefly) isn't even responsive to user input. I like it - it definitely smooths the transition into using that app.
Re:Splash screens == sloth by jiggy2011 on Monday February 20, 2012 @10:04AM (#3612569)
You can probably do that with a simple smartphone app where the first screen is basically just a static menu.

However with (let's say) eclipse or photoshop , when the program loads the first thing it displays is either my code or a graphic I am working on.

How would it allow me to interact with that in any kind of useful way without actually loading the program?

Re:Splash screens == sloth by saturdaysaint on Monday February 20, 2012 @10:56AM (#3612737)
Good question - I understand that this is a lot harder for heavy professional apps, but I'm with the author in that I'd prefer a subtler transition. Maybe show me the rudiments of the interface (toolbars, menus, etc.) and a subtle progress bar for loading/opening the app and your last file.
Re:Splash screens == sloth by jiggy2011 on Monday February 20, 2012 @11:08AM (#3612776)
I'm not sure how that's any better than a splash screen in fact I think it could cause much confusion.

I created a web app recently that had to make an Ajax call but could not allow any user input until this action had completed as various parts of the UI would have to be refreshed with new information.

I had reports from users that they thought the app had crashed since it wasn't responding to their inputs for a few seconds. It turned out the best solution was to simply whiteout the entire page and show an animated egg timer until the action had completed.

It's only really heavy professional apps that take much time to start anyway.

Re:Splash screens == sloth by Maro on Monday February 20, 2012 @10:04AM (#3612570)
iOS apps that I have that use splash screens:

Facebook, Linkedin, Flickr, IMDB, Dropbox, Angry Birds, Skype, iGo, Quotes, PCalc Lite...

Re:Splash screens == sloth by DrJokepu on Monday February 20, 2012 @10:17AM (#3612614)
This practice actually goes against the recommendation of iOS Human Interface Guidelines, although it doesn't seem like Apple actually enforces it:

  Display a launch image that closely resembles the first screen
  of the application. This practice decreases the
  perceived launch time of your application.

  Avoid displaying an About window or a splash screen.
  In general, try to avoid providing any type of
  startup experience that prevents people from using
  your application immediately.
Re:Splash screens == sloth by MatthewPhillips on Monday February 20, 2012 @10:22AM (#3612631)
That's a bit surprising to me. I haven't noticed this (not much of an app person), do many apps use the recommended technique? Personally I would find a splash screen that looks like the first screen to be confusing.
Re:Splash screens == sloth by ben1040 on Monday February 20, 2012 @10:35AM (#3612672)
Plenty do. The idea with that guideline is that it resembles the first screen the user sees, but in a "vague" manner - that is, maybe it just has the title bar and empty table view with no data filled in.

The idea is to give the user the impression the app has already started instantaneously, and you're just waiting for data to roll in to populate the UI.

Re:Splash screens == sloth by Turing_Machine on Monday February 20, 2012 @04:21PM (#3613988)
Yeah, I'm using it in the project I've got in development right now -- actually sort of a hybrid approach. It's a grayed-out version of the main UI, with a "Loading..." message overlaid. I think that's a pretty common approach (graying it out, with or without an explicit message).

The app needs to load something close to 200 fonts (it's a design-oriented app). If they're not all present, the font choice list won't render properly. Lazy-loading isn't really an option -- otherwise the user will be sitting there watching the UI slooowwwlly render each font choice, one by one, while he waits to do something with them. Better to take the hit at startup, IMO, rather than making the user pause while he's in the middle of creating something.

Re:Splash screens == sloth by DrJokepu on Monday February 20, 2012 @10:33AM (#3612666)
All Apple apps (inbuilt or downloadable) follow this guideline. Amongst the non-Apple apps that follow it are Reeder, WhatsApp, Twitter, Sykpe (sort of), AIM, Shazaam, Instapaper and so on.
Re:Splash screens == sloth by cageface on Tuesday February 21, 2012 @12:54AM (#3615379)
Adobe stuff is bloatware and sucks.

No, it's just vastly more complicated than most of the cut-down alternatives because it has to meet the needs of pro designers. Maybe there's some accumulated cruft there but I can guarantee you that Pixelmator, for example, would be similarly large if it had to support all the same use cases.

Re:Splash screens == sloth by systemtrigger on Tuesday February 21, 2012 @01:40AM (#3615486)
Yes though I suspect Photoshop's load time could be significantly reduced by limiting the features available at load time. If the method code for the 223rd most popular effect is loaded into memory prior to the user being able to do anything, Adobe is doing it wrong.
Re:Splash screens == sloth by cageface on Tuesday February 21, 2012 @02:39AM (#3615595)
Maybe so, but that kind of dependent loading might also significantly complicate the code. I have no idea how Photoshop actually handles this but it's about as close as software gets to magic already so I'm disinclined to accuse the developers of incompetence or sloth.
Re:Splash screens == sloth by jiggy2011 on Tuesday February 21, 2012 @05:05AM (#3615931)
Yes, part of the problem that Photoshop has is that it is seen as the "go-to" tool for doing any kind of graphics work at all.

Many people install pirate Photoshop to resize and put a few filters on their photos and complain that is it too slow and complicated when really they could have achieved the same result from either a freeware program or a significantly cheaper commercial one.