@ganjaman Really? That's your answer? I provided my view, based on my personal experience and based on listening to developers who I consider the best in the field.

Most people who attack PHP work with some of the languages that have the same bad reputation (for example Java). PHP is not even my main tool at the moment, but jokes about it are not only old, they also discourage young developers from using helpful tool because they make a mistake of trusting random people on the internet.

I actually didn't even want to answer to what you wrote, it's not a behavior that I like to encourage. Sometimes this community seems way too toxic for a group that complains about Stack Overflow very often.

@maushax Code in PHP is unreadable only if programmer makes it that way, just like with any other language.

If one does coding the proper way, PHP is marvelous tool for what it's supposed to do. Don't blame language for not being used properly (something that happens A LOT with Javascript).

@Root Stranger things have happened

For me it always depends on my agreement with the client. If they really wanted the technology that I never used, then of course I would bill learning time (most of it).

I would never experiment on my own just for the sake of it. That's what personal projects are for.

But if I thought certain technology could greatly improve performance (for example), there are chances I would use it. In that case I'd probably spent a lot of "free time" learning it and bill trial-and-error code at least 90%.

As long as you work on the project, and there is a progress, you should bill it.

If there's a bug because I didn't know how to use technology properly (and it was my own decision to use it), I would probably fix it without billing it. Learning is, in the end, something that you do for yourself and results stay with you much longer than whatever you get paid.

I think you should give part of the decision to your client. Especially if different technology will take longer and cost more.

@alexbrooklyn It took me a while to realize it's not Magento.

You can measure how many calories it helps you burn. If that number makes you burn more calories than you eat, it will help you lose weight.

It will help anyway. If you still eat more than you burn, it will help you gain less than you would normally (so it wouldn't help you lose weight technically, but would slow down weight-gaining process).

Walking burns more calories than sitting (citation needed!), but diet is also very important. Replace at least part of your regular sweets with (dried) fruits, and don't eat before sleeping and you'll see the results (takes some time).

Can't have any kind of issue if YOU are not responsive. Stop replying to mails, don't communicate with clients. Bugs don't exist until someone tells you they do.

New solutions and services are made every day, and the old ones are being upgraded. It only means more jobs, because more is to be done.

If you make these kind of services someone will have to maintain them, upgrade them, write plugins for them, and someone will still have to drag and drop if they feel like it.

In the past it was harder, with punching cards or even just assembly language. Then people realized they can create something more simple to speed up programming process. These new programming languages didn't cost people jobs. Quite the opposite. They created huge number of new job opportunities and even whole new industries.

There might come a day when some programming will be obsolete, but critical thinking and creativity that's necessary for it is very hard (at the moment impossible) to be machine-learned.

@rEaL-jAsE I was patient for months. Tried solving it the nice way, but obviously it didn't work.

The worst thing? I don't know what they are trying to accomplish. It does nothing but jeopardize their position. Being an a** just for the sake of it seems not only like a jerk move, but it's also stupid.

Bugs in the code I can deal with, no matter how much energy it takes. At least there is a reason behind them. I can't find logical reason for this "bug" in behavior.

@beggarboy Thanks.