Hacker Newsnew | past | comments | ask | show | jobs | submit | joethompson's commentslogin

Still seems to be based on SproutCore. You can see the list of acknowledgements at the top of one of iWork's source files (https://beta.icloud.com/applications/iw/1ABeta108/editor/1AB...) to get a rough idea of what they're using.


Going to https://beta.icloud.com/?crazyAwesome does give you a similar (exaggerated) effect you can play around with using your cursor.


I'm curious; how did you know that?

Edit: Ah, of course it's in the source.


Yeah, just poking around curious as to how they were implementing the animation.


All the sandbox entitlement files are written in that scheme-like syntax, but it's limited to that in OS X as far as I've seen.


It seems to be an actual Lisp-1 dialect, not just Scheme-like syntax. In (Lion's version of) application.sb, there are a whole bunch of lambdas and letrecs flying around. They even define a macro.


It's specifically TinyScheme, with one every-so-small modification to the parser.

This PDF goes into it in some detail: http://securityevaluators.com/files/papers/apple-sandbox.pdf


Interesting, I never really dug too deep into it, aside from making a couple of changes and standard entitlement stuff for applications. application.sb looks like a complete nightmare to maintain.


> For example, what is so bad about this? http://skeu.it/image/24908403424

Putting in a ruled notebook texture and not lining up the text makes it look a little silly.


Or, if you have Homebrew (http://mxcl.github.com/homebrew/) installed:

  brew install tree


Amazingly (and the comments on his blog also seem to jump on this), he does acknowledge that you can do it with a package manager. There's advantages to learning how to build something like this from source.


Only in this case the learning effect isn't that great, because he doesn't explain the (to me) most confusing part: Why is the edit of the make file necessary? Isn't make responsible for choosing the right configuration settings for the current environment?


No. The usual three step installation from source is

1. configure

2. make

3. sudo make install

Note the absence of 1, which would usually perform these kinds of things (checking for prerequisites, for example).


True, learning how to build things from source yourself is definitely useful, I probably wouldn't be using Homebrew if I wasn't comfortable with that first. It's definitely advantageous to be able to organise/upgrade everything via it though.


It should be noted that PPTP does have some serious vulnerabilities (http://en.wikipedia.org/wiki/Point-to-Point_Tunneling_Protoc...) and should probably be avoided if security is your primary concern.


True but it's much easier to set up on server side as well as client side. I mainly use VPN to get around firewall of China so security isn't really an issue for me.


Wouldn't getting around China's firewall mean that security is more, not less, important? I know that if I was in a country where the government could imprison me for what I read or write, I'd make double-certain my security is up to par.


Yeah, unfortunately the others are a bigger pain, main reason why I use PPTP myself.


In particular, note that MS-CHAPv2 with PPTP only provide 56-bit security.


Best/most secure option for tunnelling traffic through to your VPS? SSH is definitely secure enough for that, provided you have a strong password or even better key-based authentication.

To make something like that more user friendly though you could just install VPN software like OpenVPN on your VPS. This also ensures things like DNS queries are sent over the VPN so they can't be intercepted on their way to the server.

Of course this assumes you trust your VPS provider, at least more than your ISP.


They are as noted prototype devices – with no announced release date – so it's completely in the realm of possibility that the camera simply isn't ready yet. Of course that doesn't excuse the misleading video and pictures Nokia used to advertise it.


The one actually marked "taken on a prototype" looks legit - tonnes of ISO noise.


The comparisons do make you wonder if they fiddled with the lighting artificially though, some of the differences are surprisingly drastic.


I doubt it. The camera seems to have HDRI. That, a looong exposure time, and a tripod can do amazing things.

Plus, it's compared to a photo they took with "a competitor's phone". Even I can take an amazingly crap photo with my camera-phone, it's not hard.


I was actually wondering about this, maybe you can enlighten us. Could they not have used external ligthing for the Nokia shot, and none for the competitor shot? How do we know they used the same lighting conditions?

Not trying to feed the anti-Nokia, I've always been curious of these types of things.


Ah, yeah I guess HDR would do it, slanted comparison nonetheless.


Not using all the available new semantic markup is a little different than having a site that doesn't rely on Flash to serve audio.


Do you mean 2ch/2channel instead of 2chan/Futaba? They have similar names but are completely different sites.


Yeah, I'm aware. The problem stems from the fact that you can't type the unambiguous name "ni-channeru" without looking like an insufferable dork/weeaboo. 2ch and 2chan (.net) are the domain names of "ni-channeru" and Futaba Channel, respectively, but it's obviously very confusing to refer to them by their domains. Therefore, in English discussion, we tend to say 2chan or 2channel when we mean "ni-channeru", and Futaba when we mean Futaba Channel.


I've never had a problem with the distinction between 2ch and 2chan.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: