Difference between revisions of "Talk:Open Source Projects"

From D Wiki
Jump to: navigation, search
(Vision for this page?)
Line 2: Line 2:
  
 
To me, having a page titled »Open Source Projects« seems somewhat strange, given that there is also a »Libraries and Frameworks« list. Maybe, we should split this page – put libs on the library page, and create a new page for tools? In any case, I think it doesn't make much sense to duplicate open source libraries here. --[[User:Klickverbot|Klickverbot]] ([[User talk:Klickverbot|talk]]) 18:15, 27 November 2012 (CET)
 
To me, having a page titled »Open Source Projects« seems somewhat strange, given that there is also a »Libraries and Frameworks« list. Maybe, we should split this page – put libs on the library page, and create a new page for tools? In any case, I think it doesn't make much sense to duplicate open source libraries here. --[[User:Klickverbot|Klickverbot]] ([[User talk:Klickverbot|talk]]) 18:15, 27 November 2012 (CET)
: IMO it's important to think from perspective of user. If someone wants to look how D source code looks, want to learn something from others code - that's the tab open source projects. It includes *tools* and libraries. Libraries and frameworks are separate thing, when you're looking for code that will do work for you - ideally, you shouldn't care about its internals. It might be opensource or not. But, generally i agree with you, we should do something with this. Now, when we got semantic mediawiki it will be easier to make better categorisation and customization for each use-case.
+
: IMO it's important to think from perspective of user. If someone wants to look how D source code looks, want to learn something from others code - that's the tab open source projects. It includes *tools* and libraries. Maybe you want to look what people do in d and how they made it? It doesn't have to be a library to be worth for looking on it. Libraries and frameworks are separate thing, when you're looking for code that will do work for you - ideally, you shouldn't care about its internals. It might be opensource or not. It might be in D or in C. In my opinion `bindings` is a worse category than opensource projects. If we would have to remove one of them i would opt-in for removing `libraries and frameworks` because it's narrower. I know that programmers are used to removing redundancy, but it's a different layer - user interface layer. Generally i agree with you, we should do something with this. Now, when we got semantic mediawiki it will be easier to make better categorisation and customization for each use-case (opensource or not, library or not, etc.). --[[User:Shd|Shd]] ([[User talk:Shd|talk]]) 19:01, 29 November 2012 (CET)
--[[User:Shd|Shd]] ([[User talk:Shd|talk]]) 19:01, 29 November 2012 (CET)
 

Revision as of 18:19, 29 November 2012

Vision for this page?

To me, having a page titled »Open Source Projects« seems somewhat strange, given that there is also a »Libraries and Frameworks« list. Maybe, we should split this page – put libs on the library page, and create a new page for tools? In any case, I think it doesn't make much sense to duplicate open source libraries here. --Klickverbot (talk) 18:15, 27 November 2012 (CET)

IMO it's important to think from perspective of user. If someone wants to look how D source code looks, want to learn something from others code - that's the tab open source projects. It includes *tools* and libraries. Maybe you want to look what people do in d and how they made it? It doesn't have to be a library to be worth for looking on it. Libraries and frameworks are separate thing, when you're looking for code that will do work for you - ideally, you shouldn't care about its internals. It might be opensource or not. It might be in D or in C. In my opinion `bindings` is a worse category than opensource projects. If we would have to remove one of them i would opt-in for removing `libraries and frameworks` because it's narrower. I know that programmers are used to removing redundancy, but it's a different layer - user interface layer. Generally i agree with you, we should do something with this. Now, when we got semantic mediawiki it will be easier to make better categorisation and customization for each use-case (opensource or not, library or not, etc.). --Shd (talk) 19:01, 29 November 2012 (CET)