5 ms·

new modern, flexible CMS built for that purpose from the ground up than I am about a new blogging software I don't understand this.. Basically you're asking fo

new modern, flexible CMS built for that purpose from the ground up than I am about a new blogging software I don't understand this.. Basically you're asking for a new codebase full of bugs over a stable codebase?

krapp 13y ago
Define "stable", there was an arbitrary code execution flaw in Wordpress just in the last version. A smaller, more efficiently designed codebase which isn't hampered by backwards compatibility might well have fewer bugs. Wordpress is kind of a sprawling mess at this point, and it's got bad practices baked into it.
- lukeschlather 13y ago
  any cms as widely used as wordpress is going to have regular RCE vulnerabilities. Wordpress core is well-debugged, and no matter how much better engineered a replacement is, it's going to have more bugs, even security bugs, for at least a year. A replacement would be valuable if it could provide a better templating/plugin system that reduced the opportunity for bugs in template/plugin code.
  - malandrew 13y ago
    Maybe. Choose the right language and "framework" (which for WordPress is Apache), and that language may enforce enough constraints to eliminate many many of the bugs possible and common on abstractions such as Apache, MySQL and PHP. I know Apache is not a Framework, but a webserver. Here I'm using framework to mean operating system abstraction. Apache, being file-based and not data based first, means that it is full of abstraction holes that, while right for serving files, is all wrong for serving data and instead overly exposes the operating system for this world of dynamic web experiences we currently live in. If you knew back in the early 90s that the web would be more about streaming, real-time content, you would have designed a webserver that was designed for serving static, discretely changed content in a way that took advantages of as many features and benefits of the design of the Unix/Linux operating system (stdutils, etc.)
- Killswitch 13y ago
  What doesn't have these problems? Rails itself was not too long ago dealing with SQL injection vulnerabilities. Like stated by lukeschlather anything as widely used as either Wordpress OR Ruby on Rails is gonna have these problems.
malandrew 13y ago
I don't buy this argument. This is only valid if you want something exactly like WordPress that grew up like Wordpress and has all the benefits and the baggage that comes with its unique evolutionary path. It's 2013, we have a much better understanding today of how people use the web, from how they consume to how they socialize. Many of these habits are the product of things invented between when WordPress was invented and today. With that in mind, an experienced engineer familiar with the architecture of WordPress, it's history and the web as it exists today, would be very well equipped to choose a whole host of different abstractions at lower levels, which would permit a permit said WordPress replacement to support better features more easily, where better means "fitness for use" from now into the future (5-10 years)

krapp 13y ago

Define "stable", there was an arbitrary code execution flaw in Wordpress just in the last version. A smaller, more efficiently designed codebase which isn't hampered by backwards compatibility might well have fewer bugs. Wordpress is kind of a sprawling mess at this point, and it's got bad practices baked into it.

lukeschlather 13y ago
any cms as widely used as wordpress is going to have regular RCE vulnerabilities. Wordpress core is well-debugged, and no matter how much better engineered a replacement is, it's going to have more bugs, even security bugs, for at least a year. A replacement would be valuable if it could provide a better templating/plugin system that reduced the opportunity for bugs in template/plugin code.
- malandrew 13y ago
  Maybe. Choose the right language and "framework" (which for WordPress is Apache), and that language may enforce enough constraints to eliminate many many of the bugs possible and common on abstractions such as Apache, MySQL and PHP. I know Apache is not a Framework, but a webserver. Here I'm using framework to mean operating system abstraction. Apache, being file-based and not data based first, means that it is full of abstraction holes that, while right for serving files, is all wrong for serving data and instead overly exposes the operating system for this world of dynamic web experiences we currently live in. If you knew back in the early 90s that the web would be more about streaming, real-time content, you would have designed a webserver that was designed for serving static, discretely changed content in a way that took advantages of as many features and benefits of the design of the Unix/Linux operating system (stdutils, etc.)
Killswitch 13y ago
What doesn't have these problems? Rails itself was not too long ago dealing with SQL injection vulnerabilities. Like stated by lukeschlather anything as widely used as either Wordpress OR Ruby on Rails is gonna have these problems.

malandrew 13y ago

I don't buy this argument. This is only valid if you want something exactly like WordPress that grew up like Wordpress and has all the benefits and the baggage that comes with its unique evolutionary path. It's 2013, we have a much better understanding today of how people use the web, from how they consume to how they socialize. Many of these habits are the product of things invented between when WordPress was invented and today. With that in mind, an experienced engineer familiar with the architecture of WordPress, it's history and the web as it exists today, would be very well equipped to choose a whole host of different abstractions at lower levels, which would permit a permit said WordPress replacement to support better features more easily, where better means "fitness for use" from now into the future (5-10 years)