Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
munch117
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
munch117
17d ago
The default for paragraph layout does suck indeed. But at least the font you should be able to customize.
2.
▲
by
munch117
18d ago
The page does not set a text size. You are complaining about your own browser's defaults.
3.
▲
by
munch117
18d ago
Skeuomorphism didn't fail. It feel out of fashion with designers. We should distinguish between skeuomorphic interaction design and skeuomorphic iconography. Attempts at skeuomorphic interaction design did fail badly, I'll give
4.
▲
by
munch117
1mo ago
I read the or's as giving alternatives, only one of which needs to work. I can see how other interpretations are possible, but I don't see anything especially generous about mine. I'm not "allowing" anything: To ma
5.
▲
by
munch117
1mo ago
If the text was returned using a staged process, whereby the server first returns an instruction (JavaScript), and the web browser then executes that instruction, which is what transfers the text, then that doesn't actually change anyt
6.
▲
by
munch117
1mo ago
I think you are absolutely right. The big problem with the Turing test always was that it doesn't take into account adversarial designs. They had those chatbot contests about a decade ago, where the chatbots would regularly pass the t
7.
▲
by
munch117
2mo ago
Absolutely store the raw data. For the reasons you state. But also store derived data. Titles, authors, dates, article texts. You need those for whatever your application does. You don't want your application logic to be working wi
8.
▲
by
munch117
2mo ago
Perhaps you are talking about the ripgrep issue itself, which is fine. The others are talking about the linked analysis, which is not.
9.
▲
by
munch117
2mo ago
I would say that's a very sugarcoated version of the Monster energy drink ingredients list[1]. The real list is ten time longer than the ingredients list of a cup of black filter coffee. And one of the items is "natural flavors
10.
▲
by
munch117
2mo ago
For a piece of software designed by reading the specs and implementing accordingly, there acid3 would be a good way of demonstrating the quality of the result. But is that what happened? If you pass tests that conflict with the specs, then
11.
▲
by
munch117
2mo ago
Invisible until moused over, or scrolled by other means. Barely visible even then. In the wrong place. It may be "just styled", but it's certainly not fine.
12.
▲
by
munch117
2mo ago
If ease of repair is what you care about, then yes. But in absolute terms, sockets do make things more likely to fail. A socketed design means you have an assembly step where something is put into that socket. Probably manually. Cables a
13.
▲
by
munch117
2mo ago
Connectors are points of failure. The less of them, the more reliable.
14.
▲
by
munch117
4mo ago
The fatal flaw in PG's argument is that is doesn't mention spending at all. If you're spending your entire income on things like food and rent, then a 1% wealth tax corresponds to 0% income tax. If you're spending your e
15.
▲
by
munch117
4mo ago
I didn't suggest that implementations should entirely eliminate every form of UB. There is plenty of middle ground. For example, you could easily limit the consequences of integer overflow by specifying or partially specifying overflo
16.
▲
by
munch117
4mo ago
Both are wrong. It means "this standard does not constrain the behaviour of code that does this". It's entirely legal for implementations to have predictable behaviour, documented or not, for code that is undefined by the sta
17.
▲
by
munch117
6mo ago
Making a plan that works for the general case, but is also efficient, is rather trivial. Here's pseudocode from spending two minutes on the problem: # INPUT: lookfor: unicode var lower, upper: ascii lower = ascii_lower_bo
18.
▲
by
munch117
7mo ago
> Just clearly state your requirements. Nothing new here. Getting users to clearly state their requirements has always been like pulling teeth. Incomplete sentences and all. If the people you are teaching are developers, they should kn
19.
▲
by
munch117
7mo ago
TNG, by a country mile. B5 has "writer identifies too much with the main character" written all over it. It's the story of how Our Great Leader does the right thing and saves the world, over and over again.
20.
▲
by
munch117
7mo ago
I was reading https://www.offsec.com/blog/cve-2026-24061/ , which implies that precisely that single long string passes through getenv("USER") in the attack. The mystery is how that single long string in
21.
▲
by
munch117
7mo ago
I'm slightly taken aback by the telnetd fix: The solution to the username "-f root" being interpreted as two arguments to /usr/bin/login is to add a "sanitize" function, really? I'm not seeing t
22.
▲
by
munch117
9mo ago
> Also worth noting that the author never actually stated that they did not use generative AI for this article. I expect that they did in some small way, especially considering the source. But not to an extent where it was anywhere near
23.
▲
by
munch117
9mo ago
I struggled a bit with what to point to as signs that it's not an LLM conception. Someone else had commented on the headlines as something that was AI-like, and since I could easily imagine a writing process that would lead to headlin
24.
▲
by
munch117
9mo ago
This article is just about as un-AI written as anything I've ever read. The headings are clearly just the outline that he started with. An outline with a clear concept for the story that he's trying to tell. I'm beginning t
25.
▲
by
munch117
10mo ago
A __del__ that does any kind of real work is asking for trouble. Use it to print a diagnostic reminding you to call .close() or .join() or use a with statement, and nothing else. For example: def close(self): self._closed = T
26.
▲
by
munch117
11mo ago
> If you think you disagree with him (as I once did), please consider the possibility that you've only been exposed to an ersatz characterization of his argument. My first exposure was a video of Searle himself explaining the Chines
27.
▲
by
munch117
1y ago
Ah, I missed that 9.a-c were alternatives. And that, in the absence of custom tables or functions, they are merely defense in depth for something that is already secure, barring bugs. I withdraw my concern.
28.
▲
by
munch117
1y ago
I'm not that concerned with bugs in sqlite. sqlite is high quality software, and the application that uses it is a more likely source of vulnerabilities. But I do see a problem if you really need to use a sqlite that's compiled w
29.
▲
by
munch117
1y ago
You have just reinvented the slab allocator.
30.
▲
by
munch117
1y ago
15 years ago, was intermittent fasting even a thing back then? I wonder how many of the people eating within an 8 hour window didn't do it because of a diet, but instead because of an eating disorder or some other disease.
More ›