bjrn

I'd keep away from eXeem. It is a windows only, closed source, adware (possibly also spyware) app. It's also locked so you will only be able to use it with SuprNova, not any other torrent sites. A short summary of Bad Things about eXeem. There is also someone paying Sloneck (the guy who ran Suprnova, and now is developing eXeem), but he won't say who. I don't trust it. I'll stick with normal bittorrent. There are enough other torrent sites still up, like Bi-torrent and a big list of sites called Orb's Torrent Site Status.

I remember that a few years ago MySQLs philosophy was that the relationships were the responsibility of the application, not of the database. Meaning that the integrity had to be checked by the app.Seems like they've changed it now. Which is nice. Having to check integrity with your application was a major annoyance.

I use Maxthon and Firefox. Firefox shouldn't need an introduction, but I can say a few words about Maxthon. Maxthon is a browser which uses the IE core and basically improves IE quite a lot. It has tabbed browsing, search from the address bar, ad and pop-up blocking, URL aliases/nicknames, mouse gestures, easy page translation, and other things. It's very nice, but it's still IE, which means that it can display things strangly. Luckily the development is ongoning to have it run smoothly with the gecko engine as well. The URL aliases is one thing that I really miss with Firefox, and I haven't been able to find out if there is a plugin/other solution for it. And I don't really feel like I have the time to dive into firefox plugin development and make it myself right now. URL aliases let you set an alias so that you can (for instance) type "t17" and have the browser go to "http://forums.xisto.com/index.php;. It's very handy. I also use Opera and Netscape from time to time to check that webpages that I (or someone else) made look okay with them as well. Opera has let you switch user agents since the dawn of time. And if you use a browser which can't do that you could always use Proxomitron.

Yep. Saying "HTML or PHP?" is a bit like asking "What do you like best: A computer or a factory that builds computers?". "ASP vs PHP" would work, so would "HTML vs XHTML". Having said that I will answer both my questions: ASP vs PHP: I prefer PHP. ASP is ugly, really ugly. With PHP you at least have some chance to write readable code. There is also a distinct lack of free ASP modules. If you want something that's not in the stock PHP you can often easily get it for free somewhere. If you want the same for ASP you would often have to pay (and I prefer free to non-free ). HTML vs XHTML: This one is actually a bit harder. I very much like the idea behind XHTML, separating the markup and the layout. The problem is of course that the most used browser (IE) can't handle XHTML[1], so if you make a XHTML website you'll be forced to make a HTML copy of it as well. Which really means that unless you are certain a vast majority of your visitors are using modern browsers (gecko-family, perhaps Opera as well (not sure about that though)) you pretty much have to stick with HTML so people with older browsers (IE) don't get tag-soup. More on XHTML and why you shouldn't send it as text/html: http://forums.xisto.com/no_longer_exists/ Just my 2p [1] Assuming you are sending the XHTML as application/xhtml+xml and not as text/html. You shouldn't send it as text/html because XHTML is a subset of XML, and therefor breaks away from HTML.

All very good advice. I just wanted to comment on this bit: You can have it both ways actually, unless you are using tables for your layout (which you shouldn't be doing in any case). You can put the main content of your page (including those special first 100 words) at the top of your page, and the menu at the very bottom. Then you use CSS to position your menu on the left side. An example: http://csszengarden.com/146/page0/ which uses this HTML document. What I'm saying is that having your menu on the left or right hand side is really not the issue. It's having the menu higher up in your document than the main content. Putting lots of script and css data in the head of the page itself is a Bad Thing, since it pushes down your "100 words".