RetpolineDrama

Right? Pro devices should be 240hz now

The default setups are also _crazy_.

So you search for company A wanting to buy their product. You check out. Basically every setup I've audited has every tracking product ever for everything.

So you buy X, and the company sends that purchase event with your information to Meta, Google, TikTok, Applovin, Klaviyo, and 10 others.

This idea is hopelessly entrenched in every marketing department, who has leadership's ear: We HAVE to send EVERYTHING to EVERYONE otherwise our ROAS will go DOWN!

Every platform works this way, they're all set up to put giant red banners on your marketer's dashboards

"You could be getting 50% better results if you sent <customer_2nd_grade_report_card>!"

Low risk there, Android users are way less likely to throw a party

Yep. Flutter has been dead-end for a while. RN won't last through 2027.

Introducing SwiftUI2: Every UI is a simple prompt, and all the underlying code is generated.

>All smart TVs should be disconnected from the internet.

Not good enough. The device has sufficient storage for YEARS of conversation data.

You connect it once to update the firmware and boom everything is backfilled. Your neighbor sets up an open SSID? It all gets out.

>The way I review it is to let it finish a PR sized slice and then I review the whole diff in a separate terminal as if it’s a PR from someone else.

Insanely inefficient. It's 10x more productive to watch the thinking traces and edits in real time and steer the model appropriately.

If your workflow is typical no wonder my team members who use claude code are so much less productive.

The true-local AI chip, codename "buddy", will be the M8

>how is Grok not at the top of the list for deepfaking millions?

How is this the top comment? I can go on just about any provider and make realistic "deep fakes" of anyone.

Generating images isn't a crime?

I had this and it turned out to be my unifi firewall block triggering a false-positive in the browser.

>The vast majority of CVEs are not exploitable

Perhaps in isolation. The issue is when you can chain exploits to bypass multiple layers.

>which are the biggest contributor to the glints we can see in the night sky.

>They're such an enormous part of the problem

What an incredible life of privilege you must live to perceive a few glints in the sky as a huge problem.

Lobby wait time is rather extreme, and false-starts are really tough (40m to get full team -> get it balanced -> launch game -> someone disconnects on start, or went AFK because of the long wait time -> re re re re in chat -> launch new lobby -> only 60% rejoin -> match is now unbalanced -> wait 20m -> some god among men with 2500k ELO joins -> match is un-balancable

>Rust is perfect for writing all of code using LLM. It's strict type system makes is less likely to make very dumb mistakes that other languages might allow.

100%. I've been telling everyone who will listen this for 2 years. LLMs are infinitely more productive with swift code like

let engineCycleCount: Int = 5

vs

let eC = 5

They still make mistakes, but forcing _explicit_ typing in a strongly typed language makes them make far fewer mistakes + the compiler is catching >90% of what you try to catch with a billion rspecs in trash languages like ruby.