Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pbrowne011
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
1.
▲
by
pbrowne011
5mo ago
Feels like this would be a good candidate for Pike's programming rules ( https://www.cs.unc.edu/~stotts/COMP590-059-f24/robsrules.htm... ): "Rule 1. You can't tell where a program is going to spend it
2.
▲
by
pbrowne011
5mo ago
Very cool! TIL about Ghostscript: https://ghostscript.com/about/index.html Awesome to see someone continuing in the tradition of free/libre OSS: https://linuxclass.heinz.cmu.edu/doc/Open-Sourc
3.
▲
by
pbrowne011
5mo ago
Interesting to see how their CLI compares with GitLab's CLI interface for stacked diffs (the only support they offer at the moment): https://docs.gitlab.com/user/project/merge_requests/stacked_... . Most
4.
▲
The European Schuko socket bothers me
(blog.jgc.org)
6 points
by
pbrowne011
8mo ago
|
0 comments
5.
▲
A Wrigley Mystery (2024)
(elibaum.com)
2 points
by
pbrowne011
1y ago
|
0 comments
6.
▲
How not to Reference Papers (2014)
(igorpak.wordpress.com)
1 points
by
pbrowne011
1y ago
|
0 comments
7.
▲
by
pbrowne011
2y ago
If you'd like to read something that is less detailed, I4R (Institute for Replication) posted threads on X (formerly known as Twitter) and Bluesky about their investigation into this paper. X (Twitter): https://x.com/I4
8.
▲
Reproduction of "Improving Women's Mental Health During a Pandemic"
(osf.io)
2 points
by
pbrowne011
2y ago
|
1 comments
9.
▲
by
pbrowne011
2y ago
It seems crazy to me that vulnerabilities like this still exist today. I understand that not everything will be written in Rust, but this could have been caught by basic testing and/or fuzzing, as Nick (the person who found the vulnera
10.
▲
by
pbrowne011
2y ago
Fun to see someone decide to just write a faster JSON parser because they believed it was possible. They mentioned last year that libjansson had some intermediate layer with Emacs, which led to too many memory allocations: https:/
11.
▲
by
pbrowne011
2y ago
True, I was trying to find the variable storage requirements in the UEFI specification but couldn't (is it Section 3? 8?), so I resorted to linking to the struct definition in the EFI shell package that the author used.
12.
▲
by
pbrowne011
2y ago
Very interesting. I wonder if this a result of some "swiss cheese" effect due to constraints around UEFI and NVRAM themselves, when updating EFI variables. NVRAM must maintain atomicity of memory transactions for power failures. I
13.
▲
The Billionaire's Typewriter (2019)
(practicaltypography.com)
1 points
by
pbrowne011
2y ago
|
0 comments
14.
▲
Handling exceptions in Python like a pro (2021)
(guicommits.com)
2 points
by
pbrowne011
2y ago
|
0 comments
15.
▲
How to Prove False Statements: Practical Attacks on Fiat-Shamir
(eprint.iacr.org)
2 points
by
pbrowne011
2y ago
|
0 comments
16.
▲
There's No Such Thing as Software Productivity (2012)
(benrady.com)
130 points
by
pbrowne011
2y ago
|
135 comments
17.
▲
CRUFT: An alternative to the Technical Debt metaphor
(benrady.com)
3 points
by
pbrowne011
2y ago
|
0 comments
18.
▲
Strong Advice (2021)
(breckyunits.com)
1 points
by
pbrowne011
2y ago
|
0 comments
19.
▲
How humans write programs (2018)
(tedinski.com)
2 points
by
pbrowne011
2y ago
|
0 comments
20.
▲
Making a Tiny E-Paper Status Display for the Raspberry Pi Zero
(johnj.com)
2 points
by
pbrowne011
2y ago
|
0 comments
21.
▲
by
pbrowne011
2y ago
While this didn't get much attention on History Stack Exchange, see ConeOfArc's YouTube video (which has 963k views as of today): https://www.youtube.com/watch?v=HaRO_dTqO1E See also ConeOfArc's video from a
22.
▲
by
pbrowne011
2y ago
"The more skilled you are, the less you need advanced tools..." I wonder how well this claim holds up under strict scrutiny. At a high level, it makes sense: someone who is a master of their craft will understand their tools and h
23.
▲
by
pbrowne011
2y ago
Is the main idea to convert the model implementation from Python into C, then hardcode all possible values? Do you do this yourself in the generator code, or could you let the C preprocessor/compiler handle something like this by using
24.
▲
by
pbrowne011
2y ago
From The Register, with more comments by Filip ("Phil") Pizlo (the author): https://www.theregister.com/2024/11/16/rusthaters_unite_filc... . Other memory safe implementations for C and C++ mentioned
25.
▲
Understanding Common Factor Attacks: An RSA-Cracking Puzzle
(loyalty.org)
2 points
by
pbrowne011
2y ago
|
0 comments
26.
▲
1B Nested Loop Iterations
(benjdd.com)
1 points
by
pbrowne011
2y ago
|
2 comments
27.
▲
by
pbrowne011
2y ago
(2016) The comments on this fast range reduction are interesting, I recommend reading them (they're much longer than the post itself). Some highlights: Versions of this exist as early as 1997, in CMU's Common Lisp implementation.
28.
▲
by
pbrowne011
2y ago
More recent revision: https://isocpp.org/files/papers/P2900R10.pdf . It seems like they've added a few things since this draft. It's somewhat funny to hear "minimum viable product" in the contex
29.
▲
by
pbrowne011
2y ago
"Classic C++" and "Modern C++" refer to the language before and after C++11, respectively. Some of the key differences are use of standard library and its containers, smart pointers, and other language features that look
30.
▲
The Rubaiyat (1120 ACE)
(classics.mit.edu)
1 points
by
pbrowne011
2y ago
|
0 comments
More ›