Top all-time · #10833
ISRDI IT Blog
Company blog · tech.popdata.orgprogrammingdata
ISRDI IT Blog is the company blog at tech.popdata.org, writing about programming and data. Since 2015, 7 different Hacker News readers have linked it 9 times. The last post was in 2023, but the archive is still widely read.
Too few sampled comments (5) to say how often HN recommends it.?
Why HN links it
Posts on GPL licensing and whether linking proprietary and GPL code breaks copyright, and on flame graphs as a way to find slow functions. HN readers cite them in licensing and profiling discussions.
Summarised by Claude from a sample of 5 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
The team and tech behind the world's largest demographic databases.
Most-linked posts?
- /the-gpl-license-and-linking-still-unclear-after-30-years/2 people · 2 mentions · first linked 2024-01-12
What Hacker News says?
> If the program is closed source, then yes, you've broken copyright law. My point is that although many believe that linking proprietary code and GPL code into the same process breaks copyright law, it's not clear that the law actually forbids it. https://tech.popdata.org/the-gpl-license-and-linking-still-u... is one analysis by someone else skeptical of the FSF's position.
Comment linking /the-gpl-license-and-linking-still-unclear-after-30-years/
on “Unity's Open-Source Double Standard: The Ban of VLC”Submitted Flame Graphs: Making the opaque obvious (2017) as a story · 98 points
HN discussionBy simple example, I mean this: https://tech.popdata.org/images/flamegraph-example.svg But looking at the one you're referencing, slightly out of order: > highest-magnitude function I see there is __int__malloc. Height shows stack depth, not magnitude. > the actual culprit is Record::hasVariable, which is somewhere in the middle of the graph, and not any redder or less red, or wider or less wide, than many other fun…
Comment linking /images/flamegraph-example.svg
on “Flame Graphs: Making the opaque obvious (2017)”Submitted Why we always do a full day onsite interview as a story · 2 points
HN discussion> Probably the simplest way to use the flame graph is work from the bottom of the flamegraph and walk upwards until you find something interesting you optimize OK, so going by what is apparently the 'simple example' in the linked article: https://tech.popdata.org/images/cps1970_before_fix_dwarf_gcc... I work my way up. First thing that is really red is Conversion::Process::Run, but that probably wraps a lot of thing…
Comment linking /images/cps1970_before_fix_dwarf_gcc53.svg
on “Flame Graphs: Making the opaque obvious (2017)”Submitted Reading the Parquet Format in Rust as a story · 1 points
HN discussionBy the 'simple example', I assume you mean https://tech.popdata.org/images/cps1970_before_fix_dwarf_gcc... ? If so, the widest, reddest, and highest-magnitude function I see there is __int__malloc. Right? Yet, reading on, it seems that has nothing to do with anything, and the actual culprit is Record::hasVariable, which is somewhere in the middle of the graph, and not any redder or less red, or wider or less wide, t…
Comment linking /images/cps1970_before_fix_dwarf_gcc53.svg
on “Flame Graphs: Making the opaque obvious (2017)”Combine if they are independent pieces of software, yes. Whether linking (hard or soft/plugin) counts is a matter of legal uncertainty. The FSF has consistently said that a single function call into a GPL library constitutes a derivative work, but other legal experts disagree [1]. Certainly, if I maintain a repo which calls a function in a GPL library, it would be misleading for me to say that my repo is MIT-license…
Comment linking /the-gpl-license-and-linking-still-unclear-after-30-years/
on “Feluda – A CLI tool to detect restrictive licenses in dependencies”
