Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do Yii3 would provide SPA turn key solutions? #90

Open
ScottHuangZL opened this issue Dec 4, 2020 · 6 comments
Open

Do Yii3 would provide SPA turn key solutions? #90

ScottHuangZL opened this issue Dec 4, 2020 · 6 comments

Comments

@ScottHuangZL
Copy link

ScottHuangZL commented Dec 4, 2020

Hi Yii Team,

I really like Yii1/2 which is enable people to build traditional web application easily and robust.
We have plenty of widgets (or Kartik extensions) which were well designed and can use out of box.

SPA is more and more popular in these days. There are different approaches by different framework, such as .Net use Blazor.
Or GoLang use REST+Frontend, or some people create "gin-vue-admin" to try auto generate code to easy the developments. (Some kind like Yii Gii).

The strength of Yii framework is help user to both write frontend & backend code at same framework with high productivity, the feeling is good. Or else, if we have to split as 2 set, then people have lots of other choices, such as use Go/.Net/Java for backend, and Vue(Quasar framework look good)/React/Angular for frontend. As you know PHP speed is slow from backend perspective, the conveniences are the most attracting features.

Do Yii3 plan provide SPA turn key solutions? Such as leverage Vue or React or jQuery/AJAX or whatever to enable users build single page application easily just like before we build traditional web with widgets?

Thanks for your consideration and support in advance.

Regards,
Scott Huang

@rustamwin rustamwin added the type:feature New feature label Dec 4, 2020
@samdark
Copy link
Member

samdark commented Dec 4, 2020

Do Yii3 plan provide SPA turn key solutions?

There's a possibility but right now we focus on the backend. After it's more or less released we'll see what we can do.

Overall I tend to either build PHP-only HTML-generating traditional apps or APIs consumed by client-side projects. Both these cases are more or less covered right now:

@ScottHuangZL
Copy link
Author

Thanks for update, let's wait and see, thanks.

@garrettw
Copy link

garrettw commented Oct 13, 2024

I would like to see this as well. Specifically, I think having a first-party package to add backend support for Inertia.js would give Yii3 an incredible leg up and, let's be honest, Laravel is the elephant 😉 in the room and supporting the same stuff it does is basically necessary to be considered a contender these days.

I've been doing some development in recent months on an app using Laravel + Inertia + React + TypeScript (having no experience with any of those except Laravel starting out), and it's been pretty fun to learn. I would love to be able to build React/Vue apps with Yii3! (Granted, in addition to the supporting library, an app template would honestly be needed as well.)

(On that note, I think Yii also needs to be able to basically copy the ideas of Sail, Breeze, and Jetstream in its own way.)

@ScottHuangZL
Copy link
Author

ScottHuangZL commented Jan 8, 2025

One Python framework NiceGUI leverage FastAPI + Quasar(Based on Vue3), that NiceGUI try to have a thread to looping backend and do some dirty and quick "SPA", this portion need improved as react style if possile. But in short, it still ramp up quickly and eat some markting place from Streamlet and so on. Appreciate Yii3 able develop similar "SPA" functions ASAP. And to be frankly, I still not use Yii3, do it ready now?? Thanks.

Btw, dotnet C# Blazor looking nice. But it is too challenge for Yii3 if try mimic Blazor :)

@samdark
Copy link
Member

samdark commented Jan 9, 2025

We don't have any backend looping and actually do not plan to. There were numerous frameworks like that in the past, and there are too many now with different approaches. That means:

  1. Choosing one, we'll likely stick to it. That would be the same story as Yii2 and jQuery (the only popular approach back then) i.e. frontend may (and likely will) move to another direction, and we'll have to maintain a solution that's not the top-notch anymore.
  2. Yii is meant to cover backend needs with some exceptions: server-side content generation such as https://github.com/yiisoft/yii-bootstrap5 and other very lightweight integrations with frontend stuff. Overall, we don't want to go into frontend. We're not experts there.

@ScottHuangZL
Copy link
Author

Thank you @samdark for your clarification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants