BlogEngine.Net Vs WordPress
BlogEngine.Net Vs WordPress
Being an Asp.Net Developer lets just say I wasn’t to happy when I was forced to switch my Blogger.com account over to Google’s platform and lose the blogging features I was accustomed to. I was so unhappy that I abandoned my Asp.Net roots and headed into uncharted territory. Reluctantly, I installed MySQL and PHP followed by WordPress on my Windows 2003 server.
Then I learned about an open source blog software written in Asp.Net called BlogEngine.Net. I was interested in the blogging software being that it is closer to my roots as an Asp.Net developer. But couldn’t really find any good reviews of the features or a comparison to the industry standard WordPress, so I decided to put together a collection of posts for others to read.
The first thing I did was begin to put together a list of features I considered important and made a side by side comparison of BlogEngine.Net and WordPress. I immediately found that it wasn’t as simple as that. Some features hold much more weight than others depending on how you use your blog.
Additionally, some features not in the WordPress 2.6 core that are in the BlogEngine 1.4 core are available as third party plugins. Then I found that there are extensions and widgets for BlogEngine.Net, analogous to WordPress Plugins, that contain features not available in WordPress. Although, BlogEngine.Net has some really nice extensions, like the BlogEngine.net Photo Gallery Extension for Vertigo’s SilverLight Photo gallery available on Danny Douglas’s blog, the quantity and quality is pale in comparison to WordPress’s 2500+ Plugins. However, all of the features that are currently available as WordPress Plugins, can also be offered as a plugin in BlogEngine.Net. They just haven’t been written yet.
So I began writing a notes about what features where available on each blogging platform. I then gave my opinion on the value of the features available in each. Please note, I am not entirely intimate with either of these blog applications, so if I have my facts wrong, just let me know.
The Administration Panels
BlogEngine.Net feature an administration panel on the sidebar of all pages. To me, this should be a convenience feature and one that I don’t particularly care for. I am accustomed to being able to access the administration section for a Web site by going to a particular URL, like blog.alexanderhiggins.com/admin. In BlogEngine.Net, you can’t do that by default and that is one convention that should not be ignored. Maybe its just me, but little usability issues like this quirk me.
Side Bar administration panel for BlogEngine.Net
The benefits of being able to access an admin panel via a URL are it can be bookmaked or favorited. Further, most browsers will auto complete the web address for me as I start to type it. FireFox 3.0 will allow me to type keywords like “Blog Admin” in the adress bar and suggest the url for me.
On the other hand, WordPress has an administrative dashboard, and its the heart of their control panel. It is also noteworthy that WordPress offers a plugin, which puts an administration panel on the front end web pages as well.
Control Panel Functions
While we are discussing the control panels the biggest complaint I have read about BlogEngine.Net is that it is light on the administrative functions. Of course the savvy developer can go in and add additional functionality much easier than one could using WordPress, but for the average end user that doesn’t cut it. So for the end user, WordPress is better but for developers BlogEngine.Net wins here.
Another big difference between WordPress and BlogEngine.Net control panel ( as I mentioned above), is when you login in WordPress, you are presented with a nice dashboard . The WordPress DashBoard gives you a quick overview of your blog activities, including number of posts, pages, and comments. Addtional, it provides a quick links to perform most administrative functions as well as WordPress News and Plugin updates.
BlogEngine.Net does not have a dashboard. End users will prefer the WordPress setup, but developers and companies that plan on using the application as the core of another application, BlogEngine.Net will be preferred. For example, we currently use the WordPress platform for our clients blogs at Single Throw. However, we have our own customized version the we have optimized for SEO. The first thing we have to do is remove the default WordPress dashboard, and give it the look and feel of our clients brand.
The Dashboard as shown here WordPress in is a much needed missing feature from BlogEngine.net
The WordPress Control Panel
The BlogEngine.Net Control Panel
LIke I said before, I have read several complaints about the BlogEngine.Net control panel being light in functionality. The Bottom line is both really WordPress and BlogEngine.Net offer very similar functionality, when you don’t consider the plugins. Personally, I feel that the only thing that makes the BlogEngine.net control panel light is the lack of centralized management and the first place we’ll notice this is in managing comments. Its the extensibility offered by the thousands of available plugins that make the WordPress control panel win in this category.
However, when viewing the settings in the control panel for each blog application, it is immediately apparent that BlogEngine.Net is built on a superior framework. Once that framework matures, it will allow BlogEngine.Net to give WordPress a real run for its money. For example, BlogEngine.Net offers settings for enabling HTTP Compression, rating comments, Culture Globalization, OpenSearch, Geo Coding of comments and optimization of StyleSheets and JavaScript among other features.
Comments
Comments, or discussions as their labeled in the WordPress Control panel, are well supported by both platforms. Natively BlogEngine.Net allows users to subscribe to comments where WordPress requires a third party plugin. Additionally, BlogEngine.Net has the ability to automatically turn off comments for a given post after a certain amount of time has elapsed. Both both platforms support several avatars as well as comment moderation. BlogEngine.Net also offers a new feature called coCommenting. WordPress allows you to password protect posts but BlogEngine.Net does not. WordPress does have a plugin to Edit Comments where BlogEngine.Net currently does not have such a plugin.
This biggest drawback of BlogEngine.Net’s commenting system is there is no place to centrally manage comments. In administrate comments, you need to visit the actual page where the comments where made. Neither platform allows you to edit comments natively, although I did find a WordPress plugin that allowed me to edit them.
Another drawback of BlogEngine.Net, is that you can’t use HTML to create a hyperlink, by default although it does automatically convert a web address into a hyperlink. Actually, BlogEngine.Net doesn’t allow any HTML in the comments, but offers very few bbCode tags to format HTML.
Support for Stand Alone Web Pages
Both Platforms do a great job of supporting stand alone web pages, but BlogEngine.Net wins in this department. It supports modification of key meta tags like the description and keywords field where WordPress requires a plugin. BlogEngine.Net also allows to add additional markup in the HTML head tag as well as built in support for visitor analysis applications like Google Analytics where WordPress requires a plugin for the latter and has no support for the previous. Both allow the use of custom slugs or permalink structures.
Categories
While both blogging platforms allow the categorization of blog posts, on BlogEngine.Net integrates the same functionality into stand alone pages. Besides that the same features are available on both platforms, such as the ability create sub categories. BlogEngine.Net does not allow for the use of slugs for categories where WordPress allows you to define a category root folder as well as a custom slug for each category. Category based RSS feeds are supported by both platforms.
Permalinks
Both brands of blog software allow the use of custom slugs or permalinks for post pages. However, WordPress clearly wins in this department by allowing the assignment of permalinks for feeds, categories as well as defining a custom permalink structure for post pages. BlogEngine.Net uses a built in permalink structure and does not offer URL-Rewriting for RSS feeds, categories or tags. Instead, BlogEngine.Net uses querystrings which not good for search engine optimization. However, most people suggest that you should tag your category and tag pages as NOFOLLOW to prevent the pages from being penalized as duplicate content in the first place.
However, by digging through the source code of BlogEngine.Net I noticed that the framework is already place for customized URL rewriting. It just seems like they just haven’t got around to it yet. So I would not be surprised if the feature where made available over the next few weeks.
Tags
Both BlogEngine.Net and WordPress allow the tagging of content as well as built in implementations of the Tag Cloud. However, I must mention tags because BlogEngine.Net does not offer URL rewriting for tags at the time of this writing.
Data Providers/Database support
I must say, if WordPress doesn’t follow BlogEngine.Net’s lead on this one, it will surely be the downfall fall of WordPress. No kidding!! Although it doesn’t really matter to the end user, to the developers like myself that have to work these applications it does. And to put it simply, if developers have to jump through hoops to work with an application then they are just not going to use it. Plain and simple. Same goes for the hosting providers and the people who provide technical support for these applications.
So why can this be the downfall of WordPress? Because by default BlogEngine.Net runs out of the box, a simple copy and paste of the source code and its up and running using nothing more than XML Files as a database. That’s right. BlogEngine.Net = NO DATABASE NEEDED. And end users aren’t going to spend and additional X amount of dollars of month for database hosting when its simply just not needed.
There have been reports of performance degradation on really large sites using XML, but those reports have came from individuals who have 400 or more comments on a single post page. However, unlike WordPress where you are stuck using MySQL where you like it or not, BlogEngine.Net steps it up and allows you to swich to a database.
Impressively, BlogEngine.Net will run off of XML, MySQL, MS SQL, SQlite, Oracle, VistaDB or just about any other Data Source support by the Asp.Net Framework. WordPress only supports well, My SQL.
Pingbacks and Trackbacks
Both off these platforms separate them selves from other legacy blogging applications by fully handling Pingbacks and Trackbacks out of the box. I did read a post where someone was complaining about trackbacks not working for his BlogEngine.Net installation. However there are so many variables that come into play like firewalls, routers, network latency that his issue is probably due to his network. I am sure that I can find the same complaints about WordPress, but again, its not due to the blog software itself but becuase of the environment it is running in.
Stats
While neither blog package offers full stats tracking, BlogEngine.Net does offer referral tracking out the box. However, there are plenty of stats Plugins for WordPress. There are no extensions available at the time of this writing for its Asp.Net counterpart. However, developers can easily install free open source stats tracking as an package on either platform, or optionally include the industry standard Google Anaylitcs in either platform.
Cross Platform Compatibility
Blog Engine.Net and WordPress can run on Windows and Linux. I am by no means an experts in all of the available platform and web server combinations, but no matter what OS and web server you are running, you should be able to run either.
Integration of New Initiatives
Both platforms support XML-RPC publishing and MetaWebLog which means that they will both be able to take fully advantage of the next generation of web 3.0 applications. That means that you can easily manage posts and pages from the next generation of desktop applications like Windows Live Writer. BlogEngine.Net even takes it further supporting the OpenSearch API which allows content to be search through various client search applications, as well as the built in support to filter search results to your attention profile.
BlogEngine.Net also supports FOAF, SIOC and APML each of which are data exchange formats centered around human relations and social networking patterns. Each of these technologies promise to help bring web content categorization from titles and keywords into an neural network that doesn’t require a centralized database and may end one day being part part of an Artificial Intelligence network. Here’s the current list of all the features available in BlogEngine.net.
And the winner is….
Both platforms have their pros and cons. I really can’t pick a clear winner. Most of it depends on whether or not you are a developer and which programming language you are more familiar with. Let us know. Who do you think the winner is?
August 10th, 2008 at 2:50 am
In general, it would be cheaper to host a WordPress installation and you have a larger variety of hosting providers offering LAMP hosting as compared to .Net.
August 10th, 2008 at 3:17 am
1) BlogEngine.Net is Cross platform compatible. You can host it on windows or Linux.
2) You don’t need a database for BlogEngine.Net. It can run off of XML. Database hosting always cost extra $$$. And the larger the database gets the more $$ it costs.
2) It costs more for a hosting company to employ *nix administrators than windows administrators. That’s one reason corporate America doesn’t adopt *nux. The total cost of ownership is way higher.
3) Who needs a huge variety. I have never had a problem with finding hosting providers for my .Net applications. As long as you have a few viable alternatives to choose from that is all that should matter.
August 10th, 2008 at 3:33 am
Aha… that’s what happens when you don’t do enough research. My Bad, I had no idea about the cross-platform features of BlogEngine.net.
Well, I wanted to work on an Asp.Net blogging platform for my blog, but I have now invested way too much time working on WordPress for my blog.
I guess maybe for a new blog, I may try it out (if I ever put up a new blog).
August 10th, 2008 at 3:51 am
Yeah, maybe I should put that in bold… Its a long article but its in their. I actually have Visual Basic Version of Blog Engine.Net which I did not mention in this article.
I am also planning on reaching out the BlogEngine.Net to discuss implementing an “Import from WordPress” feature:)
August 10th, 2008 at 1:29 pm
Nice article. One point worth mentioning… The latest version of BE supports SSL based MetaWeblogAPI connections (provided you have an SSL cert on your blog) to prevent your password from being sent in the clear. Can’t do that with WordPress or any other blog engine for that matter.
The fact that WordPress only runs on MySQL illustrates an important difference between WordPress and BlogEngine. The BE team is very interactive with the BE community to provide for updates and improvements that are requested. I wonder how many people have complained to the WordPress folks to provide XML/SQL/etc support and never received a satisfactory response. Not true with BE as most all requests and comments are responded to quickly.
August 11th, 2008 at 2:25 am
Chris, I don’t think WordPress ever will offer any other database options. I love how the *nix community screams and hollers about Micro$oft not opening their doors to other platforms and technologies but fail to follow suit themselves.
Microsoft has released Asp.Net as an Open Source technology and has even stepped it up by offering a fully Linux compatible version. Call me insane, but I think that Sun has their hands in the WordPress project which would explain WordPress’s reluctance to offer compatibility with other database beside MySQL despite ongoing pressure from their community.
Like I said, if WordPress fails to follow BlogEngine.Net’s lead it will eventually be the cause of their downfall. As far as the SSL with the MetaWebLog, we have a good conversation going on. It is nice to know that BlogEngine.Net is the only platform that supports the MetaWebLog and SSL combination. However, it is bothersome to think of all of the unsuspecting WordPress users that are sending their user name and password over the internet in plain text. That might explain all of the unexplained WordPress hackings that are still unresolved in the WordPress issue tracker database.
August 11th, 2008 at 11:12 am
Hi Alex,
I tried both here on:
http://www.SeoConsultant.ie and http://www.SeoKonzultant.com
… and about 30 other blogs on WP.
The issue I have with BlogEngine.NET is that After being used to WordPress for about a year, I find hard to use BlogEngine.NET really. I simply could not find things from the Admin perspective. I used about 10 CMS’s extensively in my life, and I cannot remember one that surprised me so much in a since of finding it hard to ‘discover’ how to manage the site.
Is it just me?
Would it be different if I was not ‘hooked’ into WP already?
Ivan | JobsBlog.ie
August 11th, 2008 at 12:35 pm
You said:
“I did read a post where someone was complaining about trackbacks not working for his BlogEngine.Net installation. However there are so many variables that come into play like firewalls, routers, network latency that his issue is probably due to his network.”
Forgive my bluntness, but that’s a ridiculous assumption. I’ve never made nor seen a complaint about trackbacks not working that would lead one to believe that it could be a network issue.
Read the threads on codeplex. there have been numerous complaints about trackbacks not working properly from people using a variety of hosts. I, for example, have never gotten trackbacks to work on a host where trackbacks have worked for other software (dasBlog) that I was personally running. Additionally, others who are not on the same host as I was have problems as well.
Further, after switching hosts, I’m still having problems getting trackbacks to work. The fact is that trackback support on BE is problematic.
August 11th, 2008 at 1:30 pm
I think WordPress is still a pretty good option for a self hosted blog. PHP is easy enough, and there is plenty of support around for the platform.
For example, I was able to create a plugin in literally less than a couple of hours.
August 11th, 2008 at 2:55 pm
Christopher Estep:
So may it was your blog post I was referring to, and If I remember correctly you where hosting on GoDaddy, which blocks HttpWebRequests.
I am sure that your issue is due to your hosting providers network, becuase thousands of others seem to run BlogEngine.Net without issue with the trackbacks.
Perhaps, someone can help you troublehshoot your issues.
August 11th, 2008 at 3:08 pm
Christopher Estep:
I just posted an entry using BlogEngine.Net and the trackback showed up on you blog immediately. What exactly is the issue?
August 11th, 2008 at 3:12 pm
Ivan:
I agree with you. The lack of a centralized administration via a dashboard is the biggest grip people have with BlogEngine.Net. Hopefully this article will queue the developers to address the issue.
August 11th, 2008 at 11:24 pm
You know, part of the problem could actually be wordpress. I created a WP blog using default settings ( http://christopherestep.wordpress.com ) and while it would send them to my BE blog just fine, it didn’t go the other way. Could I get you to check that with your BE test blog too?
August 11th, 2008 at 11:50 pm
Christopher Estep:
There is no need, in my test post I linked to your BE Blog and this exact post and I did not get a track back. I think the issue is WordPress, because I know that many of my WordPress Posts should have trackbacks. I can actually see the track backs being sent in my IIS Logs, but no trackbacks show up.
WordPress is expecting trackbacks to be sent to /post-name/trackback (see the trackback url link above). The problem is that I think WordPress is the only blog engine that uses this convention. I have also linked to my this WordPress Blog using Blogspot blogs and no trackbacks show up here from them either.
Definitely a WordPress Issue…
August 11th, 2008 at 11:58 pm
1) WordPress needs to fix the issue on their end.
2) BlogEngine.Net needs to have a textbox to allow users to manually enter trackback urls, so trackbacks can be sent to trackback destinations that do not match the permalink url
August 12th, 2008 at 8:18 am
I don’t know if WP is expecting that, necessarily. The pingback should still work. In fact, it works just fine with dasBlog, so whatever dasBlog is doing (without any special setup) is likely what BE should be doing.
Even WP’s documentation differentiates between pingbacks and trackbacks on wordpress. It appears to me that BE just does things somewhat differently that WP is expecting.
As for fixing wordpress, even if it is there fault, it’s up to BE to compensate for it given that WP is far, far bigger. Kind of like the IE hacks that are used in CSS. It’s microsoft’s fault, but people need to compensate for it themselves because MS is that big.
August 12th, 2008 at 7:28 pm
Christopher,
I agree with you entirely. However, there is an issue on both ends. A quick google search shows several blogs that have cited my blog posts, and it seems the only trackbacks I am getting are those from other WordPress blogs.
I would like to see if this blog (WordPress Powered) is recieving trackbacks from dasBlog. Again, the only trackbacks/ping backs I am seeing is from other WordPress blogs and have yet to see one from ANY other blog platform.
August 13th, 2008 at 12:58 am
It is not so correct. It is pain in … to run it on linux, and you need to do many tweaks **in code** to run it with MySQL. It is not Linux ready because it is not tested well on linux.
More than that, try to find a provider that gives you a Mono on web host
Ohhh, give me a favor. Unix sys admin costs as twice as windows one but unix one can manage x10 Linx servers that windows sys admin can. I work in corporate environment and see how much effort is given to manage windows and unix servers. So all this TCO bullshit (sorry) does not buy me
Several important points
WordPress has two important features that BE.Net hasn’t:
1. WP-Cache-2 — it allows you site pass any “slashdotting” or solve any high traffic problems
2. There is WordPress.Mu — multi-user version that is hosted at sites like wordpress.com and so on
it allows creating communities.
About trackback issue? If you wan’t I may check this (I have a
written a tool that does this)
Never had TB issues with WB — are you sure it is not something about
your IIS WP installation?
August 13th, 2008 at 2:49 am
[...] Higgins Blog Personal blog of Asp.Net Developer Alexander Higgins « BlogEngine.Net Vs WordPress Test Web Designs In Multiple Browsers [...]
August 13th, 2008 at 3:08 am
[...] blog’s short 1 month history, getting a total of 81 visits, largely due to the 82 views of my BlogEngine.Net Vs WordPress Comparison in the last two [...]
August 13th, 2008 at 4:19 am
Artyom:
Many users on codeplex have been able to run BlogEngine.Net on MySQL. The only issues that have been reported are due to failure in following the documentation when setting up the MySQL database provider and bugs with MySQL itself which are fixed by applying the correct patches or upgrading the MySQL Installation.
As far as finding a hosting provider to that runs MONO, why in the world would you? That would be like finding a hosting provider that runs PHP on IIS. That’s just absurd. If I where to host a WordPress Blog, I would do so on with a WAMP host. The only time it would be concievable to do otherwise is if you are hosting yourself.
You are totally off your rocker with this one. I will agree that most Windows administrators are nothing more than paper MCSE’s that don’t even know how to run a checkdisk. But a competent Windows administrator can manage just as many servers if not more than a *nix admin can.
As far as the TCO… here’s a break down from a well published study comparing the TCO of a Linux environment Vs A Window Environment. In the study, a 250 person organization was simulated over 3 years. Linux was cheaper for an enterprise. But the main reason was the cost of third party software, like office productivity products and photoshop for end users. If you take the end users software out of the equation, windows would have been cheaper. If you left the end users software in the equation and ran the study for 5 years as it was Windows would have been cheaper. Why, IT staff salaries where $100,000 a year more in the linux enviroment. As far as hosting is concerned, we don’t factor in end users or the cost of their client software.
Again, both environments had the same amount of servers and the linux servers cost almost $100,000 more per year to run. Heres the break down of administration costs as taken from this article
Wrong…. Just becuase you couldn’t get the caching to work on Mono installation doesn’t mean that there is no caching in Be.Net. Slashdotting can be handled in any ASP.NET application by adding a simple line or two of code to the Global.ASAX file. Further more, BlogEngine.Net strips white spaces from CSS files and Javascript Files and combines each into a single file which is then compressed and sent to the client. The apply caching directly to the brain. Where WordPress will still require multiple requests per client for each CSS and Javascript file Be.Net requires only two and even then only on the initial request.
I no aboslutely nothing about Mu so I am not going to comment.
Sure, I would like to get to the bottom of this whole trackback thing
That could possibly be the issue. However, it was originally brought to my attention by others who have had the issue serveral hosting providers. I then made a test post linking to a BE.Net blog and to this exact post. The Be.Net post immediately recieved a trackback, and this page recieved nothing. However, I received trackbacks from other WordPress installations….
August 13th, 2008 at 3:23 pm
I’ve seen this study that had shown clearly that Linux solutions are cheaper overall. However you should note one single point. If they had told ONE UNIX sys admin can manage more unix stations then windows one many would tell that this is false. Why? Not because it is true but because it is hard to measure such ability.
You can measure avarage sallary of UNIX or Windows sysadmin but it is harder to manage its quality.
As a good example I can show my University that runs Debian based OS on hundreds of PCs with limited stuff. How? All PC’s run exactly same OS (by sharing common mount points) so all os management comes as managment of one single installation.
I must admit it works much better that hundereds of Windows based PCs installed all over campus.
So, yes, I can tell Linux are cheaper to manage that Win based solitions, beleve me or not.
If I **can** edit aspx files and add caching does not means that caching solution exists. For example, how would this cache behave when new comment is posted? (WP addon clears the cached pages).
I mean controlled cache, build as solution that can be installed as a simple add on, can be controlled of admin panel and so on and so far.
BTW: I managed to turn cache under IIS for other sample application.
This is not correct — even MySQL DB script will fail on Linux installation because it assumes that tables names are case insensitive (this is true under windows but not uder linux). Nobody tested MySQL setup of 1.4.5 under linux (I was first and it failed)
P.S.: I still have to send a patch
August 13th, 2008 at 4:19 pm
Ok, I tryed to send trackback to this post and…
I can’t find trackback url. Usually this url is shown on the page (in order copy-paste it) or shown in rdf:bla-bla for auto-discovery.
No one exists so I can’t send you a trackback.
Do you have trackbacks/tb-autodiscovery enabled in your WB blog.
I’ve tested sending TB to BE.Net, seems to be ok, on the other hand I can’t find a way to enter trackback URL in Be.Net manually, Is there such option at all?
August 13th, 2008 at 6:47 pm
Yeah.. this new theme has removed the link to the trackback url. Autodiscovery is enabled. Track backs should be sent to
the permalink/trackback
So for this post it would be:
http://blog.alexanderhiggins.com/2008/08/blogenginenet-vs-wordpress.html/trackback
August 13th, 2008 at 6:48 pm
Also, there is no option to manually send trackbacks in Be.Net. I have suggested this for future releases
August 14th, 2008 at 12:21 am
First of all, there is no autodiscovery for Trackback (there is for pingback only). So, BE.Net cannot send trackback to this blog.
I tryed to send trackback to the URL you given, however the server hadn’t respond according to the protocol.
(I mean correct XML respond — the output is empty)
So I assume that there is a problem with configuration/url.
August 14th, 2008 at 8:39 pm
Ok… I just stepped through the code for sending Trackbacks in the VS Debugger. Very annoying by the way.
1) BlogEngine.Web\App_Code\Extensions\SendPings.cs line 45 Kept throwing an error when calling
Uri url = item.AbsoluteLink.ToString(); which calls Utils.ConvertToAbsolute(RelativeLink) which throws an exception at
throw new System.Net.WebException(”The current HttpContext is null”);
Perhaps this call is not thread safe?? For whatever reason, HttpContext.Current is null. As as work atounf I hard coded the the url.
2) After hard coding a Uri in SendPing.cs line 45, I continued to step though the code. Eventually we get to PingBack.Cs line 45 which kept setting pingUrl to a null string here.
That needs to be recoded like this
3) And finally the call to request.GetResponse() on line 45 kept throwing an exception. The pingback worked after chacking that line to this.
August 18th, 2008 at 6:13 pm
Alexander, you’re a hero. I’ll implement these tweaks asap. Thanks
August 18th, 2008 at 9:45 pm
Here are a few wordpress themes I designed alot better than whats out there for wordpress now, and I want to share them with you guys. please enjoy these
http://rapidshare.com/files/136749398/WordpressPreThemesFeb08.rar.html
Preview my themes
greentec
freshnews
August 19th, 2008 at 7:36 pm
Here are a few wordpress themes I designed alot better than whats out there for wordpress now, and I want to share them with you guys. please enjoy these
http://rapidshare.com/files/136749398/WordpressPreThemesFeb08.rar.html
Preview my themes
http://img01.picoodle.com/img/img01/4/4/7/f_lwm_d7bfed5.png
http://i38.tinypic.com/20u9638.png
http://wseo.ws/uploads/newspress.gif
http://flicr.us/files/i4wevfzk5u0umkblyo82.png
August 25th, 2008 at 6:19 pm
I find it a little bit funny that a lot of discussion here is about Linux ./. Windows - is that really a point of discussion you should compare in the first line? I don’t think so. For example you cannot compare Gimp with a Windows/AndLinux-Setup vs. Photoshop with a Linux/Wine-Setup. It’s a matter of what programming language you prefer or which hosting provider is under consideration. In case it’s not absolute necessary I wouldn’t run .NET applications under Linux/Mono nor whould I use a PHP-Installation under Windows/IIS. I’m now programming for over ten years mainly web-applications and more than the half time I used PHP on a LAMP-Setup, so I can absolutly compare both technologies. The decission if BE.NET or WP is the “winner” isn’t a decission between Linux/PHP and Windows/.NET
A important aspect is the age of WP. BE.NET is simply too young to have as much extensions and themes avaible as the much older Wordpress. But there are daily new ones I see in different blogs and it’s as simple as in Wordpress to write a own extension or widget for BE.NET, but you must have a litte more experience as a programmer. PHP is just a programming-language for web-applications, .NET is a complete object oriented framework with much more abbilities. It just took me 1-2 hours to write my very first BE.NET-Extension but probably PHP has a shorter learning-curve for beginners. So that maybe a point - but also not for this comparission!
I think there could be made a lot of improvement for the configuration-panel in BE.NET and I haven’t much experience with WP so far. Writing themes is a lot easier with BE.NET cause you have only to edit one masterpage with the complete layout and two separate pages for postings and comments, thats a little different to WP-Themes.
In my opinion it’s not a question what blog engine has which features because you can add most of them with a small plugin on your own. The difference is that you may find it for WP a lot faster but who needs 1001 additional plugins to run a simple blog? You only distract people from the most important thing: Your articles!
Greets from germany,
Gordon
September 4th, 2008 at 2:11 am
[...] WordPress vs. BlogEngine [...]
September 20th, 2008 at 1:50 am
Hey Alex, I read one of your comments about a BlogEngine.net extension at http://www.ckurl.com/techblog/post/2008/01/Quicker-Links-13-Released.aspx . Thanks for the idea. I took a stab at writing the extension you talked about. If you like, you can check it out here: http://www.bookofkai.com/post/2008/09/19/Keyword-Linkz-10-Extension-for-BlogEngineNet-released.aspx
October 21st, 2008 at 3:48 pm
I just noticed one thing… When you put about 2000 Categories in the blank fresh installation of WordPress - the Administration GUI freezes. WP can not really cope well with the large amounts of data. Blog Engine copes with it much better (so far!
)
October 23rd, 2008 at 6:38 am
@Ivan: In case you have 2000 categories in your blog you have another problem than a freezing administration GUI in WP…
November 6th, 2008 at 1:04 am
Blin … really beautifully written! All this is so familiar … and truthfully!
November 21st, 2008 at 11:11 pm
A guy shows up late for work. The boss yells “You should have been here at 8:30!” he replies: “Why? What happened at 8:30?”
November 25th, 2008 at 12:25 am
thanks for the information about BlogEngine.Net Vs WordPress
November 30th, 2008 at 5:59 pm
Nice work