More from Law
1/ After a good night's sleep, I have a few thoughts on the impending Ripple lawsuit.
Less schadenfreude, more "what now?" https://t.co/a0oTwblBHB
2/ First of all, the USG is going to lose.
I don't even need to read the complaint. They might force a settlement, but they're outclassed on legal.
Remember Ripple engaged former SEC Chair Mary Jo White in a civil matter in 2018. A hint of their
3/ Second, the USG should lose.
The SEC restrictions on non-accredited investors; the ridiculous Howey test; 80 year old securities law like the "40 Act" all need to die in fire. They are un-American and completely outdated.
I hope Ripple wins. (WUT?)
4/ Third, it's incumbent upon industry to self-police and hold the moral high ground.
I give certain individuals A's and others F's, but as a whole, the most powerful people and companies generally take a Swiss neutrality stance on assets.
So we're effectively in this together.
5/ We're "in this together" to draw lines of regulatory demarcation.
XRP as a "security" further hurts the U.S. businesses while global comps will continue to make these markets.
XRP as a security also means other assets will meet the same fate. At least Ripple has $ to fight.
Less schadenfreude, more "what now?" https://t.co/a0oTwblBHB
BREAKING: The @SEC_News intends to sue @ripple over its sale of XRP, alleging the cryptocurrency is an unregistered security according to @bgarlinghouse.@nikhileshde reportshttps://t.co/7Z3KSWk7dn
— CoinDesk (@CoinDesk) December 22, 2020
2/ First of all, the USG is going to lose.
I don't even need to read the complaint. They might force a settlement, but they're outclassed on legal.
Remember Ripple engaged former SEC Chair Mary Jo White in a civil matter in 2018. A hint of their
3/ Second, the USG should lose.
The SEC restrictions on non-accredited investors; the ridiculous Howey test; 80 year old securities law like the "40 Act" all need to die in fire. They are un-American and completely outdated.
I hope Ripple wins. (WUT?)
4/ Third, it's incumbent upon industry to self-police and hold the moral high ground.
I give certain individuals A's and others F's, but as a whole, the most powerful people and companies generally take a Swiss neutrality stance on assets.
So we're effectively in this together.
5/ We're "in this together" to draw lines of regulatory demarcation.
XRP as a "security" further hurts the U.S. businesses while global comps will continue to make these markets.
XRP as a security also means other assets will meet the same fate. At least Ripple has $ to fight.
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.