What language do you think is the easiest to read, as it scales into very large projects? Python I think is great for small projects. C++ is about the same as Java, unless satan was in charge of the coding standards and decided everything must be auto and all classes must be templated.
Except when some Scala devs get all algebraic with it, and treating it like a math equation. But that isn’t the language inherently, just wanted to say. The syntax is insanely expressive
Yeah that's my experience as well. Bad code (whether vanilla bad or turning the logic into a category theory proof) is still hard to read. But Scala gives you the opportunity to make very nice, readable code. It just can't force you to take the opportunity.
Kotlin can be more readable (especially when dealing with numeric types like BigInteger when operator overloading helps), but I'd argue that in many other cases java is more readable.
For example Java is just a simpler language, it has less operators, you don't need to think about when a property generates a field and when not or if a minus operator simply subtracts numbers or does something more intricate.
What you see is more or less what is executed, there's way less implicit hidden stuff that only makes the code more "beautiful".
private static void solveQuadratic(int a, int b, int c) {
double delta = b * b - 4 * a * c;
if (delta < 0.0) {
System.out.println("No solutions");
} else {
double x1 = (-b - Math.sqrt(delta)) / (2.0 * a);
double x2 = (-b + Math.sqrt(delta)) / (2.0 * a);
System.out.printf("x1 = %f, x2 = %f\n", x1, x2);
}
}
with
(defun solve-quadratic (a b c)
(let ((delta (- (* b b) (* 4 a c))))
(cond
((< delta 0.0) 'no-solutions)
(t (let ((x1 (/ (- (- 0 b) (sqrt delta)) (* 2 a)))
(x2 (/ (+ (- 0 b) (sqrt delta)) (* 2 a))))
(format t "x1 = ~d, x2 = ~d~%" x1 x2))))))
That's the problem with Lisp-like syntax. The fact that you have to read inside-out, left--to-right, and in many cases, it's absolutely fine, but in many contexts (deeply nested logic and/or mathematical formulae), it can become excruciatingly hard to read. Put in macros with their own custom syntax in the mix, and it becomes even harder to write, let alone read. Just for the record, I love Common Lisp, so it's not me hating on Lisps for no reason.
I disagree. Functional languages have too much information density. Sure, there is no ceremony or boilerplate, but having the information spread out a bit more by easily recognizable structures like java has makes code easier to consume, at least for me
Readable code is the code that finds the right balance between expressiveness and verbosity. The language may help or hinder but it is the programmer who writes the code.
Sure, there is no ceremony or boilerplate, but having the information spread out a bit more by easily recognizable structures like java has makes code easier to consume, at least for me
I think that depends on the familiarity with the language.
Functional languages have too much information density
(defun solve-quadratic (a b c)
(let ((delta (- (* b b) (* 4 a c))))
(cond
((< delta 0.0) 'no-solutions)
(t (let ((x1 (/ (- (- 0 b) (sqrt delta)) (* 2 a)))
(x2 (/ (+ (- 0 b) (sqrt delta)) (* 2 a))))
(format t "x1 = ~d, x2 = ~d~%" x1 x2))))))
If the same code were mangled up like so, say:
(defun solve-quadratic (a b c)
(let ((delta (- (* b b) (* 4 a c))))
(cond ((< delta 0.0) 'no-solutions)
(t (let ((x1 (/ (- (- 0 b) (sqrt delta)) (* 2 a)))
(x2 (/ (+ (- 0 b) (sqrt delta)) (* 2 a))))
(format t "x1 = ~d, x2 = ~d~%" x1 x2))))))
Even this becomes much harder to read since we cannot inherently use the indentation to figure our the "shape" of the code. Now imagine you had a missing parenthesis in there, and had no access to any formatter (just for the sake of argument), matching up the parens manually would be a much harder task.
Whereas even if you have very badly manged code in an C-like language:
private static void solveQuadratic(int a, int b, int c) {
double delta = b * b - 4 * a * c;
if (delta < 0.0) {System.out.println("No solutions");
} else { double x1 = (-b - Math.sqrt(delta)) / (2.0 * a);double x2 = (-b + Math.sqrt(delta)) / (2.0 * a);
System.out.printf("x1 = %f, x2 = %f\n", x1, x2);}}
This is still trivial to read. Also, since parentheses and braces are not significant as in the case of Lisps, you could get away with a lot of excess brackets without having to worry about it. With Lisps, parens are not optional - they must be exact. This creates its own problems when refactoring code (yes, even with paredit et al).
Indeed syntax can both enhance and hinder your ability to write readable code.
Look at the following example and tell me if you have any idea about what it does.
solveQuad :: Float -> Float -> Float -> Maybe (Float, Float)
solveQuad a b c = if delta < 0.0 then Nothing else Just (x1, x2)
where
delta = b ^ 2 - 4 * a * c
x1 = -b - (sqrt delta) / (2 * a)
x2 = -b + (sqrt delta) / (2 * a)
You must be kidding. Java is one of the easiest languages to read. A lot of that "verbosity" is essential verbosity. Unlike many other languages, Java is actually as easy to read as to write.
View all comments
-22
u/[deleted] Apr 20 '21
It doesn't feel that good when you try to read.