[LIVE #15] New Laravel VS Code Extension, URI Parsing, and more...

[@getupkid84]

Tbh, I've always steered clear of PHPStorm. It is super resource intensive. Way too many bells and whistles. I've always preferred VSCode even for PHP. Looking forward to using this extension.

[@object-orientedprograming6709]

We need a theme extension to make the code as the code in docs

[@fhoulbr]

For me it is still PHPStorm ;)

[@sean_reyes]

is the vs-code extension open-source?

[@azrahnvazkor4597]

yes

[@isaachatilima]

Is it better than Laravel idea on phpstorm?

[@adisonmasih]

no. and i doubt it will ever be; laravel idea even supports livewire, volt, flux, inertia and much more libraries compared to this. but considering laravel idea and phpstorm are paid products, the vs code extension is promising.

[@edism]

Yes you need to support every front end adaptor library including those you don't use ​@@adisonmasih

[@adisonmasih]

​@@edism not sure if what you meant was sarcasm, but if it was, just want to say that livewire and inertia are probably one of, if not the most used libraries inside the laravel ecosystem. not including them in the vs code extension is not a wise choice if you wanna compete with laravel idea in future.

[@edism]

@@adisonmasih if you let popularity validate your stack then why not use next on Vercel? Eg. If you're using inertia in your project you're not going to need volt etc.

[@etiennez0r846]

I need the tl; dr 🥲
also would be good to know more details on your composer commands