escoz

Google is beta testing a new version of google analytics specially made for apps, it's great. Unfortunately they're making it available to a small group of users for now, afaik.

I liked it, actually. Here's the two I made for my apps: http://www.smore.com/s06g and http://smore.com/r2w1

Now if only they allowed me to pay a few bucks a month to remove all the smore links on top, i would probably use it as the main landing page for my sites.

I've been doing this for a long time now, probably for the 8-10 months, and I can safely say its awesome. Xamarin is awesome.

I'm just walking into CouchDB, specially with the couchsync mobile part of it, and about to submit my first iOS app with CouchMobile to the AppStore. It's good to read these kinds of informed posts and comments. Thanks guys.

completely agree with you.

Mistake #1: read and agree with any article you see on hackernews.

Yes, I use an asus router for my wireless, with Tomato running, and that includes a DLNA server. I added a 2Tb harddrive connected via USB to the router, so my videos stay online all the time. Pretty awesome.

I'm probably the only one, but I love the GoogleTV. Had it since early this year and use it absolutely every single day. It's always on, so it's always so easy to look up something on youtube, show somebody your pictures, watch a video from my NAS, look up a recipe or a place to visit on the web, etc.

At first I thought the full keyboard was a bit too much, but now I don't mind it at all, just makes it easier to find stuff online. I love it, can't wait for the update.

The fact that it's always on is the killer for me. One keypress and you're searching for whatever you want. Whenever people visit me and we're talking about something, I just press the search key and we can all search together for it, much more social then pulling up a phone and looking down. I love it, cant wait for the update.

This list was originally created by Apple and presented at their first world developer tour after they released the iPhone 1. I still have the exact same list saved on my notes from that presentation. I've seen a few other Apple presentations repeat the same items.

Congrats to the guy for getting the prize, but that's no excuse to just rip apple off and not mention it.

.NET, like most enterprises, afaik.

That's your experience, and highly subjective. And yes, I deploy code to dozens of enterprise servers for a global company. And that company is looking into Rails, not PHP.

I was not talking about popularity, I was talking about mindshare, two very different things. If you're talking about popularity, Java, C and C++ are more popular than php, but I don't see you pointing them as viable solutions. tiobe.com

Rails doesn't really need that much hardware, that's a very common misconception. PHP is not the fastest thing in the world either, unless you go with a compilation cache server. Rails can be easily perform well under single machines. I have VMs with 512Mb of ram handling thousands of users per day with Rails with no problem.

There are problems with ORM, but there are much larger problems with PHP+SQL. Most of the problems created by ORMs are easy to workaround, though (to the point of having to write SQL sometimes), while problems created by SQL only are not (like n+1).

Don't want to be inflamatory, but:

PHP has already been replaced by Ruby/Rails as the good thing that should be used for new projects. Only PHP developers don't see that.

You lost me when you tried to argue that ORMs are not useful. Its easy to see why PHP developers think that, though.

XCode, on the other hand looks great. But it's also a pretty horrible environment to work on. Pretty much zero helping writing the code, unlike any other IDE out there.

Looks are deceptive.

Omg.. this is getting worse.

SQL is a DSL to deal with sets of data. Unless the application you're writing is a database management app, you're pretty much doing it really wrong, I'm sorry to tell you that.

cool, we agree on that.

Selling at a loss works when every game costs 50 dollars.. for 1/2 dollar apps, it's a much harder ladder.

I hope that's the case, though, bcse I still love Palm, and would love to see WebOS succeed.

"beautiful" sql is subjective. What does it mean? SQL that looks pretty to the eye (with proper indentation)? Or is it SQL that can run on dozens of different database servers with no modifications? Or is it SQL that can be automatically generated so you don't have to spend any time thinking about it but that runs 5% slower than something you spent 1 hour on?

I would probably go with the two last options.

Just because you have an example of a probably poorly designed, over-engineered system that could be completely replaced with some hand written SQL code, doesn't mean that is the best solution for everything. Come back when you have an example of a system running on top of 500 tables, doing read-writes in a big iron server, communicating with dozens of other servers, that uses distributed caching to improve performance, and that you can explain how you can replace an ORM with SQL.

I agree with what you said about developers understanding what does on under the curtains, but regarding the NewRelic statement, I couldn't disagree more with this.

Spending time early on in the project on things that don't matter and that don't really impact the system, like the example given in the post, is exactly the kind of thing that ends up creating projects that are expensive to maintain and just bad.

Focusing on solving large performance bottlenecks, that can easily improve things 1000 times more than fixing that simple example is a much better use of your time, and is what newRelic shows you.

What? So you think Java is not expressive enough for business logic, and you think it's better to move that logic to PLSQL? Seriously?

Java may not be the best language for some things, and that's why you use DSLs, but moving that to the place you store the data is probably the worst thing you can do 99% of the time.

the big problem is that it makes refactoring and changing logic much harder, as you now two different places to maintain business logic.

In my experience, most problems that DBAs would like to use SPs for can be easily solved by refactoring/merging SQL calls and proper caching of objects during a request or session, two things that an ORM really help you with.

You always hear this from somebody who is new to ORMs, spends 3 months working on a project, and then is amazed because he doesn't like one thing or another in the file.

It'll be funny when he discovers that with just a few other lines of code he can not only fix that issue, but also completely change how data is stored in the database, use 1st and 2nd level caching for the objects, and be able to easily refactor all that stuff when the business logic changes.

By the way, I seriously doubt that query is the cause of performance problems in his system.

I agreed with you until the point that you said to replace things with stored procedures and in-memory tables.

Having the two different contexts for logic, code and SPs makes things a thousand times harder to debug and maintain, making the cost of anything skyrocket.

ORMs are indeed awesome, but the solution for problems like this is not to take ORM out of the way, is to work with it to make it work better.

Just to update, I committed this afternoon the license, everything is Apache 2.0. Thanks for reminding me of it.

Right now, all you have to do is modify your root element as you wish, and then call the reloadData on the tableView. That will show the new table automatically, although it won't show a nice animation that somebody would expect. Adding this functionality is in my todo list, and should be fairly simple to do.

What you're saying though is not really related to adding/removing cells. I'm not saying you shouldn't create UIViewControllers for specific things, actually its quite the oposite, I think you should have as many controllers as possible, so that they're really small. Funny your example is a login screen, bcse that's the example in my samples on the project. Take a look at the code: it's very simple, and it mostly has to do with the actions that will happen as a result of the form, instead of cell creation: https://github.com/escoz/QuickDialog/blob/master/sample/Logi...

I see this as a much cleaner approach to do exactly the same thing, with the benefit that a lot of the code can be reusable. As a developer, you can spend a lot less time implementing plumbing code to get the cells and fields displayed, and instead focus on how they're used.

You're right.. but from previous experience, apple doesn't usually do a lot more than 5 or so beta builds.

Still, its not like I'm doing more work anyway, going with ARC saved time on development. If Apple ends up never releasing 4.2, I would just had to "finish" the job.

Personally, I thing XCode sucks, either 3x or 4x. It's a really bad environment, I can't see how people use it or like it.

Have you tried AppCode, from JetBrains? Its still in beta, but its magnificent.