Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
cxr
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
35 ms
·
661.
▲
by
cxr
2y ago
What is "Titan" in this context?
662.
▲
by
cxr
2y ago
> One thing that was particularly valuable was ensuring ensuring every proposal came with a "alternatives" section (called "competitors" in the NABC model). We also made sure that every proposal included "do not
663.
▲
by
cxr
2y ago
Not only is this blogspam, but the whole rest of the story is missing; there's no link, just a bare claim—some network somewhere failed when an XLS file traversed its lines; no backstory, no details, no resolution.
664.
▲
by
cxr
2y ago
You seem to have me confused with someone else (such as the author, maybe—i.e. the person who injected the comparison to Google Books and wrote the part I quoted in my previous comment); except for the first two words in your comment, your
665.
▲
by
cxr
2y ago
> courts have found similar services infringing, most famously against Google Books Google was found not to be infringing.
666.
▲
by
cxr
2y ago
Geez, not this shit again. (One of the many ways you could tell Oracle was doomed in trying to find and convincingly argue a tenable position against Google: half the people half the time argued that Google should be sued for implementing
667.
▲
by
cxr
2y ago
Wrong, and that's not the question, anyway. There is nothing worse about "JS" over "JavaScript". (Whereas the reverse is not true—there is something worse about "JavaScript" over "JS". Several s
668.
▲
by
cxr
2y ago
This is a stupid non-issue. You can go ahead and call it JavaScript despite what Oracle does or doesn't say. Better yet, though: don't call it JavaScript—call it JS. "JavaScript" is and always was a dumb name. "
669.
▲
by
cxr
2y ago
> It is still possible for what Nelson refers to as "transcopyright" issues to occur on same origin transclusions, when multiple authors reuse the same origin for hosting copyrighted content, but this is not the common case, at
670.
▲
by
cxr
2y ago
The URL to Fielding's "REST APIs must be hypertext-driven" blog post (ref #20) is messed up. The actual URL is < https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypert... >, but it links i
671.
▲
by
cxr
2y ago
There's a program called bkcrack (< https://github.com/kimci86/bkcrack >) that can crack password-protected ZIPs. An interesting use case is documented in a blog post where someone (the Cloudflare CTO) uses it
672.
▲
by
cxr
2y ago
Firefox native bookmarks
673.
▲
by
cxr
2y ago
[deleted]
674.
▲
by
cxr
2y ago
The irony is breathtaking.
675.
▲
by
cxr
2y ago
I wasn't talking about hobby projects. I was talking about your personal approach to your professional work.
676.
▲
by
cxr
2y ago
> Oh that must be nice. https://prodimage.images-bn.com/pimages/9781962572439_p0_v1_... Just because the canonical approach at your org (or anywhere) is to use the NPM style of late-fetching dependencies to do an en
677.
▲
by
cxr
2y ago
You seem to specialize in half-thought out dismissals and one-liners. Do you understand what "required" and "needed" mean?
678.
▲
by
cxr
2y ago
You haven't demonstrated anywhere that this word you're using—needed—is applicable to the context: bun, etc. being shoehorned into projects' build prereqs despite most projects not needing a separate runtime for doing anythin
679.
▲
by
cxr
2y ago
"upload" and "download" are misnomers, but yeah, pretty much. To the original commenter: I don't recommend using Node. I said use the World Wide Wruntime instead. Even so, there's a difference between an app
680.
▲
by
cxr
2y ago
If you are going to use a build tool and you decide to create a new one written in JS, then please write it in standard JS (i.e. what Web browsers implement; nothing to do with standardjs.com) that calls standardized APIs (again, all brow
681.
▲
by
cxr
2y ago
(2018)
682.
▲
by
cxr
2y ago
< https://news.ycombinator.com/context?id=13602947 > And I didn't mention the guidelines (i.e. newsguidelines.html). On that note, though: > the site guidelines[...] aren't a list of proscribed behaviors b
683.
▲
by
cxr
2y ago
> Well that would be inefficient. For each command you run the kernel has to read the file, detect that it has a shebang, parse the shebang line, and then finally load the actual executable in memory. Those that exist today would, but no
684.
▲
by
cxr
2y ago
The basis if this article (and its forebear "Too DRY - The Grep Test"[1]) is that grep is fragile. It's just fragile in a way that's different from the way that IDEs are fragile. 1. < http://jamie-wong.co
685.
▲
by
cxr
2y ago
- You're fully aware that it would be better to be able to use tooling for $THING, but tooling doesn't exist yet or is immature.
686.
▲
by
cxr
2y ago
Sure the food that this restaurant serves is pricey, but you have to remember that it also tastes terrible.
687.
▲
by
cxr
2y ago
Before building an app that depends on the Wayback Machine (or other Archive infrastructure) it's good to keep in mind this post from their blog: < https://blog.archive.org/2023/05/29/let-us-serve-you-b
688.
▲
by
cxr
2y ago
CSP is a poorly designed, dangerous, user-hostile standard that should have never been written, let alone implemented. Better idea than "using Content-Security-Policy to block untrusted scripts": don't link against untrusted
689.
▲
by
cxr
2y ago
But that's not a CORS problem. It's a CSP problem. (And CSP deserves to be despised.)
690.
▲
by
cxr
2y ago
> Not that any of the other DEs would serve as better bases, unfortunately. No matter what making a Mac-style DE is going to be a steep uphill climb. No idea what the Elementary, helloSystem, Etoile, etc. folks are messing around about.
More ›