For those of you who are not on the FileMaker Technical Network (and if you aren't why aren't you?!?), a little background: A few weeks ago a developer posted to the forums saying that he was frustrated with FileMaker to the point that he was giving up on it. I've probably read his post a half dozen times, and read every reply to it. I resisted the urge to reply immediately, and after thinking about it, I finally posted this reply this evening:
I've been thinking about this "Bye Bye FileMaker" thread for a few days now - and from the responses I've seen, a lot of others have been, too. The thread seems to have taken on a life of its own.
Something about it struck a chord with me. Maybe it's because I've been where Daniel (the original poster) seems to be - frustrated with FileMaker, and ready to throw in the towel. In fact, I've been there several times in the 20 years that I've been using FileMaker. (I've been using it since FileMaker version 2.)
Like many of you, when I've reached that point of frustration, I've taken time to research some of the alternatives to FileMaker. I've been down the Access path before. (Access is... Well, it's Microsoft. It's Windows. It's not me. I'm a Mac guy, and happy and proud to be able to say that.) I've experimented with 4D and been intrigued by Servoy (both of which are too obscure for me). And I have a very heavy SQL and Web development background, having built my fair share of browser-based solutions using combinations of PHP, ColdFusion, ASP along with SQL Server, MySQL, and Oracle. The browser-based solutions that I've created have been very successful, but I'd be lying if I said I enjoyed working on those projects. (Things like the DOM and CSS and JQuery, and how they work sometimes and not others, drive me insane!)
So here's what I've found: Not one of those technologies is a silver bullet. Each one has its strengths and weaknesses, is good for certain things but not for others. And the same can be said for FileMaker.
And that is what I think we tend to forget. We get so caught up in how cool FileMaker is that we forget to take the time to ask if it is the right tool for the problem that we need to solve. That's especially true when prospective clients come along wanting "help with FileMaker." They've seen how amazing FileMaker is, and have already made the assumption that FileMaker is the right technology for their situation - so it's all too easy to make that assumption with them. There's a quote attributed to Abraham Maslow that reads, "If you only have a hammer, you tend to see every problem as a nail."
My most recent episode of being frustrated with FileMaker started towards the end of June. I'm not exactly sure what brought this one on, but if I had to guess, I'd say it was months of burnout, a severe lack of sleep, and the insane heat that we've had here in Virginia this summer. But it couldn't have happened at a better time, because a few weeks into it I found myself at DevCon, where I saw:
- New techniques that are now possible using the new features in FileMaker 12.
- The talent and knowledge of the FileMaker Inc development team that has helped to make the FileMaker 12 product line the best version of FileMaker yet - and some of the amazing things that they are working on now that will be coming in the future.
- A general sense of excitement and enthusiasm from the hundreds of other FileMaker developers that attended.
- A community that I feel good being a part of - one where people share ideas, help each other, and genuinely care.
- A business (FileMaker Inc) being run by some extremely talented people that is thriving and making all the right moves, even in this insane economic climate.
- And much, much more.
But of all the things that I saw at DevCon, it was the seeing solutions that other developers have created that really helped me to get perspective (or, as my mom would say, helped me to "get my head screwed on straight"). Their solutions were inspiring and enlightening. They were diverse - everything from a database being used by a company that works on ponds to one being used to manage motorcycle races, and everything in between. But what those solutions had in common - and what I think made them successful - were that in every case FileMaker was the right tool for the job. And that is the biggest takeaway for me this year, making DevCon worth every penny.
And so, once again, I've come back to FileMaker. It's comfortable. It's fast. It's powerful. It's flexible. It's forgiving. It's stable. It runs on iPhones and iPads. It freakin' rocks!
I'm not sure if Daniel will see this post or not - it sure sounded like it was his last post here. But if he does see it, I hope he'll read it and take this advice: Think about what FileMaker is good for, and what it isn't. Use it where it makes sense, and don't use it where it doesn't. That will very likely save you from having to use those "endless workarounds" and from the "endless problems" that you've been experiencing.
As far as the "ignorance from filemaker to acknowledge any problems" and "persistence from filemaker not to address any known bugs and problems," I can assure you - and I think the hundreds of other developers that were at DevCon this year can, too - that FileMaker is listening to us. It's in their best interest to continue to make the platform the best tool that it can be, and they are working hard to do just that.