edb

Of course. We got lucky this time, it was just a robot, which is easy to fend off with robots.txt. But what if it was a user who did the same thing?

The issue though, is that we had thought that the address wasn't exposed. We're still baffled as to how the address got exposed to google, but we're assuming one of our employees must have done it somehow.

That made me thing though... can you trust your users not to expose their private URL addresses? Aren't you trusting it to them, and if you have a user without internet experience signing up, what happens if he submits his private URL to google and makes it public? Doesn't that create a security hole?

I think this is an unfair blanket statement. I think that every APPLICATION, forget framework-dependent or not, will have its bottlenecks.

I see so many size comparisons about which framework is faster than the other... People need to realize that a framework is nothing more than an application library. A smart developper will know how to use it to his/her advantage and will know how to identify bottlenecks and optimize them.

The point is to get your ideas into the wild fast. All you need for that is a development environment YOU'RE comfortable in, be it RoR, CakePHP, Code Igniter, Zend, whatever..

Once your idea is in the wild and generating traffic that breaks all your best optimization tricks, I'd hope that you have enough revenue or interest generated to then start rethinking the framework that it was built upon.

I think if you're rewriting frameworks and tools like wordpress from the get-go, you're missing the point.

I never understood why nobody has built a documentation webapp where you just enter the SVN/CVS/GIT of a project and the webapp checks out the code onto the server's backend at a fixed internval then generates documentation from a standardized commenting layout, kind of like doxygen but more social.

It could be neat, you could even have the app merge user submitted comments or changes to documentation (submitted via the web-app) back into the code documentation in the repository. Maybe set a convention where you create a DocApp folder for pages, all synced with the online webapp.

I hope this is what Nodata is working towards.

excellent. So no, don't make what I say.

This is neat. I always thought a hosted reddit/HN solution would be a good startup idea. Imagine a site where I could start my own reddit/HN type space with a unique url. I could then control who comes in (be it co-workers or friends) and have a place where we could all privately share links and start discussions. Great for companies, project groups, families, friends, etc...

I know I won't have time to build this, but I think somebody should.

To my credit, I also tend to recognize that I fall into the trap of learning new things because I like to learn new things and never use them. This is the same trap that catches you always starting projects and never finishing them.

Learning a new language to me would be just that; starting a NEW project. Instead, I'd like to take something I know well and learn to do even more with it. That to me would be an educational effort well spent.

In that vein I feel that working with other devs who code at my level on a collaborative goal would be something I have yet to experience and that I think I could learn alot from.

The problem is that CakePHP is so easily deployable, so I need it for client work. (Alot of my clients won't switch hosts, so cakePHP has been a key tool for me).

I'm also not interested in learning yet ANOTHER language/framework now. I'd like to work on something in a larger group that will overlap at least a little with my current work.

I guess it's because I'm still working that I feel that there's no time for that. Maybe when I free myself up completely I'll be able to sacrifice a bit of time towards learning rails.

Thanks for the advice.

This is the thing.. My experience dictates that I'll pick up RoR pretty quickly, but what really makes or breaks a framework is what happens when you try to do things outside of basic CRUD administrative interface stuff. I find it takes at least a couple of months of serious coding before you REALLY get to know what a framework's about.

... or is that just because cakePHP is badly documented? :)