allertonm

15 ms·

91.
by allertonm 16y ago
+1: I'm doing almost exactly this with an old Macbook, with a good quality outboard DAC to drive my amp/speakers. So I appear to be target market for this product...
92.
by allertonm 16y ago
In addition, Shimano has an 11-speed alfine hub coming that's getting close to Rohloff's versatility at a fraction of the price.
93.
by allertonm 16y ago
Yielding inside a callback isn't a problem. I was actually thinking of the other yield you would need, the equivalent of suspending the continuation - but I later realize that this is no harder than the continuation case. So I was just bein
94.
by allertonm 16y ago
Perhaps I'm being a bit dense, but it's hard to see how one could take an existing asynchronous API and adapt it to use co-routines, since the point where you'd ideally want to "yield" is behind the API - and it may not be desirable or even
95.
by allertonm 16y ago
Good piece - having built a big Rails application, I love the speed of development but your comments about scaling totally resonate. Actually it was even worse in my case due to us using jruby (add VM overhead to the mix.) RAM is often the
96.
by allertonm 16y ago
I pointed to that image only in relation to the EXIF metadata, since the original article suggested that this problem was the "straw that broke the camel's back" - i.e even if you were prepared to live with the 2-application workflow, even
97.
by allertonm 16y ago
Well, the point is that the photos didn't originally have geotag info, that came from the iPad - but the resulting photos have that and the original EXIF metadata.
98.
by allertonm 16y ago
Author of Windows app suggests customers choose a Windows netbook over an iPad - film at 11. FWIW, I don't buy the claim that it's impossible for applications to get hold of photo metadata - I happen to know someone who is working on an iPa
99.
by allertonm 16y ago
Same on Safari (4.0.5, Mac)
100.
by allertonm 16y ago
I'm sorry, but he's just not that into you.
101.
by allertonm 16y ago
Attacking CAP seems to be a recent theme - Stonebraker did this a few weeks back ( http://cacm.acm.org/blogs/blog-cacm/83396-errors-in-database... ) Abadi's take seemed more interesting to me since it isn't rubbishing CAP as such, but notin
102.
Problems with CAP, and Yahoo’s little known NoSQL system(dbmsmusings.blogspot.com)
52 points by allertonm 16y ago|9 comments
103.
by allertonm 16y ago
Unlike an iPhone, the iPad is not designed to be carried in a pants pocket.
104.
by allertonm 17y ago
We'll have to see how this pans out. The language in 3.3.1 puts Javascript and the Cs into two separate categories with regard to access to "the documented APIs" and taken at face value would appear to rule out Phonegap. (and yes, I have
105.
by allertonm 17y ago
"providing in WebKit's javascript engine access to system services" Yes, it's almost as if it were some kind of "intermediary" or "translation layer".
106.
by allertonm 17y ago
I've seen it stated a few times that "EA uses Lua on the iPhone" - but my googling hasn't revealed any evidence to support this. Does anyone have a cite for this?
107.
by allertonm 17y ago
Firstly, that's a call to authority argument, so automatically suspect. Secondly you don't present any evidence that EA uses Lua on the iPhone or that it receives an exemption from Apple to do so.
108.
by allertonm 17y ago
I'm pretty certain that ActionScript is not an example to the contrary, and I'm fairly fond of it as a programming language. I'd go so far as to suggest that the majority of the non-Apple tools that people are proposing to use instead of Ob
109.
by allertonm 17y ago
Yes, just completely change the context from one where the code runs at the user's expense, to one where it runs at the developer's, and my comment sounds like nonsense. Aren't you the clever one.
110.
by allertonm 17y ago
If you are only able to make a profit by cutting corners on app development time, perhaps that means you aren't charging enough for your services. At least one benefit of this change is that it levels the playing field for developers such a
111.
by allertonm 17y ago
This post from a former QNX marketing VP appears to disagree with you: http://saunderslog.com/2010/04/09/rim-didnt-buy-qnx-for-its-... "QNX has long been looking for a partner with whom to enter the mobile space. For example, almost 10 y
112.
by allertonm 17y ago
FWIW, despite being the author of a Clojure/Cocoa bridge, I was never under any illusion that this would ever be able to run on the iPhone. (See "Why is this a terrible idea?" at http://github.com/allertonm/Couverjure )
113.
by allertonm 17y ago
I find it hard to believe this is just about automotive. QNX makes a very well regarded embedded OS, people I know who've worked with it rave about it. So I can't help wondering if RIM has just bought their next-gen mobile OS, especially gi
114.
by allertonm 17y ago
Hmmm. I assume you're referring to VisualAge. It's a bit of a stretch to call that "the original version of Eclipse". A predecessor, yes - but the only thing the two have in common is that they were both IDEs.
115.
by allertonm 17y ago
Of course, the language that is now called Javascript 2 is not the same language that Yegge was referring to.
116.
by allertonm 17y ago
He's had a bit of a change of heart about Cloud Computing since 2003, eh? 2003: "But the thing I'm most interested in is software as a service. That idea that every customer who wants to do accounting on computers, or every customer who wan
117.
by allertonm 17y ago
Everywhere but Goldman, it appears.
118.
by allertonm 17y ago
This idea has been bounced around by a few people interested in getting Clojure onto the iPhone/iPad platform too, since the JVM is unlikely to ever be there. MacRuby suggests that it's not a complete pipedream, but the experience of the Un
119.
by allertonm 17y ago
>transparent unless you have a side-effect Only if you believe the side effect of using the CPU doesn't count.
120.
by allertonm 17y ago
This doesn't affect your point, since ObjC does still deal in raw memory addresses, but it has supported garbage-collection since Objective-C 2.0 (i.e since Leopard/10.5)

More ›