a Node.JS server might use SQL directly or call out to a GraphQL API, but I literally don't think it's possible to let client-side JavaScript (safely) call a SQL database server directly.

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

Points: 2

# Comments: 1

Edit

> A somewhat common way to delay imports is to move the imports into functions (inline imports), but this practice requires more work to implement and maintain, and can be subverted by a single inadvertent top-level import. Additionally, it obfuscates the full set of dependencies for a module. Analysis of the Python standard library shows that approximately 17% of all imports outside tests (nearly 3500 total imports across 730 files) are already placed inside functions or methods specifically to defer their execution. This demonstrates that developers are already manually implementing lazy imports in performance-sensitive code, but doing so requires scattering imports throughout the codebase and makes the full dependency graph harder to understand at a glance.

I think this is a really weak foundation for this language feature. We don't need it.

The credibility is ranking. The ranking is a function of engagement. The engagement is a function of human nature. Things delightful, shocking, or unusual usually strike that chord. Sprinkle capitalism into the mix and people become professionally delightful, shocking, or unusual.

I don't think the ranking algorithms are the problem here.

Kinda sped read the article so apologies if I missed it, but why does the author here feel so entitled to something that clearly the company feels unreasonable to continuously maintain? They're clearly a struggling business, it feels like this author has a personal vendetta against the company and would rather they go out of business than break a 14 year old promise made from an entirely different internet economy era.

> Jackson says he now lives in “exile” in Dover, where he goes to the socializes with friends and plays video games.