Live data from Hacker News

25 Years of PHP

jetbrains.com

21–30 of 426 posts

Re: 25 Years of PHP

#21
post #9

Fine. After 20+ years of PHP development I'm going to give it a shot. Will be attempting to migrate from VSCode. Any tips for that transition in particular, or for setting up PHPStorm in general? I have a subscription to Laracasts and plan on watching that series, but I'm not sure if it's outdated. Thanks!

There’s a fairly good plugin for JetBrains IDEs called “Key Promoter X” that reminds you whenever you do an action (click build, open a terminal, change directories) of the keyboard shortcut to do that same thing. It’s very handy for getting into the workflow quickly.

Re: 25 Years of PHP

#22

"Smarty released. The best-known templating engine for PHP. Rasmus realized that he had done something wrong when people started writing template engines for his template engine in his template engine" :D

[deleted]

Re: 25 Years of PHP

#23
post #9

Fine. After 20+ years of PHP development I'm going to give it a shot. Will be attempting to migrate from VSCode. Any tips for that transition in particular, or for setting up PHPStorm in general? I have a subscription to Laracasts and plan on watching that series, but I'm not sure if it's outdated. Thanks!

I use it every day and love it. Probably the biggest thing is getting the keyboard shortcuts setup how you like and knowing them.

- "Search Everywhere" with double tapping shift (at least on mine) is really nice. And the fuzzy file search might be the thing I use most often. - Git support is great, especially the shelving changes support. - I use navigating around words using Alt+arrow-left/arrow-right all the time as well. - "Extend selection" command can be very useful for selecting increasingly larger blocks intelligently. - Go to matching symbol (default Ctrl-Shift-M on KDE keymap) is useful

Loads more, I read the daily tips to figure out some of the newer stuff, or look through the keymap.

If you like Vim style keys, there's a plugin for that.

Re: 25 Years of PHP

#24

"Smarty released. The best-known templating engine for PHP. Rasmus realized that he had done something wrong when people started writing template engines for his template engine in his template engine" :D

Yes. The thing he did wrong IMO was to unleash a scripting language hiding in SGML-ish processing instructions without HTML-aware context-dependent escaping upon the world (when SGML has plenty of rules for delimiter recognition in particular parsing contexts), and then later make up for this with braindead quoting routines (like real_escape_string). In other words, the quick and dirty way was chosen, and that choice has plagued websites in the form of injection attacks (and DDOS using PHP injection attacks targetting even non-PHP sites) to this date.

Re: 25 Years of PHP

#25

[flagged]

Once or twice a year I have to peak at the code of a C app that was developed by interns more than 10 years ago. No framework was used, max 3 letters variables are the norm, no blank lines and the only comments are from code copy pasted from examples. These days I would be more inclined to celebrate the death of C than its birthday !

I'm not sure why this comment identically copies the GP with the exception of the last line, but it doesn't appear to be a spam account.

Re: 25 Years of PHP

#26
post #6

PHP is damn fast now, no joke. And with all of the modern features it's actually not so bad to work in. I'm becoming increasingly puzzled every time I see PHP hate now, especially when I read tired comments like "just use rails". Laravel is arguably as good or even better than rails at this point, and PHP 7+ is definitely light years faster and lighter. One thing that still sucks is package management / composer.

I took a look at it about 1,5 years ago while having worked with very early versions (2, 3 or 4?) as a teen. It was the first language I put some effort in to learn more about. Not that I remember too much, but it is a complete different language by now.

I would have thought only dinosaurs like Algol or Fortran can be that old.

Re: 25 Years of PHP

#27
post #6

PHP is damn fast now, no joke. And with all of the modern features it's actually not so bad to work in. I'm becoming increasingly puzzled every time I see PHP hate now, especially when I read tired comments like "just use rails". Laravel is arguably as good or even better than rails at this point, and PHP 7+ is definitely light years faster and lighter. One thing that still sucks is package management / composer.

[deleted]

Re: 25 Years of PHP

#28
post #9

Fine. After 20+ years of PHP development I'm going to give it a shot. Will be attempting to migrate from VSCode. Any tips for that transition in particular, or for setting up PHPStorm in general? I have a subscription to Laracasts and plan on watching that series, but I'm not sure if it's outdated. Thanks!

Local history will save your butt. Right click in a file and see the local VCS. Survives all sorts of external events or losses.

Re: 25 Years of PHP

#29
I started with PHP 15 years ago, but after 5 years I just moved to Java.

The worst thing with PHP was people and standards, everything was a mess, there was no right way to do stuff and larger projects had like 100 different implementations for the same thing. PHP was really challenging to work with as coming to a shared agreement for how one should implement stuff was a recipe for personal conflicts.

So after a few years, I just started to code web applications with Java. A completely different, but much more enjoyable environment and much more friendly people.

I guess PHP is much more fun today, it was really fun to code in PHP as it was really simple and you feel productive and powerful. But in the old days, bad defaults often caused issues in production. And some of the documentation/knowledge sharing was dangerous(tutorials lacked warnings and information about preventing SQL injections).

Re: 25 Years of PHP

#30
post #29

I started with PHP 15 years ago, but after 5 years I just moved to Java. The worst thing with PHP was people and standards, everything was a mess, there was no right way to do stuff and larger projects had like 100 different implementations for the same thing. PHP was really challenging to work with as coming to a shared agreement for how one should implement stuff was a recipe for personal conflicts. So after a few…

Reading this comment it seems JS is the new PHP, culturewise.
Post reply on HN