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

91–100 of 159 posts

Re: WooThemes joins Automattic

#91

Post by mdesq »

ereckers wrote: post #55
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…

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…

Not to mention Drupal is its own little disaster.

Re: WooThemes joins Automattic

#92

Post by mdesq »

mgkimsal wrote: post #90
csomar wrote: post #51

Earlier quoted context omitted.

Gentrification. You can find a theme for $45 that will cost $30K to develop from scratch. You'll find a few plugins that will do exactly what you want that will cost $50k to develop in-house. WordPress is great because you have things that will cost you $xx,xxx to develop and they are already available for you at a minuscule cost.

But it must have been great at something else first, because that wasn't the case years ago - it was obviously better at something else some years ago.

The ease of installation, upgrades, and enhancement (plugin installation) was what made it really stand out. It wasn't always as mature as it is now, but it was always a little bit ahead.

Re: WooThemes joins Automattic

#93

Post by crixlet »

dugmartin wrote: post #24
photomatt wrote: post #20

Earlier quoted context omitted.

WordPress.com, to be exact. :) We contribute and volunteer a lot for core WordPress.

One of the things I love about HN is you often get the answer right from the "top".

in part a result of HN, but another part from the fact that Matt actually reads into the weeds of HN comments! Awesome!

Re: WooThemes joins Automattic

#94

Post by mdesq »

wmeredith wrote: post #61
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…

This is an awesome comment. It's like a mechanic saying Chevy's are a nightmare under the hood. The percentage of people buying cars that give a fuck is rapidly approaching zero because they never even see it.

Exactly. It's a free car that a ton of people drive and lots of auto shops work on but that German mechanics think is an embarrassment.

Re: WooThemes joins Automattic

#95

Post by deckiedan »

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…

Because of this:

1) Users want to be able to update site-name (etc) from the admin interface.

2) We therefore need to store it somewhere.

3) We have a database!

The alternatives are:

- Storing in wp-config.php (which is also done...), but then it's not user-editable from the admin interface.

- Storing in a INI or JSON or similar document, which has only marginal if any benefits over storing in the database.

For deployment, since the location of the database values is fixed, you can set the variables with your deployment scripts.

Re: WooThemes joins Automattic

#96

Post by joeyspn »

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…

https://github.com/roots/bedrock

Re: WooThemes joins Automattic

#97

Post by wodenokoto »

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…

I think you missed the benefit where the theming is done in php.

Why would I want to learn an obscure theming language when I can do my theming in one of the best documented, most used languages for web-development?

Wordpress is a hackers dream. You can open the database and understand what is going on, you can make you site do anything because themes are in php, so even if you don't understand how to write a plugin, you can still hack together the functionality you desire.

Re: WooThemes joins Automattic

#98

Post by joeyspn »

ereckers wrote: post #55
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…

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…

> I've got to ask. If a builder of websites was looking for something that wasn't horrible and built by smart people, which one would that be?

I hope he doesn't reply NodeJS/Express/Ghost cos the corporate site and blog of Strongloop (main nodejs core contributors and express mantainers) is built with wordpress... And with django and rails core devs we could have another surprise... Who knows...

xD

Re: WooThemes joins Automattic

#99

Post by anu_gupta »

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…

Download wp-cli. (http://wp-cli.org/)

  wp seach-replace 'old domain' 'new domain'
Done

Re: WooThemes joins Automattic

#100

Post by morgante »

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…

> It's true however that while Wordpress gets a lot of heat from PHP devs, there is no effort from the PHP community to build something like Wordpress with a better codebase, and a better db schema.

That's not true. Several ex-WordPress developers started the Habari Project to build a modern and clean PHP CMS: http://habariproject.org/en/

Post reply on HN