Hacker News new | past | comments | ask | show | jobs | submit | benatkin's comments login

Better than Toy Story, but Toy Story is much better known and does the same thing

Yeah..except that The Brave Little Toaster has a specific anti consumerism slant..

I can't imagine why the toy based story that was designed from the get-go to shovel plastic into kids via emotional hooks took off better and was better supported by the industry...


Looking through these three graphs, there's more to it than that.

Breast cancer mortality by age: https://www.cancerresearchuk.org/health-professional/cancer-...

Prostate cancer mortality by age: https://www.cancerresearchuk.org/health-professional/cancer-...

Testicular cancer mortality by age: https://www.cancerresearchuk.org/health-professional/cancer-...



It has obvious annoyances like these deeply nested paths:

quarkdown-quarkdoc-reader/src/main/kotlin/com/quarkdown/quarkdoc/reader/dokka/DokkaHtmlContentExtractor.kt

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...


I think in a way it's similar to ShadowRealm in JavaScript. https://github.com/tc39/proposal-shadowrealm/blob/main/expla...


> Machine learning (ML) has the potential to advance the state of the art in technical writing. No, I’m not talking about text generation models like Claude, Gemini, LLaMa, GPT, etc. The ML technology that might end up having the biggest impact on technical writing is embeddings.

This is maybe showing some age as well, or maybe not. It seems that text generation will soon be writing top tier technical docs - the research done on the problem with sycophancy will likely result something significantly better than what LLMs had before the regression to sycophancy. Either way, I take "having the biggest impact on technical writing" to mean in the near term. If having great search and organization tools (ambient findability and such) is going to steal the thunder from LLMs writing really good technical docs, it's going to need to happen fast.


Realistically, it's probably the combination of both embeddings and text generation models. Embeddings are a crucial technology for making more progress on the intractable challenges of technical writing [1] but then text generation models are key for applying automated updates.

[1] https://technicalwriting.dev/strategy/challenges.html


It gets the last one, maybe it would be better if it got the first one: https://rosettacode.org/wiki/100_doors#C


The Claude logo spinning is quite an unsettling thing to see.


They let you encapsulate the logic pretty much however you want, same as not using web components.


When you call document.querySelector("something") in the main HTML document, it will not find "something" inside the internal HTML of a web component.


You can use the shadow DOM outside of custom elements, and can use custom elements without a shadow DOM.

Edit: I just added a shadow root to a div in your comment, saving its content beforehand, moved its content inside the shadow root, and added a style with * { all: initial } and your comment text got Times New Roman.


I think it’s time to go back to Unobtrusive JavaScript. What is needed for this are lightweight libraries or practices you can code yourself. HTMX is lightweight which is nice but it’s like script tags. I would rather the urls and methods go in plain HTML and stuff like hx-target be determined by JavaScript, using data- attributes if needed. That way all the unused HTMX features aren’t included.


Shoutout to Facet also[0].

[0]: https://github.com/kgscialdone/facet



Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: