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

WP21

ma.tt

Post reply on HN
Print view View original

141–150 of 183 posts

Re: WP21

#141

Post by [deleted] »

9dev wrote: post #43
MangoCoffee wrote: post #30

WP is 21 years old, and people on HN still bishing and crying about it. How come no one has offered something that can beat WP in 21 years?

Nah, that’s not how it works. People are also complaining about the quality of Google‘s search results, but has anyone come up with a something that can beat them? Technically, yes! But practically, Wordpress has such a velocity, it’s mostly impossible to stop at this point. There’s an ecosystem of millions of plugins, themes, entire agencies around Wordpress, that’s something you can’t really solve. So just because…

[deleted]

Re: WP21

#142

Post by blain »

deerfeeder wrote: post #120
askonomm wrote: post #66

I just wish WordPress actually adhered to development standards, not actively tried to break them. Using globals everywhere and encouraging spaghetti code with its classic themes, and with its new themes it evidently learned nothing and is encouraging JSON inside HTML comments which obviously has no editor support, is very prone to errors, besides being just plain stupid (like seriously, some senior engineers I assum…

If I have to work with WP I always use the timber framework instead of the block/classic version https://timber.github.io/docs/v2/

I have worked with themes that used Timber and it has its own set of quirks.

I also have an opinion that using things like Timber in WP themes just adds to the inconsistency instead of helping it. Taking over website with Timber when you never heard of it is fun.

I don't want discourage, use what you like. Just my 2 cents.

Re: WP21

#143

Post by rob74 »

Do you know what makes you feel old? When you read "WP" and think not of WordPress (which would now apparently be accepted as an adult in even the most conservative countries), but of WordPerfect (https://en.wikipedia.org/wiki/WordPerfect - which is now at "midlife crisis" age).

Re: WP21

#144

Post by Tijdreiziger »

rrreese wrote: post #86
ssalat wrote: post #25

Quick judgments and strong opinions have unfortunately become part of the community. Having spent the last 2-3 months working excessively on WordPress development, I would like to say a word about the excellent isolation of code with blocks ("Gutenberg"). As standalone plugins or in combination with Advanced Custom Fields, these allow for perfect, modular websites and development flows (design system), where even the…

>Quick judgments I think most peoples judgments have been formed over 21 years. WordPress initially gained a reputation for being a fast and easy way to setup a website, then gained a reputation for being a security nightmare. Maybe its not anymore but people are right to be sceptical. I sure do see a lot of CVEs in the weekly update I check - maybe they're all low risk, or relate to rarely used plugins.

Personally (and this is just based on my gut feeling), I don’t think WP core is more insecure than other CMSes.

The real problem is the plugin ecosystem, which is not impossible to navigate for the disciplined, but at times bears resemblances to the Wild West.

So, what ends up happening is:

1. Cheap ’experts’ install every plugin under the sun.

2. One of these plugins inevitably gets pwned.

3. Headline: ‘WordPress backdoored’.

Re: WP21

#145

Post by askonomm »

Tijdreiziger wrote: post #140
zelphirkalt wrote: post #77

Earlier quoted context omitted.

They encourage lots and lots of bad practices. I mean, just look at themes and how they are built by default. Comments in a CSS file describe the theme metadata. Using concattenation instead of composition everywhere, so that parts of HTML are not reusable. CSS, inside JS inside HTML inside PHP ... Part of it is this implicit structure it defines, which file it loads adter ehich other file to make a whole page. It se…

Their mantra of ‘never break backwards compatibility’ is a double-edged sword. It makes them extremely friendly to non-technical users, which I think is the majority of their userbase. However, it makes it impossible for them to change technical decisions made in the past.

That would be fine, imo. But seeing as their new development efforts (Block/Gutenberg themes) are also making horrible decisions when they no longer have to (such as putting templating markup inside of HTML comments as JSON)[1]

E.g:
I've lost any faith I had in their core development teams competence. I would understand if development choices made 20 years ago weren't all that great by todays standards, and never breaking backwards compatibility would be the reason it still is bad today, but their new themes can be used independently from their old themes as an entirely different implementation, so they had a chance to finally do what is industry standard, and they chose to again make it horrible to write theme markup code that is prone to errors, has no editor support (what editor supports JSON in HTML comments?) and enforces more spaghetti to be made.

[1]: https://developer.wordpress.org/block-editor/getting-started...

Re: WP21

#147

Post by todotask »

todotask wrote: post #32
MangoCoffee wrote: post #30

WP is 21 years old, and people on HN still bishing and crying about it. How come no one has offered something that can beat WP in 21 years?

It's more objective if you compare by carbon footprint among others and how you build your site.

Meaning there is always challenges is all software and everyone has different expectations, I don't see why I get downvoted.

Re: WP21

#148

Post by Raed667 »

debesyla wrote: post #137
Raed667 wrote: post #111

I will always fondly remember that time i was in college (~2011), and created a fully working social network for my classmates using WordPress and ungodly amount of Plugins, and ducktape code I barely understood. A user profile display was ~30 SQL queries (who needs cache), and my poor 5$ VPS was sweating ... learned a lot on what not to do! fun times !

30 SQL queries are basically normally functioning WordPress, it's a bit more unusual when it gets to 150+ queries zone :)

I remember laughing because one of the plugins was storing the HEX color value of a small banner in a DB and for every page load it needed to fetch it again even if the banner was nowhere on the page.

Suddenly it changed my look on all all those "easy" knobs and fields from the admin panel and they looked very costly

Re: WP21

#149

Post by [deleted] »

kunley wrote: post #121
rrreese wrote: post #86

Earlier quoted context omitted.

>Quick judgments I think most peoples judgments have been formed over 21 years. WordPress initially gained a reputation for being a fast and easy way to setup a website, then gained a reputation for being a security nightmare. Maybe its not anymore but people are right to be sceptical. I sure do see a lot of CVEs in the weekly update I check - maybe they're all low risk, or relate to rarely used plugins.

I think the root of bad reputation was due to various plugins and their usage pattern: lots of non-tech users heard that they can use plugins X Y Z for fun and profit, so they started to use them, but no one told them that managing dependencies requires some skill or at least discipline; that the fact some 3rd party pluggable software exists doesn't automatically mean it's good, viable, maintainable and safe; and tha…

[deleted]

Re: WP21

#150

Post by paulryanrogers »

5636588 wrote: post #128
JeanMarcS wrote: post #109

Earlier quoted context omitted.

WordPress is a great blogging CMS. The fact that people use it for something else is what create strong opinions. Example : woo commerce. Products ? In the WP_POST db. Orders ? In the WP_POST db. And in every post about WP it says that using WP_POST for storing your data is good practice. Well I don't think it is (but it's only my opinion. A strong one). And the problem is that a LOT of plugins and themes are like th…

FYI, WooCommerce added the ability to store orders in a separate database table.

Do you mean table(s)?
Post reply on HN