Name: PHP - コーダーが嫌う理由... (PHP - Why Coders Hate...)
Uploaded: 2021-01-14T10:18:26.000Z
Duration: 9 min
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

基礎数量詞

So question is why do so many coders hate?

動名詞

If you're thinking about learning PHP and you go out, read it or you go out.

You to go to some other social media platform when we say I am about to learn Ph.

Ah, lot of people are going to say, What's wrong with you?

You need to learn python or Java Sea sharper something else.

What you're going to find is a lot of coders out there are going to tell you it is utterly stupid.

Learn PHP and that you should better go often learn a different language.

One of the main problems with PHP is that Pee HB is so easy a more or less a secretary can use it.

One of the things with PHP is it was designed to be incredibly easy to use again.

PHP does all of that basic kind of like administrative tasks that lower level professionals may need to dio things such as again collecting e mails, doing email, blast, doing reports, all that kind of basic stuff.

So when PHP was designed, it was designed so that people could write code very easily, even if that code didn't go by normal programming standards.

So normally, when you look at code for Java or C Sharp or these other programming languages, it looks all nice.

Other coders can understand what's going on.

Not only is it functional, but it's also readable as long as you understand how to read the code.

One of the issues with PHP is you could make some ugly coat.

He could make some truly or of a local code that works.

But if you're somebody else trying to look at the code after worth, it could be an utter nightmare to look at the code one of the problems with it, too.

As you'll hear a lot of people can complain about security issues of PHP.

One of the problems is that it's very easy to write insecure code and PHP, and it could be very difficult to audit that code to take a look at it, to see exactly where it's what's going on to be able to see the security loopholes.

So the thing with PHP is it's very easy to create something functional.

But it's also very easy to create something functional that has a lot of problems that is very difficult for other people to go back and try to figure out what is going on.

So that is one of the big problems that people have with PHP is they just feel they just feel it creates too many people that use it, create bad code.

Um, and then it's then that goes out in the world and it can create a lot of nightmares.

Do realize with a lot of coding projects a lot of coding.

It's kind of like that little stupid side thing, um, that you gave the intern and then somehow it's six years later and your entire enterprise runs off of it.

You think about things such as asset tracking.

So in larger organizations, larger corporation ah, fixed asset tracking is a big deal, making sure you know all of the computers that you have in your inventory, knowing when they were purchased, knowing the price they were purchased for knowing the depreciation over time and So you may have a company that was growing very quickly that did not have a good way of tracking their fixed assets.

So you bring in a little help desk technician or you bring in an intern.

The intern looks around, goes Oh, hey, you know what I could D'oh!

I can create a fixed asset database for our department.

So let's say you're in the desktop support department and so you think you know what?

I'm going to create a little inventory control system for us so we can track our hard drives and contract our Ram, who can track all of all of the components that we're using to make life easier on us?

Well, the thing is, imagine that little intern of that little desktop support engineer who knows who knows how to swap hard drives doesn't really know how to code very well.

And they slapped together this PHP code and it's some ugly PHP gets ugly PHP code.

But you have a nice little form and have a low bar code reader that's able to take information dumping in the forum you hit Submit that dumps into the database.

You're able to pull reports and it actually works really well.

And then it works so well functionally for the desktop support department.

Then the director sees that it goes, Oh, hey, you know, we should deploy that for the other, the other departments and i t.

We should use that to do fixed asset for the server room and the data center.

And so that that that code that application that was created now is not only collecting all the information for the desktop support department, which wasn't any big deal.

Now it's two collecting all the information for the entire I T department, and that's going along so well.

You know we have to track desks and we have to track shares with the track of vehicles and all this other stuff attracts.

And this this little Web application that they in turn, created.

No, it's doing pretty well, So why don't we?

And then every time it gets expanded, that little intern on the desktop support person you know, adds a little module adds a little thing and the ugly way that they add and then all of a sudden, that desktop support engineer actually feels like they can code pretty well.

They get a job somewhere else, you know, for twice the pay.

They go off to that other company for twice the pay.

And then somebody within the company has to sit down.

Ah, and at some point, the IittIe director goes, Oh, okay, well, we want to add this additional functionality to this asset control system, and then you have somebody that sets down.

They open up the code, and they just see just pages, just thousands of lines of just mess that they literally don't know what the hell to do with again.

Or is this more of a problem of making sure that people write code the appropriate way that you have code auditing so that the rest of the organization knows what's going on with the code that's being deployed on a wide scale so on and so forth?

And so that's one of the big problems that you run into is that the small little projects that some little Internet stop support engineer create?

They somehow start getting used corporate wide and then sometime in the future, five years in the future.

Some poor person has to go in and try to deal with that code in order to bring it up to the standards that they need.

And so that's one of the reasons why people looking down on PHP now the important thing to is that people will also say that PHP is not the most functional language.

If you're going to be learning a programming language nowadays, a python is the big one.

Why learn PHP when you can learn a python with this?

That actually is a very true argument, depending on what you're going to be doing.

So if you want to be a new coder, right, So if you want to go out there and you want to build applications, you're gonna go out there, you create your startup company, you're going to go out there and you are building applications, then learning a different Cody language, such as python or one of the other languages.

Buy a learning that one language you will be able to do more once you've actually learned it.

The the the converse side of this that the argument with it, though, is that if you're going to be something, somebody going out there and supporting technology supporting code, the reality is, is that there is just a tremendous amount of Ph.

If you go when you learn python and you get to be an expert python and then you go into an environment where they already have a lot of PHP code written, then you're gonna have to go back and learn PHP code anyway, to be able to understand what's happening and basically go in there and try to clean up whatever the hell that intern did five years ago.

So that is an argument where if you're trying to create things with much more function, is going to be trading desktop applications, you're gonna be creating higher level applications.

Other programming languages are able to do things a PHP can't but again just realized that PHP has a specialization.

Other programming languages have their specialization, and so, again, that gets to be a bit of ah, you know, squishy argument, right?

If you're only going to be building new stuff may be better to use a different toe, learn a different programming language.

But if you are going to be trying to maintaining older things, learning PHP can be very valuable.

So those are some of the arguments against PHP.

They are to be clear, they are real arguments.

But with all of these things, you have to look at context.

You have to look at situations you have to look at, why you're trying to do whatever it is that you're going to dio and go from there.

But I still think PHP is a valuable language.

And the reality is is that if you're going to be going out is a knight professional You're gonna be dealing with PHP at some point anyway, so you might as well learn.

 And even if you learn it and then go off and do something cooler, just learn it. 