boucher

60 ms·

601.
by boucher 17y ago
Not a particularly good source, but I've heard this several times over the years. The iPod was developed in six months: http://www.ilounge.com/index.php/news/comments/apple-more-th...
602.
by boucher 17y ago
Actually, they do have this capability, but they haven't used it.
603.
by boucher 17y ago
No, you don't. A lot of people think that this would be a great win for any JavaScript library, but I guarantee that every single library author would disagree. The last thing we want to do is give browser vendors more control over any part
604.
by boucher 17y ago
This is actually pretty neat. I'd much prefer it to what jQuery source looks like today. And I'd argue there's no reason not to want to optimize the syntax like this.
605.
by boucher 17y ago
In fact, browsers were that fast in 2006, when this was written. Not fast enough to do some things that we're doing today, but more than fast enough to parse a simple language like this.
606.
by boucher 17y ago
For what it's worth, all of us have programmed 68k assembly.
607.
by boucher 17y ago
Unlikely. 30% is already pretty high, probably more than any startup would have been able to credibly command. It's another instance of the lack of choice allowing Apple to dictate whatever terms they like, however unfavorable they may be.
608.
by boucher 17y ago
I don't think it's a protection thing, and loss-leader isn't entirely fair. The App Store makes money, there's no question about that. It's just that the profits from the hardware make the App Store money irrelevant. Apple almost certainly
609.
by boucher 17y ago
Thanks for the feedback. Accurate assessment. This is definitely still too early to use for most people. We're not really trying to push the beta, we're just looking for dedicated users to help give us great feedback.
610.
by boucher 17y ago
Linux support should come with windows support, because of the way we're doing it.
611.
by boucher 17y ago
If you feel it's inappropriate, please don't pay. We feel that we're providing something that a certain group of people want at a very reasonable price. If you don't think it's a fair trade, we'd rather have you wait until the final version
612.
by boucher 17y ago
It's impossible for something that has no price to be overpriced. But thanks for the feedback.
613.
by boucher 17y ago
Well, it's as unlikely to cost $1000 as it is to cost $20. That being said, Atlas is completely optional. Everything built with Cappuccino to date did NOT use Atlas. And this will always be a viable option. This beta is not intended to get
614.
by boucher 17y ago
Yeah, Atlas 1.0 is a downloadable app with a one time charge. Eventually we will have an online component.
615.
by boucher 17y ago
I can tell you that it will be a lot more than $20, and it will be less $1000. Big range, I know.
616.
by boucher 17y ago
We're just hosted on heroku. If you'd like more info, there are a few videos available on http://280atlas.com Don't worry though, this is a beta, and it's meant for people who already know what Atlas is and already want it.
617.
by boucher 17y ago
We haven't set a final price yet. We're hoping to use our beta members as a sounding board for determining the right price point. It's worth noting that all of the stuff Atlas builds is still usable without Atlas, though there will be no wa
618.
by boucher 17y ago
Agreed. But it's live now. Sorry for making you wait. http://news.ycombinator.com/item?id=943616
619.
by boucher 17y ago
ross at 280north dot com
620.
by boucher 17y ago
That's fine. We're not looking to convince anyone. We are recognizing that we have something useful now, and that there are people who are willing to pay for it now. We are providing it to those people, and making it known that we believe t
621.
by boucher 17y ago
It's $20 actually. But you're only paying for a development tool. The language, the framework, the runtime -- everything else is open source.
622.
by boucher 17y ago
On point number 2, the compiler ships with the open source project. It's written in Javascript. It runs in the browser, or on the command line. We are planning on getting a new compiler in 2010, and it will still do all those things. It wil
623.
C gibberish to English translator(ridiculousfish.com)
1 points by boucher 17y ago|0 comments
624.
by boucher 17y ago
Some code is so bad that it's hard to have sympathy for the people who wrote it when stuff breaks. Overriding undefined is one of those things. If we're getting that nitpicky, having an isDef method at all is adding an unnecessary function
625.
by boucher 17y ago
I'd say it isn't. As you said, most of the problems are minor. Some of the performance assumptions are false. Very little of this seems to be of any consequence.
626.
by boucher 17y ago
Interesting idea. It's worth mentioning that one file in Cappuccino means one file per bundle, plus the index.html file and Objective-J.js. A typical app has the Cappuccino bundle, and one bundle for the app code, but using an external fram
627.
by boucher 17y ago
The default jakefile we will ship just automatically bundles any image resource in the project. ImageBundle sounds pretty solid. I guess they are inferring the orientation of an image somehow? I'd like to see how that works. If you use an i
628.
by boucher 17y ago
I believe the GWT thing requires you to specifically create a bundle subclass, and put all the image files in that bundle (as methods with or without annotations). Please correct me if I'm wrong.
629.
by boucher 17y ago
Typical cappuccino apps are cached all at once with far future expires. Simply changing the URL (in an automated way) is enough to break the cache for new versions. The caching tradeoff is there for any spriting technique, it will always be
630.
by boucher 17y ago
We turn this feature off for images over 32KB.

More ›