By popular demand, here is the official Mystery Grove Film Recommendations list. Watch all of these in order if you want to truly understand the world we live in today.
More from Culture
You May Also Like
#24hrstartup recap and analysis
What a weekend celebrating makers looks like.
A thread
👇Read on
Let's start with a crazy view of what @ProductHunt looked like on Sunday
Download image and upload
A top 7 with:
https://t.co/6gBjO6jXtB @Booligoosh
https://t.co/fwfKbQha57 @stephsmithio
https://t.co/LsSRNV9Jrf @anthilemoon
https://t.co/Fts7T8Un5M @J_Tabansi
Spotify Ctrl @shahroozme
https://t.co/37EoJAXEeG @kossnocorp
https://t.co/fMawYGlnro
If you want some top picks, see @deadcoder0904's thread,
We were going to have a go at doing this, but he nailed it.
It also comes with voting links 🖐so go do your
Over the following days the 24hr startup crew had more than their fair share of launches
Lots of variety: web, bots, extensions and even native apps
eg. @jordibruin with
What a weekend celebrating makers looks like.
A thread
👇Read on
Let's start with a crazy view of what @ProductHunt looked like on Sunday
Download image and upload
A top 7 with:
https://t.co/6gBjO6jXtB @Booligoosh
https://t.co/fwfKbQha57 @stephsmithio
https://t.co/LsSRNV9Jrf @anthilemoon
https://t.co/Fts7T8Un5M @J_Tabansi
Spotify Ctrl @shahroozme
https://t.co/37EoJAXEeG @kossnocorp
https://t.co/fMawYGlnro
If you want some top picks, see @deadcoder0904's thread,
We were going to have a go at doing this, but he nailed it.
It also comes with voting links 🖐so go do your
#24hrsstartup was an amazing event
— Akshay Kadam(A2K) \U0001f47b (@deadcoder0904) November 19, 2018
I never went to a hackathon but this just felt like one even though I was just watching \U0001f440
Everyone did great but there were a few startups that I personally loved \U0001f496
Some of my favorites are in the thread below\U0001f447
Over the following days the 24hr startup crew had more than their fair share of launches
Lots of variety: web, bots, extensions and even native apps
eg. @jordibruin with
\U0001f3a8\U0001f3c3\u200d\u2640\ufe0f DrawRun just launched on Product Hunt! Idea to App Store to Product Hunt in 68 hours!\u2070\u2070https://t.co/mxnLZ8FRSu
— Jordi Bruin (@jordibruin) November 20, 2018
Thanks for the motivation @thepatwalls @arminulrich @_feloidea
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.