Re: 1 Million Lines of Code (1 MLOC)

[Brian Hulette]

You can run loc and tokei with a --files arg to get a breakdown by file.
They're just classifying one file as autoconf:
https://github.com/apache/beam/blob/master/sdks/python/MANIFEST.in

On Mon, Jun 3, 2019 at 1:02 PM Kenneth Knowles  wrote:

> Where's the autoconf?
>
> On Mon, Jun 3, 2019 at 10:21 AM Kyle Weaver  wrote:
>
>> > 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! )
>>
>> @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
>> | +1650203
>>
>>
>> On Mon, Jun 3, 2019 at 10:11 AM Ruoyun Huang  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 
>>> 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 >>> > > 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 >>> > > 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 >>> > > 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
 > 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
 > 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 FilesLines
 > Blank  Comment Code
 >
  
 
 >   Java  3681   673007
 > 78265   140753   453989
 >   Python 497   131082
 > 225601337895144
 >   Go 333   105775
 > 136811107381021
 >   Markdown   20531989
 >   6526025463
 >   Plain Text  1121979
 >   6359015620
 >   Sass92 9867
 >   1434 1900 6533
 >   JavaScript  19 5157
 >   1197  467 3493
 >   YAML14 4601
 > 454 1104 3043
 >   Bourne Shell30 3874
 > 470 1028 2376
 >   Protobuf17 4258
 > 677 1373   

Re: 1 Million Lines of Code (1 MLOC)

[Kenneth Knowles]

Where's the autoconf?

On Mon, Jun 3, 2019 at 10:21 AM Kyle Weaver  wrote:

> > 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! )
>
> @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
> | +1650203
>
>
> On Mon, Jun 3, 2019 at 10:11 AM Ruoyun Huang  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  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 >> > > 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 >> > > 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 >> > > 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
>>> > 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
>>> > 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 FilesLines
>>> > Blank  Comment Code
>>> >
>>>  
>>> 
>>> >   Java  3681   673007
>>> > 78265   140753   453989
>>> >   Python 497   131082
>>> > 225601337895144
>>> >   Go 333   105775
>>> > 136811107381021
>>> >   Markdown   20531989
>>> >   6526025463
>>> >   Plain Text  1121979
>>> >   6359015620
>>> >   Sass92 9867
>>> >   1434 1900 6533
>>> >   JavaScript  19 5157
>>> >   1197  467 3493
>>> >   YAML14 4601
>>> > 454 1104 3043
>>> >   Bourne Shell30 3874
>>> > 470 1028 2376
>>> >   Protobuf17 4258
>>> > 677 1373 2208
>>> >   XML 17 2789
>>> > 296  559 1934
>>> >   Kotlin  19 3501
>>> > 347 1370 1784
>>> >   HTML60 2447
>>> > 148

Re: 1 Million Lines of Code (1 MLOC)

[Kyle Weaver]

> 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! )

@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 |
+1650203


On Mon, Jun 3, 2019 at 10:11 AM Ruoyun Huang  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  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 > > > 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 > > > 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 > > > 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
>> > 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
>> > 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 FilesLines
>> > Blank  Comment Code
>> >
>>  
>> 
>> >   Java  3681   673007
>> > 78265   140753   453989
>> >   Python 497   131082
>> > 225601337895144
>> >   Go 333   105775
>> > 136811107381021
>> >   Markdown   20531989
>> >   6526025463
>> >   Plain Text  1121979
>> >   6359015620
>> >   Sass92 9867
>> >   1434 1900 6533
>> >   JavaScript  19 5157
>> >   1197  467 3493
>> >   YAML14 4601
>> > 454 1104 3043
>> >   Bourne Shell30 3874
>> > 470 1028 2376
>> >   Protobuf17 4258
>> > 677 1373 2208
>> >   XML 17 2789
>> > 296  559 1934
>> >   Kotlin  19 3501
>> > 347 1370 1784
>> >   HTML60 2447
>> > 148  914 1385
>> >   Batch3  249
>> >   570  192
>> >   INI

Re: 1 Million Lines of Code (1 MLOC)

[Ruoyun Huang]

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  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  > > 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  > > 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  > > 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
> > 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
> > 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 FilesLines
> > Blank  Comment Code
> >
>  
> 
> >   Java  3681   673007
> > 78265   140753   453989
> >   Python 497   131082
> > 225601337895144
> >   Go 333   105775
> > 136811107381021
> >   Markdown   20531989
> >   6526025463
> >   Plain Text  1121979
> >   6359015620
> >   Sass92 9867
> >   1434 1900 6533
> >   JavaScript  19 5157
> >   1197  467 3493
> >   YAML14 4601
> > 454 1104 3043
> >   Bourne Shell30 3874
> > 470 1028 2376
> >   Protobuf17 4258
> > 677 1373 2208
> >   XML 17 2789
> > 296  559 1934
> >   Kotlin  19 3501
> > 347 1370 1784
> >   HTML60 2447
> > 148  914 1385
> >   Batch3  249
> >   570  192
> >   INI  1  206
> >   21   16  169
> >   C++  2   72
> > 4   36   32
> >   Autoconf 1   21
> > 1   164
> >
>  
> 
> >   Total 5002  1000874
> >   132497   173987   694390
> >
>  
> 

Re: 1 Million Lines of Code (1 MLOC)

[Maximilian Michels]

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 > 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 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 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
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
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

Re: 1 Million Lines of Code (1 MLOC)

[Alex Amato]

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  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  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  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  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  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 FilesLinesBlank  Comment
>  Code
>
> 
>  Java  3681   67300778265   140753
>453989
>  Python 497   1310822256013378
> 95144
>  Go 333   1057751368111073
> 81021
>  Markdown   20531989 65260
> 25463
>  Plain Text  1121979 63590
> 15620
>  Sass92 9867 1434 1900
>  6533
>  JavaScript  19 5157 1197  467
>  3493
>  YAML14 4601  454 1104
>  3043
>  Bourne Shell30 3874  470 1028
>  2376
>  Protobuf17 4258  677 1373
>  2208
>  XML 17 2789  296  559
>  1934
>  Kotlin  19 3501  347 1370
>  1784
>  HTML60 2447  148  914
>  1385
>  Batch3  249   570
>   192
>  INI  1  206   21   16
>   169
>  C++  2   724   36
>32
>  Autoconf 1   211   16
> 4
>
> 
>  Total 5002  1000874   132497   173987
>694390
>
> 
>
> [1] https://github.com/cgag/loc
>

Re: 1 Million Lines of Code (1 MLOC)

[Brian Hulette]

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  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  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  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  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 FilesLinesBlank  Comment
Code

 
  Java  3681   67300778265   140753
  453989
  Python 497   1310822256013378
   95144
  Go 333   1057751368111073
   81021
  Markdown   20531989 65260
   25463
  Plain Text  1121979 63590
   15620
  Sass92 9867 1434 1900
6533
  JavaScript  19 5157 1197  467
3493
  YAML14 4601  454 1104
3043
  Bourne Shell30 3874  470 1028
2376
  Protobuf17 4258  677 1373
2208
  XML 17 2789  296  559
1934
  Kotlin  19 3501  347 1370
1784
  HTML60 2447  148  914
1385
  Batch3  249   570
 192
  INI  1  206   21   16
 169
  C++  2   724   36
  32
  Autoconf 1   211   16
   4

 
  Total 5002  1000874   132497   173987
  694390

 

 [1] https://github.com/cgag/loc

>>>

Re: 1 Million Lines of Code (1 MLOC)

[Anton Kedin]

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  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  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  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 FilesLinesBlank  Comment
>>>Code
>>>
>>> 
>>>  Java  3681   67300778265   140753
>>>  453989
>>>  Python 497   1310822256013378
>>>   95144
>>>  Go 333   1057751368111073
>>>   81021
>>>  Markdown   20531989 65260
>>>   25463
>>>  Plain Text  1121979 63590
>>>   15620
>>>  Sass92 9867 1434 1900
>>>6533
>>>  JavaScript  19 5157 1197  467
>>>3493
>>>  YAML14 4601  454 1104
>>>3043
>>>  Bourne Shell30 3874  470 1028
>>>2376
>>>  Protobuf17 4258  677 1373
>>>2208
>>>  XML 17 2789  296  559
>>>1934
>>>  Kotlin  19 3501  347 1370
>>>1784
>>>  HTML60 2447  148  914
>>>1385
>>>  Batch3  249   570
>>> 192
>>>  INI  1  206   21   16
>>> 169
>>>  C++  2   724   36
>>>  32
>>>  Autoconf 1   211   16
>>>   4
>>>
>>> 
>>>  Total 5002  1000874   132497   173987
>>>  694390
>>>
>>> 
>>>
>>> [1] https://github.com/cgag/loc
>>>
>>

Re: 1 Million Lines of Code (1 MLOC)

[Lukasz Cwik]

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  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  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 FilesLinesBlank  Comment
>>  Code
>>
>> 
>>  Java  3681   67300778265   140753
>>  453989
>>  Python 497   1310822256013378
>> 95144
>>  Go 333   1057751368111073
>> 81021
>>  Markdown   20531989 65260
>> 25463
>>  Plain Text  1121979 63590
>> 15620
>>  Sass92 9867 1434 1900
>>  6533
>>  JavaScript  19 5157 1197  467
>>  3493
>>  YAML14 4601  454 1104
>>  3043
>>  Bourne Shell30 3874  470 1028
>>  2376
>>  Protobuf17 4258  677 1373
>>  2208
>>  XML 17 2789  296  559
>>  1934
>>  Kotlin  19 3501  347 1370
>>  1784
>>  HTML60 2447  148  914
>>  1385
>>  Batch3  249   570
>>   192
>>  INI  1  206   21   16
>>   169
>>  C++  2   724   36
>>32
>>  Autoconf 1   211   16
>> 4
>>
>> 
>>  Total 5002  1000874   132497   173987
>>  694390
>>
>> 
>>
>> [1] https://github.com/cgag/loc
>>
>

Re: 1 Million Lines of Code (1 MLOC)

[Ankur Goenka]

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  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 FilesLinesBlank  Comment
>  Code
>
> 
>  Java  3681   67300778265   140753
>  453989
>  Python 497   1310822256013378
> 95144
>  Go 333   1057751368111073
> 81021
>  Markdown   20531989 65260
> 25463
>  Plain Text  1121979 63590
> 15620
>  Sass92 9867 1434 1900
>  6533
>  JavaScript  19 5157 1197  467
>  3493
>  YAML14 4601  454 1104
>  3043
>  Bourne Shell30 3874  470 1028
>  2376
>  Protobuf17 4258  677 1373
>  2208
>  XML 17 2789  296  559
>  1934
>  Kotlin  19 3501  347 1370
>  1784
>  HTML60 2447  148  914
>  1385
>  Batch3  249   570
>   192
>  INI  1  206   21   16
>   169
>  C++  2   724   36
>32
>  Autoconf 1   211   16
> 4
>
> 
>  Total 5002  1000874   132497   173987
>  694390
>
> 
>
> [1] https://github.com/cgag/loc
>

1 Million Lines of Code (1 MLOC)

[Ismaël Mejía]

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 FilesLinesBlank  Comment Code

 Java  3681   67300778265   140753   453989
 Python 497   131082225601337895144
 Go 333   105775136811107381021
 Markdown   20531989 6526025463
 Plain Text  1121979 6359015620
 Sass92 9867 1434 1900 6533
 JavaScript  19 5157 1197  467 3493
 YAML14 4601  454 1104 3043
 Bourne Shell30 3874  470 1028 2376
 Protobuf17 4258  677 1373 2208
 XML 17 2789  296  559 1934
 Kotlin  19 3501  347 1370 1784
 HTML60 2447  148  914 1385
 Batch3  249   570  192
 INI  1  206   21   16  169
 C++  2   724   36   32
 Autoconf 1   211   164

 Total 5002  1000874   132497   173987   694390


[1] https://github.com/cgag/loc