ghusbands

8 ms·

61.
by ghusbands 2y ago
Please consider changing the name - it's already hard to find the pages out there talking about how to fix technical issues or use the javascript developer console or such as a jaws user, and your project will end up hiding some of tho
62.
by ghusbands 2y ago
When you're down to 90% of them only providing location (unless you stop caring about topology), it's no longer as clear-cut. I was only really arguing against the implication that it's "funny" to use nodes; the top
63.
by ghusbands 2y ago
Your wiki link states that multiple nodes can share the same latitude and longitude (different heights/layers), so the ID could not be subsumed. (Unless you were trying to imply something else?)
64.
by ghusbands 2y ago
> This (index ordering resulting in useless indices) is not true, at least not in newer versions of Postgres (I just tried with 15). > While the query will take much longer (for me, it was about 47 msec vs 0.6 msec for 2,000,000 rows)
65.
by ghusbands 2y ago
Bookmarks become outdated or the pages may be updated to no longer have the text you are interested in. If you're bookmarking a page that's fairly static, you're probably more interested in the content than the URL.
66.
by ghusbands 2y ago
Most programming languages have easy and well-known string concatenation and the simplest querying function typically takes just a string - it's easy to see why people naturally reach for string concatenation.
67.
by ghusbands 2y ago
Trampolines can help with that.
68.
by ghusbands 2y ago
That was fairly standard startup behaviour across all makers. The comment you're replying to talks about the heatsink suddenly falling off - a very specific testcase seemingly chosen to make a company look bad.
69.
by ghusbands 2y ago
Just don't extract archives into a non-empty folder. That will always be dangerous/insecure.
70.
by ghusbands 2y ago
A factor of six is a very long way off, pretty much universally.
71.
by ghusbands 2y ago
I assure you that people made the same mistake plenty in the old days, too. Most programmers who come across an array of values assume they know what the values mean, and that stands true across time. Many paint packages and other programs
72.
by ghusbands 2y ago
> There's another one which hits every 2 minutes without fail [...] it's the one feed user-agent I've had to block outright. It doesn't stop requesting things [...] Clearly, I need to use a bigger hammer. I'd be
73.
by ghusbands 2y ago
That was such a common technique that it's odd to talk about just one game in particular doing it.
74.
by ghusbands 2y ago
This comment is just a copy/paste of a quarter of the article.
75.
by ghusbands 2y ago
The article says "C64 games did a lot of work to stay single-load since the C64 drive is so slow" - what are you surprised by, since you seem to be in agreement?
76.
by ghusbands 2y ago
If you play it, though, expect something that's not a challenge but more just an interesting presentation of some ideas.
77.
by ghusbands 2y ago
I've read them and somewhat disagree. The protaganist(s) in the book almost never choose a sensible course of action for their goals, even given elapsed decades in which to make them. If I can come up with much better plans on the fly
78.
by ghusbands 2y ago
If the two parties are equal, sure. If it's a person vs a corporation of significant size, then no, it's not safe to assume that people have free choice. That's also ignoring motivations apart from business ones, like them ac
79.
by ghusbands 2y ago
The direct link is https://shakti.com/document/sql.d
80.
by ghusbands 2y ago
Many ORMs have similar features - jOOQ is not unique in this. The article is talking about an addition to SQL syntax, not a DSL embedded in another language.
81.
by ghusbands 2y ago
> All in all, I would not call this a simplification. It is a simplification, as it gives you less that you need to understand and decode. Working with a query with ten to twenty joins and join conditions, you have to juggle a lot of int
82.
by ghusbands 2y ago
Graph databases aren't particularly relevant to a novel syntax for relational databases. The part of the related standard that is about relational databases (SQL/PGQ) demands that every table hold either edges or vertices, but not
83.
by ghusbands 2y ago
Natural joins are terrible in that they match on any equal column names. Let's hope you don't have employees with names and departments with names. In any case, even with natural join syntax, you end up with queries longer than th
84.
by ghusbands 2y ago
Well, language benchmarks fairly uniformly show that to be untrue in general. None of the fastest languages have forced immutability. It's not like it's a novel, untested idea.
85.
by ghusbands 2y ago
It's easy to see that altering an entry in an array (size N) is O(1) with mutability and at least O(log N) with immutability, and that affects many algorithms. Altering any small part of a larger data structure has similar issues. In t
86.
by ghusbands 2y ago
It also gets pinch and spread gestures back to front, so it seems someone just got a sign wrong somewhere.
87.
by ghusbands 2y ago
Well, if you use pinch or spread gestures, they are also reversed, so it is indeed getting it back to front compared to some default.
88.
by ghusbands 2y ago
That's active electronic noise cancellation - there have been many of those described and very few delivered over the past thirty years. Presumably because it's the sort of thing that is angle-sensitive and hard to set up and main
89.
by ghusbands 2y ago
I have seen such a thing in an article, though I don't know how to find it. It was a window with a square grid of circular holes in it - air could flow through, but sound waves were dissipated.
90.
by ghusbands 2y ago
If you want encryption enough, you can probably pay for a three-person business plan and just not set up the extra users. Looks like it would double your monthly subscription over the most expensive personal plan.

More ›