21–30 of 71 posts
> PHP isn’t a great language, but it is a good language [...] it’s just as possible to write good, well-structured code in PHP as in most other languages That isn't what "good language" means.
Yes it is. You probably haven't written code in a bad language, but they exist. Most programmers are pretty lucky these days.
> PHP isn’t a great language, but it is a good language [...] it’s just as possible to write good, well-structured code in PHP as in most other languages That isn't what "good language" means.
Yes it is. You probably haven't written code in a bad language, but they exist. Most programmers are pretty lucky these days.
Not really true because HHVM has to run basic PHP before it can apply the Hack annotation. You can pull out the annotations and it's still PHP.
> PHP isn’t a great language, but it is a good language [...] it’s just as possible to write good, well-structured code in PHP as in most other languages That isn't what "good language" means.
So what is a great language? If it runs the largest active user app on the planet (FB), the most widely used CMSes (WP,Drupal,EE), message boards, MVPs, etc. Why continue the hate, then end the article on how you've chosen it as the greatest option to run some of your systems.
I'm not much of a PHP coder, so I tend to watch these flamewars from a distance on the sidelines. However, I've never really understood why people criticize or mock Facebook for pouring so many resources into PHP. For building cross-compilers, toolchains, and syntactic extensions on top of a language that is seen as a fundamentally weak foundation. I mean, I DO understand all of those criticisms. I just don't get how…
> PHP isn’t a great language, but it is a good language. So what is a great language? If it runs the largest active user app on the planet (FB), the most widely used CMSes (WP,Drupal,EE), message boards, MVPs, etc. Why continue the hate, then end the article on how you've chosen it as the greatest option to run some of your systems.
Quite honestly, there's only a couple or so languages that I would truly describe as "great".
Earlier quoted context omitted.
I think you're just trolling. But on the off-chance that you may actually be interested in discussion from someone who does a lot of JS, has done a lot of PHP: No, they're different. Firstly: - js is the only choice in browsers. for server stuff, you have an almost infinite choice. - javascript has warts, sure. but if you stick to "the good parts", then it is possible to use in a relatively sane manner. the compile-t…
> if you stick to "the good parts", then it is possible to use in a relatively sane manner Is there any language for which this is not true?
> Expert Sexchange Hahaha! Bigotry is funny! Hahaha!
I'm not much of a PHP coder, so I tend to watch these flamewars from a distance on the sidelines. However, I've never really understood why people criticize or mock Facebook for pouring so many resources into PHP. For building cross-compilers, toolchains, and syntactic extensions on top of a language that is seen as a fundamentally weak foundation. I mean, I DO understand all of those criticisms. I just don't get how…
I think you're just trolling. But on the off-chance that you may actually be interested in discussion from someone who does a lot of JS, has done a lot of PHP: No, they're different. Firstly: - js is the only choice in browsers. for server stuff, you have an almost infinite choice. - javascript has warts, sure. but if you stick to "the good parts", then it is possible to use in a relatively sane manner. the compile-t…
As for the logic of using a single language throughout your stack, I would argue two points:
[1] It's a myth. If you are a professional software developer, you are going to learn multiple languages... and if you're a GOOD software developer, then this excites you rather than bums you out.
So you're using JavaScript on both the client-side and server-side. Okay, how do you get information from your database without learning SQL? Just stick with MongoDB as the only datastore you will ever use? Document stores are great for the things that document stores are great for (another tautology), but suck horribly when you try to shoehorn them into situations calling for a relational database.
What about the HTML and CSS knowledge you already need to work on the client-side? Do those "not count", because a JavaScript developer usually happens to know them? Nonsense. Doing real work requires knowing multiple languages, because different ones are better suited for different domains.
[2] I would argue that the skills and considerations required to do non-trivial work on the server-side are generally different from those skills needed to do non-trivial work on the client-side. You may be smart and/or experienced enough to master both domains, but you approach design and coding issues differently in those domains.
If you take a developer who is senior on the server-side, but is so junior level on the client-side that he or she barely understands the DOM, then they will struggle at first in the other context. Vice-versa if you take a senior client-side web developer and throw them into the backend world. You're going to need to learn completely different skills, quickly. I'm not convinced that clinging to your "home" language really speeds up that process, rather than impairing it.