Explore >> Select a destination
|
You are here 
|
nathan.torkington.com | ||
| | | | |
www.thepollyproject.org
|
|
| | | | | ||
| | | | |
richardmiller.co.uk
|
|
| | | | | Background I am recreating Lime Thinking's current website [http://www.limethinking.co.uk] using Symfony2 [http://symfony.com/], much of the site is made up of what are effectively static pages. The main content of the page is stored as an XML file which then has the overall XSL template | |
| | | | |
tomasvotruba.com
|
|
| | | | | Final classes have [many](https://ocramius.github.io/blog/when-to-declare-classes-final/) [great](https://tomasvotruba.com/blog/2019/01/24/how-to-kill-parents) [benefits](https://matthiasnoback.nl/2018/09/final-classes-by-default-why/) for future human readers of your code. They have even more benefits for static analysis and Rector rules. But what if we have a project with 1000+ classes and 10 minutes and want to automate the finalization process safely? | |
| | | | |
nolanlawson.com
|
|
| | | I've been doing web performance for a while, so I've spent a lot of time in the Performance tab of the Chrome DevTools. But sometimes when you're debugging a tricky perf problem, you have to go deeper. That's where Chrome tracing comes in. Chrome tracing (aka Chromium tracing) lets you record a performance trace that... | ||
