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

101–110 of 159 posts

Re: WooThemes joins Automattic

#101

Post by codygman »

coldtea wrote: post #73
themodelplumber wrote: post #11

Earlier quoted context omitted.

WordPress' API and its limitations are so annoying that I just can't imagine developing for this platform unless you desperately need money. Ideally they develop some new product that is more competitive than the current combination of WP & WC.

> WordPress' API and its limitations are so annoying that I just can't imagine developing for this platform unless you desperately need money. Yes, it's for professionals. Hobbyists can always use some Haskell web framework.

Implying API limitation and annoyance means professional... Yuck.

Professionals can also use a Haskell web framework. Increasingly so for their day jobs, at least in my case.

Re: WooThemes joins Automattic

#102

Post by pknight »

luisrock wrote: post #79

Any plans for Sensei plugin? My business depends on it and I am a little scared…

Usually an acquisition spells trouble for the product's users, but this is a different kind of situation. I think WooCommerce and Sensei will only get better as a result. The only folk who have to worry is the people building competing products.

Re: WooThemes joins Automattic

#103

Post by pknight »

usaphp wrote: post #38
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 number one reason of its success are themes and plugins.

The number one reason is because it is FOSS, easy to install, easy to use and easy to extend. The thriving themes and plugins ecosystem is the result of the platform becoming popular because of the aforementioned. If it wasn't FOSS WordPress wouldn't be where it is today.

Re: WooThemes joins Automattic

#104

Post by aasarava »

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?

Looking for one CMS or platform that can fit every kind of website seems strange to me. It'd be sort of like recommending a TV-DVD-DVR combo unit to both your mother who just wants to watch some TV, and to your developer friend who wants a high-performance gaming display.

I've worked primarily with Drupal for the past 8 years. But the clients tend to have very complex needs, including multiple roles and workflows applied to varying content types.

If a client were to come to me and want a blog or a simple brochure site that will be edited by no more than a couple marketing staff, I will tell them Wordpress might be a better option.

Re: WooThemes joins Automattic

#105

Post by rhblake »

mgkimsal wrote: post #87
jwdunne wrote: post #78

Earlier quoted context omitted.

For some of the websites I have had to maintain in Joomla, it would be much more efficient for the company if I converted to Wordpress and the writers use that. Wordpress is easy to use. With plugins, such as advanced custom fields, you can do even more. I've impressed many clients with how easy to use the "website's CMS" in turn around times they have never experienced before. The code is shocking. The plugin archit…

> It's just impossible to match it with the number of extensions It's almost precisely because there's very little uniformity between anything. It's often much more efficient to just install a new wordpress, migrate some content over and start 'fresh' than it is to modify an existing theme with new functionality; just find a different theme that does what you want and migrate your content and images over to that. Tha…

CCK has been part of Drupal core since version 7 (2011). Now simply known as "fields". Fields+views is simply fantastic compared to what WordPress - including its plugins - gives you. (Views will by the way be in Drupal 8 core.)

Re: WooThemes joins Automattic

#106

Post by lightlyused »

Domenic_S wrote: post #54
tacone wrote: post #47

Earlier quoted context omitted.

Quite frankly, Drupal 7 is a complete nightmare. It's so heavy it has to cache aggressively for even the basic DB operations, and you'll get Mb's of cache in exchange of nothing. The DB schema is so structured that even exporting a table content is extremely difficult to do in plain SQL. You often find PHP code stored in the DB, so taking over a former contractor is pretty hard. The code style is as old school as Wor…

If you "often" find PHP code in the DB, you're taking over for some godawful contractors. The PHP filter is rarely used and is even being deprecated from D8.

First thing I remove from D7.

Re: WooThemes joins Automattic

#108

Post by oldmanjay »

deckiedan wrote: post #95
Domenic_S wrote: post #88

Earlier quoted context omitted.

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 deplo…

Giving users everything they want is a surefire way to build a disaster of a codebase. I have no knowledge of WordPress, that's just a general principle. Users are a bit too silly to trust.

Re: WooThemes joins Automattic

#109

Post by lightlyused »

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…

This comes from developer and client feedback in poll after poll of WordPress users and developers.

If you've never experienced anything else, of course what you have is always the best.

Re: WooThemes joins Automattic

#110

Post by Domenic_S »

deckiedan wrote: post #95
Domenic_S wrote: post #88

Earlier quoted context omitted.

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 deplo…

Certainly there are configuration options that are appropriate to store in the database, but I'm trying to understand why domain is one of them. The site knows what domain it is on by virtue of being hosted on that domain.

Storing the domain in the DB may be reasonable if it's done once, but WP does it multiple times: WP_SITEURL ("the address where your WordPress core files reside"), WP_HOME ("the address you want people to type in their browser to reach your WordPress blog") and of course GUIDs for every post have the domain hardcoded into their values (that can mess up links in a weird way, where you're on your local environment, click a link, and now you're silently on prod).

I could definitely be missing something, but I can't for the life of me figure out why this is a good idea.

Post reply on HN