> time to delete the entire project and start over again Agreed, but this time using Rust. (Just think of all the good press we'll get on Hacker News! </s>)
@ruoyun looks like the c++ is a basic `echo` program for an example pipeline? https://github.com/apache/beam/tree/master/examples/java/src/main/java/org/apache/beam/examples/subprocess Kyle Weaver | Software Engineer | github.com/ibzib | kcwea...@google.com | +16502035555 On Mon, Jun 3, 2019 at 10:11 AM Ruoyun Huang <ruo...@google.com> wrote: > interesting stats. > > I am very curious in what we can benefit from merely *32* lines of c++ > code in a MLOC repository. > > On Mon, Jun 3, 2019 at 2:10 AM Maximilian Michels <m...@apache.org> wrote: > >> Interesting stats :) This metric does not take into a account Beam's >> dependencies, e.g. libraries and execution backends. That would increase >> the LOCs to millions. >> >> On 01.06.19 01:46, Alex Amato wrote: >> > Interesting, so if we play with https://github.com/cgag/loc we could >> > break it down further? I.e. test files vs code files? Which folders, >> > etc. That could be interesting as well. >> > >> > On Fri, May 31, 2019 at 4:20 PM Brian Hulette <bhule...@google.com >> > <mailto:bhule...@google.com>> wrote: >> > >> > Dennis Nedry needed 2 million lines of code to control Jurassic >> > Park, and he only had to manage eight computers! I think we may >> > actually need to pick up the pace. >> > >> > On Fri, May 31, 2019 at 4:11 PM Anton Kedin <ke...@google.com >> > <mailto:ke...@google.com>> wrote: >> > >> > And to reduce the effort of future rewrites we should start >> > doing it on a schedule. I propose we start over once a week :) >> > >> > On Fri, May 31, 2019 at 4:02 PM Lukasz Cwik <lc...@google.com >> > <mailto:lc...@google.com>> wrote: >> > >> > 1 million lines is too much, time to delete the entire >> > project and start over again, :-) >> > >> > On Fri, May 31, 2019 at 3:12 PM Ankur Goenka >> > <goe...@google.com <mailto:goe...@google.com>> wrote: >> > >> > Thanks for sharing. >> > This is really interesting metrics. >> > One use I can see is to track LOC vs Comments to make >> > sure that we keep up with the practice of writing >> > maintainable code. >> > >> > On Fri, May 31, 2019 at 3:04 PM Ismaël Mejía >> > <ieme...@gmail.com <mailto:ieme...@gmail.com>> wrote: >> > >> > I was checking some metrics in our codebase and >> > found by chance that >> > we have passed the 1 million lines of code (MLOC). >> > Of course lines of >> > code may not matter much but anyway it is >> > interesting to see the size >> > of our project at this moment. >> > >> > This is the detailed information returned by loc >> [1]: >> > >> > >> >> -------------------------------------------------------------------------------- >> > Language Files Lines >> > Blank Comment Code >> > >> >> -------------------------------------------------------------------------------- >> > Java 3681 673007 >> > 78265 140753 453989 >> > Python 497 131082 >> > 22560 13378 95144 >> > Go 333 105775 >> > 13681 11073 81021 >> > Markdown 205 31989 >> > 6526 0 25463 >> > Plain Text 11 21979 >> > 6359 0 15620 >> > Sass 92 9867 >> > 1434 1900 6533 >> > JavaScript 19 5157 >> > 1197 467 3493 >> > YAML 14 4601 >> > 454 1104 3043 >> > Bourne Shell 30 3874 >> > 470 1028 2376 >> > Protobuf 17 4258 >> > 677 1373 2208 >> > XML 17 2789 >> > 296 559 1934 >> > Kotlin 19 3501 >> > 347 1370 1784 >> > HTML 60 2447 >> > 148 914 1385 >> > Batch 3 249 >> > 57 0 192 >> > INI 1 206 >> > 21 16 169 >> > C++ 2 72 >> > 4 36 32 >> > Autoconf 1 21 >> > 1 16 4 >> > >> >> -------------------------------------------------------------------------------- >> > Total 5002 1000874 >> > 132497 173987 694390 >> > >> >> -------------------------------------------------------------------------------- >> > >> > [1] https://github.com/cgag/loc >> > >> > > > -- > ================ > Ruoyun Huang > >
