Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
defanor
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
34 ms
·
331.
▲
by
defanor
6y ago
- Not sure if it's still the case in most recent versions, but apparently w3m used to be snappier (I suspect there is some blocking still happening in eww, or maybe it's just that it loads emacs/elisp more). - w3m just ignore
332.
▲
by
defanor
6y ago
There is http://dir.xiph.org for Icecast radio stations.
333.
▲
by
defanor
6y ago
Not OP, but also packaging binaries into .debs, and the primary reasons for that (as opposed to using tarballs or rsync) are centralized package management, including dependency checks, and scripts to execute on installation (e.g., add syst
334.
▲
by
defanor
6y ago
> Now I feel like I owe the world a subset of HTTP and HTML to put my money where my mouth is. There are such subsets around: the one used by Texinfo's HTML export for portability [1] and by XMPP for XHTML-IM [2], the ones supported
335.
▲
by
defanor
7y ago
I'm using a similar setup and for similar reasons, particularly for XMPP, but finding it hard to recommend to others because of the awkward bits involved (and because not everyone uses/prefers Emacs, of course). It's mostly o
336.
▲
by
defanor
7y ago
There's an article with a similar premise by Charlie Stross [1]. Though both seem to apply to basically any software, not just statistical (or whatever currently falls under "AI"), and perhaps (AIUI) can be generalized to jus
337.
▲
by
defanor
7y ago
I keep seeing (and mostly sharing) sentiments like this, but a couple of things to note: - Sets of proposed features vary (happens to both lightweight WWW and modernized Gopher proposals). I guess a more viable approach may be a less strict
338.
▲
by
defanor
7y ago
I keep wondering whether there's a job scheduler for me too, but not finding much. At work I'm using/writing a custom one: with multiple schedules in crontab format for each task, frequent automated task updates (by an identi
339.
▲
by
defanor
7y ago
> Just getting away from a serif font makes the third you linked way better to me. The original one doesn't use CSS at all (and doesn't set fonts with serifs), while all the others try to alter fonts and/or their sizes, po
340.
▲
by
defanor
7y ago
I keep checking those minimalism-related websites and guidelines, as well as software projects, just to find out how much views on such a seemingly simple thing vary. For instance, this article argues against unnecessary elements, yet it&#x
341.
▲
by
defanor
7y ago
I blame the bloat. In some high-level languages even BSD sockets (and many other POSIX functions) aren't in the standard library, and there are various wrappers to provide "ease of use" and integration with a language's
342.
▲
by
defanor
7y ago
Mechanical shocks are indeed the concern. > you could drive it right in to a computer non-stop until the battery runs out and it's not going to do any meaningful damage What is this based on (i.e., are HDDs and all the smaller compo
343.
▲
by
defanor
7y ago
> They would need the decryption key, and if the server doesn't have it how would they get it? Either carry it with them or enter a passphrase (for use with a key derivation function; I guess/hope that Ring requires some passph
344.
▲
by
defanor
7y ago
That's my concern about their home vacuum cleaners as well: if a battery runs out, it would hit my computer. There are some programmable models though (were not available here at the time), and various certainly programmable DIY ones (
345.
▲
by
defanor
7y ago
My experience is similar, though nngroup.com has some reports that look like an okay research (though unreplicated as well). NASA's color graphics pages [1] seem to be based at least partially on research, contain further references, a
346.
▲
by
defanor
7y ago
Text contrasts (or, rather, lack of those: red on dark blue, light grey on lighter grey, dark grey on dark orange) are appalling too, as are the tiny font sizes. The website on which it is written has similar issues (and a sticky header in
347.
▲
by
defanor
7y ago
For POSIX systems, syslog is the standard way. For systemd-based ones, journald may be preferable because of its additional features; both support sending of logs to a remote server. I'd suggest to avoid custom logging facilities (incl
348.
▲
by
defanor
7y ago
I didn't have a question, though perhaps not quite seeing where those advices are coming from (what are the threat model and underlying assumptions) can be stated as a question, as well as the definition of "better" here. For
349.
▲
by
defanor
7y ago
There seems to be quite a few light contradictions (or perhaps just varying views exposed) in both the post and the way it's referenced here. I assume that OP's question implied that there generally are downsides to using separate
350.
▲
by
defanor
7y ago
There are different definitions of "low level language", but I think a charitable interpretation of the one in this article is that they view processors as providing a virtual machine, and count "levels" from what's
351.
▲
by
defanor
7y ago
The article blames C for the processor designs that emulate older (non-parallel) processors. I think it can be summarised as C having a relatively straightforward translation into hardware-friendly assembly in the past, but these days both
352.
▲
by
defanor
7y ago
I'd think that exercises for small children are based on more mainstream (nowadays) classical logic and ZFC (and likely with finite sets), and certainly are informal. If so, the reasoning can go as "here's a set of cats, take
353.
▲
by
defanor
7y ago
> ISO ironed out all the details Not quite: the paywalled standard itself contains bits like "dot or comma" for fractional part separators, which are then interpreted differently. Some software would use a dot (for printing and
354.
▲
by
defanor
7y ago
I wonder whether smartphone software "helpfully" suggests to adjust privacy settings when it's unable to access information, as some websites do with ad blockers and JS, or desktop and server software does with root access. I
355.
▲
by
defanor
7y ago
Both "webmaster" and "security" are standardized in RFC 2142, so one should be able to contact those easily. It's indeed not what happens in practice most of the time, but not sure if throwing more standards at it i
356.
▲
by
defanor
7y ago
Not sure if it became much better in the past few years; I seem to run into issues less and less often (and all were solvable rather quickly), but it may be simply because of the avoidance of problematic packages and approaches. Here is a b
357.
▲
by
defanor
7y ago
Longer names can be seen as unnecessary and duplicating information. One has to balance between being verbose and laconic when it comes to naming in general, but judging by the lack of annotations in this case, not much care was put into it
358.
▲
by
defanor
7y ago
That documentation indeed could be improved, but I guess the intention here is that basic usage is learned from the tutorials. Though it's possible to figure from that documentation alone as well (I'm reading it for the first time
359.
▲
by
defanor
7y ago
Not sure what's meant by "simple" here, but it looks quite complicated to me. Even though I use something similar at work (with Servant), but much simpler (FSVO "simple") approaches as a hobby: - Those frameworks re
360.
▲
by
defanor
7y ago
Nothing of value, but there usually is some (silly, IMO) justification, such as badges and warranty (practically useless). Funnily, Comodo starts its list of key features with "value" [0]. They also seem more expensive now than I
More ›