5 ms·

You say > medium quality framework with many flaws Yet you only point out > you can't autocomplete normally with an IDE > You won't see methods that you may

You say > medium quality framework with many flaws Yet you only point out > you can't autocomplete normally with an IDE > You won't see methods that you may call Firstly if there are "many flaws" list them because it seems you only don't like the developer experience with the autocomplete. I noticed no problem with browsing the Laravel API [0] with my short adventure with it. > framework is 10-100 times slower than others citation needed. Also you didn't mention what you tried to use it for but remember software engineers are paid to pick the right tool for the job, Laravel is not the top pick for highly-concurrent idempotent microservice on Kubernetes, it's for monolithic app replacing that old WordPress installation without changing the tech stack [0]: https://laravel.com/api/8.x/index.html https://laravel.com/api/8.x/index.html

gremlinsinc 6y ago
> Laravel is not the top pick for highly-concurrent idempotent microservice on Kubernetes, Taylor Otwell would like to introduce you to Larvel Octane, i.e. support for swoole/workerman with 6k+ reqs per seq on a basic desktop. Laravel with swoole basically makes it as performant as elixir/phoenix.
- cutler 6y ago
  But do you have to rewrite all your code async-style? And what are the implications for using non-async PHP libraries?
  - gremlinsinc 5y ago
    Presumably, you pick/choose which would use swoole or be delivered on php-fpm maybe run both with nginx proxying swoole, then your old code would just run sync and newer could run async if required --maybe for things like chat/websockets and not for just static pages.