Probably not, but it’d be closer to Clojure. Depending on codebase you’ll likely have also many repeating namespace imports (can be avoided whith implicit usings in modern C#) etc.
We start with the source-code markup you can see, remove comments, remove duplicate whitespace characters, and then apply minimum GZip compression. The measurement is the size in bytes of that GZip compressed source-code file.
Thanks to Brian Hurt for the idea of using size of compressed source-code instead of lines of code.
median
February 2025
===============
Toit 558
Perl 570
Lua 580
PHP 581
Ruby 583
Python 3 585
Julia 634
Chapel 646
Racket 696
JavaScript 698
OCaml 741
Erlang 798
Go 831
Dart 847
Smalltalk 871
Haskell 892
Java 910
Lisp 938
Swift 939
F# 943
Pascal 959
Fortran 1091
C# 1117
C 1121
C++ 1129
Rust 1235
Ada 1825
I'd expect programming style to have a lot to do with it. Many modern languages are evolving toward Lisp and support ever more of its features. Generic programming and meta programming for instance.
(I think the tool used accounts for imports and defines.)
mrsmrtss|11 days ago
so-cal-schemer|5 days ago
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
How source-code size is measured
We start with the source-code markup you can see, remove comments, remove duplicate whitespace characters, and then apply minimum GZip compression. The measurement is the size in bytes of that GZip compressed source-code file.
Thanks to Brian Hurt for the idea of using size of compressed source-code instead of lines of code.
unknown|5 days ago
[deleted]
so-cal-schemer|11 days ago
(I think the tool used accounts for imports and defines.)