coffeecoders

I agree. Specialized engineering is very different from software, you can't easily replace that expertise.

My question is more on software roles, those CRUD or React component roles, where the work can be done remotely. Instead of Americans filling those positions, companies may/will simply hire those engineers abroad.

But look at the other side. An engineer living in Seattle pays taxes and contributes to the economy. Seattle loses that benefits if that same job moves to India.

So, I am not sure if that housing argument alone makes that a better outcome for America (and workers).

I know this is a much popular opinion now. But I can't help and ask this again:

If a company hires an engineer in India, instead of Seattle, how does America (and workers) benefit? Software doesn't require factories, or supply chains, its just a hiring decision.

The question is whether these restrictions increase American employment or just accelerate the exodus of jobs while making the US a less attractive place for talented people.

What is interesting to me is that stripping the C2PA data is easy, but faking it is hard.

You can resave the file and the "made with Claude" signal disappears, but you cannot make a random file pass as Claude-made without Anthropic's signing key. So the useful guarantee is one-way. No signature means almost nothing.

One place where I find the Flash models surprisingly bad is Google Search's "AI Mode".

A recent example - I searched for how to unsubscribe from Pearson emails. Google Search "AI Mode" confidently gave me a sequence of steps along the lines of Settings > Profile > Email preferences > Unsubscribe.

Of course, I looked for an unsubscribe link before asking Google. None of those options existed. The correct answer was there is no way to unsubscribe through the account, so I just blockthe emails instead.

I've run into this pattern quite a few times. AI Mode seems to make up things all the time.

It only makes sense if we are measuring raw capability per dollar. Once you factor in noise, physical size, idle power, battery etc, I think the calculation changes.

For a home sever that's mostly idle, it is almost like commuting in a pickup truck.

Just add this to uBlock origin:

``` linkedin.com##main#workspace section:has(div[componentkey*="container-update-list_mainFeed-lazy"]) ```

I think the problem is concentration. AI now absorbs almost all of the oxygen from every category. A story about new chips becomes an AI story. Cloud pricing becomes an AI story. Even personal projects get pulled into the same orbit.

I need this but for dentists.

If I am archiving PBs of data for 10+ years, I don't want to rely on a WASM interpreter being available and performant in the future just to read a file. I want a dead-simple, heavily documented byte specification like Parquet.

Additionally, putting the decoding logic inside an WASM binary introduces an active execution layer into what should be a cold storage.

It's a selection bias issue. The categories you have listed are essentially web services wrapped in an app shell. Of course they need the internet. Consider these examples:

- Photo/Video editors - Snapsheed, Lightroom, Video trimmers etc.

- Document readers & scanners - PDF viewers, e-readers, OCR scanners

- Note taking - Obsidian

- File/Password managers - Authenticators etc.

- Single player games - Chess, puzzles etc.

- Audio/Video players - VLC players

We've just become conditioned to accept that every app needs to phone home for tracking and ad-delivery.