I don't think its really reasonable to say 'X sucks' without taking uses cases into account. While PHP has a number of shortcomings, it is great for things where ruby/rails would be huge waste of time. Build some small brochure websites in rails, and build the same ones in PHP. I bet you'll be done much sooner & deployed more cost effectively using PHP. This might not be the kind of work you aspire to doing, but I think the example still holds.
It still looks like an inferior clone. The typefaces are all wrong, the kudos button has a wonky shape. Its differences are just enough to hit the uncanny valley for me.
Probably not, but you might want to give phpcpd, pdepend and pmd a try. They're all open source static analysis tools for PHP, and will find a number of potential issues.
I also find getting a good set of rules for phpcs is extremely helpful in PHP. You can use its sniffs to catch past mistakes and enforce consistent coding standards.
Even more sad if you live in a northern climate. You get go to work in the dark, and return in the dark. Daylight is just something that happens during work.
While I can understand this might have been fun from a hacking/building experience, I don't understand why do it. Everything except the micro templating already exists in python.
Sure it costs nothing until you are compromised and any valuable data you have is taken. Remote code exploits are extremely dangerous. And mitigating them with a small amount of i/o overhead seems like a fair trade off.
That's clearly not the case in all situations though. If its simply a userid there would be no reason to use pickle. JSON or simple string storage would be sufficient. Clearly people are storing far more than just a userid in their client side sessions.
Depending on the situation you would want database inserts to reflect the passage of time, and not always stick to a 'start of request/job' time. I can see the desire of the parent to want to have all the HTML generated with the same understanding of time, but as a general practice I still think its a bad one to fix time.
I call BS on this. From my experience in Toronto, there are many companies looking for developers and having a difficult time finding quality candidates.
Last I checked zepto doesn't have support for any of the simulated selectors like `:checked`, `:input` and friends. If you use any of them, its not drop in.
Sure but $('.clicky').on('click', doSomething); means no loops at all, and will bind events to all matching elements. I don't think there is a native API way to do this.
Well one nice affordance jQuery offers, is you can do manipulations en-mass without having to write out a loop, or use Array.forEach(). This helps simplify event binding and manipulation code. Also there are selectors in jQuery that are not available in querySelectorAll. And lastly querySelectorAll has some pretty buggy implementations. jQuery smoothes these out.