Talk:Comparison of browser engines: Difference between revisions

Content deleted Content added
Criteria for being an 'engine': modify comment for archived thread
move criteria thread to top
Line 4:
}}
{{Archives}}
 
== Criteria for being an 'engine' ==
 
This is in response to the end of [[Talk:Comparison of browser engines/Archive 2#Inclusionist vs deletionist|an archived thread]] about the criteria for what should be considered an engine. In principle it's not that hard to define. The [[browser engine]] article already does a good job of this, though what's covered there is most applicable to the mainstream engines (which collectively account for over 99% of actual browser usage).
 
It's a bit trickier for the tiny niche hobbyist projects, like NetSurf and LibWeb. The consensus reached abovein the archived thread on NetSurf is a good guideline, in that the set of libraries and components that can be called an "engine" could, in theory, be used by another group of hobbyists to make a different browser. This is, after all, at the heart of what a software engine is: a large component that can be reused for a different software project. However, the nature of these types of hobby projects is heavily DIY: the lure of designing and implementing their own new thing is what tends to motivate them. But this doesn't invalidate the design of the software to feasibly be reused by a different project (even if that never actually happens). --[[User:Pmffl|Pmffl]] ([[User talk:Pmffl|talk]]) 02:17, 1 September 2023 (UTC)
 
== Adding Eww (Emacs web browser and engine)? ==
Line 45 ⟶ 51:
:::As for the other item, a second table is not a good idea. Only stuff that's actually relevant to the current websites (especially the big ones, like Alexa top 1000) belongs in those tables. -[[User:Pmffl|Pmffl]] ([[User talk:Pmffl|talk]]) 02:07, 17 February 2024 (UTC)
::::Again, this doesn't justify making the blanket statement "everything Google does is part of the web and everything it doesn't do isn't", and it definitely doesn't justify not having a second table of less common standards. //[[User:TalyaNe|Talya]] - [[Special:Contributions/TalyaNe|My contributions]] - [[User talk:TalyaNe|Let's talk]]// 05:32, 17 February 2024 (UTC)
 
== Criteria for being an 'engine' ==
This is in response to the end of [[Talk:Comparison of browser engines/Archive 2#Inclusionist vs deletionist|an archived thread]] about the criteria for what should be considered an engine. In principle it's not that hard to define. The [[browser engine]] article already does a good job of this, though what's covered there is most applicable to the mainstream engines (which collectively account for over 99% of actual browser usage).
 
It's a bit trickier for the tiny niche hobbyist projects, like NetSurf and LibWeb. The consensus reached above on NetSurf is a good guideline, in that the set of libraries and components that can be called an "engine" could, in theory, be used by another group of hobbyists to make a different browser. This is, after all, at the heart of what a software engine is: a large component that can be reused for a different software project. However, the nature of these types of hobby projects is heavily DIY: the lure of designing and implementing their own new thing is what tends to motivate them. But this doesn't invalidate the design of the software to feasibly be reused by a different project (even if that never actually happens). --[[User:Pmffl|Pmffl]] ([[User talk:Pmffl|talk]]) 02:17, 1 September 2023 (UTC)