diff options
| -rw-r--r-- | gemfeed/DRAFT-ultrarelearning-java.gmi | 97 | ||||
| -rw-r--r-- | gemfeed/atom.xml | 8 |
2 files changed, 55 insertions, 50 deletions
diff --git a/gemfeed/DRAFT-ultrarelearning-java.gmi b/gemfeed/DRAFT-ultrarelearning-java.gmi index ff4007d9..8e274e91 100644 --- a/gemfeed/DRAFT-ultrarelearning-java.gmi +++ b/gemfeed/DRAFT-ultrarelearning-java.gmi @@ -1,97 +1,106 @@ -# Ultra(re)learning Java +# Ultra(re)learning Java - My takeaways -> Published by Paul at XXXX-XX-XX +> Published by Paul at 2022-12-24 -As a regular participant of the annual Pet Project competition at work I always try to find a project where I can learn something new. You can read about my motivations in my "Creative universe" post: +=> ./2022-12-24-ultralearning-java-my-takeaways/learnjava.jpg + +As a regular participant in the annual Pet Project competition at work, I always try to find a project where I can learn something new. In this post, I would like to share my takeaways after revisiting Java (Spoiler: I am still not the biggest Java fan, but Java has its uses). You can read about my motivations in my "Creative universe" post: => ./2022-04-10-creative-universe.gmi Creative universe -I have been programming in Java back in the days as an university student and even my Diploma Thesis was implemented in Java (it would require some overhaul so that it is fully compatible with a recent version of Java, though - It still compiles and runs, but with a lot of warnings!): +I have been programming in Java back in the days as a university student, and even my Diploma Thesis I implemented in Java (it would require some overhaul so that it is fully compatible with a recent version of Java, though - It still compiles and runs, but with a lot of warnings, though!): => https://codeberg.org/snonux/vs-sim VS-Sim: Distributed systems simulator -However, after that, I became a Linux Sysadmin and mainly continued programming in Perl, Puppet and bash and a little Python. For personal use, I also programmed a bit in Haskell and C. After my Sysadmin role I moved to London and became a Site Reliability Engineer (SRE), where I mainly programmed in Ruby, bash, Puppet and Golang and a little bit of C. +However, after that, I became a Linux Sysadmin and mainly continued programming in Perl, Puppet, bash, and a little Python. For personal use, I also programmed a bit in Haskell and C. After my Sysadmin role, I moved to London and became a Site Reliability Engineer (SRE), where I mainly programmed in Ruby, bash, Puppet and Golang and a little bit of C. -At my workplace, as an SRE, I usually don't do Java a lot. However, most of our stack is programmed in Java and our Software Engineers use Java as their primary programming language. I have been reading Java code to understand the software a bit better so that I can apply and suggest work around or fixes to existing issues and bugs. +At my workplace, as an SRE, I don't do Java a lot. I have been reading Java code to understand the software better so I can apply and suggest workarounds or fixes to existing issues and bugs. However, most of our stack is in Java, and our Software Engineers use Java as their primary programming language. ## Stuck at Java 1.4 -Over time, I felt that I have been missing out on many of the new features which were added to the language since Java 1.4, so I decided to implement my next Pet Project in Java and to also learn every new aspect of the language as my main goal. Of course, I wanted to win a Pet Project Prize too, but the main objective was to level up my Java skills (or to re-learn Java). +Over time, I had been missing out on many new features that were added to the language since Java 1.4, so I decided to implement my next Pet Project in Java and learn every further aspect of the language as my main goal. Of course, I still liked the idea of winning a Pet Project Prize, but my main objective was to level up my Java skills. -## Ultra(re)lerning & upskilling +## Ultra(re)lerning & upskilling to Java 18 ### Effective Java -This book was recommended by my brother and also by at least another colleague at work to be one of the best, if not the best, book about Java programming. I read the whole book from the beginning to the end and immersed myself into all the new best practices. I fully agree, this is a great book. Every Java developer or software engineer should read it! +This book was recommended by my brother and also by at least another colleague at work to be one of the best, if not the best, book about Java programming. I read the whole book from the beginning to the end and immersed myself in it. I fully agree; this is a great book. Every Java developer or Java software engineer should read it! -=> TODO: Insert Effective Java book cover picture +=> ./2022-12-24-ultralearning-java-my-takeaways/effective-java.jpg -I also highly recommend to read the 90 part long Effecitve Java Series on `dev.to`. It's a perfect companion to the book as it explains all the chapters again but from a slightly different perspective and helps you to really understand the content. +I recommend reading the 90-part effective Java Series on `dev.to`. It's a perfect companion to the book as it explains all the chapters again but from a slightly different perspective and helps you to really understand the content. -=> https://dev.to/kylec32/series/2292 Kyle Carter's 90 part Effective Java Series +=> https://dev.to/kylec32/series/2292 Kyle Carter's 90-part Effective Java Series ### Java Pub House -During my lunch breaks I usually have a walk around the block or in a nearby park. I used that time to listen to the Java Pub House podcast. I listened to *every* episode and learned tons of new stuff. I can highly recommend this podcast. Especially GraalVM, a high-performance JDK distribution written for Java and other JVM languages, captured my attention. GraalVM can compile Java code into native binaries which can improve performance and also eases the distribution of Java programs. Because of the latter, I should release a VS-Sim GraalVM edition one day through an Linux AppImage ;-). +During my lunch breaks, I usually have a walk around the block or in a nearby park. I used that time to listen to the Java Pub House podcast. I listened to *every* episode and learned tons of new stuff. I can highly recommend this podcast. Especially GraalVM, a high-performance JDK distribution written for Java and other JVM languages, captured my attention. GraalVM can compile Java code into native binaries, improving performance and easing the distribution of Java programs. Because of the latter, I should release a VS-Sim GraalVM edition one day through a Linux AppImage ;-). => https://www.javapubhouse.com => https://www.graalvm.org ### Java Concurrency course -I also watched a course on O'Reilly Safara Books online about Java Concurrency. That gave a great refresher of how the Java thread pools work and what were the concurrency primitives available in the standard library. +I also watched a course on O'Reilly Safari Books online about Java Concurrency. That gave an excellent refresher on how the Java thread pools work and what were the concurrency primitives available in the standard library. ### Read a lot of Java code -I started to read more and more Java code at work. I did that every time when I didn't understand how something worked. First of all, the source code is often the best documentation (if programmed nicely), and secondly, it helps to get the hang of the language and common practices. +First, the source code is often the best documentation (if programmed nicely), and second, it helps to get the hang of the language and standard practices. I started to read more and more Java code at work. I did that whenever I had to understand how something, in particular, worked (e.g. while troubleshooting and debugging an issue). ### Observed Java code reviews -Another great way to get the hang of Java again was to sneak into the code reviews of the Software Engineer colleagues. They are the expert of the matter and are a great source to copy knowledge from. It's OK to stay passive and only follow the reviews. In some cases it's OK to step up and take ownership of the review. The developers will also be always happy to answer to any of the naive questions you might have. +Another great way to get the hang of Java again was to sneak into the code reviews of the Software Engineer colleagues. They are the expert on the matter and are a great source to copy knowledge. It's OK to stay passive and only follow the reviews. Sometimes, it's OK to step up and take ownership of the review. The developers will also always be happy to answer any naive questions which come up. ### Took ownership of a roadmap-Java project -Other than my Pet Project, I also took ownerships of a regular roadmap Java project at work making an internal Java service Kubernetes aware. This was a bunch of smaller changes and adding a bunch of smaller classes and unit tests. Not part of my job description, but it was fun and I learned a lot. The service runs smoothly in production now. Of course, all of my code got reviewed by my Software Engineering colleagues. +Besides my Pet Project, I also took ownership of a regular roadmap Java project at work, making an internal Java service capable of running in Kubernetes. This was a bunch of minor changes and adding a bunch of classes and unit tests dealing with the statelessness and a persistent job queue in Redis. The job also involved reading and understanding a lot of already existing Java code. It wasn't part of my job description, but it was fun, and I learned a lot. The service runs smoothly in production now. Of course, all of my code got reviewed by my Software Engineering colleagues. -## Java language and feature takeways +## The good -From the new language features and syntaxes there are many personal takeways and I can't possible list them all, but here are some of my personal highlights: +From the new language features and syntaxes, there are many personal takeaways, and I can't possibly list them all, but here are some of my personal highlights: -* Static factory methods and public constructors both have their uses, and it pays to understand their relative merits. Often static factories are preferable, so avoid the reflex to provide public constructors without first considering static factories. -* Java streams were completely new to me. I really love how they can help to produce more compact code. But it's challenging to set the line of when enough is enough. Overuse of streams can have the opposite effect: Code becomes more complex and more difficult to understand. And it is so easy to parallelize the computation of streams by "just" marking the stream as `.parallel()` (more on that later in this post). -* I think the functional interfaces, which Java provides now, are awesome. Their full powers shine in combination with the use of streams. Over all, there seems to be a tendency for object oriented languages to include more and more functional paradigms. A full book can be written about the Java functional interfaces, so I leave it to you to do any further lookup.. +* Static factory methods and public constructors both have their uses, and it pays to understand their relative merits. Often static factories are preferable (cleaner and easier to read), so avoid the reflex to provide public constructors without first considering static factories. +* Java streams were utterly new to me. I love how they can help to produce more compact code. But it's challenging to set the line of when enough is enough. Overusing streams can have the opposite effect: Code becomes more complex and challenging to understand. And it is so easy to parallelize the computation of streams by "just" marking the stream as `.parallel()` (more on that later in this post). +* Overall, object-oriented languages tend to include more and more functional paradigms. The functional interfaces, which Java provides now, are fantastic. Their full powers shine in combination with the use of streams. An entire book can be written about Java functional interfaces, so I leave it to you to do any further digging. * Local type inference help to reduce even more boilerplate code. E.g. instead of `Hash<String,Hash<String,String>> foo = new Hash<String,Hash<String,String>>();` it's possible to just write `var foo = new Hash<String,Hash<String,String>>();` -* Class inheritance isn't the preferred way anymore to structure reusable code. Now, it's composition over inheritance. E.g. use dependency injection (inject one object to another object through it's constructor) or prefer interfaces (which now also support default implementations of methods) over class inheritance. -* I learned the `try-with-resources` pattern. Very useful ensuring closing resources again correctly. No need anymore for complicated and nested `finally`-blocks which used to be almost impossible to get right previously in case of an error condition (e.g. I/O error somewhere deeply nested in an input or output stream). -* It's considered to be cleaner to prefer immutable variables. I knew that already, but for Java it always seemed to be a lot of waste of resources (creation of completely new objects whenever states change), but apparently, it's not a big problem. Optimize only when really required. Java also performs a lot of internal tricks for performance optimization here, e.g. interning strings. -* I learned about the concept of static member classes and the difference to non-static member classes (also sometimes known as inner classes). Non-static member classes have full access of all members of it's outer class (think of closure), whereas static member classes act like completely separate classes without such access but provide the benefit of a nested name which can help to group functionality in the code. -* I learned about the existence of thread-local variables. These are only available to the current thread and aren't shared to any other threads. -* I learned to love the new `Optional` type. I knew the concept from Haskell already, where `Maybe` would be the corresponding type. `Optional` helps to avoid `null`-pointers, but come with some (minimal) performance penalty. So at the end, you end up with both, `Optional` types and `null`-pointers in your code (depending on the requirements). But I like to prefer `Optional` over `null`-pointer when "no result" is a valid result from a method. -* The `enum` type is way more powerful than I thought. Initially I thought an `enum` can only be used to define a list of constants and then to compare an instane of it to another instance of the same. An `enum` is still there to define a list of of constants, but it's also almost like a `class` (you can implement constructors, methods, inherit from other enums). There are quite a lot of use cases... -* A small but almost the most useful thing I learned is to always use the `@Override` annotation when overriding a method from a parent class. If done, Java helps to detect any typos or type errors when overriding methods. That's really useful and safed me a lot of time debugging. -* Lambdas are a much cleaner, shorter and easier to read than anonymous classes. There are tons of Java libraries requiring passing instances of (anonymous) classes (e.g. in Swing) to other objects. What makes Lambdas so nice is that they are mostly compatible to the passing of anonymous classes so they are a 1:1 replacement in many instances. Lambdas also play very nicely together with the Java functional interfaces, as each Lambda got a type and the type can be an already existing functional interface (or, if you got a special case, you could define your custom functional interface for your own set of Lambdas, of course). - -There are also many ugly corners in Java. Many are doomed to stay there forever due to historic decisions and ensuring backwards compatibility with older versions of the Java language and the Java standard library. +* Class inheritance isn't the preferred way anymore to structure reusable code. Now, it's composition over inheritance. E.g. use dependency injection (inject one object to another object through its constructor) or prefer interfaces (which now also support default implementations of methods) over class inheritance. This makes sense to me as I do that already when I program in Ruby. +* I learned the `try-with-resources` pattern. Very useful in ensuring closing resources again correctly. No need anymore for complicated and nested `finally`-blocks, which used to be almost impossible to get right previously in case of an error condition (e.g. I/O error somewhere deeply nested in an input or output stream). +* Optimize only when required. It's considered to be cleaner to prefer immutable variables (declaring them as `final`). I knew that already, but for Java, it always seemed to be a waste of resources (creating entirely new objects whenever states change), but apparently, it's okay. Java also does many internal tricks for performance optimization here, e.g. interning strings. +* I learned about the concept of static member classes and the difference between non-static member classes (also sometimes known as inner classes). Non-static member classes have full access to all members of their outer class (think of closure). In contrast, static member classes act like completely separate classes without such access but provide the benefit of a nested name that can help group functionality in the code. +* I learned about the existence of thread-local variables. These are only available to the current thread and aren't shared with other threads. +* I learned about the concept of Java modules, which help to structure larger code bases better. The traditional Java packages are different. +* I learned to love the new `Optional` type. I already knew the concept from Haskell, where `Maybe` would be the corresponding type. `Optional` helps to avoid `null`-pointers but comes with some (minimal) performance penalty. So, in the end, you end up with both `Optional` types and `null`-pointers in your code (depending on the requirements). But I like to prefer `Optional` over `null`-pointer when "no result" is a valid return value from a method. +* The `enum` type is way more powerful than I thought. Initially, I felt an `enum` could only be used to define a list of constants and then to compare an instance to another instance of the same. An `enum` is still there to define a list of constants, but it's also almost like a `class` (you can implement constructors, and methods, inherit from other enums). There are quite a lot of possible use cases. +* A small but almost the most helpful thing I learned is always to use the `@Override` annotation when overriding a method from a parent class. If done, Java helps to detect any typos or type errors when overriding methods. That's useful and spares a lot of time debugging where a method was mistakenly overloaded but not overridden. +* Lambdas are much cleaner, shorter and easier to read than anonymous classes. Many Java libraries require passing instances of (anonymous) classes (e.g. in Swing) to other objects. Lambdas are so lovely because they are primarily compatible with the passing of anonymous classes, so they are a 1:1 replacement in many instances. Lambdas also play very nicely together with the Java functional interfaces, as each Lambda got a type, and the type can be an already existing functional interface (or, if you got a particular case, you could define your custom functional interface for your own set of Lambdas, of course). +* I love the concept of Java records. You can think of a record as an immutable object holding some data (as members). They are ideal for pipe and stream processing. They are much easier to define (with much less boilerplate) and come with write protection out of the box. + +## The bad and the ugly + +There are also many ugly corners in Java. Many are doomed to stay there forever due to historical decisions and ensuring backward compatibility with older versions of the Java language and the Java standard library. * Finalizers and cleaners seem obsolete, fragile and still, you can use them. -* In many cases, extreme caution needs to be taken to minimize the accessibility of class members. You might think that Java provides the best "out-of-the-box" solution for proper encapsulation, but there are so many loop-holes in the language. -* In the early days, Java did't support generics yet. So what you would use is simply `Object`. Now, Java fully supports generic (for a while already), but you can still cast everything `Object` and back to whatever type you want. That can lead to nasty runtime cast errors. Also, there's the special case to convert between an Array of Object to an Array of String, or from an Array of String to a List of String. Java can't convert between these types automatically and extreme caution needs to be taken when enforcing so (e.g. through explicit type casts or custom methods). In many of these cases, Java would print out warnings which then would need to be manually suppressed via annotations. Programming that way, converting data between old and new best practices, feels clunky. -* If you don't know what you do, Java streams can be all wrong. Side effects in functions used in streams can be really nasty to debug. Also, don't just blindly add a `.parallel()` to your stream. You need to understand what the stream does and how it exactly works, otherwise parallelizing a stream can impact the performance drastically (in a negative way). There's no language construct preventing you doing the wrong things. That's so much easier to do it right in a pure functional programming language like Haskell. -* Java is a pretty old language (already), so there are many obstacles to consider. In most cases, when you write an API, every method you program needs to be documented, so that the user won't encounter any surprises using your code. There are just too many exceptions and different outcomes of how Java code can behave. Writing and reading a lot of documentation seems to be quite the overhead, in my humble opinion. -* Java serialization seems to be broken. It works, and it is still supported by the language, but you better don't use Java's native way of object serialization and deserialization. Unbelievable how much can get wrong here. -* Being a bit spoiled by Golang's Goroutines, I was a bit shocked about the limitations of the Java threads. They are quite resource hungry and you can't just spin up millions of them, like you would do with Goroutines. I knew this limitation of threads already, but still, I was pretty shocked when I got reminded of them again. Of course, there's a workaround: Just use asynchronous sockets, so that you don't waste a whole thread on a single I/O operation (in my case, waiting for a network response). Golang's runtime does that automatically for you: An OS thread will be re-used for other tasks until the network socket unblocks. +* In many cases, extreme caution needs to be taken to minimize the accessibility of class members. You might think that Java provides the best "out-of-the-box" solution for proper encapsulation, but the language has many loopholes. +* In the early days, Java didn't support generics yet. So what you would use is to cast everything to `Object`. Java now fully supports generics (for a while already), but you can still cast everything to `Object` and back to whatever type you want. That can lead to nasty runtime errors. Also, there's a particular case to convert between an Array of Object to an Array of String or from an Array of String to a List of String. Java can't convert between these types automatically, and extreme caution needs to be taken when enforcing so (e.g. through explicit type casts). In many of these cases, Java would print out warnings that need to be manually suppressed via annotations. Programming that way, converting data between old and new best practices, is clunky. +* If you don't know what you do, Java streams can be all wrong. Side effects in functions used in streams can be nasty to debug. Also, don't just blindly add a `.parallel()` to your stream. You need to understand what the stream does and how it exactly works; otherwise, parallelizing a stream can impact the performance drastically (in a negative way). There need to be language constructs preventing you from doing the wrong things. That's so much easier to do it right in a purely functional programming language like Haskell. +* Java is a pretty old language (already), so there are many obstacles to consider. There are too many exceptions and different outcomes of how Java code can behave. In most cases, when you write an API, every method you program needs to be documented so the user won't encounter any surprises using your code. Writing and reading a lot of documentation seems to be quite the overhead when the method name is already descriptive. +* Java serialization is broken. It works, and the language still supports it, but you better not use Java's native way of object serialization and deserialization. Unbelievable how much can get wrong here, especially regarding security (injecting arbitrary code). +* Being a bit spoiled by Golang's Goroutines, I was shocked about the limitations of the Java threads. They are resource hungry, and you can't just spin up millions of them as you would with Goroutines. I knew this limitation of threads already (as it's not a problem of the language but of how threads work in the OS), but still, I was pretty shocked when I got reminded of them again. Of course, there's a workaround: Use asynchronous sockets so that you don't waste a whole thread on a single I/O operation (in my case, waiting for a network response). Golang's runtime does that automatically for you: An OS thread will be re-used for other tasks until the network socket unblocks. Every modern programming language should support lightweight threads or Coroutines like Go's Goroutines. + ## Conclusion -While (re)learning Java I felt like a student again and I was quite ethusiastic about it in the beginning. I invested around half a year immersing myself intensively with Java (again). The last time I did that was many years ago as an university student. I even won a Silver Prize at work implementing a project in it this year. I feel much more confident now with understand, debugging and patching Java code at work and it gave me a boost in my debugging and troubleshooting skills. +While (re)learning Java, I felt like a student again and was quite enthusiastic about it initially. I invested around half a year, immersing myself intensively in Java (again). The last time I did that was many years ago as a university student. I even won a Silver Prize at work, implementing a project this year (2022 as of writing this). I feel confident now with understanding, debugging and patching Java code at work, which boosted my debugging and troubleshooting skills. + +I don't hate Java, but I don't love programming in it, either. I will, I guess, always see Java as the necessary "evil" to get stuff done (reading code to understand how the service works, adding a tiny feature to make my life easier, adding a quick bug fix to overcome an obstacle...). But still, I lost the Java groove on the way. -But still, I think I lost the Java groove on the way. I don't hate Java, but I don't really love programming in it. I will, I guess, always see Java as the necessary "evil" to get stuff done (reading code in order to understand how the service works, adding a tiny feature to make my life easier, add a quick bugfix to overcome an obstacle...). +Although Java has significantly improved since 1.4, its code still tends to be more boilerplate. Not mainly because due to lines of code (Golang code tends to be quite repetitive, primarily when no generics are used), but due to the levels of abstractions it uses. Class hierarchies can be ten classes or deeper, and it is challenging to understand what the code is doing. Good test coverage and much documentation can mitigate the problem partially. Big enterprises use Java, and so also look at the languages. There are too many libraries and too many abstractions that are bundled with too many legacy abstractions and interfaces and too many exceptions in the library APIs. There's even an external library named Lombok, which aims to reduce Java boilerplate code. Why is there a need for an external library? It should be all part of Java itself. -Although, Java has improved a lot, I still think the code is still too boilerplate. Not mainly because due to lines of code (Golang code tends to be quite repetitive, especially when no generics are used), but due to the levels of abstractions it uses. Class heirachies can be 10 classes or more deep and it's really difficult to understand what the code is really doing. A good test coverage can mitigate the problem partially. Java is used by big enterprises, and so also looks the languages. There are too many libraries, too many abstractions, that bundled with too many legacy abstractions and interfaces and too many exceptions. +=> https://projectlombok.org/ -I believe Java needs a clean cut. The clean cut shall be incompatible to previous versions of Java and only promote modern best practices without all the legacy burden carried around. Same can be said for other languages, e.g. Perl but in Perl they already attack the problem with use flags which change the behaviour of the language to more modern standards. Or do it like Python, where they had a hard (incompatible) cut from version 2 to version 3. It will be painful for sure. But that would be the only way I would actually enjoy using that language as one of my primary languages to code new stuff in. As of now, my Java will stay limited to very few projects and/or the smaller things already mentioned in this post. +Java needs a clean cut. The clean cut shall be incompatible with previous versions of Java and only promote modern best practices without all the legacy burden carried around. The same can be said for other languages, e.g. Perl, but in Perl, they already attack the problem with the use of flags which change the behaviour of the language to more modern standards. Or do it like Python, where they had a hard (incompatible) cut from version 2 to version 3. It will be painful, for sure. But that would be the only way I would enjoy using that language as one of my primary languages to code new stuff regularly. Currently, my Java will stay limited to very few projects and the more minor things already mentioned in this post. -Am I a Java expert now? No, by far not. But I will have a look at features I don't know once in a while when encountering them by accident. +Am I a Java expert now? No, by far not. But I will look at features I don't know once in a while when encountering them accidentally. E-Mail your comments to paul at buetow dot org! :-) diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 147a0719..bc317313 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"> - <updated>2022-12-17T12:27:04+00:00</updated> + <updated>2022-12-24T22:38:03+02:00</updated> <title>foo.zone feed</title> <subtitle>To be in the .zone!</subtitle> <link href="gemini://foo.zone/gemfeed/atom.xml" rel="self" /> @@ -1455,11 +1455,7 @@ v = 008 [v = p*c*(s != c ? 2 : 1)] Total logical CPUs <summary>Perl (the Practical Extraction and Report Language) is a battle-tested, mature, multi-paradigm dynamic programming language. Note that it's not called PERL, neither P.E.R.L. nor Pearl. 'Perl' is the name of the language and 'perl' the name of the interpreter or the interpreter command.. .....to read on please visit my site.</summary> <content type="xhtml"> <div xmlns="http://www.w3.org/1999/xhtml"> - 1c1 -< -rw-r--r--. 1 paul paul 16789 Dec 17 11:19 ../foo.zone-content/gemtext/gemfeed/2022-05-27-perl-is-still-a-great-choice.gmi ---- -> -rw-r--r--. 1 paul paul 16784 Dec 17 11:25 ../foo.zone-content/gemtext/gemfeed/2022-05-27-perl-is-still-a-great-choice.gmi -<h1>Perl is still a great choice</h1> + <h1>Perl is still a great choice</h1> <p class="quote"><i>Published by Paul at 2022-05-27, last updated at 2022-12-17, Comic source: XKCD</i></p> <a href="https://foo.zone/gemfeed/2022-05-27-perl-is-still-a-great-choice/regular_expressions.png"><img src="https://foo.zone/gemfeed/2022-05-27-perl-is-still-a-great-choice/regular_expressions.png" /></a><br /> <p>Perl (the Practical Extraction and Report Language) is a battle-tested, mature, multi-paradigm dynamic programming language. Note that it's not called PERL, neither P.E.R.L. nor Pearl. "Perl" is the name of the language and <span class="inlinecode">perl</span> the name of the interpreter or the interpreter command.</p> |