So I’m probably taking this discussion about ‘nationalism’ on Twitter with @nealjclark1 @AnarContrarian & @RizomaSchool way more seriously than I should, but it prompts me to say a little more about nationalism & localism – and why I don’t want to mix them up 🧵
More from All
ChatGPT is a phenomenal AI Tool.
But don't limit yourself to just ChatGPT.
Here're 8 AI-powered tools you should try in 2023:
1. KaiberAI
@KaiberAI helps you generate beautiful videos in minutes.
Transform your ideas into the visual stories of your dreams with this Amazing Tool.
New features:
1. Upload your custom music
2. Prompt Templates
3. Camera Movements:
Check here
https://t.co/ivnDRf628L
2. @tldview TLDV
Best ChatGPT Alternative for meetings.
Make your meetings 10X more productive with this amazing tool.
Try it now:
https://t.co/vOy3sS4QfJ
3. ComposeAI
Use ComposeAI for generating any text using AI.
It’s will help you write better content in seconds.
Try it here:
https://t.co/ksj5aop5ZI
4. Browser AI
Use this AI tool to extract and monitor data from any website.
Train a robot in 2 minutes to do your work.
No coding required.
https://t.co/nNiawtUMyO
But don't limit yourself to just ChatGPT.
Here're 8 AI-powered tools you should try in 2023:
1. KaiberAI
@KaiberAI helps you generate beautiful videos in minutes.
Transform your ideas into the visual stories of your dreams with this Amazing Tool.
New features:
1. Upload your custom music
2. Prompt Templates
3. Camera Movements:
Check here
https://t.co/ivnDRf628L
2. @tldview TLDV
Best ChatGPT Alternative for meetings.
Make your meetings 10X more productive with this amazing tool.
Try it now:
https://t.co/vOy3sS4QfJ
3. ComposeAI
Use ComposeAI for generating any text using AI.
It’s will help you write better content in seconds.
Try it here:
https://t.co/ksj5aop5ZI
4. Browser AI
Use this AI tool to extract and monitor data from any website.
Train a robot in 2 minutes to do your work.
No coding required.
https://t.co/nNiawtUMyO
You May Also Like
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.