In such a situation, one creates an abstraction of files. That's how one gets files in the first place.
But yes, your point makes sense. In Rosetta Code, it wouldn't make sense to create a file abstraction for programming languages which don't support file I/O inherently. However, it would make sense to provide a programming example which makes use of a library which provides that abstraction.
The reason for the wikispam is an SEO contest...a kind of contest where one wins by having the highest search engine rankings at the end of the contest. The contest mentioned specifically points to Wikipedia as a resource.
So, to recap:
The spammers are participating in a contest.
To win the contest, you must have the highest rank in search engines.
Adding nofollow to links removes Wikipedia's value as a tool in raising one's pagerank, which removes it's primary value to the wikispammers participating in the contest.
Just out of curiosity, why not? And what would you suggest instead? A Wiki is essentially just an editable website. It must be manually ordered; tables of contents put in, pages linked to other pages, and so forth. I make use of as many MediaWiki features as I know how. There's one template for programming languages, one for compilers, one for interpreters, one for programming tasks, etc. Adding the template to a new page automatically adds the page to the related category, and the category index pages are the primary tool for browsing the site.
In short, our Tables of Contents are automatically updated for us by the wiki engine. It's cool.
This is find for data that has a very general structure, such as an encyclopaedia or a manual of some kind. But the Rosetta Stone concept is highly structured, cross-referencing programming languages with programming problems, and it seems to me as if this cross-referencing would be better done automatically, rather than making several Wiki pages and maintaining them manually. The site concept would be better suited to some sort of customised CMS, or perhaps something designed from scratch. The benefit of using a wiki, and why I chose to use it, is that in each of these intermediary pages, one can place descriptive information about the relationship. The net effect is that an encyclopedia forms around the structured data. This has only happened in a couple places, such as the page about LAMP, and the page about GCC, but it's something I want to see continue.
Every mention of a language, compiler, interpreter or platform comes with a hyperlink to a page specifically about that tool. So if one wants to learn about GCC, one can click on the appropriate link, or type it in the search field. If one wants to learn about Haskell, one can click on Haskell's link.
I have no problem with criticism. It tells me how I can improve.
The exposure has pointed me to several other sites and projects with similar aims. I won't rip code off, but I will be investigating how they run their projects.
Slashdot Mirror
In such a situation, one creates an abstraction of files. That's how one gets files in the first place.
But yes, your point makes sense. In Rosetta Code, it wouldn't make sense to create a file abstraction for programming languages which don't support file I/O inherently. However, it would make sense to provide a programming example which makes use of a library which provides that abstraction.
Check out this page. That'll be the basis of browsing the site soon. :-)
Is she single?
No, the average girl is already married.
Check now: C, C++, Java, C#. No VB implementation yet, oddly enough. I wonder what language Slashdot users don't touch often...
Tried sending you an email. Rosetta Code's been up for a couple days now. It's all I've been able to do to keep up with all the users. :)
You might think that the average person wouldn't stand for it. But I recall someone once saying the "average person" is 5' tall, female, and Chinese.
While China may only house 15-20% of the world's population, that's still a huge fraction. That would be one hell of an astroturf.
So, to recap:
When is a link to a clothing store a "spam link", and when is it an example or cited resource?
Stop by blog.rosettacode.org. I'll make an announcement there.
Too bad it didn't cache the CSS.
We'll be back up some time today. I just need to get back into the server and tweak the database settings.
Wow. Eerily similar. I left a message on their Sysop's talk page mentioning my site, and asking for pointers on setting up infrastructure.
I'm going to have to add a links page to RC.
Someone didn't know what was required for #1.
We'll be back up some time today.
At the moment, it's a PHP misconfiguration on the server. Hopefully, this will be taken care of tomorrow morning.
Updates will be at blog.rosettacode.org.
This will hopefully be fixed soon. :-(
That's actually the page that inspired the site.
I have a really hard time developing using software I didn't write. Believe me, if it was possible, I would have written custom software.
But, being a full time college student only halfway through to his Bachelor's, I have neither the time nor the skills.
In short, our Tables of Contents are automatically updated for us by the wiki engine. It's cool. This is find for data that has a very general structure, such as an encyclopaedia or a manual of some kind. But the Rosetta Stone concept is highly structured, cross-referencing programming languages with programming problems, and it seems to me as if this cross-referencing would be better done automatically, rather than making several Wiki pages and maintaining them manually. The site concept would be better suited to some sort of customised CMS, or perhaps something designed from scratch. The benefit of using a wiki, and why I chose to use it, is that in each of these intermediary pages, one can place descriptive information about the relationship. The net effect is that an encyclopedia forms around the structured data. This has only happened in a couple places, such as the page about LAMP, and the page about GCC, but it's something I want to see continue.
That's one of the reasons the "User Output" task specifies the output text to be "Goodbye World!"
I'm waiting for DNS to propagate to our new server. :-/
Every mention of a language, compiler, interpreter or platform comes with a hyperlink to a page specifically about that tool. So if one wants to learn about GCC, one can click on the appropriate link, or type it in the search field. If one wants to learn about Haskell, one can click on Haskell's link.
Meta has been very helpful. Of course, I hadn't referenced it in how to set up a proper server...
The server load average at the moment is 178.35, 153.35, 143.98. I don't think Dreamhost wants me any more.
I have no problem with criticism. It tells me how I can improve.
The exposure has pointed me to several other sites and projects with similar aims. I won't rip code off, but I will be investigating how they run their projects.
I'll add a link to your site, if you like. Really, though, I'd like to see your code and tasks included on RC.
I'm following up on an offer to move the site to a faster, dedicated server. We'll see how it works out. :-)