PHP Sucks
evertpot.com/PHP-Sucks/Posted Jun 15, 2016, 10:18 PM UTC
41133
evertpot.com
Fucking fanboyism...
I'm not a PHP developer, I'm a developer. I'll switch languages and technologies as I or my employer sees fit. I may stop at some point using a certain language, but I'm never going to actually leave it nor unlearn it.
The current available jobs in my vicinity are mostly PHP/JS. Most enterprise jobs are in Java. C for the embedded folks and rare C++ jobs for higher end game development. Go? Ruby? Practically non-existent, and Python is apparently not a language for the web, but a "good to have" thing for sysadmins who need to do some quick scripting. Ugh.
PHP can't be "enterprise ready" yet because there aren't big suits behind it. Linux wasn't enterprise ready until many Linux companies put on a tie and went on to do some evangelizing.
And in order to make PHP palatable to the masses and cease this weird reputation, it needs to do some standardization in the library, ditch many backwards-compatible shit and fix some quirky behavior. That's it. It's already quite fast and stable.
I am currently diddling around with Go, same as the author, but I have to say I'm constantly scared that Google will let it go down the drain if it ceases to be interesting to them, as they've done so with many other projects.
18
And in order to make PHP palatable to the masses and cease this weird reputation, it needs to do some standardization in the library
As a beginner I confirm. Cryptic identifiers, messy documentation, quirks, all the tools to install... I want to be proficient with a modern, java-like PHP, but I spend much more time learning PHP than I did with javascript, with less results and more frustration.
7
all the tools to install...
a) PHP
Optional:
a) text editor of preference
b) an actual httpd (PHP has a built-in web server that's good enough for starters)
c) any real website will also have a database... but that's true regardless of the programing language.
am I missing something?
0
any real website
Front-end is real work.
3
I'm not dismissing front end.
Front end is a whole different animal.
your options:
markup language: HTML
Programming language: Javascript (or some higher level language that transpiles to javascript)
CSS (or SASS/LESS... that gets converted to CSS)
Pretty images: SVG, PNG, JPG... and the tools necessary to create em
1
How.... in the world does that have anything to do with the tools you need to install to do PHP?
1
Google will not let it go "down the drain" because they created it for their own reasons. They use it a ton within google itself (a little bird told me).
The thing you should be concerned about related to go is that since google uses it internally so much and it was created to solve their own problems they aren't going to be as open to add new things unless they need it because they don't want to slow their stuff down.
Now someone could fork it and make golang_community or something but then it would fragment go.
At the end of the day the "grass isn't always greener on the other side". If you know how to solve problems and you know at least a handful of languages then you shouldn't have any issues. If you are an expert in a single language then you decided to do that and hopefully you did it for a good reason.
1
they aren't going to be as open to add new things unless they need it because they don't want to slow their stuff down.
This has never been the case with Go. Not once did they reject a pull/feature request because it would "slow them down". On the contrary, they are very active within the community (see r/golang, the official subreddit and golang-nuts mailing list).
Also, Go is slowing down by design and that is a good thing.
3
Maybe my use of the "slow them down" was incorrect. My point was PHP has FIG and other languages have other community boards/groups/whatever you want to call them that vote on things getting in. golang has google as the final say that is all.
Is it an issue? idk I'm not that big into golang but people that I know who are have been moving away from golang. Now maybe they are moving away because they want to use the next big thing (rust or whatever) but it is also possible that they are moving away for a reason.
1
but it is also possible that they are moving away for a reason.
I'm sure they have their reasons, but I'd be very surprised if lack-of-FIG is one of them. Don't get me wrong, organizations like FIG are great for PHP, because it is very much needed. When a language has 10 different ways of doing the same thing, each with its own weird quirks, a group of volunteers agreeing on standards is an excellent idea!
Go, on the other hand, is a tiny language where there is only one of every feature (e.g there is only for, but no while, do or foreach). You can even read the entire spec in an hour or two. Given that, the need for an independent standards body doesn't really exist.
1
One of my big gripes with PHP is its half-way-in-the-water style of OOP. Let's say you want to create an array and add a value via push.
C# has a List<T> which behaves like PHP array:
List<string> myArray = new List<string>();
myArray.Add("super cool value");
JS has an array that behaves like PHP array:
var myArray = [];
myArray.push("super cool value");
Then PHP, despite declaring an array, makes you do this FP pattern:
$myArray = array();
array_push($myArray, "super cool value");
It's not a huge deal or anything, but I'd much prefer if PHP's array functions were exposed as methods of the array object, instead of as exterior functions.
1
$myArray[]="value";
1
Ah, that’s pretty old school right?
Coincidentally, I just spoke with a recruiter last Friday who was surprised to here that OOP could be done with PHP. I tried telling him that the non-OO PHP days were over a decade ago, but he didn't seem to care :(
16
I had a very similar discussion with a recruiter recently. He argued that I should talk about Lavarel and Drupal but avoid talking about vanilla PHP.
11
"you should talk about making chairs and tables but avoid talking about wood"
20
This made me laugh because I get the same flack when I talk about working on PHP runtimes.
"This is C/C++ I'm talking about. I'm growing the damned trees."
12
its wrong and silly and the reality.
8
"I don't give a shit about wood, I want somewhere to sit and eat"
1
which is cool when you are a customer, but definitively not when you are the one making and selling chairs and tables.
4
I'm in this position right now. We had to chose our next application's languages. Since we have a small dev team, we outsourced. Angularjs front end (written in coffeecript) with a PHP backend (using Laravel).
Up to this point I had built so many classes and then one of the outsource devs said "you write straight PHP code? You're a dinosaur!". Luckily, Laravel is fun to learn, but damn it feels like just yesterday when I was interweaving PHP inside of html. Now, it's a whole new ball game.
Learn Laravel when you get the chance, but you knowing PHP is an absolutely amazing asset when beginning the framework
5
yesterday when I was interweaving PHP inside of html. Now, it's a whole new ball game.
Please let me know how to sign up for this new ball game. I work on a Magento site, built recently by an overseas development team for my employer, and all the frontend is just a nightmare of PHP + HTML. Send help.
3
but he didn't seem to care :(
It's a recruiter so that's no surprise. The only concern they have is to get an ass in the chair and earn that 20-40% commission off the salary.
6
lets put it into a chef analogy.
would you hire a chef who doesn't differentiate between fresh and dry meat? Because thats what the recruiter is doing with his "don't talk about meat, tell me about steaks" non sense.
1
i like the advertising line directly under this article
"Looking for a PHP developer for your next project? I'm looking for work!"
6
Lol. Yea its time to take that one out ;)
3
So in the end is money and illiterate recruiters, CEOs and undocumented developers? Hmmm, okay.
Honestly, heard this so many times. In the end, for certain things PHP rocks, but for some does not.
If you feel you need social approval, go just learn something else: Ruby, Python, JS, Java or Go... and enjoy it as much as coding in PHP! :)
4
In the end, for certain things PHP rocks, but for some does not.
Exactly. It is just a tool. It either makes sense for the project or it doesn't. If all you know is PHP then you're kind of screwed anyway.
2
As much as you may disagree with the article, I lost many many many job opportunities for very interesting projects because more "hip" or "enterprisey" languages are picked, and a different contractor wins on a certain bid, and builds the same crap that an outsourced team would have built.
Don't think it has to do w/ social approval, but rather the jobs he's after people look down on PHP.
1
In the end, for certain things PHP rocks, but for some does not.
1
If you feel you need social approval, go just learn something else
is what I'm responding to which has nothing to do w/ what I quoted.
1
Finally someone said it, i many times said on r/PHP that wordpress is anti-pattern of everything and mostly i got downvoted pretty hard.
4
Why is Wordpress an anti-patter of everything?
1
Because there isn't any good practice to see in Wordpress, nothing to learn, pluuuuus, everything is done is some odd and weird ways, i find it myself very painfull to look at code written in that way i personally don't like it, and it's just my opinion. And if somebody ask me some good software to digg around for some good code i would rather recommend october then wordpress.
1
Hm you kind of confirmed my suspicion... is Drupal 8 better?
1
Never worked with drupal, sorry. You should ask author of this text, i think he mentioned something about drupal. But for example, this is one interesting project https://github.com/bolt/bolt
1
[deleted]
1
What is lol about that?
1
Am I the only one interested in why
echo b"foo";
is valid?
3
https://web.archive.org/web/20090403051843/http://us2.php.net/manual/en/function.is-binary.php
Note the PHP version. It's useless, they simply forgot to remove that.
4
[deleted]
1
echo b"foo";
b is indicating that this is binary string. its same like echo (binary) "foo";
You can read more about it here http://php.net/manual/en/language.types.type-juggling.php
3
Thanx!
2
npz
1
This is why I love this subreddit. Thank you!
2
when somebody asks me in the future what I use for programming, the answer might be: “mostly Golang”.
Hipster
3†
With 2 points and currently 51% positive votes, I'd like that people don't downvote this blog post only because of the title. The article is an insight about PHP's professional reputation and real-world jobs, which you don't read everyday. Explain if you disagree with his impressions.
2
I worry about this and I've been working with PHP since 2001. Every time I search for PHP frameworks I get too many results and it comes down to whatever I pick is wrong because of reason X or Y.
My last search was laravel vs zf2. I picked zf2 and have been content with it. I've been able to bend it to my will for things like nested REST routes. I might have been easier in laravel but it's too late now.
I'm really curious if it's time to give this up and move over to node development. One language from front to back would be nice.
2
you'll get even waaay more results for frameworks on node, and the popular ones change month by month unlikely year by year in php.
1
Well the author made a point, PHP's reputation is surely a drawback in many case scenarios. Its understandable hes moving on to a new language, not everyone can withstand the low reputation of PHP which can backfire. But, why Golang? To me its the most overhyped language that does not have any practical use cases. I've seen enough of this hype and its starting to get annoying. You will be way better off picking up Java, C#, Python, Ruby, or even stay with PHP, than GoLang.
1
To me its the most overhyped language that does not have any practical use cases.
What use cases have you tried and why do you think it was not a good fit?
Here are some big Go projects:
These are very popular projects that cover a wide range of topics from server management, systems monitoring to web development. There is also a massive list of high quality Go projects at awesome-go and on the official wiki.
Go is hyped for a reason. It is a huge breath of fresh air for a lot of people who have been using Java, PHP and C#for a long time. A statically linked, strongly typed, compiled language with cheap and fast concurrency? Yes please!
It is also stupidly simple to learn, and extremely minimal (you can read the entire spec in a few hours). I strongly recommend trying it, it just might surprise you.
2
Add Gogs to that list. It's a brilliant bit of software.
4
Of course I've tried it, and never liked it. And yeah, its hyped for a reason. Not saying it doesnt deserve a bit of excitement from some programmers, but it clearly its way too overhyped. I mean, overhyped, too many people jumping on its bandwagon just because it feels like a cool new little thing to them.
And why do those programmers need so-called 'breath of fresh air'? I think this 'fresh air' benefit is totally subjective. I love the C family syntax of Java/C#/PHP/Swift, and even if I want something new I can always go for Smalltalk and Ruby. I honestly, dont see what Go has to offer that cannot be done easily in another language.
Does Go have its place in the world of programming language? Yes of course. But does Go deserve this much hype it receives? Nope, not at all.
3
And why do those programmers need so-called 'breath of fresh air'? I think this 'fresh air' benefit is totally subjective.
YES! It is subjective, that's why those programmers need a breath of fresh air. PHP, to me, is suffocating and when you find yourself in that position (as so many others can tell you) Go is most definitely a much needed relief.
Yes of course. But does Go deserve this much hype it receives? Nope, not at all.
So because you "never liked it" and "don't see what Go has to offer" it doesn't deserve the attention? Well allright then.
1
Indeed, you agree that it is subjective, then everything is easy from here. And I am afraid I am not the only one who never liked it, and not many people really need this so-called fresh air as you described. Look at this Tiobe Index and you understand that, those programmers who find GoLang a fresh air is still, a minority:
http://www.tiobe.com/tiobe_index
Well Go does deserve attention, but its getting way too much attention and hypes than it deserves. Its a usable language and a good choice for certain programmers, but not like the future of programming. Just some bandwagon programmers advocating for Go doesnt mean it will replace the mainstream programming languages. The Tiobe Index shows clearly that Go is nowhere near as popular as some developers hype it to be, I think you need to chill and deal with this.
2
Golang is probably getting hyped because it's ridiculously good for OPs code. A static typed language that can compile to a static binary with a feature-full base library I can use for all manner of shims, etl, and tiny web services that solve problems the full dev group won't take the time to fix? Yes please.
1
Good try, but no - it still has "hip" reputation ;)
Just to refresh: main use-case is service-oriented architecture, then go is suitable (in spite of mentioned projects). Even writing daemons is a case, but for most commercial projects it's not suitable.
1
what's with the := assignments?
1
:= is declaration + assignment. = is just assignment.
1
"Fun" fact Crystal Reports also uses := syntax.
1
So does Pascal which is a nice callback to the first language I really loved.
1
For my the choice was between Golang, Swift and Rust. Clearly given the list you stated you are more leaning towards traditional languages.
I think a more modern language, even if it's 'hyped' can quickly lead to bigger innovations, it's easier to attack and influence the status quo and there's actually good career reasons to go with something a little bit more modern.
In my next company I'll also be in charge of hiring, and hiring for a less established language is actually a bit easier, because most of your candidates will have learned the language because they think it's cool, not because it just happened to be part of their curriculum.
1
I've been happy with my rust experiments so far. I hope to get an opportunity to do more with it. Definitely worth keeping tabs on!
1
More excuses for bad products, unhappy deliveries and lost pitches. Great products can be written in any language. Stop making excuses to why your products are shit.
1†
I see that you've done a good job reading the title of the post.
3
All the way down " Looking for a PHP developer for your next project? I'm looking for work! Check out my resume or drop me a line! "
1
I have no idea where this "I can't get paid to do PHP" idea comes from. I get six-figure jobs thrown at me all the fucking time and I don't even live near a metro area of any significance. You can land jobs with most of the Fortune 500 with PHP skills.
1
Ah, French sucks because I don't attract the French girls. Chinese sucks because it is so weird. German sucks because you only can write philosophical books with it. You cannot use English in scientific context since it is bad designed for that purpose. Dutch sucks because nobody speaks it. Swedish is declining and you better do not learn that language. If you want to buy oil you better use Arabic. You simply cannot translate from one language to the other and if you cannot say something then obviously the language sucks. Never ever speak several languages and only use the language with the best design. Can we agree on that and go on?
1
This sums up pretty much the language debate.
1
Has PHP ever though about rebranding and changing it's name? Especially since version 7 and upwards are leagues better than what it used to be. Perhaps v8 = new branding with a more solid core (tons of backward breaks).
1
7 and upwards are leagues better than what it used to be..
A chain is only as strong as its weakest link. Or a tower is only as stable as its base. Php is built on rotten core. As long as it remains, any new additions ends up merely cosmetic.
Most of the development world gets it. Sadly Php programmers don't.
1
Pretty much why my last statement was breaking backwards compatibility and fixing all the shit in core.
1
I think PHP is heading that way, but it's easy to say it, than actually do it. PHP powers hundreds of millions of websites, and you can't just break all backwards compatibility from one major version to another. You do it one major version at a time.
1
A rebranding would be more than just a major version upgrade though. It's pretty much, "this language is much different than it used to be, you can patch old code to work here, but its suggested you start from scratch". More of just a wishful thinking thought.
1
If you can live with tons of backwards breaks, why not keep PHP backwards compatible and switch to a language that does have the things you need? PHP is PHP, it's easier to just work with the language you want than to hope that PHP becomes it. There's plenty of options out there.
1
Hence the rebranding and backwards incompatibility. More of just a shower thought.
1
Yea so basically you're saying, I want to use something that's not like PHP and is also not called PHP. What am I missing? ;)
1
Missing the point completely? The name would be different and any internal bullshit bugs (that should be fixed but aren't because of BC) would be squashed. It's still the same language, same syntax, same functionality. Just slightly better.
1
Like hhvm?
0
[deleted]
1
I think PHP as a language also suffers form this, let's call it "minority complex". Because PHP often gets dismissed by enterpris-y types, more and more RFCs get approved and frameworks become popular (cough symfony cough) that seem more enterprise-y and complicated just so PHP gets less looked down upon. In no other language there are frameworks that are this unnecessarily complex just for the sake of being more enterprise-y. And PHP's OOP type system really sucks because too much is stuffed into it without thinking about the consequences.
0†
I just laugh because most of those Enterpris-y types are probably working in Java or .NET and can ONLY work in Java or .NET (i.e. the languages designed specifically for outsourcing).
1
PHP is going to be COBOL at some point. The 20 devs who can still do it get boatloads of cash to work on legacy applications.
-1
The trouble is that PHP is easy to use while COBOL is certainly not
1
I imagine COBOL was easy when there were hundreds of people developing it. Having not used it heavily in years and then come back you'd be surprised how PHP's screwy lexicon will mess with your head after using anything else.
1
That could be said for any language really... If you think having a pretty shiny new language will help with that, I think you are fare overestimating the capabilities of the languages. The problem is rarely the language, but the codebase itself, regardless of the language.
1
That's what I'm saying, every language eventually shows it's flaws. And if you can stand working around those flaws when everyone else abandons the language for greener pastures you can write your own checks.
1
Eh, another idiot looking for attention.
-9
another idiot not reading the article
2
As much as you may disagree with the article, I lost many many many job opportunities for very interesting projects because more "hip" or "enterprisey" languages are picked, and a different contractor wins on a certain bid, and builds the same crap that an outsourced team would have built.
PHP has an awful reputation coming from tools that most of us already know (the typical blogging platform, and its "wonderful" ecosystem).
It will take time to get this reputation eradicated: as much as it will take for Micro$oft Windows and OracleDB to become popular among open-source developers.
If that is the case you should consider becoming a "developer" and not a "PHP developer". In my 20+ years of software development I have been paid to develop in idc/htx pages (predecessor to ASP), ASP, C, JAVA, VBA, PERL, PHP, JavaScript, and a few others I don't recall right now.
For fun I have developed some projects on my own using ruby on rails, golang, python, etc.
A good developer can work with any language. It is just a tool. Keep your tools clean by using them often. You learn a lot by using other languages that you will never learn if you just stick to just one or two.
I think this is missing the point. What is it that makes a developer an "$x developer"? Is it their exclusive knowledge of the language itself, or their extensive knowledge of the ecosystem (tools, processes, idioms etc)? As the author of the article pointed out:
I know lots of good programming principles and best practices and have been applying them in the context of PHP for a long time. When I got a job as a JS developer, I transferred a lot of that knowledge and experience to JS (even though the work is largely functional and asynchronous instead of object-oriented and synchronous). But fuck me if I know how to actually build up a JS application from scratch using various combinations of browserify, webpack, babel, gulp, grunt, vue|react|angular loaders and compilers/transpilers or what have you....
I can start up a new composer project and publish it to packagist in no time. But have you seen what shit goes into doing the same for a JavaScript package on NPM? At the end, this guy has like 30 dev dependencies just for a simple script that randomly gets an element from an array........
And that's just ONE way of doing it
Anyway, small rant aside, my point is that despite doing almost exclusive PHP programming for ages (e.g. being a "PHP Developer"), I was able to easily transfer a lot of that knowledge to writing JavaScript - even in a different style and paradigm. But, I know dick all about the larger process and ecosystem around JS even though I can write very good code in JS.
But that knowledge takes a long time to learn to build a mental map of. You can't be a generic "developer" because of all that extensive knowledge you need to really set your self apart. You can be a generic programmer, but programming is only part of development.
So what makes you a developer isn't your ability to pick up and learn the language, it's how extensive your knowledge is of the whole shebang related to that language. OP isn't a "PHP Developer" because of his knowledge of the language, it's because he knows how to use all of its tooling and knows which tools are good and which are bad.
I've been doing professional software development for over 20 years. I've hired dozens of developers in my time as well. I can tell you that my requirements have never hinged on the developer knowing a particular language.
My interview process is very very simple. I get them in a room and I give them a problem to solve. We work on it together so that I can determine if they have problem solving skills, can work as a team, and to make sure we get along. At the end of the day a developer needs to know how to solve problems. The language they use should be dictated by the problem they are solving not by what language they know.
Yes I have sat in interviews myself where they want you to write perfect code in a particular language using a pencil and paper to solve a problem but those are few and far between. I honestly haven't heard of anyone having an interview like that in at least 10 years because the language doesn't and shouldn't matter. It's a tool.
I get what you are saying in terms of getting everything setup but that is a very small portion of a project. Even if you work for a company that creates hundreds of sites a year the setup process for a project compared to the overall project is very very small. That is why we make notes, create scripts, or in worse case just copy from another project to get started.
I'll get it out of the way. Maybe I'm just a shit-level developer.
I believe what you say is true in that you actually do that. What I don't believe is that the "language doesn't matter". Every job I've seen has been for "Senior X Developer" or "five years doing programming in Y". There is no way I'm going get a job where I live (US, middle) without stating and knowing at least one language very well. More specifically, if they're hiring for X language - and I've never used - I won't be getting a call for an interview. But that's just finding a job.
Doing a job is different. Doing a job well is different from that. I'm sure most programmers can probably get a
Hello worldup and running in most languages. That doesn't mean they will be effective on a project. Even within the same language you can have completely different workflows, tools, methodologies, etc depending on what the project is, what framework you're using, or what CMS.You're not the only one to say that. Matter of fact, developers love to say it. It's just that I really have never seen it in practice. Somebody hop over to a new language and be as effective as somebody that has been doing it for five years. I'm not saying you should stick to one language or anything like that. Developers should branch out. What I am saying is that I think people overstate how effective they are.
each language mostly bring it's own paradigm, switching syntax is considered to be easy, but switching paradigm, how things work in lang X and how things work in lang Y, its usually difficult
Oh, it's not like I wouldn't learn other programming languages (I know a few), it just isn't as simple as switching when your core knowledge is around one. You wouldn't start a project for a client in a new language by having only some theorical knowledge and some experimentation done, wouldn't you?
Being hired in a team and being hired as external expert consultant are different things ;-)
Yes, but it has to be the right kind of project and a long runway. Luckily I had that opportunity recently. Honestly, the only way to really learn a new technology is to jump in with both feet. You can't really go at it half-way or it will always remain a hobby.
I've been hired for Ruby and Python jobs before knowing either language, and have chatted with someone about helping build an Android app despite not knowing that ecosystem. It's of course a bit less efficient, but general OOP design all works about the same way (learning Rust was comparatively painful, but for different reasons). In the Ruby case, it literally was starting the project from scratch in a new language. Wouldn't have been my preference, but it wasn't that bad.
I find that I'm probably working at 80-90% productivity compared to PHP, which I know best, in less than a week.
I completely agree that it's a good idea to keep exploring new tools, but "Jack of all trades, master of none" comes to mind. I don't want to just be the guy that can build an application in a language, I want to be the guy that writes the tools in that language that everybody uses.
I'm not saying I reached that with PHP, or ever will, but picking up a new language and being able to write something with it is a long shot from being a well-known expert in that community, which is something I aspire to and u/ocramius is.
Switching to Go for me is also starting from scratch with something I've built up over a very long time.
I think I made the same point you just did. If you want to be an expert PHP developer, expert WordPress person, or expert x then that is your choice. It is your choice to be known in the community and be hired just for that. You are selecting that. If you have selected that path for your career then that is your choice and I respect it. We need those people. I just don't want to be one of them.
I want to develop software solutions and I want to use the right technology for the job. To do that I have to know a good amount about a lot of languages and technologies. I don't want to use PHP because I know it. That isn't the right way to go about solving problems for the clients I work with.
Facing the same situation, when talking with teams about languages stack. The trend to criticize PHP seems to be dying at last, but the language reputation is improving very slow.
My 5 cents (who is not familiar: I'm the author of Php Inspections (EA Extended)) are also aiming to bring PHP into Enterprise faster.
I guess thing will turn better as generation of Best Practice/PhpStorm/SCA Tools developers terns into PMs and so on. At the end lot of those guys are using both Java and PHP, but reasonably: not "hip" or "enterprisey" like-judging =)
Just wanted to say thanks for EA. Imho it's the most important plugin in storm.
You are welcome, and thank you for using it )
This might sound weird but I actually use this fact as motivation to try and start my own project/company. I think a lot developers dream of being entrepreneurs and making a living off the software they write, and I'm certainly in that camp. At some point I'd like to start thinking of the companies building their software on the MEAN stack as either potential customers or competitors, as opposed to potential employers. I could jump on the NodeJS bandwagon, or I could try to write software that people love with PHP and try to make it on my own. Haven't succeeded yet, but I haven't given up either ;)
I haven't given up either, but the point made by u/evert is understandable.
I don't think it will take that much... PHP is OSS, it can change without needing a CEO to shuffle through powerpoint slides in front of shareholders.
"ohh yes I have a very cool tool for php that works exactly like ruby on rails but doesn't need to know ruby to do it" and give them yii2.
if i ever get a customer to ask me for node js i will tell them the same and give them slim framework.
Come on, you were doing soo well and that $ instantly turned you into an edgy 14 year old. I mean, really?
I believe that term was used ironically.
What, you want a free Windows 10 upgrade? You could have told me upfront!
I haven't used Windows in 14 years, but sure, if it makes you feel better, why not? :)
I scheduled it for tonight, just before your mission-critical cronjobs run.