Windows or Linux Hosting?

[GHOwner]

wow..that's real L A M E reason you got there.

omg..Facebook doesn't share their source code..i'll never use it.
wtf..i dont have the source code of google search engine..f 'em..boycott google.

have some solid argument next time.

That makes so sense, maybe you should have knowledge of what people are talking about before you open your yap, for your message was inaccurate, horrible reference, and rude. Your examples are 3rd-party only services, and not end-user software. Software that can be easily configured in the backend is a plus, where as closed source limits ability to customize. So, Linux is a plus in that area, but Windows Server does have a bigger user-friendliness factor as well as some other advantages (and disadvantages). deuterium does give an example of a pro, but I don't really care to bother analyzing the OS's in my post.

Be less childish and more knowledgeable next time.

vBulletin is technically closed source.

You can view, read, and change the source code on a human level (a high level programming language, even) and thus is not closed source. Being a paid product, if that's what you were referencing, does not mean it is closed source.

[Sador]

You can view, read, and change the source code on a human level (a high level programming language, even) and thus is not closed source. Being a paid product, if that's what you were referencing, does not mean it is closed source.

Doesn't open source technically mean you can see, modify ánd spread the (edited) code? As far as I know, you're only allowed to see the (source)code when you payed for it, which doesn't seem to make it open source in my opinion.

I might be wrong, of course.

[ChopSuey]

YOu may not edit the original vB Files, breakin license agreement.

[Shamil.]

I dont think it is?

I can see the source code just fine and modify it as needed

You can view, read, and change the source code on a human level (a high level programming language, even) and thus is not closed source. Being a paid product, if that's what you were referencing, does not mean it is closed source.

That's visible source, not open source.

Open source refers to:


1. Free Redistribution
2. Source Code
3. Derived Works

as the main 3. vBulletin only satisfies condition 2.

[beishe8]

YOu may not edit the original vB Files, breakin license agreement.

You may edit them but because of them, you might lose official support until the edits are there.

[mcrider]

YOu may not edit the original vB Files, breakin license agreement.

You can edit the original files you just are not allowed to distribute any of the original code.

If you weren't allowed to edit the original files many custom modifications would have been impossible especially before the hook system.

[BoyStav]

I use windows 2008 web on all my servers, it's stable and fast. I have tried to use linux server for deploy php sites, but close in month because windows easy to configurate and support!

[rEd86]

Can anyone direct me to documentation and best practices on installing vBulletin 4.x in a Microsoft Windows/SQL Server environment? I'd would like to run some of my own tests and see what I find out.

Thanks!

--Ed

[Shamil.]

Can anyone direct me to documentation and best practices on installing vBulletin 4.x in a Microsoft Windows/SQL Server environment? I'd would like to run some of my own tests and see what I find out.

Thanks!

--Ed

There is no good documentation, but, http://php.iis.net and http://www.mysql.com . Download and run Web PI, upgrade to PHP 5.3 (VC9), install MySQL as developer instance, and it just works

vBulletin doesn't support MySQL, hence I'm still considering moving to IPB.

[Mark.B]

vBulletin is not closed source, but neither is it open source, it is "visible source".

[jmurrayhead]

vBulletin doesn't support MySQL, hence I'm still considering moving to IPB.

Correction: vBulletin doesn't support MS SQL

[rEd86]

Correction: vBulletin doesn't support MS SQL

Seriously? Wow. I can see back when Jelsoft was developing it they wouldn't have supported MS SQL with limited resources but once IB acquired it, I assumed they would have implemented support for it by now. I was hoping to leverage some of the reporting tools that are built into MS SQL. I am sure there are equivalent solutions for mySQL but we don't have the in-house expertise with that like we do with MS SQL.

Hmmm. Going to have to rethink some things.

--Ed

[punchbowl]

windows=localhost
linux=live

[rEd86]

windows=localhost
linux=live

yourpost = cryptic

I have no idea what point you are trying to make with that post. If you're saying that Windows is an inferior OS to Unix, let's not get into that heated/useless debate here, not helpful. The question at hand is what best practices are there for hosting in a Windows environment.

--Ed

[punchbowl]

Information overload? I use linux hosting. Is that not obvious?

The thread title is "Windows or Linux Hosting?" not "The question at hand is what best practices are there for hosting in a Windows environment."btw.