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

PHP template engines #42

Closed
4rterius opened this issue Mar 21, 2017 · 5 comments
Closed

PHP template engines #42

4rterius opened this issue Mar 21, 2017 · 5 comments

Comments

@4rterius
Copy link

Yeah, I know many people dislike PHP, but if somebody decides to learn it, shouldn't they at least know about template engines like blade, smarty, twig, etc.?

@mahald
Copy link

mahald commented Mar 22, 2017

my advice if u want to learn web development today:
forget about server-side templates engines MVC and such old shit ... Learn angular (angular.io).
the server side should only speak GraphQL inbound and json outbound (And use JWT for auth). and nothing else.

@4rterius
Copy link
Author

Well, deciding whether PHP is dead or not is not the point of this issue. There are two opposite opinions on the topic, and we seem to stand on different sides.
Hovewer, since PHP

  • is mentioned in this roadmap
  • is still one of the top-10 most popular languages in the world (proof link),

addition of several template languages doesn't seem a very bad idea, at least for me. We also shouldn't forget that "old" technologies happen to return back eventually, so... Why not?

@Gmacky2
Copy link

Gmacky2 commented Mar 22, 2017

The point and click worked betert

@mahald
Copy link

mahald commented Mar 22, 2017

php is prefectly fine, but "server-side template engines" are a technologie that is outdated.
so using a template engine with php is a bad idea to learn nowadays.
angular is the (by far and by many reasons) more modern approach, and there it's pure client side.

@kamranahmedse
Copy link
Owner

Hi @rakhack,

Thank you for reporting but this repository focuses more on the core development technologies; if you don't learn templating engines, you can still go-by. Plus if you look at 2017, there are mostly SPAs and stuff and I think it would be fine if you don't want to learn templating engines.

Thank you though.

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

No branches or pull requests

4 participants