I started doing this the other day for a JS framework I'm using. Cannot recommend this practice highly enough. You learn so much.
Reading OpenBSD source code daily
71–80 of 86 posts
Re: Reading OpenBSD source code daily
#72Re: Reading OpenBSD source code daily
#73Here's the latest daily chat transcript, from Jun 9th: The topic was OpenBSD nc(1) and libtls, but it wandered over to pledge(2) and other code fixes from new participants eager to contribute. https://junk.tintagel.pl/openbsd-daily-nc.txt
Re: Reading OpenBSD source code daily
#74Here's the latest daily chat transcript, from Jun 9th: The topic was OpenBSD nc(1) and libtls, but it wandered over to pledge(2) and other code fixes from new participants eager to contribute. https://junk.tintagel.pl/openbsd-daily-nc.txt
May i suggest maintaining a repo on github with such material? Would be easier to keep up and might bring in some contributions
Re: Reading OpenBSD source code daily
#75Earlier quoted context omitted.
Granted, Jira ends up costing way more than $24,000 yearly, because all plugins need to be purchased for all users, and Jira tends to require employing at least one full-time admin. All-told, it's more in line with a few hundred thousand dollars yearly. With that said, $1.2 million for 2,000 users yearly for a code-search tool is some pretty insane Kool-Aid pricing, and it prevents me from even recommending it to my…
A JIRA installation with 2,000 users probably has many fewer developers, and you'd only pay for Sourcegraph for developers. For customers where this makes a big difference, we work with them on the pricing. But if you're a large company with 2,000 engineers, then you could be spending nearly a half-billion dollars on engineering salaries alone. If Sourcegraph makes your developers at least 0.5% more productive, then…
Re: Reading OpenBSD source code daily
#76Earlier quoted context omitted.
There's a tool called OpenGrok that pretty much does this except it's free and open source and it works on C code. Someone has it run on the openbsd code here: http://bxr.su/OpenBSD/ and it should produce a much more useful representation of the code, see http://bxr.su/OpenBSD/lib/libutil/bcrypt_pbkdf.c#98 Mozilla also has one called DXR which is designed for their large, C++ heavy codebases: https://wiki.mozilla.org…
On first impressions, since I have no experience with OpenGrok nor Sourcegraph, they look to serve about the same core need and provide most the same core functionality, but Sourcegraph is about what I would expect from a company providing usability and features on top of what is generally available for free. That is, Sourcegraph looks to compare to OpenGrok like Github compares to Gitweb. At least from a cursory loo…
Re: Reading OpenBSD source code daily
#77Earlier quoted context omitted.
On first impressions, since I have no experience with OpenGrok nor Sourcegraph, they look to serve about the same core need and provide most the same core functionality, but Sourcegraph is about what I would expect from a company providing usability and features on top of what is generally available for free. That is, Sourcegraph looks to compare to OpenGrok like Github compares to Gitweb. At least from a cursory loo…
Considering that Sourcegraph doesn't support C or C++ and those are pretty much the only languages I write that have less than perfect IDE crossrefence support I don't really see a point in Sourcegraph at the moment.
Re: Reading OpenBSD source code daily
#78Great idea. What other code bases are there that lend themselves to this? Some kind of curated genius.com for source code would be interesting.
The Go standard library is very well written and depending on which parts you read you can learn about lots of things like file operations, HTTP, crypto, etc. It's easy to read it all on the web, the docs are here: https://golang.org/pkg/ and clicking on a function name shows the source.
Re: Reading OpenBSD source code daily
#79Completely agree. But the tools don't make this very easy. Back in college I was working on patches to OpenSSL, Chrome, Firefox, Apache, etc., to add support for TLS-SRP, and it was a huge pain to jump into these massive codebases and try to understand them. I was using Emacs and had all of the various language support modes configured, but go-to-definition and cross-references barely worked. Searching was slow, and…
Meanwhile, most IDEs, QtCreator, KDevelop, VS, Eclipse... had this feature for years.
Re: Reading OpenBSD source code daily
#80Earlier quoted context omitted.
Considering that Sourcegraph doesn't support C or C++ and those are pretty much the only languages I write that have less than perfect IDE crossrefence support I don't really see a point in Sourcegraph at the moment.
Didn't one of the sourcegraph founders post a link to OpenBSD in sourcegraph at the top of this thread? That's C. Am I misunderstanding what you're taking about?