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

WordPlate: WordPress on Composer with sensible defaults

github.com

Post reply on HN
Print view View original

61–70 of 105 posts

Re: WordPlate: WordPress on Composer with sensible defaults

#61

Post by nicbou »

montroser wrote: post #39

WordPress is plain crazy. Marketing people insisted on WordPress so we reluctantly put it off in its own isolated network and expected bad things to happen. And, they did... - WordPress consultant hired by marketing people while "editing the theme" introduced an infinite loop which caused OOM killer. That's when we learned you can point-click your way to editing actual php code in the admin web interface! Complete an…

I found Craft CMS to be WordPress made by sensible people. Well worth the licence. You can simply disable admin changes in production, or set fine grained permissions.

Re: WordPlate: WordPress on Composer with sensible defaults

#62

Post by zach_garwood »

iambateman wrote: post #36

Adding composer to WordPress isn’t gong to fix it. The problem is more fundamental - WP was conceived as a blog engine and has proven itself constitutionally incapable of truly moving beyond that frame. * features People say that “you can just add a plug-in” for whatever, and that’s true. But so many things that should be core are not (advanced custom fields, forms) and other features have no place in modern WordPres…

I'd be interested in your page builder. Can I get in on the beta?

Re: WordPlate: WordPress on Composer with sensible defaults

#63

Post by tyingq »

berkle4455 wrote: post #60
tyingq wrote: post #28

Earlier quoted context omitted.

>Also $wpdb->prepare() uses parametrised values. They appear to be a hand-rolled PHP version of imitation client-side parameterized values, not the actual database library ones. https://github.com/WordPress/WordPress/blob/master/wp-includ...

Wow. That is so much code just to avoid calling mysqli_prepare(). And they insist on using a weird printf inspired syntax instead of ? or :field.

I suppose it's pretty battle-hardened by now, but I'd be afraid to ever touch that code for fear of introducing a SQL injection.

Re: WordPlate: WordPress on Composer with sensible defaults

#65

Post by e12e »

iambateman wrote: post #36

Adding composer to WordPress isn’t gong to fix it. The problem is more fundamental - WP was conceived as a blog engine and has proven itself constitutionally incapable of truly moving beyond that frame. * features People say that “you can just add a plug-in” for whatever, and that’s true. But so many things that should be core are not (advanced custom fields, forms) and other features have no place in modern WordPres…

Best of luck on your cms - I must admit I think the future lies with something like deno/fresh (https://fresh.deno.dev) or astro (https://astro.build) along with cdn/edge computing.

> Recently I spun up a site for a client and the plug-ins cost over $1000 just to get them going.

I think that's the wrong way around - you/your client could buy stuff costing a thousand dollars because of the huge wp ecosystem (however dysfunctional it may be - I once looked briefly at how to write and sell a wp theme - and quickly moved on to different pursuits). Now, how much value did you get from that? That's one of the big draws of wp.

Im sure your new system will cover 80% of that - but what about the themes and plug-ins someone else needs?

Re: WordPlate: WordPress on Composer with sensible defaults

#66

Post by e12e »

jpoesen wrote: post #3

What advantages does WordPlate have over Bedrock[1], some of whose packages WordPlate also uses? [1] https://roots.io/bedrock/

Found some discussion here, but tbh it's a little light for me not to think that NIH syndrome doesn't come into it?

https://github.com/vinkla/wordplate/issues/234

Re: WordPlate: WordPress on Composer with sensible defaults

#67

Post by cricalix »

minusf wrote: post #16
kijin wrote: post #9

Earlier quoted context omitted.

There's much more to WordPress than the ecosystem. If we just think of it as a legacy tool that is only limping along because of the plugins, we will forever be perplexed that it continues to exist. WordPress is the FLOSS alternative to Wix et al. It is the only practical software that enables people to create and self-host an online presence without having to type a single line of code, and without being beholden to…

php's success is tightly connected with LAMP, namely apache mod_php and mysql/mariadb. it wouldn't be hard to put together the base of wordpress in python on top of django. but hosting companies for decades cared only about mod_php and had no one click uwsgi/fastcgi solutions. although this still doesnt answer why wordpress became king of the hill in the php ecosystem. was textpattern/drupal/joomla/etc that much wors…

Anecdotally, yes Joomla and Drupal were much harder to work with and get them to look "nice".

Re: WordPlate: WordPress on Composer with sensible defaults

#68

Post by iambateman »

zach_garwood wrote: post #62
iambateman wrote: post #36

Adding composer to WordPress isn’t gong to fix it. The problem is more fundamental - WP was conceived as a blog engine and has proven itself constitutionally incapable of truly moving beyond that frame. * features People say that “you can just add a plug-in” for whatever, and that’s true. But so many things that should be core are not (advanced custom fields, forms) and other features have no place in modern WordPres…

I'd be interested in your page builder. Can I get in on the beta?

Yep! Just shot you an email back.

Re: WordPlate: WordPress on Composer with sensible defaults

#69

Post by iambateman »

e12e wrote: post #65
iambateman wrote: post #36

Adding composer to WordPress isn’t gong to fix it. The problem is more fundamental - WP was conceived as a blog engine and has proven itself constitutionally incapable of truly moving beyond that frame. * features People say that “you can just add a plug-in” for whatever, and that’s true. But so many things that should be core are not (advanced custom fields, forms) and other features have no place in modern WordPres…

Best of luck on your cms - I must admit I think the future lies with something like deno/fresh ( https://fresh.deno.dev ) or astro ( https://astro.build ) along with cdn/edge computing. > Recently I spun up a site for a client and the plug-ins cost over $1000 just to get them going. I think that's the wrong way around - you/your client could buy stuff costing a thousand dollars because of the huge wp ecosystem (howev…

I’ll check out fresh and Astro!

As far as costs go…

Beaver builder - 250 Custom fields - 100 Faceting - 100 forms - 150 Import/export - 100

It doesn’t take long to get to $1000!

The new system I’m working on will be extensible for various needs using new composer packages. So if someone wanted to write an obscure form handler, they could trivially add it to Prodigy as well.

Re: WordPlate: WordPress on Composer with sensible defaults

#70

Post by 9dev »

unity1001 wrote: post #57
9dev wrote: post #6

Just reading this again gives me a backflash of the horrors of working with WordPress. If you haven’t seen the source, you don’t know just how god-awful the code is - and it just won’t die, because of all the ecosystem traction it has. Even the PHP developers have chosen to ignore WordPress in language evolution considerations, as the WordPress community refuses to do accept kind of progress for their project - they…

> If you haven’t seen the source, you don’t know just how god-awful the code is And yet, it runs 50% of all websites and 30% of all ecommerce websites. ... Apparently it is not god awful. If running 50% of the web is godawful, anybody would want their software to be that much 'godawful'... Empty elitism contrasting the actual reality of life and business...

Just because we don’t have a better choice doesn’t make Wordpress a good choice.
Post reply on HN