NewsReader42

Not rocket science, block it with "deny" ...

It's still Wordpress, still slow, still insecure so why should we care?

If you're not willing to learn or be adaptive to your customer' needs then you have no place creating websites as a profession

or just remove wordpress and use something secure, not bloated and easier to develop with.

Avoid at all costs caching the cachable parts of the app will save you nothing in the REAL WORLD

Let's hope they made theirs faster than yours because your website is painfully slow.

usertesting.com

I found it quite insightful

Step 1. Uninstall Wordpress. Step 2. Install something faster, less bloated and more secure. Step 3. Drink beer :)

Can't even click the links down the RHS in the demo. (FF 33.0.2)

He said "Lightweight"

We ourselves built a project with speed and security in mind and are working on open sourcing it in 2015

Recruiters don't like to have their eyes baffled by complex resumes this is a known fact, they like clear and concise information laid out in an informative way. They care even less about irrelevant information on a resume because it's a waste of time.

Haha, now try getting it on a site with images and other content i/e a normal website.

I've been at the forefront of pagespeed since before it was trendy, I've achieved 100% 3 times and 95% or above about 50 times, my sites load in less than 500 milliseconds - that's ENTIRE page load and DOM ready, when you can achieve that then you can boast!

the + attribute is not supported everywhere so please for the love of god stop giving out your bad in fact terrible tutorials and polluting the internet with bad code

The json_decode() function decodes the value passed as a string (JSON) into the data in correct format (in this case: an array).....

That's incorrect. json_decode with no second argument creates a standard object not an array. If you want an array then pass true as the second argument

I don't know where to start.... Telling people to not write fast code for the sake of other people checking that code is absolute madness. The code is ran thousands or millions of times per day and is the obvious choice to lean toward when optimizing instead of leaning toward optimizing for some theoretical idiot who likes to read lines of code in a fast and efficient manner to do his job.

This job may be ran once or twice a year which is nowhere near the amount of savings in various computational power / hardware etc compared with the wages of some geek who simply can't be bothered to do his job well.

I don't know where to start with your ramblings.

1. Don't use an ODM - MongoDB is scheme-loose for a reason yet you want to lock in a schema with a mapper????? 2. Go use PostGres if you're that worried about so called schema rot else write migration scripts like everyone else.

There is always a price to pay for flexibility and scalability

Speed your own website up first before you do :)

By size I mean dimensions.

You should also check the size of the image to make sure it's actually an image. I can quite easily get a php file into your system using your current way as you ONLY check for extension.

Does not work.

You have a size wrong in the Iphone 5. You're not taking into account the width of the scroll bar (if any).

The wrapper should be 20em wide and the iframe inside should have 21.2em wide. You should also use overflow:hidden on the wrapper.

Out of all of these I've found this guy has done it the best so far and is the best representation of how a websie actually looks on an iPhone 5

http://www.nodex.co.uk/services/mobile-responsiveness-intera...

Perhaps you can look at his CSS and see how he did it?

Why are you blatently trying t rip off the older nginx logo? . Do you think it will give your poor attempt at an app some credibility?

Doesn't work

wow, you want a medal?

If this is anything like your terrible CSS blogs then this should be comical

Your slow ass website sucks ballz

Also, you claim that you designed Tag Heuer's website to be mobile first. This is a complete fabrication plus their site is terrible on a mobile.

More bad advice from this guy.

STOP POLLUTING THE GLOBAL CSS NAMESPACE.

Finally you advise something that it right.

It only took about 50 blog posts!