Don’t judge PHP by what you saw in WordPress. Modern PHP is amazing, WordPress had horrible code when it started and they definitely didn’t fix things afterwards. It’s a horrible slow mess of a code. Look at some modern PHP (for example this api of mine ) to compare.
Ah enjoy your single thread. I’ll be there writing writing kick ass code in rust and wondering about important stuff like… err… who owns that fucking variable…
The best tool is the best tool for the job. My php code was immaculate - import header, write your content, import footer. I wrote it all in a few hours, and I think my university is still using it today. One of my proudest moments was when a team member whose abilities I respected gushed over how easy my code was to work with
I haven’t used it since.
I’m led to believe modern PHP has become pretty good. It’s also never been the right tool for the job since then
Mojo sounds incredible - python is a beautifully consistent language, and I’ve written a shit load of it. I like it a lot. It’s often not the right tool for the job, but mojo promises to turn it into something extraordinary that shores up its weaknesses… It’s just promises so far though, I really hope they pan out
But always ask yourself - what’s the right tool for the job?
Don’t judge PHP by what you saw in WordPress. Modern PHP is amazing, WordPress had horrible code when it started and they definitely didn’t fix things afterwards. It’s a horrible slow mess of a code. Look at some modern PHP (for example this api of mine ) to compare.
Thanks for sharing a modern php codebase. It makes me confident that giving it up and switching to Python was the right choice.
lol
Ah enjoy your single thread. I’ll be there writing writing kick ass code in rust and wondering about important stuff like… err… who owns that fucking variable…
Cool story. Rust didn’t exist when I switched from php to Python.
Imagine going to the slowest and ugliest interpreted language there is and feeling superior about it.
Like, modern Python is basically what PHP was at its lowest point, PHP 4 (20 years ago).
No, it’s worse. PHP never had shit like virtual environments and a million different incompatible package managers.
Virtual environments are a great thing.
I’d argue that the concept of isolated environments is great. Python’s implementation… leaves something to be desired.
It’s still a bit hacky, even in Python 3. Tools like
uvandpdmexist in the gaps to smooth it out.That said, it’s something that the core community is actively working on and it’s not something users will face day to day.
I say this as someone who moved from PHP 3 to Python 2 to Ruby to PHP 6+ to Python 3 as their goto language over the years.
Hahahahaha. Are you seriously defending crap like __autoload and package management built on top of that hack?
Mojo is what is keeping me vindicated that python was a good choice. That and it’s worked for every project I’ve ever used it for lol
But that’s small potatoes in the technologist game
The best tool is the best tool for the job. My php code was immaculate - import header, write your content, import footer. I wrote it all in a few hours, and I think my university is still using it today. One of my proudest moments was when a team member whose abilities I respected gushed over how easy my code was to work with
I haven’t used it since.
I’m led to believe modern PHP has become pretty good. It’s also never been the right tool for the job since then
Mojo sounds incredible - python is a beautifully consistent language, and I’ve written a shit load of it. I like it a lot. It’s often not the right tool for the job, but mojo promises to turn it into something extraordinary that shores up its weaknesses… It’s just promises so far though, I really hope they pan out
But always ask yourself - what’s the right tool for the job?
Nice code, good job!