I’ve become the primary maintainer of a jumbled mess of a PHP/Laravel project we use as our"mission control" at work and I’ve been dying due to lack of dev tools. Might have to take a look at this (pester my manager for a license) assuming it has Laravel support.
I don’t do PHP. But I used other JetBrains tools for Go, Python and Java and they are very helpful. The AI Assistant is pretty good for explaining code. I am not in anyway paid by them. Good Luck
That article makes little sense. There is not a non-php version of WordPress at this time. I know Gutenberg uses Node and NPM, but the heavy lifting is still PHP. There has always been client side scripting and server side scripting with WP. I’ll buy that devs are lobbying clients to use something else, but to say this is because WordPress is driving the change can’t be right.
It is far more likely that this is from the rise of “sexier” server-side coding languages like Rust. Now I don’t know much about Rust (although I will look into it more) but I a bit of Googling on Rust vs PHP a while back and PHP is still a solid choice for a lot of things and there seem to be a lot more people out there who can code in it, making it a.good choice for FOSS projects.
Here’s hoping you have Docker installed, because Laradock rules. (It’s not just for Laravel.)
If the project is a Laravel project, Laravel Herd just came out. If you’re on a Mac, there’s also Valet. If you prefer a VM, there’s Homestead - a PHP Vagrant config.
Great that it worked out, did you use apt remove or apt purge?
You might want to put your code in triple back ticks so it renders as code block :) Currently isn’t visible on some clients (boost for Lemmy in my case)
I don’t have a solution, but wanted to comment this is a reason to use docker. Instead of tinkering with your host system in ways you’ll probably forget, declare all the steps in a nice containerized system that does one thing: hosts a php website as you develop.
Expose your project through a volume for a mostly seamless file sharing experience between the host and container.
No Data Checking: It directly uses data from an API without checking if it’s safe or correct.
Dynamic Properties: Adding properties to an object on the fly can make the code hard to manage.
External Data Dependency: Relying on API data structure without checks can lead to issues if the API changes.
If you don’t know the data is safe (it’s not), it’s a lot better to use an associative array. Additionally, if it’s from a json, it’s quicker and easier to iterate over array. Don’t make it complicated for no reason.
Final keywords–like locks on a door–are just a suggestion. If someone wants to light a stick of dynamite and play hot potato with it, that’s their own problem. As long as they aren’t wasting upstream dev’s time or publishing packages that depend on this to work, it’s not worth getting upset about.
I hate JavaScript, along with the whole of web 2.0 and moving shit around as it loads, making the user wait to input rather than taking the input and processing as quickly as possible, and in general the whole theme of software no longer being designed for the user to use but for the publisher to extract value from the user.
php
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.