https://t.co/kZwv4TlmRB
1/12 @HathorNetwork offers a unique set of features for both builders and users. Some well known ones, others not so much. Let’s look at why you might want to consider Hathor as the layer 1 solution for your project. $HTR @HTRFDT #BuildOnHathor
https://t.co/kZwv4TlmRB
More from Tech
These past few days I've been experimenting with something new that I want to use by myself.
Interestingly, this thread below has been written by that.
Let me show you how it looks like. 👇🏻
When you see localhost up there, you should know that it's truly an experiment! 😀
It's a dead-simple thread writer that will post a series of tweets a.k.a tweetstorm. ⚡️
I've been personally wanting it myself since few months ago, but neglected it intentionally to make sure it's something that I genuinely need.
So why is that important for me? 🙂
I've been a believer of a story. I tell stories all the time, whether it's in the real world or online like this. Our society has moved by that.
If you're interested by stories that move us, read Sapiens!
One of the stories that I've told was from the launch of Poster.
It's been launched multiple times this year, and Twitter has been my go-to place to tell the world about that.
Here comes my frustration.. 😤
Interestingly, this thread below has been written by that.
Let me show you how it looks like. 👇🏻
Recently I just refunded all Poster's sales from Gumroad. Being that said, I decided to not using that service anymore.
— Wilbert Liu \U0001f468\U0001f3fb\u200d\U0001f3a8 (@wilbertliu) November 19, 2018
Here's a little story \U0001f447\U0001f3fb
When you see localhost up there, you should know that it's truly an experiment! 😀
It's a dead-simple thread writer that will post a series of tweets a.k.a tweetstorm. ⚡️
I've been personally wanting it myself since few months ago, but neglected it intentionally to make sure it's something that I genuinely need.
So why is that important for me? 🙂
I've been a believer of a story. I tell stories all the time, whether it's in the real world or online like this. Our society has moved by that.
If you're interested by stories that move us, read Sapiens!
One of the stories that I've told was from the launch of Poster.
It's been launched multiple times this year, and Twitter has been my go-to place to tell the world about that.
Here comes my frustration.. 😤
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.
There has been a lot of discussion about negative emissions technologies (NETs) lately. While we need to be skeptical of assumed planetary-scale engineering and wary of moral hazard, we also need much greater RD&D funding to keep our options open. A quick thread: 1/10
Energy system models love NETs, particularly for very rapid mitigation scenarios like 1.5C (where the alternative is zero global emissions by 2040)! More problematically, they also like tons of NETs in 2C scenarios where NETs are less essential. https://t.co/M3ACyD4cv7 2/10
In model world the math is simple: very rapid mitigation is expensive today, particularly once you get outside the power sector, and technological advancement may make later NETs cheaper than near-term mitigation after a point. 3/10
This is, of course, problematic if the aim is to ensure that particular targets (such as well-below 2C) are met; betting that a "backstop" technology that does not exist today at any meaningful scale will save the day is a hell of a moral hazard. 4/10
Many models go completely overboard with CCS, seeing a future resurgence of coal and a large part of global primary energy occurring with carbon capture. For example, here is what the MESSAGE SSP2-1.9 scenario shows: 5/10
Energy system models love NETs, particularly for very rapid mitigation scenarios like 1.5C (where the alternative is zero global emissions by 2040)! More problematically, they also like tons of NETs in 2C scenarios where NETs are less essential. https://t.co/M3ACyD4cv7 2/10
There is a lot of confusion about carbon budgets and how quickly emissions need to fall to zero to meet various warming targets. To cut through some of this morass, we can use some very simple emission pathways to explore what various targets would entail. 1/11 pic.twitter.com/Kriedtf0Ec
— Zeke Hausfather (@hausfath) September 24, 2020
In model world the math is simple: very rapid mitigation is expensive today, particularly once you get outside the power sector, and technological advancement may make later NETs cheaper than near-term mitigation after a point. 3/10
This is, of course, problematic if the aim is to ensure that particular targets (such as well-below 2C) are met; betting that a "backstop" technology that does not exist today at any meaningful scale will save the day is a hell of a moral hazard. 4/10
Many models go completely overboard with CCS, seeing a future resurgence of coal and a large part of global primary energy occurring with carbon capture. For example, here is what the MESSAGE SSP2-1.9 scenario shows: 5/10