Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WooThemes joins Automattic

woothemes.com

Post reply on HN
Print view View original

121–130 of 159 posts

Re: WooThemes joins Automattic

#121

Post by ereckers »

Domenic_S wrote: post #88
MichaelTieso wrote: post #71

Earlier quoted context omitted.

I won't go into detail on that here but know that there's a very good reason for it. Plugin and theme developers should be using for example `esc_url( home_url( '/' ) );` when requiring the URL of the site.

Ok, as someone who's battled with this... feature... of WP I am super curious as to the very good reason for storing the domain in the DB. Why couldn't links be relative (no need to know the domain), or set only as a sitewide variable in wp-config.php? edit: and just discovered the 'guid' column on the posts table is hardcoded as the URL of the post -- the domain you're on at the time you create the content + the pos…

These are very old and well fought battles:

URLs delivered to the browser should be root-relative https://core.trac.wordpress.org/ticket/17048

WP Development & Production Sites http://lists.automattic.com/pipermail/wp-hackers/2010-Novemb...

Relative vs. Absolute URLs stored in db http://lists.automattic.com/pipermail/wp-hackers/2010-Decemb...

Re: WooThemes joins Automattic

#122

Post by ereckers »

Domenic_S wrote: post #48
aikah wrote: post #37

I'm fascinated by Wordpress success. It's an horrible peace of software, with horrible PHP code 4.x style, a db schema only a beginner could have come up with and an ecosystem with a lot of trash(not even talking about the admin which is hideous ). Yet it's a blazing success in the CMS space, because of 3 things that are insanely overlooked by other CMS developers : - Ease of installation - It runs on a minimal PHP/A…

Here's something crazy to me about WP - it stores the site's domain in the database . This makes it incredibly obnoxious to set up a local environment of a live site (or automated CI environments with arbitrary subdomains). I had to hack together a bash script to fire UPDATEs to the db to modify these values. Drupal on the other hand looks for /sites/$DOMAIN/settings.php, and there's nothing domain-specific in that f…

These are very old and well fought battles:

URLs delivered to the browser should be root-relative https://core.trac.wordpress.org/ticket/17048

WP Development & Production Sites http://lists.automattic.com/pipermail/wp-hackers/2010-Novemb...

Relative vs. Absolute URLs stored in db http://lists.automattic.com/pipermail/wp-hackers/2010-Decemb...

Re: WooThemes joins Automattic

#123

Post by infinii »

themodelplumber wrote: post #32
wonderyak wrote: post #14

Earlier quoted context omitted.

The thousands of developers making a living mostly off of WordPress development would probably disagree with you. It's low hanging fruit, not a lot of effort for decent return.

It's a technical debt trap. You dive in with a one-click install and follow up with a bunch of plugins that seem to fit the bill. Then you spend 2-3x more time creating a custom theme for someone than you would in a sensibly-architected CMS, and only then do you begin to realize that maintenance costs down the road are going to be absolutely crazy. Especially when plugins X and Y start requiring a different theming a…

You're not the first person to make such a comment. You're also not the first to make such comments without suggesting an alternative CMS that addresses all of your concerns.

Re: WooThemes joins Automattic

#124

Post by torbit »

aikah wrote: post #37

I'm fascinated by Wordpress success. It's an horrible peace of software, with horrible PHP code 4.x style, a db schema only a beginner could have come up with and an ecosystem with a lot of trash(not even talking about the admin which is hideous ). Yet it's a blazing success in the CMS space, because of 3 things that are insanely overlooked by other CMS developers : - Ease of installation - It runs on a minimal PHP/A…

WordPress has out of the box experience that clients can wrap their heads around. Drupal requires you to mix modules to basically create your own "plugins" which means more time and a higher price for a client. Wordpress just hits the spot.

Re: WooThemes joins Automattic

#126

Post by karlshea »

Immortalin wrote: post #119
ereckers wrote: post #55

Earlier quoted context omitted.

First, I should mention that I'm glad to see this dismissive and negative comment voted to the top. I was starting to worry that HN was losing its edge. Next, you mention: > Yet it's a blazing success in the CMS space, because of 3 things that are insanely overlooked by other CMS developers : - Ease of installation - It runs on a minimal PHP/Apache/Mysql setup (cheap hosting) - It has a great backward compatibly, unl…

One thing that WordPress got right is deployment and automatic updates. It is a nightmare to keep Drupal updated and ensure that nothing is broken.

> It is a nightmare to keep Drupal updated and ensure that nothing is broken.

Except in very rare cases, I've only found that to be the case for websites I've inherited that were built by someone that didn't know how to build a site in Drupal.

Re: WooThemes joins Automattic

#127

Post by ShirsenduK »

I'm a fan of Wordpress but not the templates which are available. They never take performance into consideration. Most wordpress sites are slow primarily Becuase of the frontend performance. 5 css and 10 JavaScript files seems to be the average. As for woothemes it's 2015 and the page where they have announced this acquisition still isn't responsive and they want to take over 51% of the web. Hope they switch gears and innovate.

Re: WooThemes joins Automattic

#128

Post by edwinyzh »

camworld wrote: post #23

This is a really smart acquisition. WordPress continues to dominate the CMS market. With the upcoming REST API, it's only going to get better. I'm watching niche CMS industry after niche CMS industry crumble under the continual migration to WordPress. The latest victims are the small CMS vendors who have been selling proprietary CMS solutions to public school districts for the past 15 years, charging far too much mon…

Is this the REST API you are talking about: wp-api.org

Re: WooThemes joins Automattic

#129

Post by annnnd »

aikah wrote: post #37

I'm fascinated by Wordpress success. It's an horrible peace of software, with horrible PHP code 4.x style, a db schema only a beginner could have come up with and an ecosystem with a lot of trash(not even talking about the admin which is hideous ). Yet it's a blazing success in the CMS space, because of 3 things that are insanely overlooked by other CMS developers : - Ease of installation - It runs on a minimal PHP/A…

Absolutely agree with the sentiment.

A few times I had to help out friends customize something I was horrified at the overall level of code quality. It looks as if a B-level programmer started it and C-level programmers helped... And I think this is the crux of it. A-level programmers in general are not interested in such frameworks because they know how to use less friendly ones (and thus don't work on WP & co.) while C-level programmers need such a solution and are willing to help... to the best of their ability of course.

That said, they made WP very convenient to use (great admin console, easy installation, no major headaches... well, apart from vulnerabilities ;). Other projects should learn from that. Who cares about great foundation if UX sucks? (Typo3 anyone?)

EDIT: replaced "C programmers" with "C-level programmers". I am not talking about those who use programming language C. :)

Re: WooThemes joins Automattic

#130

Post by annnnd »

MichaelTieso wrote: post #120
lamosty wrote: post #58

Earlier quoted context omitted.

> It's an horrible peace of software, with horrible PHP code 4.x style, a db schema only a beginner could have come up with and an ecosystem with a lot of trash [...] I must disagree with these statements. Although it is not the most elegant one I've seen, using the word "horrible" is simply out of place. Have you ever built some sites with it? Do you realize that WordPress is developed in open source with many talen…

I wish this comment was voted higher. There's a lot of misinformation in this thread.

The fact that this is not shows that not many people (here) agree. :)

I personally have no opinion on DB schema because I never looked that deep, but last time I had to deal with WP its codebase was just horrible. And don't get me started on plugins' code quality, it goes to entire other level of "horrible". The project might have a lot of talented contributors, but they seem to be overshadowed by everyone else.

They might have fixed it from the last time I looked of course (though I doubt it, judging by never ending stream of vulnerabilities).

Post reply on HN