Sometimes your app just stops working because of some typo in your code
I don't know of any programming language that will auto-correct typos for you.
or the spaghetti code becomes just too unreadable.
If you don't write spaghetti code, you won't have a problem
PHP just doesn't seem exciting for me anymore. There doesn't seem to be anything exciting happening.
PHP isn't some 0.6-pre-alpha release software that douchebag developers use for production apps and get excited about when the core API changes every 3 weeks.
not much has been happening with the language and nothing interesting as far as apps or frameworks.
so you, as a developer, are complaining that no interesting apps are being developed in a specific language..?
Since I'm not a sysadmin, I prefer to pay extra to have my code managed by someone.
Sysadmin's don't manage code. You are a developer, you should be managing your own code.
Interfaces and reflection are awesome.
both of which PHP has.
Go helps me write cleaner and more maintainable code
I doubt it. You claimed that your code "becomes" spaghetti. Which implies that it starts out "clean and maintainable". I'll wait with baited breath for how long it takes your new code to also "become" shit.
Thanks you for writing this, I'm on my tablet so it would have been difficult. My thoughts EXACTLY!!! In fact this seems like Google trying to take advantage of PHP getting some bad PR recently and pointing people to use Go and inadvertently, Apps Engine.
>I don't know of any programming language that will auto-correct typos for you.
I know of many compilers that will point them out to you, and IDEs that will offer to auto-correct them (Eclipse, XCode and Visual Studio for example).
>If you don't write spaghetti code, you won't have a problem
Yes. And if you don't make any memory allocation errors you don't need a GC. Hell, if you don't make any errors period, you can just program in hex, building the executable code directly and skip assembly.
The thing is, different languages have different inherent characteristics (syntax, features) and different cultures (pertaining to libs, common practices, frameworks, etc), so one can tend to create more spaghetti code than the other, the programmer being equal.
"The thing is, different languages have different inherent characteristics (syntax, features) and different cultures (pertaining to libs, common practices, frameworks, etc), so one can tend to create more spaghetti code than the other, the programmer being equal."
That's simply not true. If you are organized, you will use whatever structures the language you are using provides to you (classes, modules, namespaces, etc.) to NOT write spaguetti code.
Spaguetti code it's not inherent to the language, it's inherent to the programmer.
