htunnicliff's comments

Canonical article source: (paywalled) https://fortune.com/2026/02/21/laptops-tablets-schools-gen-z...

Have any public library systems ever tried to partner with Standard Ebooks to help improve the discoverability and accessibility of classics for ebook users?

It would be neat to see those editions show up in when browsing collections in apps like Libby or Overdrive (at least in the U.S.).

I’d love to know more about the pattern of keeping each book in individual repos, rather than in a singular repo.

    I also modified a script I've been using for a few years to patch pylsp so it can now see uv script envs using the "uv sync --dry-run --script <path>" hack.

This sounds like a really useful modification to the LSP for Python. Would you be willing to share more about how you patched it and how you use it in an IDE?

I’d love to buy one of these.

For a stranger to the Ruby ecosystem, what are the benefits of YJIT?

> Throughout the pandemic, the media focused on the idea of the “urban doom loop,” in which remote work would kill downtowns, triggering a downward spiral of reduced services that would cause people to leave cities. What went overlooked has turned out to be the bigger and even more consequential story: the human doom loop, a cycle in which people stop connecting in real life, reducing the quality of in-person activities and the physical realm itself, further discouraging IRL activities, and so on. Nearly five years after the pandemic, it’s not the real estate we need to worry about. It’s us.

> The pattern is clear: The more we go online, the less we show up in person. And the less we show up, the less likely our physical realm will offer experiences that can compete.

Thanks! I used it today and thought others might enjoy.

One of the best parts of this release:

    ref as a prop: Refs can now be used as props, removing the need for forwardRef.

TL;DR: Several new UUID versions have been standardized

UUIDv5 is meant for generating UUIDs from "names" that are drawn from, and unique within, some "namespace" as per Section 6.5.

UUIDv6 is a field-compatible version of UUIDv1 (Section 5.1), reordered for improved DB locality. It is expected that UUIDv6 will primarily be implemented in contexts where UUIDv1 is used.

UUIDv7 features a time-ordered value field derived from the widely implemented and well-known Unix Epoch timestamp source, the number of milliseconds since midnight 1 Jan 1970 UTC, leap seconds excluded. Generally, UUIDv7 has improved entropy characteristics over UUIDv1 (Section 5.1) or UUIDv6 (Section 5.6).

UUIDv8 provides a format for experimental or vendor-specific use cases. The only requirement is that the variant and version bits MUST be set as defined in Sections 4.1 and 4.2. UUIDv8's uniqueness will be implementation specific and MUST NOT be assumed.

The only explicitly defined bits are those of the version and variant fields, leaving 122 bits for implementation-specific UUIDs. To be clear, UUIDv8 is not a replacement for UUIDv4 (Section 5.4) where all 122 extra bits are filled with random data.

Background for the changes:

Many things have changed in the time since UUIDs were originally created. Modern applications have a need to create and utilize UUIDs as the primary identifier for a variety of different items in complex computational systems, including but not limited to database keys, file names, machine or system names, and identifiers for event-driven transactions.

Question for Stainless folks: For Node.js/JavaScript SDKs, did you consider using Proxy instances in lieu of classes for each resource, to reduce the amount of actual code generated?

> Sequoia's breached cloud system stored an array of sensitive personal data, including names, addresses, dates of birth, gender, marital status, employment status, Social Security numbers, work email addresses, wage data related to benefits, and member IDs as well as any other ID cards, Covid-19 test results, and vaccine cards that individuals uploaded to the employment system.

Though I think the author’s tone may work against him here when it comes to receptivity of his claims, I did feel that ChatGPT’s responses to his questions had indications of bias.

It seems harder to tell whether any apparent bias in ChatGPT was intentionally programed or unintentionally learned. I’m not sure if there is a way to learn the reason for the answers aside from the OpenAI folks chiming in.

Having entered the software engineering world in the “age of GitHub,” I really appreciate learning more about the practical ways in which the advent and growth of GitHub have made community and discovery more difficult.

I often read about nostalgia for the days of mailing lists and IRC but have struggled to understand the appeal since I never experienced those forms communication myself. This analysis really opened a window into that world for me, and I now find myself in agreement with Michael that GitHub has not made discoverability and community engagement a priority.

GitHub has the ability to restore the soul of open source and make things much more exciting for 100,000 projects out there without an audience. It should do everything in it’s power to cultivate that excitement for everyone, not just a few lucky people.

I agree wholeheartedly and would love to see GitHub take steps in this direction.

Care to share more about your small startup?

I discovered my previous job (senior software engineer) by using Remote Leaf! I would highly recommend this to anyone looking for a new remote job.