Look, I'm the first person to yell about poor working conditions for Amazon factory workers, but this particular cited case dances on a fine line. If the equipment you are provided does not let you do your job adequately, you raise that up to management as high as it is required to go, usually the equipment gets repaired. If not, instead of spending the gas to drive 120 miles and not get paid, or let your back get hurt by picking things up constantly, you spend $30 and buy a laundry guard and use that until they fix your workstation. 120 miles at 20 miles a gallon is 6 gallons of gas at $3 is $18 a day. After 2 days, you spent less on the laundry guard and didn't hurt your back.
Long before you care about what language to use/work in (which you should take the time to select based on the job you're doing and the experience/skillset of the engineers you have available), you need to understand the people you will work with.
I love PHP, I'm using PHP 7.1 for personal projects and will soon migrate to PHP 7.3 (I could live without nullable return types for now) and I can write better code in there than anything I ever did in.NET (which I haven't used for almost a decade). That said, professionally, I'm doing a mix of Python, Go, and Java.
The reality is, almost every language can be abused. You can write bad Java, bad Python, bad PHP, bad Ruby, and lots of other bad code (especially.NET).
You know what's hard to write bad code in? Go. Also hard? Rust. So if your goal is to write great, concise, clear, performant code then you should switch to Go or Rust.
But if you just need a quick website, maybe just internally, or informational, with few moving parts, I cannot recommend PHP enough. The MVC frameworks range from super simple to absurd. Python and Django are way more complicated. Ruby on Rails wants to be simple but fails miserably when it comes time to deploy unless you're using Heroku.
Also, don't use.NET because it's the least portable of the bunch.
Slashdot Mirror
Look, I'm the first person to yell about poor working conditions for Amazon factory workers, but this particular cited case dances on a fine line. If the equipment you are provided does not let you do your job adequately, you raise that up to management as high as it is required to go, usually the equipment gets repaired. If not, instead of spending the gas to drive 120 miles and not get paid, or let your back get hurt by picking things up constantly, you spend $30 and buy a laundry guard and use that until they fix your workstation. 120 miles at 20 miles a gallon is 6 gallons of gas at $3 is $18 a day. After 2 days, you spent less on the laundry guard and didn't hurt your back.
Unions would help.
Long before you care about what language to use/work in (which you should take the time to select based on the job you're doing and the experience/skillset of the engineers you have available), you need to understand the people you will work with.
.NET (which I haven't used for almost a decade). That said, professionally, I'm doing a mix of Python, Go, and Java.
.NET).
.NET because it's the least portable of the bunch.
I love PHP, I'm using PHP 7.1 for personal projects and will soon migrate to PHP 7.3 (I could live without nullable return types for now) and I can write better code in there than anything I ever did in
The reality is, almost every language can be abused. You can write bad Java, bad Python, bad PHP, bad Ruby, and lots of other bad code (especially
You know what's hard to write bad code in? Go. Also hard? Rust. So if your goal is to write great, concise, clear, performant code then you should switch to Go or Rust.
But if you just need a quick website, maybe just internally, or informational, with few moving parts, I cannot recommend PHP enough. The MVC frameworks range from super simple to absurd. Python and Django are way more complicated. Ruby on Rails wants to be simple but fails miserably when it comes time to deploy unless you're using Heroku.
Also, don't use