Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
gnu
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
gnu
4y ago
Very nice post Robin! And so honest! Subscribed via my rss reader.
2.
▲
by
gnu
5y ago
I also forgot to add one thing that tripped me recently but I am sure a solution exists for it that I am not aware of. In Debian we do: apt-cache search <search string> It gives quick results. The equivalent in nix is (correct me if I
3.
▲
by
gnu
5y ago
NixOS and Guix are nice! Guix folks are doing some wonderful work off late. I have used NixOS for a while. But for casual desktop GNU/Linux users, it seem like solving a problem that doesn't exist. Have been using Debian on all my
4.
▲
Amateur Radio at fault for reportedly causing interference to insulin pumps
(youtube.com)
1 points
by
gnu
5y ago
|
1 comments
5.
▲
by
gnu
6y ago
Christian Kellermann wrote this nice "Code it yourself Manifesto" [0] that always rings true with me. It is more important now than ever before. I believe OP is talking more or less the same thing. [0] https://pestilenz
6.
▲
by
gnu
6y ago
Same. I am in the industry for 20+ years and thankfully none of my jobs have involved anything close to ads.
7.
▲
by
gnu
6y ago
I have been meaning to learn the Plan 9 dialect of C but haven't gotten around to it.
8.
▲
by
gnu
6y ago
I too learned C from K&R and really loved it. I did not have any other thing to do and there was no internet and no one telling me that C is bad. Nor was I aware of other cool languages. I did not even have a computer at that time, so I
9.
▲
by
gnu
6y ago
Sure, but that is meant as a personal thing and not meant as a general statement. Everyone should evaluate whether the book (any book) works for their needs. The main reason is that, it was a very dry read with various rules and syntax etc
10.
▲
by
gnu
6y ago
I didn't enjoy this book, to be blunt. K&R still holds up as an interesting read, despite it not being updated to latest ANSI C standards. It is probably not a good first book. A few C books I like: * C: A reference manual. *
11.
▲
What changed in OpenSSL after heartbleed
(arxiv.org)
158 points
by
gnu
6y ago
|
64 comments
12.
▲
by
gnu
6y ago
Awesome! Thanks.
13.
▲
by
gnu
6y ago
Thanks so much for giving us BigBlueButton. Some of the folks in the Debian community have been trying to package it up in Debian and found it a bit challenging that some of the dependencies of BBB work only with specific Ubuntu versions. W
14.
▲
Teaching my MIT classes with only free/libre software
(gnu.org)
455 points
by
gnu
6y ago
|
222 comments
15.
▲
by
gnu
6y ago
Relevant: https://www.gnu.org/philosophy/right-to-read.en.html
16.
▲
by
gnu
6y ago
Interesting! Is there any document that I can read about your reimplementation? Or any code?
17.
▲
by
gnu
6y ago
Exposing something as files is kind of like a "protocol". The alternative would have been a library (implemented in a language) that would make things confine itself to the ecosystem of the language. Instead, anyone who can talk t
18.
▲
by
gnu
6y ago
keybase is unfortunately one of those programs that combine many things into one - somewhat antithetical to the Unix philosophy of doing one thing well. For kbfs, tahoe-lafs is a nice alternative. I don't know about the fuse interface
19.
▲
by
gnu
6y ago
There is tahoe-lafs. Give it a try.
20.
▲
by
gnu
11y ago
Thanks. Where can I see the second edition draft? edit: This one? https://github.com/rust-lang/book.git
21.
▲
by
gnu
11y ago
> Many of Rust's designers are experienced systems programmers. A _lot_ of effort goes into making it systems-ready. That is promising. Thanks. I am certainly playing with it at home.
22.
▲
by
gnu
11y ago
> Systems programming does not preclude a language from having a good type system or higher level abstractions. I didn't say that system programming does not need a good type system. I am also not saying that it is impossible to de
23.
▲
by
gnu
11y ago
Great. They all look great. The ones like higher kinded types are the ones that I am highly suspicious of. The typical C programmer who pokes around hardware data sheets and writes drivers and stuff will likely not pay much attention to Rus
24.
▲
by
gnu
11y ago
Another gripe I have is that the Rust Book examples are all targeted at non-system programmers. It would have been nice if certain programs written in K&R book or from one of those books from the Bell Labs Unix folks (like "The pra
25.
▲
by
gnu
11y ago
May I ask what those big ones are? How is it going to affect/improve the life of a systems programmer?
26.
▲
by
gnu
11y ago
I was referring to the RFCs. They also seem to include language changes. Happy to be proved wrong.
27.
▲
by
gnu
11y ago
Rust is nice. But the article miss one important point. Modern software engineering is a collaborative effort (well, it has always been, afaik). I write code for others to understand. I find Rust code significantly hard to read (I am saying
28.
▲
Letter to a young Haskell enthusiast (2014)
(comonad.com)
2 points
by
gnu
11y ago
|
0 comments
29.
▲
The question that made me quit the best job I ever had
(brandonhays.com)
1 points
by
gnu
11y ago
|
0 comments
30.
▲
by
gnu
11y ago
How are the security update/fixes handled in NixOS?
More ›