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

Dear WordPress

ma.tt

Post reply on HN
Print view View original

71–80 of 80 posts

Re: Dear WordPress

#71

Post by kijin »

jacques_chester wrote: post #57
jasey wrote: post #56

Earlier quoted context omitted.

Yes It would be nice, but there is just to many options on how to do the caching and this all depends on the hosting environment. http://codex.wordpress.org/Class_Reference/WP_Object_Cache#P... On the other hand, as of my understanding Drupal does page caching to DB by default (straight out of the box?) and seems super quick.

Yes, yes, the famous hosting environment argument. It comes up whenever the WP team just don't want to do work on the actual guts of the system as opposed to tickbox features. When they added autoupdate, that had large host environment implications. Import/export has host environment implications. It goes on and on. There's no technical reason they can't have a simple page cache in mainline that turns itself off when…

Not to mention that WordPress is now popular enough to bully hosting companies if they wished to do so. What hosting company would want to admit that their services are incompatible with the latest version of WordPress? WordPress is no longer under any realistic obligation to respect the lowest common denominator of hosting environments, because whatever it requires will become the norm. It's a trememdous power that few open-source projects enjoy, and one that could be used for the greater good. If the next version of WordPress just went ahead and required PHP 5.4, for example, the hosting industry would have no choice but to upgrade their PHP versions a.s.a.p.

Re: Dear WordPress

#72

Post by BellsOnSunday »

egypturnash wrote: post #50
sgdesign wrote: post #45

Earlier quoted context omitted.

I'm not sure I agree about the "do not want to know" part. After 5 minutes with Git I don't see how anyone would want to stick with FTP… But yeah, the fact that WordPress hosting plays so badly with git is a big part of the reason why I probably won't be using it again.

FTP: lots of graphical clients available for all OSs, your host can probably give you a bookmark to drop into one for a Windows client and a Mac client, and if they don't it's pretty easy to make a new bookmark pointing to your server with your login/password. You're done, start uploading stuff! Git: Hi! Let me teach you about version control! We'll start with the command line version. Also you may have to ask your h…

@pornelski:

> They say git gets easier once you get the basic idea that branches are homeomorphic endofunctors mapping submanifolds of a Hilbert space.

Re: Dear WordPress

#73

Post by john-n »

adrianhoward wrote: post #68
john-n wrote: post #6

I can appreciate what wordpress has achieved over the years, and what it has helped to create. But the current wordpress code base is a nightmare to work with, and doesn't scale well. Having said that, it is an excellent blogging platform and CMS, but this is something that is usually forgotten, resulting in it finding itself shoehorned into the most inappropriate places.

> But the current wordpress code base is a nightmare to work with, Agreed. But it's also considerably less of a nightmare than it was five years back. Which gives me some kind of hope for the product ;-)

Thats a scary thought.. :) But also yes, some hope.

Re: Dear WordPress

#74

Post by john-n »

jasey wrote: post #54
john-n wrote: post #6

I can appreciate what wordpress has achieved over the years, and what it has helped to create. But the current wordpress code base is a nightmare to work with, and doesn't scale well. Having said that, it is an excellent blogging platform and CMS, but this is something that is usually forgotten, resulting in it finding itself shoehorned into the most inappropriate places.

>But the current wordpress code base is a nightmare to work with I agree >and doesn't scale well. Wordpress scales fine, but it dosent do it magically its self out of the box (but what hobbyist web project written 10 years ago did?) Smashing magazine talked to some of the bigger wp installs to see how they did it (Hot air is doing 45mil /page view a month) http://wp.smashingmagazine.com/2012/09/12/secrets-high-traff.…

Unfortunately most of the issues come from WordPress being written for a web that existed 10 years ago. Static pages with little dynamic content.

This doesn't really work on a more "modern" style of site, where the content is more dynamic and changeable.

Again, a lot of these issues only really arise when your product moves past being a blogging-style platform (such as happened to us), but this is something that either WP, or the WP community, seems to be striving for more and more.

Re: Dear WordPress

#75

Post by 3825 »

username111 wrote: post #28
3825 wrote: post #22

Earlier quoted context omitted.

You're right. It even looks better on IE8. http://i.imgur.com/xrhfJGp.png Here's a screenshot of nightly with a similar issue. http://i.imgur.com/HP02e5b.png Even this, with the font stripped out looks better http://i.imgur.com/6KB2iuG.png

Are you on XP? (I ask because it looks like you don't have any anti-aliasing on). If you adjust your cleartype settings (or turn it on in XP) it will look a bit more normal.

On Windows 7 but yes, you were right. I got a new machine and the cleartype was not turned on yet. It looks much better now. http://i.imgur.com/73Ic6w0.png I appreciate your help.

Re: Dear WordPress

#76

Post by tibbon »

Nux wrote: post #67
dangrossman wrote: post #48

Earlier quoted context omitted.

How is that going to help when over 10 million people are running WordPress on shared hosting accounts where MySQL and FTP are the only database and only file transfer options?

Many shared hosting providers nowadays offer SSL FTP and even SFTP. It's just a question of educating the users.

Exactly. I don't expect all users to start manually SSH'ing into systems, but at least use SSL FTP or SFTP.

Re: Dear WordPress

#77

Post by tibbon »

dangrossman wrote: post #48
tibbon wrote: post #17

Dear Wordpress- meet MVC, git, postgres, sane security and 100% testing. Please leave your old friend FTP- he was never all that safe or great to begin with.

How is that going to help when over 10 million people are running WordPress on shared hosting accounts where MySQL and FTP are the only database and only file transfer options?

I don't see what would prevent those hosts from updating. Its not like installing SFTP and Postgres is that big of a deal (even on a huge deployment, it shouldn't take that long...)

Re: Dear WordPress

#78

Post by tibbon »

alxhill wrote: post #49
sgdesign wrote: post #45

Earlier quoted context omitted.

I'm not sure I agree about the "do not want to know" part. After 5 minutes with Git I don't see how anyone would want to stick with FTP… But yeah, the fact that WordPress hosting plays so badly with git is a big part of the reason why I probably won't be using it again.

> After 5 minutes with Git I don't see how anyone would want to stick with FTP… You're assuming you're dealing with someone at least a bit technical. To them, FTP is drag and drop, git is either 'hacking' or magic.

I think for basic functionality, we still have a long way to go with Git clients.

There's no reason we can't make a Git client that's as simple to use as FTP, and obscures advanced functionality completely unless a user asks for it. Github's desktop clients still aren't quite this.

I'm sure someone would ask why use Git at all then if you're not going to be branching/merging all the time- but at least then when I (more advanced person) need to come in and fix someone's site, I've got a good place to work from, even if they've always just committed linearly to a single branch.

Re: Dear WordPress

#79

Post by reeses »

jasey wrote: post #69
pavs wrote: post #63

Earlier quoted context omitted.

> Where Wordpress does not scale is the default install on shared hosting or a VPS with little resources. True for shared environment but WP does fine even on a low-end vps. 2-3 years ago I helped someone setup wp on a lowend vps server which successfully handled ~5million pageviews under 24 hours, the vps had a measly 1gb memory and the memory usage never went over 700mb. nginx/php-fpm/varnish/apc/w3t done. Took me…

> nginx/php-fpm/varnish/apc/w3t done. Took me less than 1 hour to set it up. Yeap, you got it. Php-fpm and apc goes a long way ;)

They're just weird enough that they are off most people's radar and small enough that installing them is quick.

They're always in my "secret weapons" arsenal when I need to checklist a slow PHP/Drupal installation, especially when they're hosted on VPC or AWS.

Re: Dear WordPress

#80

Post by 3825 »

michalstanko wrote: post #23
3825 wrote: post #14

Dear Matt, Could you please use any font other than Source Sans Pro[1]? It looks terrible on at least one major desktop operating system.[2] [1] https://www.google.com/fonts/specimen/Source+Sans+Pro [2] http://i.imgur.com/9gOuTdH.png

Looks like you need to turn on ClearType.

I did. That was my problem. https://news.ycombinator.com/item?id=5779561
Post reply on HN