PHP the final redpill

Redpill me on PHP

Other urls found in this thread:

arewewebyet.org/
oldversion.com/windows/america-online-9-0-optimized
help.aol.com/articles/manually-set-up-the-dial-up-modem
help.aol.com/articles/what-is-aol-search-on-the-welcome-screen
help.aol.com/articles/Configure-AOL-for-Broadband-on-Mac-OS-X-USH1793
gophp71.org/)
twitter.com/NSFWRedditImage

I never minded working with PHP all that much.

The only thing is I never set up a debugger for it. It was hard to debug you had to do printf debugging,

If you have the choice I would use a different serverside language. There are better options now.

Remote debugging is a pain in the ass.
Lack of unified style tends to make legacy work a pain in the ass
It has a lot of online resources
It may not be the fastest but it's reliable

It's shit
You're shit for asking
Take you x_pill shit to back to I hope you step on a mega dogshit while wear flip flops
Have a fucking nice day

It's actually pretty nice, especially if you have a lodern version.

Hating php is a meme perpetuated by pajeets and women who can only understand ruby

>Hating php is a meme perpetuated by pajeets and women who can only understand ruby
>He's oblivious of PHP's sins
>He probably also codes in JS, thinking is a winning combo
Are you 15??

No, tell us how you really feel.
Php 7 is pretty comfy and fast

Did they finally get rid of errors like

if (1 == "1.0")
return true;


and/or inconsistent behaviour on the core library?

Full metal jacket pill yourself retard.

>PHPfags will defend pic related
You're as bad as the golang retards

>It has a lot of online resources
This is both a pro and a con. A lot of those resources are absolute shit, and if you look in the wrong place, you'll find code that mostly works, but is unmaintainable fucking garbage you should never use, but nobody will tell you and you won't find out until it's too late.

What is "===" ya cum consumers?

this happens for any dynamically typed and cast-on-the-fly languages. Its a part of the sacrifice. Like the other user said, if you're using == and but are in need of a type comparison too, you need ===.

"0" -> FALSE
"00" -> TRUE

>Redpill me on PHP

>PHP7 fast and sexy as fuck.
>Best documentation online
>Composer
>Top tier frameworks like Symfony
>Painless deployment

Overall pure 7/10 would code.

Just stay away from Wordpress and all the Codeigniter pajeet code.

Only reason people hate on PHP is because it's a dynamic language in the sense that you don't need to create types for your variables, that opens up alot of possibilities and flexibility.
These cucks hate anything that isn't C anyway, fucking losers.

It's unequivocally shit. You should switch to an object oriented language, so you take the red pill and realize OOP sucks.

I like the elephant, it's cute. I like php, it let's me job hopefully.

Use Perl.

pip install django

array_filter($array, $callback);
array_map($callback, $array);


#JustPHPThings

it pays the bills

non aussie detected. git -push out me country

>django
>muh every model is a separate "app"
>muh controllers are views
>muh views are templates
>wait muh controllers are actually part of the framework
>no they're views

muh dick

array array_filter ( array $array [, callable $callback [, int $flag = 0 ]] )
array array_map ( callable $callback , array $array1 [, array $... ] )

kys OK?

This. Django is a pile of shit created as a cms for a newspaper. Rails is far supierior and much more comfy.

Learn tour table

As far as scripting languages go, I'd unironically pick PHP over Python or Ruby any day. And not just for web (I'm not a webdev faggot), we're talking general purpose scripting.

>comfy C-like syntax
>no GIL, so can into actual multithreading with pthreads
>fast
>sane scoping rules
>sane OO implementation (with proper fucking encapsulation)
>anonymous functions way comfier than in Python and Ruby
>dynamic but supports type hinting (including scalar types and return type hints as of recently) so you get best of both worlds

Sure PHP has some disgusting warts, but if you don't need the language to babysit you and if you know what you're doing, PHP just gets the fuck out of your way and lets you create shit. Unfortunately for most """webdevs""" who have no clue about programming, it also gets out of your way when you're creating disgusting spaghetti to hang yourself from. The terabytes of absolutely shitty code written by clueless Pajeets is the main reason for PHP's shit reputation, BTW. This and some ancient abominations like Wordpress refusing to fucking die already.

> having to remember this amount of bullshit just in order to be able to write some basic backend for your webapp
shiggy.tiff

You

1) It's literally everywhere. Throw a stone and you'll hit a website written in PHP.

2) Tons of jobs. PHP doesn't bring you high salaries like Python, Ruby or Go (unless you are really experienced, of course). But if you want "the comfy way", do PHP. It will still bring you enough money to live comfy and you'll meet laid back developers.

3) Sup Forums hates is, and it's generally good advise to do the opposite of what Sup Forums tells you.

4) Super easy deployment, LAMP stack is still one off the most common stacks and you'll get PHP hosting for small money and little configuration.

5) Laravel.

6) You can work pretty close to bare metal, when you are more experienced. Things like Go, Ruby or Python always tempt you to use frameworks, but it's perfectly fine to have an (almost) static website with some dynamic PHP comments in between.

7) You can avoid writing more JS than necessary.

Hahaha..


I think both Django and Rails have their good sides and their bad sides.

Rails is super comfy, whatever you want to do, Rails has your back. Downside is if you get better with programing you might find some things more restrictive or not really benefit for them. For example I don't really like active record. It's sometimes "overkill".

Django is not so comfy, you have to do more config by yourself and it's not the "aim/fire!" feeling of rails. But I found Django cleaner than rails, you don't have to dig so deep to find out where in the world you did configure some module.

Both frameworks are good on their own.

>Laravel.
is joke

>===
>having to remember

are you retarded or something?

Not retarded, just prefer not to fight the very programming language I'm using while writing code. Now go manage your NPE that your retarded PHP has barely learned how to catch a couple of releases ago

>just prefer not to fight
>not to fight
>fight at all

WTF dude8? You are the one who insist strict mode. Those are the rules of the language then. You're not fighting shit.

Take it or leave it.

since we're talking pajeet languages here - even the fucking java is better - at least it's consistent. While you don't even have a sane namespace implementation...

how about that

Seriously, how often have you compared text to numbers throughout your programming life?

In every programming language on earth you would do some kind of type check first, if you expect text.

The early internet was all about "try to make it work", that's why JS or CSS were implemented to keep on going if something weird happend (i.e. compare text to number). Same goes for PHP.

Have you ever used parseInt()? If you did, it is kind of the same.

>what is dynamic language
You are fucking retarded nigger

and yet racket/clojure/SBCL don't have this problem. MAYBE - just maybe - they refrain from doing retarded type conversions, as any sane dynamic language would.

It was considered AIDs, per this example:
Some people switched to rails, and then it turned to shit.

Then some bright individual unleashed server-side JavaScript upon the world. JavaScript, where not giving a fuck about primitive types is a """"""""feature""""""""" among other things.

Then people realized that php wasn't that bad. And was actually tried and tested and worked well with web servers for most things.

Its now anti-bloat web 1.0 contrarian to use php and that's pretty weird but great.

> It sucks but at least it's not ruby or javascript
this

Its literally just C for the internet. A real coders dreamland.

This.

Hate to break it down for you, but C for the internet is C. PHP is a crap language that can't even make up its mind on what the fucking kind of a language it wants to be: OOP, procedural, or all of them at once.

The only reason it's even still relevant today is that it enabled the pajeets to quickly copypaste code in HTML and it just worked. Oh, and that steaming pile of garbage that's wordpress/drupal/joomla/ecc., which are dying because even the pajeets themselves are disgusted by their code.

Stop pretending that the language you use at your shitty overpaid backend webdev job is even acceptable to be used by anybody with half a brain.

doesn't happen for python
dynamic typing does not imply weak typing

t. larping node tranny

>C for the internet
have you ever anything cgi?
and c is way more consistent than php ever was or will be (backwards compatibility is kind of a must, v7 changed some things but not everything)

I'm a lisp programmer, but I kinda understand the node """"code artisans"""": I'd cut my dick off too, if the only platform I knew was node

There's nothing to say.

It was created as a templating engine for personal use by one man, who admitted that he hates programming, does not have a fucking clue on how to create a programming language and used strlen as a hashing function for the hashmap with function names, which is why we have the amazingly inconsistent standard library we have today

Eventually it was picked up by jews. Then, some people started using it on their websites. It seemed easy to use, you could just take your existing HTML page and add PHP tags to output something dynamic. If you had chosen C or Perl, you'd have to convert your entire page into a series of prints or one huge clusterfuck printf that you can play the game "where does the placeholder go" with.

PHP has always been a non-programming language for non-programmers. So when actual PHP programmers entered the scene, all hell broke loose. PHP makes it way too easy to create buggy programs and MORE THAN ANYTHING insecure programs.
SQL injections and XSS have never been such a huge issue in other languages as they have been in PHP. You might say "Yes, but that's not the language's fault, but the programmers'!, but you're wrong. The reason there have always been very few PHP programmers and many retards is because anyone clever enough to use PHP well is already clever enough to notice its flaws and choose something else to program in.

The PHP community has worked hard and has created an ecosystem - standards (PSR), package management and standardized autloading (composer, PSR-0, PSR-4) that makes using PHP versions after 5.3 somewhat bearable.

But it's still basically a retarded Java at this point. Any paradigm except for OOP is completely unusable today and even that is just a worse version of Java's, the standard library and operators are a complete mess that can never be fixed (muh backwards compatibility) and thus every general purpose language with an HTTP library and good templating does PHP's job better now.

this

>complains about crap languages
>lisp

ittig

> hates PHP
> recommends Java

lol

> in a thread about PHP
> thinks he can talk about some actual programming languages
blub programmer pls go
not him but as shit as it is, java is still better than *that*

Fuck no, I don't recommend Java. If I have to recommend something, it would be C# or Go.

Most efficient languages are just horrible for web development. Maybe Rust can change things?

>I'm a lisp programmer
gave away the trole too soon m9

clojure is lisp, pal

>Fuck no, I don't recommend Java. If I have to recommend something, it would be C#
lmao

You can word replace this whole post with ruby or javascript. The cancer exists in silicon valley.

Without these commercialized bloat jew salesmen, we'd all think a front-end templating languages were pretty neat for small projects.

And thus we illustrate why PHP is still widely used today. Aside from inertia itself, other options are also hated and maligned for different reasons. Justly or not, PHP doesn't quite get enough hate to overcome it's few strengths.

What would Rust do for webdev?

Got a second interview for a php dev role. My php has gone to shit since I've not used it in so long, I barely remember it. I'm running through the php lessons on laracast right now.

What can I do to get ready for the interview? I think I have 2 weeks or so.

C# does everything Java does better.

There are no "good" languages to write web servers in. They all suck.
But at least C# is pretty good as a language. And with .net core and asp.net core, you can now host C# webservers everywhere.

>C# does everything Java does better.
In the same way that C++ does everything C does better, I guess.

Check arewewebyet.org/ and see if it fits your needs.

Spoken like someone who never used it.

not an argument

this isn't the early internet anymore though. there's no excuse for it

saying java is better is not the same as recommending java

yup, php is a retarded choice

I'm not here to convince you of anything.

Other than that PHP is a disgusting language.

We can both agree on that at least.

It's a statement. Being able to tell statements from arguments should be a pretty fundamental skill if you want to comment on programming languages.

At least you got one thing right, php sucks ass no matter how you look at it

ANNOUNCING AOL 9.0 OPTIMIZED!
>AOL 9.0's enhanced sign-on interface consists of a customizable welcome screen with a larger video panel and more video programming for broadband users than in previous versions. there's also an msn-style quickview page of personalized daily information services. you can select from six welcome screen navigation tool sets, such as nightlife and great discoveries, and six corresponding stories and features categories.

>1099 Hours for free!!!
AOL 9.0 optimized (broadband service, $54.95 monthly, direct; dial-up, $23.90 or $239.40 prepaid yearly; with another isp, $14.95 monthly)

Join the discussion in AOL chatroom "TECH TALK"

>DOWNLOAD
oldversion.com/windows/america-online-9-0-optimized

>TUTORIALS
help.aol.com/articles/manually-set-up-the-dial-up-modem
help.aol.com/articles/what-is-aol-search-on-the-welcome-screen
>Macfags:
help.aol.com/articles/Configure-AOL-for-Broadband-on-Mac-OS-X-USH1793

What does /pro/g/ think of the new meme perpetuated by PHPfags that goes like this
>well sure the language USED TO suck but that was before PHP 7
>PHP 7 fixed PHP and now it is as good as $another_language

What did PHP7 even "fix"?

use === or no equal signs at all
it's the same as python or JS.
NaN === NaN is the real CPU fucker

PHP its a pretty decent language. No matter what people here say it. There is a big difference bettween "coding" php and know how to code it. In any language.

If php was a new hipster language everybody here ll kiss is ass.

> You can work pretty close to bare metal, when you are more experienced
Heheeh now idiots call something without framework or restrictive patterns bare metal? Nu developers

At least it's the only good thing, you can program shit the way you want without having to be fucking enclosed in a shitty framework like ruby, but at most cases php is just chaotic especially when you end up with several files a d classes. Still prefer than ruby.

That's absurd. It hardly fixed anything.
There are completely worthless type hints, which will work differently depending on whether the file the caller is in (not the function being called) uses the new declare strict types bullcrap which is a horrible design decision in itself.

They also don't do shit for you if you need your function to work with multiple different types.

The return types in 7.0 were completely worthless because they were not nullable. That's why every single library skips 7.0 and goes straight for 7.1 (gophp71.org/)
They're still pretty much crap because there are no generics, though. This is the bane of every single PHP collection library, which are unfortunately needed because the SPL collections are worthless and "arrays" being a frankenstein-monster amalgamation of every data structure ever that keeps changing between what it actually is.

PHP's fundamental flaws can't be fixed, it's way too late for that. The standard library and its awful inconsistencies, the operators, the $, the "array" syntax, the inability to be used as a real templating engine because you can't auto-escape output, php.ini, superglobals...
Even if the core devs were willing or able to fix things, they couldn't.

I'll admit one thing, though: The null coalescing operator is a fine addition.
Much better than isset or the massive performance hit and all around wrong practice of using the error silencing operator (@).

phps arrays are fine. they can be used as a hash, an array, or a dictionary. it's not rocket science.

XDebug literally takes minutes.

PHP has plenty of issues if you write shit code, but so does every other language. PHP 7 mitigates most of them if you use the new features like type hinting. Most PHP hate stems from people having to work on legacy code written by someone who was a shit developer.

Yeah, and they change between them depending on the keys.

[0 => 'Hello', 1 => 'World!']

Is treated as a list.

[1 => 'FUCK', 2 => 'THIS LANGUAGE']

Is treated as a hashmap.

json_encode the first and you get a JSON-array. Serialize the second and you get a JSON object. Congrats, that already fucks up most json consumers.

Or if you use array_merge to merge two "arrays" into one, merging the first with itself would yield

[0 => 'Hello', 1 => 'World', 2 => 'Hello', 3 => 'World']

While merging the second with itself would just yield

[1 => 'FUCK', 2 => 'THIS LANGUAGE']

Because it operates differently. Depending on the fucking array keys. You can NEVER trust a function to always return a hashmap. If you don't check for this all over your code, stuff will break in mysterious ways.

It's also pretty easy to accidentally transform lists into hashmap. A simple array_filter or unset will do. Well, whoops!

This is a huge fuck up. I don't think any other language has these problems. There are lists (different kinds, for different performance requirements) and maps/dictionaries (also usually different ones).
PHP doesn't give a fuck. It was designed to be "easy to use", but all they did was make it easy to fuck up unless your program is trivial.

That's the thing. PHP was designed to solve trivial things. Show a list of things from your database in your page. Show the current time.

The language fails to support complex programs by design.
There's only so much we can fix with wrapper libraries for PHP's standard library and community standard guidelines.

You are retarded on so many levels.

Let me help you:

>idiots call something without framework or restrictive patterns bare metal

When it comes to web design, "bare metal" refers to raw HTML. Or if you are such a hotshot, than you can also program PHP directly on the Xen hypervisor. Bare metal enough for you?

>without having to be fucking enclosed in a shitty framework like ruby

Ruby is a language. You probably mean Rails, right?
Also you can program with Ruby pretty direct, i.e. one the apache mod. Or more common: using the Rack interface.

>Still prefer than ruby.

You probably mean "PHP is still preferable to Ruby", right? Somehow I don't think you have ever programmed in Ruby.


But anyway, thanks for your opinion!
You certainly brought this discussion to a whole new level.

Having one "array" type for everything is PHP's biggest failing.

By now asp classic is better. And asp classic isn't even more maintened by Microsoft.

>Running atop of a interpreter is bare metal now

Excellent. Web developers are the cancer of development.

>PHP doesn't bring you high salaries like Python, Ruby or Go
That's because there are barely any jobs in Ruby or Go. Python is a maybe.

Laravel is complete fucking trash.

And what the fuck is your idea of a high salary? With no college degree, as a PHP architect I make close to 200k.

Dude, maybe you should google libvirt and xen.

Laravel is pants on head retarded.

I will never understand why they use symfony's amazing dependency injection library only to tightly couple objects together (and to the framework) by encouraging "facades".

>Php architect
Almost meme like a code artisan

Elaborate please.

Laravel is pretty smooth and just as good as Django or Rails.

>===
why not just make == work the way everyone expects it to?

Because when you're constantly receiving data from the web, you don't get guaranteed strings or ints. That's how it was back in the day.

Sorry but I'm failing to see your point.
It don't matter if you can manage libvirt with php, php still is an interpreted language running atop of php DLLs who also needs a webserver to run.
Afaik there isn't a way to compile php code to machine code so you can never say it's bare metal.