S
source{d} Blog
blog.sourced.tech · Company blog · on HN since 2016
The source{d} engineering blog covers machine learning on source code, GitHub data analysis and Go tools like a Git library and ORM.
What HN saysHN links it for its GitHub data analyses and Go tooling; the one comment given here is a general remark on C++ safety, not about the blog.
21HN people shared it
1linked it in comments
36stories submitted
352story points
7 years agolast shared
2016people per year2026
Most-shared posts
- 1Kallax: Why we built yet another ORM for Go3 people · 6 points · first shared 2017 · discussion on HN
- 2Comparing Git trees in Go3 people · 5 points · first shared 2017 · discussion on HN
- 3Workdays vs. Weekends and Morning vs. Night GitHub Commit Analysis3 people · 5 points · first shared 2017 · discussion on HN
- 4Babelfish is a universal code parser2 people · 5 points · first shared 2017 · discussion on HN
- 5Detecting licenses in code with go and ml2 people · 4 points · first shared 2018 · 1 comments on HN
- 6Topic Modeling of GitHub Repositories2 people · 3 points · first shared 2016 · discussion on HN
- 7Deduplicating Files in Public Git Archive2 people · 2 points · first shared 2018 · discussion on HN
- 8Analyzing GitHub, how developers change programming languages over time1 people · 186 points · first shared 2017 · 56 comments on HN
- 9Towards Yinyang K-means on GPU1 people · 61 points · first shared 2016 · 14 comments on HN
- 10100 Awesome Women in the Open-Source Community You Should Know1 people · 34 points · first shared 2016 · 5 comments on HN
- 11Fun with GitHub repositories statistics1 people · 6 points · first shared 2016 · 4 comments on HN
- 12Setting Up Google Cloud Dataproc with Jupyter and Python 31 people · 6 points · first shared 2016 · discussion on HN
- 13Measuring code sentiment in a Git repository1 people · 6 points · first shared 2018 · discussion on HN
- 14GitHub contributions graph: 6 handshakes theory and PageRank1 people · 5 points · first shared 2017 · discussion on HN
- 15Jonker-Volgenant Algorithm and T-SNE = Super Powers1 people · 3 points · first shared 2017 · discussion on HN
What HN people wrote when they linked it
pcwalton · 2017-07-26
There have been lots of solutions like "SaferCPlusPlus" over the years. In my view, the real reasons why these have not been adopted widely are (1) aversion to any sort of runtime overhead greater than zero; (2) cognitive overhead of introducing new language machinery, type-level or otherwise; (3) interoperability with existing code; (4) few people want to be the first to adopt these kinds of tools in production due to the perceived risk; (5) denial that memory safety problems are indeed problems.
If you're going for wide usage, I think it's actually easier to start over with a new language rather than to try to graft safety features onto C++. A lot of low-level folks don't realize it, but C and C++ are no longer the behemoths they used to be. If you look at the languages people are switching to rather than just absolute usage share, the usage chart [1] paints a very different picture.
[1]: https://blog.sourced.tech/post/language_migrations/eigenvect_stack_22l…