|
No, just as PHP coders don't always show their source.
I'm saying languages maintained by the community.
Brad
Australian
By contacting your lawyer you negate the right to sue me.
|
|
|
|
|
The site is Microsoft-centric. In fact that's one of its biggest selling points - the fact that it's specialized towards Microsoft-technologies, and thus attracts articles on those specific topics. It also results in a membership base that almost exclusively works on Windows and .NET technologies. Bringing Php, Java, Mainframe COBOL, etc. would dilute the content and deviate from the core target audience. I don't see any reason why the management of the website or its membership base would want that to happen.
|
|
|
|
|
Your statements carry some truth, but I don't think you would find .Neters leaving because of a PHP/Whatever forum. If anything we might bring over a few coders that will be able to contribute some general purpose articles that we otherwise would not have gotten.
In addition I think that it would be beneficial to anyone who wanted to learn a couple extra languages.
In short I don't think we would lose anyone, only gain a few new members.
Brad
Australian
By contacting your lawyer you negate the right to sue me.
|
|
|
|
|
Nishant Sivakumar wrote: it's specialized towards Microsoft-technologies
Let's keep it that way 
Some people have a memory and an attention span, you should try them out one day. - Jeremy Falcon
|
|
|
|
|
Nish,
I agree with everything you said, but at the same time I would like to learn about other technologies, such as PHP. Doing a quick search for PHP showed that there were already several articles about PHP here on CP, and so I think that sometime in the future (maybe not now) the number of PHP articles would merit its own section.
I thought it was interesting that your post said "Windows and .NET technologies", rather than (for example) "Windows and C# technologies". Why is Nish linking Windows with a framework, when the OP was talking about a language? I wondered. One of the reasons I keep coming back to CP is that (so far at least) it is not exclusionary. I can read articles about .Net, and then read an article about ATL or MFC. In fact, it would be reasonable to rename the "C++ Libraries" section to "Frameworks", with ATL, WTL, MFC, and .Net as subsections, since all of them have one thing in common: a Win32 base.
Best wishes,
Hans
|
|
|
|
|
I think it is a VERY bad idea of moving all web stuff to ASP.NET/AJAX area. For example, HTML and CSS have nothing (or little) to do with it.
I understand your idea of joining all web things into one, but old name of the section (Web/Scripting) seems much more correct.
Best regards,
Dmitry.
-- modified at 9:17 Saturday 25th November, 2006
-------------------------
Don't worry, be happy  )
|
|
|
|
|
I think it should be all moved into the Web Development forum.
Brad
Australian
By contacting your lawyer you negate the right to sue me.
|
|
|
|
|
If you select ASP/ASP.NET in the Most Popular Articles section there are probably 10-20 articles that are duplicated.
E.g.:
1. asp.net popup control
2. asp.net popup control
(both link to the same article)
This is happening for various articles on all five pages. So you probably only get to see the top 80 asp.net articles, not the top 100.
"For fifty bucks I'd put my face in their soup and blow." - George Costanza ~ Web SQL Utility - asp.net app to query Access, SQL server, MySQL. Stores history, favourites.
|
|
|
|
|
Thanks Ashley. I'll add it to the TODO.
-- modified at 18:46 Monday 27th November, 2006
Should be fixed now
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
In my opinion, VB.NET forum is more compatible with C# one...
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
|
|
|
|
|
cpallini wrote: VB.NET forum is more compatible with C# one.
i second that
|
|
|
|
|
I disagree.
It is vital that all VB users be quarantined in the VB forum upon first arriving. Once they are able to prove themselves free of disease, they may be allowed into other forums suited for their abilities, such as "ASP.NET", "SQL / ADO / ADO.NET" and "Subtle Bugs", until such a time as they have gained sufficient strength of body and mind to live in harmony with a wider populace. Splitting the VB forum would encourage premature travel, and doubtless expose the good citizens of CodeProject to many a dread lurgy. Also, the necessity of hastily burning infected bodies would soon pollute the site with the foul smoke of deceased VBers.
A wholly undesirably situation, i'm sure you'll agree.
To show that we are not without sympathy for those of the VB persuasion, i suggest an alternate plan: the construction of a wall between the VB forum and the C# one. With neither gates nor windows, nor flaws that might allow hands to find purchase. Solid, ten cubits high, and a full cubit thick, widening as it rises, and with barbed wire strung across the upper portions thereof. Such a noble construct would then relieve the wretched VBer of the tormented spirit that comes with accidental observation of one's betters. In lieu of verbal expressions of gratitude, a tax may be levied on those poor souls and the resulting revenue used to recoup the expense of construction, as well as that of a large plaque, wrought of bronze and richly engraved, honoring myself and making careful note of the date and time upon which this suggestion was freely gifted to the CodeProject community.
|
|
|
|
|
|
Shog9 wrote: A wholly undesirably situation, i'm sure you'll agree.
yes i agree but
Shog9 wrote: encourage premature travel,
1) they are already doing it
2) basic idea is is to separate the two like (Visual C++ / MFC) & ((Managed) C++/CLI)
because a vb coder might get vb.net answer and vice versa
and they will get enough number of supporters
instead it should be separated as (vb.net) & (visual basic / vba)
the fact is that they are quite different to be categorized as one
|
|
|
|
|
Shog9 wrote: To show that we are not without sympathy for those of the VB persuasion, i suggest an alternate plan: the construction of a wall between the VB forum and the C# one. With neither gates nor windows, nor flaws that might allow hands to find purchase. Solid, ten cubits high, and a full cubit thick, widening as it rises, and with barbed wire strung across the upper portions thereof. Such a noble construct would then relieve the wretched VBer of the tormented spirit that comes with accidental observation of one's betters. In lieu of verbal expressions of gratitude, a tax may be levied on those poor souls and the resulting revenue used to recoup the expense of construction, as well as that of a large plaque, wrought of bronze and richly engraved, honoring myself and making careful note of the date and time upon which this suggestion was freely gifted to the CodeProject community.
That's a fine piece of writing. Where did you learn to write like that?
|
|
|
|
|
VB6 is obsolete. The forum should be renamed to just VB.Net, and any VB6 specific questions ignored or derided.
|
|
|
|
|
All VB stuff on this site should be deleted. - No, wait... That would result in a reduction in membership to around 30,000...
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
John Simmons / outlaw programmer wrote: All VB stuff on this site should be deleted.
I don't imagine it would be missed either 
|
|
|
|
|
John Simmons / outlaw programmer wrote: All VB stuff on this site should be deleted.
If that happened, all those 'programmers' ( cough.. splutter.. cough.. ) would spread out on the internet infecting all those that come close. At least here they are quaranteened.
We could however try renaming it to VBS ( expanding the acronym would probably get me banned )( from the VB forum  )
|
|
|
|
|
Well, instead of eliminating VB, CP could just deprecate it - you know, like MS decided to do with CRT string functions, that are still part of C++ standard.
|
|
|
|
|
Rob Graham wrote: VB6 specific questions ignored or derided
I don't like this kind of discrimination.
Moreover, we don't need to be stuck in the cooler language to get interesting questions.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
|
|
|
|
|
Rob Graham wrote: VB6 is obsolete. The forum should be renamed to just VB.Net, and any VB6 specific questions ignored or derided.
What about the people who still use it? You can't just ignore them, especially if they're writing business software.
|
|
|
|
|
MatrixCoder wrote: What about the people who still use it? You can't just ignore them, especially if they're writing business software.
Why not? MS ignores the unmanaged C++ developers...
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
John Simmons / outlaw programmer wrote: the unmanaged C++ developers...
There's no such thing as unmanaged code, John, I'd expect you to know that. It's their 'self managed', or it's managed by a framework that takes that control away from you.
Actually, even that's not true, you need to do your own memory management in managed code, too.
Christian Graus - C++ MVP
'Why don't we jump on a fad that hasn't already been widely discredited ?' - Dilbert
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
