pswenson

Given that most code degrades into either wrapping checked exceptions into runtime exceptions or most methods having "throws Exception" declared...I think it's safe to say Checked Exceptions don't work well in the real world. There is a reason no other language created in computer history uses them.

exceptions usually happen because of one of two reasons: 1) bugs 2) system failures.

bugs you can't recover from, you need to fix them.

system failures can sometimes be recovered from, but often they need manual intervention. usually it's best to just report them and let someone fix the problem rather than spending a bunch of resources trying to code some way around the problem (which introduces more bugs).

there are situations where it might be appropriate to try to recover. If an HTTP call fails, no reason not to retry a few times. But if your DB is down - sorry you are F'ed. Alert it - make it visible.

why use Redis for sessions?

@josteink you have any stats that back up your assertion that iOS is headed "soon into sub 10% marketshare"?

I didn't think so.

Anyway, I think the market is convinced Apple can't grow earnings much any more. And the market is probably right. Law of large numbers has taken effect.

But this notion that iOS is getting crushed and is headed into oblivion is a product of the simplistic "winner take all" mentality. Just because it happened with Windows doesn't mean it happens with mobile - or anything else for that matter.

I've been pushing for trello over the much slower, less intuitive sprint.ly.

the main hangup is the lack of a daily digest report. anyone have a solution?

Not pedantic, just misunderstood. Yep IJ is awesome. I tried eclipse again a couple years ago and there is no contest

why would you be stuck on eclipse when working on java?

filepicker.io is cool. But your backend service wouldn't be needed if the image uploading & resizing straight to s3 could be done in the browser. Your product would simply be a javascript lib.

how do you do #2?

Coolest would be an ability to have 1) a great filepicker UI (drag target + multi file upload w/ progress bar) 2) resizing/thumbnails in the browser 3) no server side other than s3

guessing #2 isn't possible?

Most exceptions aren't recoverable. They are usually a result of bugs or system problems. This means 1) the bug needs to be fixed. 2) the system needs to be fixed (start up a DB service, clean disk-space, add memory, etc).

This is where java went wrong, java checked exceptions treats everything as recoverable when recovery is unlikely.

I mean, someone tries to login to a web site and the DB is down. What do you do? Or there is a bug that throws a null pointer exception. How do you recover from that?

I think the error code approach has the same effect as CheckedExceptions. People will tend to code to ignore the problems and not report them. Exceptions are great in that they bubble up to the top of the stack, so they are easy to report/alert on.

Didn't we try error codes back in the day? I think exceptions are brilliant. They let you write your error code in one place (at the top of the stack), instead of planning for every contingency at every level.

Once I discovered exceptions back in the 90s, life got a lot easier.

Of course Java ruined exceptions with the invention of the CheckedException, maybe this tainted the Go designers' thinking?

Not sure if they should kill JavaFX. But they should kill the browser plugin. No one uses java in the browser anymore and it's a giant security hole.

You didn't explain what's wrong with the JVM. Please do.

The JVM is very fast and ubiquitous. Targeting the JVM allows the language developers to focus on the language rather than re-inventing a runtime (which is a monster project)

no idea what you are getting at.

what's wrong with the terminal?

hit cmd-q to close an app.

no idea what you mean by insane window switching behavior.

you gave no examples of how Ubuntu/Fedora is better to rebut on UX. care to share some?