You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is obvious that there was no testing done using MariaDB. Otherwise I would not have received an error of all kinds. I am trying to remove one by one but later I was not able to seed. Following ar the files that are not compatible on MariaDB.
One of the biggest drawback of Laravel is a wild development by the core team. They deliver raw and half cooked food. This causes all other developers lag in their testing and development in multiple areas throwing hundreds of other projects lagging behind in development.
Laravel core team also suffers from a syndrom that only developers and highly qualified professionals could use it. It does not allow most kind of user-friendlyness. They have failed to deliver core areas that are developed and made available by some user-friendly approach. All they deliver is something that can be achieved with a huge learning curve. Thus all other users are dependent of such similat boiler plates.
The above area is one of them. Even a simple boilerplate crashes. It the main framework had certain detections, such a development wouild have never occured.
Thanks.
The text was updated successfully, but these errors were encountered:
Hello!
It is obvious that there was no testing done using MariaDB. Otherwise I would not have received an error of all kinds. I am trying to remove one by one but later I was not able to seed. Following ar the files that are not compatible on MariaDB.
Please test:
One of the biggest drawback of Laravel is a wild development by the core team. They deliver raw and half cooked food. This causes all other developers lag in their testing and development in multiple areas throwing hundreds of other projects lagging behind in development.
Laravel core team also suffers from a syndrom that only developers and highly qualified professionals could use it. It does not allow most kind of user-friendlyness. They have failed to deliver core areas that are developed and made available by some user-friendly approach. All they deliver is something that can be achieved with a huge learning curve. Thus all other users are dependent of such similat boiler plates.
The above area is one of them. Even a simple boilerplate crashes. It the main framework had certain detections, such a development wouild have never occured.
Thanks.
The text was updated successfully, but these errors were encountered: