In my view, DX should be renamed "Developer Convenience" as we all know that convenience is often a trade-off.
Please forgive the self-promotion but this was exactly the premise of a conference talk I gave ~18 months ago at performance.now() in Amsterdam: https://www.youtube.com/watch?v=f5felHJiACE
iirc, most content delivery networks have now configured initcwnd to be around 40, meaning ~58kb gets sent within the TCP slow start window and therefore 14kb is no longer relevant to most commercial websites (at least with H1/H2, as you mentioned QUIC/H3 uses UDP so it's different)
This will make complex upserts so much more simple, fantastic addition.
I really hope `RETURNING` support gets added to `MERGE` asap though (I believe it's been noted as a fairly trivial addition to come in future), then it'll be super powerful for doing bulk upserts that require post-processing.
You've got a fairly heafty JS file on the critical rendering path (350kb), so one option to help your roundtrips 3 is to preload the other files it uses so it's not dependent on the JS download and executing before they are discovered. See: https://web.dev/preload-critical-assets/
I don’t want to distract from the tragedy itself but, even after all this, more people will continue to suffer due to the subsequent cladding scandal.
The UK government are trying to pass the costs of remediation for other cladded buildings on to leaseholders who didn’t have any involvement in the design, build or sign-off of their buildings.
Some people are already being bankrupted through extortionate waking watches, mitigation and remediation bills and I’ve even heard that one person in my city (Leeds) has killed themselves due to the stress.
According to the select committee reviewing the Building Safety Bill, “the only people who believe leaseholders should pay are the government”.
The House of Lords has proposed an amendment to the bill stating that leaseholders won’t be made to pay (note: not forcing the tax payer to pay, just ensuring the leaseholders don’t) and the Housing Committee (namely MP Robert Jenrick) are rejecting this on the basis that the tax payer shouldn’t foot the bill.
We’re talking sums amounting to up to £100k being charged to people who paid similar amounts for their apartments in the first place! One affected block was built since Grenfell, so the entire ownership could effectively be in massive negative equity.
The government have put together a fund of £1bn for non-ACM cladding remediation, expecting that to cover ~600 buildings, but already over 2,700 buildings have applied and the estimated cost UK-wide is upwards of £15bn.
The whole thing is an utter shambles and people are stuck unable to sell their properties (stalling the first time buyer market as they can’t move up to other properties, and meaning they cannot move for work in a time when there are masses of redundancies) or even remortgage!
> schwinn: were the filmstrips enough to convince them, or did your bosses want to see numbers/stats like how many were dropping off your site for each x-seconds of delay?
There are some great stats on bounce rate / abandonment on WPOStats: https://wpostats.com/
This is my favourite:
> 53% of visits to mobile sites are abandoned after 3 seconds according to research from Google's DoubleClick.
One thing to note, to those stakeholders who are aware of web traffic stats, is that if a site uses client-side analytics (e.g. Google Analytics) and it hasn't loaded the analytics script by the time the user abandons the site, they won't be tracked, so the bounces won't be affected – it'll be like they were never there.
So ultimately, bounce rates in analytics tools can typically be significantly worse than reported when web performance is poor.
One technique I've seen work well for getting bosses to care is showing them how much slower their sites are than their competitors - nobody wants to be worse than their competition.
In SpeedCurve, for just around $8/mo per page/site you can set up daily synthetic checks for the business and its competitors, covering multiple profiles: mobile/3g, tablet/4g, desktop/fibre.
You can use both the metrics (Start Render, SpeedIndex, Hero Paint) [1] and the filmstrip videos to literally show them how they compare side-by-side [2] – this is super-powerful as it's so visual.
Disclaimer: I don't work for SpeedCurve, just a fan of the tool.
iOS is getting Service Worker support in 11.3 [1], this is one of the key foundations for PWA support, so the situation is improving. I reckon it’ll be a long time before we see PWAs in the App Store though!
Are 16x TB3, 4x TB2 AND 4x USB3 actually achievable with current/near-future hardware?
If Apple were to implement this, I'd imagine it would be N x TB3/USB3 USB-C format ports, an ethernet port and maybe HDMI (though a dongle would possibly negate that – if 2.1 can be achieved that way)
Can anyone comment on the best way to run multiple DNS services?
Is this as simple as setting up the same records on multiple providers and updating your nameservers to point to the different providers? Or is there more involved?
Are there any providers which will replicate records from your 'master' provider, or is this going to be manual?
It's not so much about performance, it's about specificity. To override anything in `.c-button.primary` you'd need something to have equal or greater specificity (meaning you couldn't do `.c-button--large`).
Obviously this is a fairly basic example, but with more chaining comes more levels of specificity which makes for increasingly difficult changes and worse productivity.
Does anyone know if this is going to be available via the standardised Web Payments API? [1] (support being worked on by Chrome [2] and Microsoft Edge [3]) That way web developers won't need to build different implementations for different platforms.
Please forgive the self-promotion but this was exactly the premise of a conference talk I gave ~18 months ago at performance.now() in Amsterdam: https://www.youtube.com/watch?v=f5felHJiACE