wiki filemaker pro windows compatability

It’s presentation of UI without having to mess with data binding is second to none. It’s lack of fundamental features like patern matching (regex) is almost unforgiveable. It’s handling of data structures like arrays is abysmal.

It’s what you discover and what you’ve outgrown.Īs a technology, FileMaker has definite pluses and minuses. Perspective of what YOU know in relatation to what’s known by those who you know. It’s an infatuation with CMS systems then security issues remind us that static web sites suit 80% of the use cases.Īll of these variances are coming from perspective. Then HHVM comes along and makes PHP cool again - wait, JavaScript is still better. It’s PHP/Symfony then JavaScript and Node. This year it’s Ruby/Rails, the next it’s Python/Django.

Outside of the small world/community of FileMaker developers it’s a lot like “Eggs are good for you.” no “Eggs are bad for you”, ok “Eggs are good for you”. Like ALL software, there will be an ebb and flow to what’s popular and what’s not. Here’s my (somewhat) quick little take on Tim’s post. This post is a response to my friend Tim Dietrich’s post about “Goodbye, FileMaker” Given the recent discussions I thought this article from 2015 quite interesting, especially considering the interest and influx of FileMaker developers following Tim Dietrich’s very public move:

Wiki filemaker pro windows compatability