City Manager Spencer Cronk: As a City, we are doing our best to help those in need.
LIVE: ❄️ City of Austin leadership including @AustinEnergyGM will address the unprecedented severe weather.
💻 Due to tech limitations, it will only be available via Facebook Live here: https://t.co/PchiwUgP0M
We will be live-tweeting in this thread.
City Manager Spencer Cronk: As a City, we are doing our best to help those in need.
How can people without power get to warming centers if they're asked to stay off roads?
Ortiz: If you need to get to a warming center, make the decision now and go when it is still daylight. If you wait, it's going to get more complicated.
Sargent: We have some situations where we've had some outages and we're including that in our load shed requirements. Right now, that is all wrapped together to meet those requirements from ERCOT.
Sargent: We are working with our Utility Contact Center to back up @ATX_311. We are working in conjunction with our City IT and they're working very diligently to restore those services.
Sargent: We are making those requests. We have reached out to specific groups of customers and they are responding by conserving. The thing I talked about that individuals can do - lowering thermostat, closing blinds, will help us.
Sargent: That is not the case. The outages are across the system. They are designated by specific circuits and those are circuits - if you look at the outage map, they're across our service territory.
Sargent: If we see that continue across the entire footprint, across our state, that we'll continually to have challenges to meet the demand. Asking customers to conserve will continue to be critical.
More from Tech
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.