This is the
talk page for discussing improvements to the
Laravel article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
![]() | This article was nominated for deletion on November 1 2012. The result of the discussion was delete. |
![]() | This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||
|
![]() | Individuals with a conflict of interest, particularly those representing the subject of the article, are strongly advised not to directly edit the article. See Wikipedia:Conflict of interest. You may request corrections or suggest content here on the Talk page for independent editors to review, or contact us if the issue is urgent. |
Hello, Helique! As I've noted in my edit summary, having a section describing Laravel history is really great, but we need references. In the meantime, it's better not to have unreferenced content at all, as the rest of the article is well-referenced so there's no need to degrade the article quality that way. Also, that section will need quite a bit of work on improving the writing style, but I'll take care of that once you provide references. Hope you agree. — Dsimic ( talk | contribs) 07:06, 9 May 2015 (UTC)
I added the 2015 dates for Laracon and my edit was reverted by User:Dsimic with the justification of WP:NOTNEWS. I feel this guideline is not at all intended for this purpose. In fact, the section immediately before that, WP:BALL, explicitly says "Individual scheduled or expected future events should be included only if the event is notable and almost certain to take place" which the 2015 Laracon falls under. Additionally, if you look at the articles for other conventions, the vast majority of them include information about upcoming events. Here are some extremely notable conventions that all list information about upcoming dates:
I do not know of any guidelines in Wikipedia policy against including future dates, and I don't believe WP:NOTNEWS applies here since listing this information is not at all comparable to journalism, news reports, who's-who, or diaries. 217IP ( talk) 03:20, 9 July 2015 (UTC)
Hello, Msnicki! Regarding your edits, please use a search engine to check the notability of Laravel. It's a widely used PHP framework, and we can't expect a Ph.D dissertation about it (or something similar) that could be used as a reference. That's what it is with highly active software projects. Of course, I'm more than open to discussing this further. — Dsimic ( talk | contribs) 16:00, 2 September 2015 (UTC)
Could you, please, provide a couple of excerpts that, in your opinion, "glorify" Laravel in the article? Please don't get me wrong, I want the article to be as neutral as possible, but it's sometimes hard to see issues in something you've been looking at for a long time. :) I'm really thankful for your input, and I'll be more than happy to improve the wording. — Dsimic ( talk | contribs) 17:52, 2 September 2015 (UTC)
According to a March 2015 developers survey on PHP frameworks popularity, Laravel was listed as the most popular PHP framework of 2015based on an unreliable source + numerous overly breathless phrases, e.g.,
Major new features,
a more advanced alternative to the CodeIgniter framework,
a complete rewrite,
Such a layout allowed much better extendibility,
significant changes,
Besides bringing various new features and improvements to already existing ones,
numerous bundled features already available for easy addition to applications, etc, etc. (How many more do you need?) This is the kind of language I expect to read in a vendor's description of their product, not an encyclopedic article here on WP. Msnicki ( talk) 17:59, 2 September 2015 (UTC)
You still have work to do. For example, one of its features is its "expressive syntax"? Doesn't every language have that? The whole thing is still too laudatory. Msnicki ( talk) 16:08, 4 September 2015 (UTC)
What does this mean? Is it actually one of the most popular, or not? If not, who is doing the "regarding"? Equinox ◑ 15:07, 5 December 2017 (UTC)
I came to this article with the hope of learning from where comes from the notions of service containers and service providers in Laravel. They seem to be fundamental notions in Laravel. They are mentioned in all the sections on Architecture Concepts of the Laravel web site: https://laravel.com/docs/5.8/lifecycle, https://laravel.com/docs/5.8/container, https://laravel.com/docs/5.8/providers, https://laravel.com/docs/5.8/facades and https://laraveel.com/docs/5.8/contracts. We even have sections dedicated to these concepts. Here is a quote from the first web page that I found about service provider in Laravel :
Overview. If you‘ve ever used Laravel framework in your project, you will hear about server container and service provider. They are the backbone of the Laravel framework and do all heavy jobs when your application runs.
— https://medium.com/grevo-techblog/service-provider-in-laravel-3b7267b0576e
Yet I believe these concepts existed before Laravel. So, I would have been happy to see something on this subject in the History section. Though, as I said, I came to this article to learn. Dominic Mayers ( talk) 19:40, 11 August 2019 (UTC)
This is the
talk page for discussing improvements to the
Laravel article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
![]() | This article was nominated for deletion on November 1 2012. The result of the discussion was delete. |
![]() | This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||
|
![]() | Individuals with a conflict of interest, particularly those representing the subject of the article, are strongly advised not to directly edit the article. See Wikipedia:Conflict of interest. You may request corrections or suggest content here on the Talk page for independent editors to review, or contact us if the issue is urgent. |
Hello, Helique! As I've noted in my edit summary, having a section describing Laravel history is really great, but we need references. In the meantime, it's better not to have unreferenced content at all, as the rest of the article is well-referenced so there's no need to degrade the article quality that way. Also, that section will need quite a bit of work on improving the writing style, but I'll take care of that once you provide references. Hope you agree. — Dsimic ( talk | contribs) 07:06, 9 May 2015 (UTC)
I added the 2015 dates for Laracon and my edit was reverted by User:Dsimic with the justification of WP:NOTNEWS. I feel this guideline is not at all intended for this purpose. In fact, the section immediately before that, WP:BALL, explicitly says "Individual scheduled or expected future events should be included only if the event is notable and almost certain to take place" which the 2015 Laracon falls under. Additionally, if you look at the articles for other conventions, the vast majority of them include information about upcoming events. Here are some extremely notable conventions that all list information about upcoming dates:
I do not know of any guidelines in Wikipedia policy against including future dates, and I don't believe WP:NOTNEWS applies here since listing this information is not at all comparable to journalism, news reports, who's-who, or diaries. 217IP ( talk) 03:20, 9 July 2015 (UTC)
Hello, Msnicki! Regarding your edits, please use a search engine to check the notability of Laravel. It's a widely used PHP framework, and we can't expect a Ph.D dissertation about it (or something similar) that could be used as a reference. That's what it is with highly active software projects. Of course, I'm more than open to discussing this further. — Dsimic ( talk | contribs) 16:00, 2 September 2015 (UTC)
Could you, please, provide a couple of excerpts that, in your opinion, "glorify" Laravel in the article? Please don't get me wrong, I want the article to be as neutral as possible, but it's sometimes hard to see issues in something you've been looking at for a long time. :) I'm really thankful for your input, and I'll be more than happy to improve the wording. — Dsimic ( talk | contribs) 17:52, 2 September 2015 (UTC)
According to a March 2015 developers survey on PHP frameworks popularity, Laravel was listed as the most popular PHP framework of 2015based on an unreliable source + numerous overly breathless phrases, e.g.,
Major new features,
a more advanced alternative to the CodeIgniter framework,
a complete rewrite,
Such a layout allowed much better extendibility,
significant changes,
Besides bringing various new features and improvements to already existing ones,
numerous bundled features already available for easy addition to applications, etc, etc. (How many more do you need?) This is the kind of language I expect to read in a vendor's description of their product, not an encyclopedic article here on WP. Msnicki ( talk) 17:59, 2 September 2015 (UTC)
You still have work to do. For example, one of its features is its "expressive syntax"? Doesn't every language have that? The whole thing is still too laudatory. Msnicki ( talk) 16:08, 4 September 2015 (UTC)
What does this mean? Is it actually one of the most popular, or not? If not, who is doing the "regarding"? Equinox ◑ 15:07, 5 December 2017 (UTC)
I came to this article with the hope of learning from where comes from the notions of service containers and service providers in Laravel. They seem to be fundamental notions in Laravel. They are mentioned in all the sections on Architecture Concepts of the Laravel web site: https://laravel.com/docs/5.8/lifecycle, https://laravel.com/docs/5.8/container, https://laravel.com/docs/5.8/providers, https://laravel.com/docs/5.8/facades and https://laraveel.com/docs/5.8/contracts. We even have sections dedicated to these concepts. Here is a quote from the first web page that I found about service provider in Laravel :
Overview. If you‘ve ever used Laravel framework in your project, you will hear about server container and service provider. They are the backbone of the Laravel framework and do all heavy jobs when your application runs.
— https://medium.com/grevo-techblog/service-provider-in-laravel-3b7267b0576e
Yet I believe these concepts existed before Laravel. So, I would have been happy to see something on this subject in the History section. Though, as I said, I came to this article to learn. Dominic Mayers ( talk) 19:40, 11 August 2019 (UTC)