How have you found dealing with the Navigation/Router and passing props. From my experience it was a real pain, for example when you change route the props wouldn't update or other odd quirks.
I haven't had this issue, but I have had subtle bugs where I was ultimately the root cause. Debugging hasn't gotten better over time. Good old print statement proves extremely useful here.
Part of it is that PHP has evolved to address some very web-specific needs; in this process, developers of all skill levels have tacked on functionality which tends to give it more of a "thrown together" look which may be horrifying to developers who prefer languages that have been more carefully cultivated.
Part of it is a tribal, "Coke vs. Pepsi" kind of thing: the thing I am familiar with is good, what I am not familiar with is threatening and/or bad.
Part of it is because there are some downright terrible examples of PHP code out there. One of PHP's implementation strengths is a PR weakness: it is very easy for complete beginners to use it. It's like a zero-entry pool: anybody who wants to get into the pool can get into the pool. Some of those people shouldn't go into the deep end, but do so anyway.... and the byproduct of this can be horrifying and perhaps counterproductive for others.
As a PHP developer for 5+ years (with plenty of experience prior with ASP.NET and ColdFusion), I can attest that the language is a bit homely and doesn't posess a lot of cool features supported by other languages. But it works, it works well at what it was designed for, and continues to evolve (albeit slowly sometimes).
It's an adjustable wrench set that sometimes gets criticized because it doesn't include screwdrivers or hammers.
I might want to add that since PHP is so available (it really is) - it's easy to throw functionality together get it "working" and try selling it - the buyers of course getting disappointed and thus hating PHP.
And that hiring a PHP developer with "experience" doesn't really mean much, so a hiring person/firm that is not entirely specific with requirements will get really angry and disappointed with the results.
This can be avoided quite easily by not being a cheap SOB (There's no such thing as 800$/month Sr dedicated developer), choosing a developer with proper references and actually planning the project before starting to work on it.
1) PHP allows you to go wild and embed PHP inside HTML code. This causes your code to be unreadable and unstructured when it grows. Other languages just can't do it, so you're forced to use MVC, which is nicer by design.
2) As a language, it is not that advanced. It has a single namespace, and most of the functions used commonly in PHP are not object oriented. It also does not have advanced structures such as iterators, coroutines, etc.
3) There's $ signs everywhere.
1) the key word in this is ALLOWS.
My car ALLOWS me to drive it off a fucking bridge, but does that mean it’s the fault of the car if I choose to do that?
2) define advanced. I’ve seen Java web apps that needed stupidly complex getters and setters just to be able to handle a form post with a variable number of fields. How much of what PHP does out of the box, does a language like ruby or python support, and how much requires a framework like Rails or Django?
3) You are a fucking idiot. That sentence has just as much weight as your third point, possibly more so.
Very nice looking app. Although a feature I really think a lot of people need is a nice icon in the status bar. How else are we meant to know we have a message whilst glancing at our screens?
PHP is actually next on the list, but I can't say when it will be ready, but shouldn't take long. I think I have some ideas for another demo app in mind, I guess we have too see when I get the time to actually put it together. Thank you for your appreciation, we will not make you disappointed! :)
