F: is he saying "super moms"?
me: I think he is?
I don't know how @ErrataRob is dealing with this...the stuff on the live stream is *UNHINGED*.
@ErrataRob The sincere stupidity is arresting and terrifying in equal measure.
"we the people" is now a triggering phrase
Big Karen Energy
~3 seconds of googling later~

does Mike Lindell know what the phrase "red team" actually means?

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with Alex Russell

Alex Russell Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @slightlylate

10 Aug
Your shopping website is not an SPA.

I repeat: your shopping website is not an SPA.

Stop trying to sculpt David with a JS chainsaw and get yourself an HTML/CSS chisel.
Like, it *could* be an SPA, in the same sense that one *could* use a solid rocket booster to power one's car.
How do I know it's ridiculous to apply this much JS to the problem?

Because I helped build e-commerce sites with similar features (filtering, carts, etc.) that had to work on 4.0 browsers over 33.6 modems to WebTV boxes in 1999.
Read 6 tweets
16 Jul
"$120 smartphone being sold for $500" you say? Why yes, cheap Androids *are* my beat.

A quick 🧵 on the technical specs of the UMIDIGI A9 Pro (a.k.a. "Freedom Phone") and how it stacks up against vs. legit $500USD devices.
The chip inside is the 8-core MediaTek Helio P60 (a.k.a., MT6771). It was initially released in early *2018* and was not a competitive part even then:


By modern standards it's a pile of 💩; no device above ~$200 should use it.
Looking at the headline specs, this thing's a dog. There are 8 cores, but as with most Android devices, that's less than half the picture.

The *fast* cores (4 x A73's) are a design from *2016*:


The slow cores are 2012's A53:

Read 19 tweets
8 Jul
There's a lot of cultural rot packed into this and, per usual, California's *messed up* land use and tax policies are the backdrop.

To recap: Prop 13 means housing gets cheaper the longer you hold, not just 'cuz feds subsidize mortgages, but also property taxes.
Combined with now-rampant NIMBY-ism from the last generation to enjoy tax-funded higher ed, spiraling property costs mean the dream of owning a reasonable home and starting a family is a receding vision.

How bad is it?


The "way up" is "supposed to be" tech -- one of the few industries often paying enough to get you a slice of California. And for the lucky few, it absolutely is.

But the path to that is brutal.
Read 12 tweets
8 Jul
I take this blog post to mean that Play will provide WebAPKs to competing browsers and that I'll be able to install other stores on my Pixel.

Do I have that right?
My contention for something like a decade has been that if your tree is closed for half the year, you're "kept source", regardless of the license code eventually drops with:

One quick point and then a longer one.

Quickly, the distance between Play's mission and Google's mission has always been both obvious and disappointing.

So why does it persist? To grok that, we have to understand the origin stories.

Read 15 tweets
23 Dec 20
Even the truth in the original demonstrates ignorance: front-end (and client-side generally) has layers to occupy you for multiple careers!

Codecs, databases & storage, graphics (2d & 3d), languages & runtimes, fonts & layout, networking, performance: all harder on the client.
It *is true* that working across layers is a key trait of highly effective engineers. Respecting those who do it on the client is good.

The idea that one must "graduate" to the back end carries the same stench as every overconfidently presented "full stack" failure I trace.
Front-end demands humility because it is *different* and, in key respects, *harder*.

There's an asymmetric hubris here: those of us who work the client don't tell back-enders that their work is trivial. Nor do we gate-keep the "full stack" crowd, no matter how poorly they do.
Read 5 tweets
13 Oct 20
The cognitive dissonance of anti-web and anti-choice rules made & justified because device resource scarcity [1] against the marketing of ALL POWERFUL CPUs [2] is dizzying.

[1] infrequently.org/2020/09/the-pu…
[2] macworld.com/article/357533…
For a sense of scale, when the anti-choice, anti-web rules were laid down, Apple's fastest device was the iPhone 3G; a single-core, 32bit, in-order, ~400MHz chip attached to 128MiB of system memory.

Today, the slowest device you can buy directly from Apple is based on the A12...
The A12 is a 64 bit, 6-core, 2-and-change-GHz part with ~~8MiB of L2 cache~~ attached to 3GiB of RAM in the most resource-impoverished device Apple markets today:

Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!