The concept of a "mom test" is condescending as well. Many moms code.

If you load 10 images in 1 request, you've reduced network latency and avoided the connection limit.

This process results in faster load times.

Comments URL: https://news.ycombinator.com/item?id=38191716

Points: 2

# Comments: 8

Please share your story about selling or licensing intellectual property (in this case code-based IP). Was it a net positive? Would you do something differently if you had the chance?

Thanks (in advance) for sharing.

Comments URL: https://news.ycombinator.com/item?id=38084508

Points: 3

# Comments: 0

Say you wanted to populate a social media feed... you'd need to dynamically call media. That produces a huge amount of requests.

What if you want to batch 10 images per request? Does anyone currently do that?

Note: I am familiar with HTTP2 multiplexing.

Comments URL: https://news.ycombinator.com/item?id=38019011

Points: 1

# Comments: 6

I'm talking about websites that function like apps but have the privacy/security benefits of being sandboxed inside the browser (accessed by URL or link).

It seems we may be talking about different things. I am not advocating for downloadable apps (I've never liked the app store paradigm nor the access it grants random developers). I'm advocating for more capable websites (which IMO "ought" to protect user data--not leverage it).

Imagine visiting this website, Hacker News, to read a few posts/discussions. Does the idea of circumventing a refresh offend you? You could click into a threaded discussion (from the homepage) and back without triggering a reload or needing the data beforehand.

Other than the indexability problem, it seems like an ideal solution. In many use cases, the indexability problem is actually a feature too.

That is to say: You would load your desired website (the standard way) and then experience a "refresh-less" session for the duration of your visit.

Edit: It is almost AJAX. The more I think about it the more the boundaries get blurry. Essentially, it's AJAX that does not fetch or receive resources directly. It interacts with a buffer that holds JSON which describes the next batch of cards. The images are streamed via tag, so the buffer is small relative to the media it represents.

https://www.youtube.com/watch?v=6eSDuAe3pHA

The only potential drawback I see is whether or not search crawlers could index content that's introduced via JS after a page load.

Edit: It also appears to protect from scraping... so I suspect it would conflict with indexability. That's a pretty big downside if true.

Why is the standard approach still transactional?

Comments URL: https://news.ycombinator.com/item?id=37764040

Points: 1

# Comments: 14

Delete my account.

Incorrect.

The risk vs. reward component also needs to be managed in order to deter criminal behavior. This starts with regulation.

For the record, I believe regulation of AI/ML is ridiculous. This is nothing more than a power grab.

The LLM is also discrete.