# programming-languages Published articles for programming-languages. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Swift 6.4 unifies building across Linux, macOS, Windows DevFeed: [Swift 6.4 unifies building across Linux, macOS, Windows]() Original publisher: [Read original article]() Author: Joab Jackson Published: 2026-09-17T04:27:00Z Content type: article Language: en Sources: [www.theregister.com - Articles]() Topics: [Swift](), [swift-package-manager](), [Development](), [Linux](), [macOS](), [Windows]() Tags: [build](), [cross-platform-development](), [devops](), [linux](), [macos](), [open-source](), [programming-languages](), [swift](), [swift-6-4](), [swift-package-manager](), [windows]() ### AI overview Swift 6.4 makes Swift Build the default engine for the Swift Package Manager, with building unified across Linux, macOS, and Windows. ### Source excerpt Swift Build is now the default engine for the Swift Package Manager ## Go 1.27 will make some allocations cheaper DevFeed: [Go 1.27 will make some allocations cheaper]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-08-15T20:59:19Z Content type: article Language: en Sources: [Daniel Lemire]() Topics: [Go Language](), [Programming](), [Compiler](), [Data structures]() Tags: [compiler](), [data-structure](), [go](), [memory-management](), [programming](), [programming-languages]() ### AI overview The article explains Go's stack and heap allocations, including how escaping values, slices, and dynamic data structures can cause heap allocations. It notes that Go 1.27 is intended to make some heap allocations cheaper, while the supplied excerpt does not specify the implementation details. ### Source excerpt Like most programming languages, Go has both stack allocations, whose lifetime is limited to the current function, and dynamic (or heap) allocations. The name stack comes from the fact that the memory management is somewhat trivial. There is typically one stack per thread (or goroutine in Go). When a function needs memory, it simply appends ... Continue reading Go 1.27 will make some allocations cheaper ## Java vs. JavaScript: What's the Difference? (They're Not the Same Thing) DevFeed: [Java vs. JavaScript: What's the Difference? (They're Not the Same Thing)]() Original publisher: [Read original article]() Author: Dev Support Published: 2026-08-13T17:48:00Z Content type: tutorial Language: en Sources: [Treehouse Blog]() Topics: [Java](), [JavaScript](), [coding]() Tags: [coding](), [java](), [java-vs-javascript](), [javascript](), [learn](), [learn-programming](), [llearn-to-code](), [programming-languages]() ### AI overview This tutorial explains that Java and JavaScript are separate programming languages with different creators, syntax, use cases, and execution models. It also discusses their naming history and contrasts Java's compilation and static typing with JavaScript's runtime interpretation or JIT compilation and dynamic typing. ### Source excerpt If you've ever typed "is Java the same as JavaScript" into a search bar, you're in good company. It's one of the most common questions in coding, and the confusion is completely understandable -- the names are nearly identical, both... The post Java vs. JavaScript: What's the Difference? (They're Not the Same Thing) appeared first on Treehouse Blog. ## Creator of Lua: Scripting, Programming Languages, Predictions | Roberto Ierusalimschy DevFeed: [Creator of Lua: Scripting, Programming Languages, Predictions | Roberto Ierusalimschy]() Original publisher: [Read original article]() Author: Ryan Peterman Published: 2026-08-03T13:05:15Z Content type: article Language: en Sources: [The Developing Dev]() Topics: [Lua](), [Programming](), [Scripting](), [C++](), [C](), [Code]() Tags: [c](), [c-plus-plus](), [lua](), [programming](), [programming-languages](), [python](), [scripting]() ### AI overview A conversation with Lua creator Roberto Ierusalimschy explains how Lua works as an embeddable scripting language alongside C or C++, including how applications can call Lua or Lua can call C. The discussion also covers Lua's use in games such as World of Warcraft and Roblox and recommendations for learning other programming languages. ### Source excerpt When I worked at Instagram, most of the codebase was in Python but occasionally I'd see these bindings into C++. ## On programming languages, targets, and platforms DevFeed: [On programming languages, targets, and platforms]() Original publisher: [Read original article]() Author: Nicolas Fränkel Published: 2026-06-21T00:00:00Z Content type: opinion Language: en Sources: [Nicolas Fränkel]() Topics: [Programming](), [Programming language](), [multiplatform](), [Scala](), [Java](), [JavaScript]() Tags: [developer](), [development](), [java](), [javascript](), [kotlin](), [languages](), [multiplatform](), [programming](), [programming-languages](), [python](), [rust](), [scala]() ### AI overview A personal discussion of how programming languages have evolved from targeting a single compilation target and platform toward supporting multiple targets. It uses Scala.js as an example and mentions Kotlin and Clojure as other JVM-originated languages targeting JavaScript. ### Source excerpt I started as a Java developer, but for some time now, I have broadened my horizons. Recently, I thought about how early languages were dedicated to a single target and platform, and now they are broadening their focus. In this post, I want to write down my thoughts in the hope that it may be useful to others, probably to my future self. Definitions You may have been wondering about the title terms. ## Why Choose Pulumi Over Terraform? DevFeed: [Why Choose Pulumi Over Terraform?]() Original publisher: [Read original article]() Author: Pablo Seibelt Published: 2026-06-02T00:00:00Z Content type: comparison Language: en Sources: [Pulumi]() Topics: [Infrastructure as code](), [Terraform](), [cloud-infrastructure](), [Programming](), [Software Engineering](), [Refactoring](), [Tooling](), [migration]() Tags: [cloud-infrastructure](), [general](), [infrastructure-as-code](), [migration](), [platform-engineering](), [programming](), [programming-languages](), [pulumi](), [refactoring](), [software-engineering](), [terraform](), [tooling]() ### AI overview This comparison explains why teams may choose Pulumi over Terraform for infrastructure as code. It highlights Pulumi's use of general-purpose programming languages, package managers, IDEs, testing, refactoring workflows, encrypted secrets, reusable components, and safeguards for destructive changes, while noting that provider bugs, drift, eventual consistency, unknown values, and poor abstractions still require engineering discipline. ### Source excerpt Terraform is a proven infrastructure as code tool with a large provider and module ecosystem. Many teams choose Pulumi when they want to keep that infrastructure as code model, but write and maintain infrastructure with general-purpose programming languages, familiar package managers, IDEs, testing, and software engineering patterns, while still understanding the refactoring tradeoffs in Terraform's own module refactoring guidance. Why choose Pulumi over Terraform? Pulumi's language SDKs let teams define cloud infrastructure in TypeScript, JavaScript, Python, Go, .NET, or Java -- with YAML and HCL also supported as authoring languages -- while adding first-class workflows for refactoring with Pulumi aliases, secrets, protect, retainOnDelete, deleteBeforeReplace, replaceOnChanges, provider resources, Pulumi stacks, testing, and incremental migration with pulumi import. Pulumi does not remove every hard problem in cloud infrastructure, but it gives teams stronger tools for many day-to-day pain points. Executive summary Pulumi is often a better fit when infrastructure code needs to behave like application code: reviewed, tested, packaged, refactored, and shared across teams. The biggest advantages show up when teams need safer refactors, encrypted secret values, reusable components, clearer provider resources, and guardrails around destructive changes. The tradeoff is important: Pulumi is still an infrastructure as code engine. Provider bugs, cloud API eventual consistency, drift, preview-time unknowns, and poorly designed abstractions still require engineering discipline. The advantage is not magic. The advantage is a stronger programming model and a more familiar developer workflow. Need Terraform pattern Pulumi advantage What still needs care Languages and tooling HCL plus Terraform-specific functions and expressions Pulumi supports general-purpose languages, YAML, and now HCL natively, with the normal IDE, test, and package workflows for each Teams still need code re ## A brief history of C/C++ programming languages DevFeed: [A brief history of C/C++ programming languages]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-04-09T14:58:53Z Content type: opinion Language: en Sources: [Daniel Lemire]() Topics: [C](), [C++](), [Programming](), [Java](), [C#](), [Fortran](), [Go Language](), [JavaScript](), [Python]() Tags: [c-c-plus-plus](), [compilation](), [garbage-collection](), [go](), [history](), [languages](), [memory](), [programming](), [programming-languages]() ### AI overview This article presents a brief history of C and C++, explaining how C emerged for low-level systems programming and how C++ added object-oriented, generic, and compile-time metaprogramming features. It then contrasts their portability challenges with Java and discusses JavaScript, Python, C#, and Go. The supplied text ends mid-sentence. ### Source excerpt Initially, we had languages like Fortran (1957), Pascal (1970), and C (1972). Fortran was designed for number crunching and scientific computing. Pascal was restrictive with respect to low-level access (it was deliberately "safe", as meant for teaching structured programming). So C won out as a language that allowed low-level/unsafe programming (pointer arithmetic, direct memory access) ... Continue reading A brief history of C/C++ programming languages ## Kotlin Coroutines Compared with Reactor for Sequential and Asynchronous Operations DevFeed: [Kotlin Coroutines Compared with Reactor for Sequential and Asynchronous Operations]() Original publisher: [Read original article]() Published: 2025-10-06T00:00:00Z Content type: comparison Language: en Sources: [Kt. Academy]() Topics: [Coroutines](), [Kotlin](), [kotlin-coroutines](), [Reactive Streams](), [RxJava](), [async/await](), [Android](), [Back end]() Tags: [android](), [async](), [asynchronous](), [await](), [backend](), [compare](), [comparison](), [coroutines](), [kotlin](), [kotlin-coroutines](), [programming](), [programming-languages](), [reactive-streams](), [rxjava](), [simple](), [time](), [workshop-learning-programming]() ### AI overview This article compares Kotlin Coroutines with Reactor for backend and Android development. It argues that coroutines provide more readable and straightforward syntax for sequential and asynchronous operations, while Reactor requires additional operators, concepts, and patterns. ### Source excerpt A comparison of Kotlin Coroutines and Reactor, highlighting the elegance and simplicity of Coroutines over the complexity of Reactor. ## Cangjie -- a programming language from Huawei DevFeed: [Cangjie -- a programming language from Huawei]() Original publisher: [Read original article]() Author: Jasper Morgan Published: 2025-08-19T07:37:53Z Content type: opinion Language: en Sources: [Snapp Mobile - Medium]() Topics: [Programming language](), [huawei](), [Programming](), [Code](), [Embedded Systems](), [Cross-Compilation](), [Mobile](), [cloud-computing](), [Package Management](), [debug](), [Testing](), [ide]() Tags: [architectures](), [bytecode](), [cangjie](), [china](), [cloud](), [cross-compilation](), [debugging](), [developers](), [development](), [embedded-systems](), [huawei](), [huawei-developers](), [language](), [mobile](), [package-management](), [programming](), [programming-language](), [programming-languages](), [tools]() ### AI overview This article examines Cangjie, an open-sourced programming language from Huawei. It describes Cangjie as a C-like language with features associated with Swift and Kotlin, support for embedded systems, mobile development, and cloud architectures, interoperability with C and Python, JVM bytecode compilation, cross-compilation, and integrated developer tools. The article suggests Huawei created it to gain more control over its language roadmap and consolidate development skills across products. ### Source excerpt Cangjie -- a programming language from Huawei Huawei have been busy. Last month they open-sourced a programming language that is looking pretty interesting. Whilst you might not be writing in Cangjie next week, it's good to see what one of the world's largest technology companies is doing such that they have created a new programming language. TL;DR Cangjie is a C-like programming language that feels more like Swift/Kotlin than Java/C# or JavaScript/Typescript. The idea is for Cangjie to become the common programming language to be used throughout Huawei. Cangjie can be used for embedded systems, mobile development, server-side cloud architectures. It supports a variety of programming paradigms (function, OO, procedural), compilation and integration options. Cangjie can call C libraries (and be called from C), use Python libraries and even compile to JVM bytecode. Cangjie supports language extension to create lightweight DSLs. Primarily Cangjie programs are compiled into machine code -- this include cross compilation which mean they can run natively on different computer architectures. Cangjie comes with a set of in-built tools for developers such as package management, debugging, testing and IDE integration. Cangjie is openly available since this month and is in version 0.53.13. Why create a new language? Simply put, Cangjie gives Huawei a level of control and an economy of scale that they cannot get from other languages. Most mainstream languages are driven predominantly by teams in USA and Europe. It is hard to influence the road map for these languages -- especially for those tightly controlled by corporations (e.g. Java/Kotlin/Swift). Furthermore, consolidating programming skills could be a big efficiency gain for Huawei -- engineers working on products ranging from routers to petabyte storage to cloud computing and mobile devices can coalesce around one language and toolset. Show me some code I won't go into any detail here so this is just to satisfy your curiosit ## How Lean Propositions Differ from TypeScript Booleans DevFeed: [How Lean Propositions Differ from TypeScript Booleans]() Original publisher: [Read original article]() Published: 2025-08-16T00:00:00Z Content type: tutorial Language: en Sources: [Dan Abramov]() Topics: [Lean](), [Programming](), [Mathematics](), [Code](), [TypeScript]() Tags: [mathematics](), [programming](), [programming-languages](), [types](), [typescript]() ### AI overview This tutorial compares logical expressions in TypeScript with propositions in Lean. It explains that Lean treats propositions as distinct values and types, and that proving a proposition requires supplying a proof rather than simply computing a Boolean result. ### Source excerpt What is the type of 2 + 2 = 4? ## the algebra of dependent types DevFeed: [the algebra of dependent types]() Original publisher: [Read original article]() Published: 2025-05-29T00:07:51Z Content type: article Language: en Sources: [Tony Finch's blog]() Topics: [Programming](), [Functional programming](), [Standard ML](), [Rust]() Tags: [algebra](), [enum](), [functional-programming](), [languages](), [programming-languages](), [type-system](), [type-theory](), [types]() ### AI overview An explanation of why big-sigma and big-pi notation appears in dependent type theory. It connects dependent functions and dependent pairs to algebraic data types, showing how products correspond to multiplication and sum types to addition, with examples from type theory, Standard ML, Haskell, and Rust. ### Source excerpt TIL (or this week-ish I learned) why big-sigma and big-pi turn up in the notation of dependent type theory. I've long been aware of the zoo of more obscure Greek letters that turn up in papers about type system features of functional programming languages, μ, Λ, Π, Σ. Their meaning is usually clear from context but the reason for the choice of notation is usually not explained. I recently stumbled on an explanation for Π (dependent functions) and Σ (dependent pairs) which turn out to be nicer than I expected, and closely related to every-day algebraic data types. sizes of types The easiest way to understand algebraic data types is by counting the inhabitants of a type. For example: the unit type () has one inhabitant, (), and the number 1 is why it's called the unit type; the bool type hass two inhabitants, false and true. I have even seen these types called 1 and 2 (cruelly, without explanation) in occasional papers. product types Or pairs or (more generally) tuples or records. Usually written, (A, B) The pair contains an A and a B, so the number of possible values is the number of possible A values multiplied by the number of possible B values. So it is spelled in type theory (and in Standard ML) like, A * B sum types Or disjoint union, or variant record. Declared in Haskell like, data Either a b = Left a | Right b Or in Rust like, enum Either { Left(A), Right(B), } A value of the type is either an A or a B, so the number of possible values is the number of A values plus the number of B values. So it is spelled in type theory like, A + B dependent pairs In a dependent pair, the type of the second element depends on the value of the first. The classic example is a slice, roughly, struct IntSlice { len: usize, elem: &[i64; len], } (This might look a bit circular, but the idea is that an array [i64; N] must be told how big it is - its size is an explicit part of its type - but an IntSlice knows its own size. The traditional dependent "vector" type is a sized li ## Dijkstra's Views on Theory, Academia, and Programming Languages DevFeed: [Dijkstra's Views on Theory, Academia, and Programming Languages]() Original publisher: [Read original article]() Published: 2025-05-13T14:23:11Z Content type: opinion Language: en Sources: [Jeremy Kun]() Topics: [Programming]() Tags: [essays](), [programming](), [programming-languages](), [shortform]() ### AI overview The author reflects on Edsger Dijkstra's speech "Under the spell of Leibniz's Dream," focusing on its view that elegant theory can have practical value. They critique Dijkstra's dismissive attitude toward industry, students, and modern universities, while discussing his praise of ALGOL 60 and its language innovations. ### Source excerpt I was inspired to browse some of Edsger Dijkstra's essays today, and came across his speech, "Under the spell of Leibniz's Dream". It's the sort of personal history I love to read, which gives one person's sense of the world over a period of change. One quote that immediately struck me was his view of his country's spirit after WWII: An important side-effect of the hard times was the creation of a spiritual climate in which the distinction between pure and applied science had vanished: of all the things you could do, you just did the most urgent one, and the development of some urgently needed theory was often the most practical thing to do. ## HarmonyOS App Development 101 DevFeed: [HarmonyOS App Development 101]() Original publisher: [Read original article]() Author: Jasper Morgan Published: 2025-01-18T23:23:13Z Content type: tutorial Language: en Sources: [Snapp Mobile - Medium]() Topics: [App](), [Development](), [ide](), [huawei](), [SDK](), [Tooling](), [jetbrains](), [Package Management](), [Testing](), [Open Source]() Tags: [android](), [app](), [app-development](), [apps](), [code-completion](), [debug](), [deployment](), [development](), [harmony-os](), [huawei](), [ide](), [jetbrains](), [open-source](), [package-management](), [programming-languages](), [refactoring](), [sdk](), [testing](), [tools](), [ui](), [ui-framework]() ### AI overview An overview of HarmonyOS Next app development, covering the Huawei-based DevEco Studio IDE, project configuration, SDK versions, modules, and common development features. The article also outlines programming languages, UI frameworks, build tools, package management, execution, debugging, testing, and profiling. ### Source excerpt Huawei have taken a big step in moving away from the Android platform with the launch of new devices running HarmonyOS Next. This is a brand new operating system that had been design specifically for devices. This means it is lightweight, supports a range of device types, is modular and extensible. In this article we aim to give you an overview of what is available to developers wishing to build apps on this new platform. To that end, we will be looking at the following topics: The IDE Programming Languages UI Framework Build Tools Package Management Running code (devices/emulators) Debugging Testing Profiling Other cool stuff If you are curious about the Harmony platform, its Open Source foundations (OpenHarmony) and its global reach (Oniro), we have written about it here. The IDE The development environment for Harmony apps is currently a Huawei-based IDE which is based on the JetBrains IDE platform. The good news is that JetBrains offers a world-class IDE platform and it makes for a very solid development experience for Harmony apps. For those, wanting to keep to the Open Source side of Harmony (OpenHarmony and Oniro), you are out of luck right now. DevEco Studio is proprietary, albeit free to use software. Let's look at a couple of IDE features -- these should not surprise you but hopefully demonstrates that the platform is already in a good place (as far as IDEs go). Project Creation Creating a project will look familiar already for many. There are a few project templates to choose from to bootstrap your project. New Project Templates You will also then need to configure a couple of options -- a couple of notes on these (which could probably be expanded into a separate article). Firstly, the bundle name is used for app signing and identity. Secondly, an app supports a single SDK version. (The latest SDK version is 13, however version 11 is still widely used.) Thirdly we can specify the module name. The default ('entry') isn't very descriptive. If you have a singl ## On Long Term Software Development DevFeed: [On Long Term Software Development]() Original publisher: [Read original article]() Published: 2024-12-22T17:00:00Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [Development](), [Software](), [Open Source](), [CI/CD](), [Programming](), [Framework](), [Esolang]() Tags: [ci](), [continuous-deployment](), [continuous-integration](), [dependencies](), [development](), [framework](), [mastodon](), [open-source](), [programming](), [programming-languages](), [software]() ### AI overview An opinion article reflecting on long-term software development through a talk about the Dutch Electoral Board's open-source Abacus vote tabulation software. It contrasts continuously deployed, heavily tested services with safety-critical software that must remain stable for decades, and discusses dependencies, programming languages, and frameworks as long-term design choices. ### Source excerpt Recently the Dutch Electoral Board (where I am also a very part time advisor) invited me to do a talk reflecting on their open source Abacus vote tabulation software. Much software is now provided as a service, and is typically deployed continuously (CD, continuous deployment), surrounded by enough automated testing (CI, continuous integration) that we can be reasonably sure that a new revision is likely to at least work to some extent. ## The problem of union types for type systems DevFeed: [The problem of union types for type systems]() Original publisher: [Read original article]() Published: 2024-06-10T00:00:00Z Content type: opinion Language: en Sources: [Kt. Academy]() Topics: [union types](), [Kotlin](), [Programming](), [subtype](), [generics]() Tags: [generics](), [inference](), [interfaces](), [kotlin](), [programming](), [programming-languages](), [smart-cast](), [static](), [subtype](), [type](), [types](), [union](), [workshop-learning-programming]() ### AI overview This article explains why general union types are difficult to add to Kotlin and other statically typed systems. It discusses ambiguity in subtype relationships and generic type inference, including the claim that inference is NP-hard, then describes Kotlin's proposed limited use of union types for representing errors through rich errors. ### Source excerpt Why union types are not such a good idea for static type systems. ## Ep. 4: Type Coercion in Rust: Ensuring Safety and Preventing Data Loss DevFeed: [Ep. 4: Type Coercion in Rust: Ensuring Safety and Preventing Data Loss]() Original publisher: [Read original article]() Published: 2024-05-03T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Rust](), [Programming](), [C](), [Go Language]() Tags: [c](), [code](), [data-type](), [go](), [integrity](), [languages](), [memory-handling](), [memory-safety](), [pitfalls](), [programming-languages](), [rust](), [safety](), [safety-concerns](), [software](), [type-coercion](), [types]() ### AI overview This video tutorial explains type coercion and data type conversions, including how inadvertent conversions can produce unexpected results. It compares C, Go, and Rust, emphasizing Rust's Into and TryInto traits, explicit casts, error handling, safety, and code integrity. ### Source excerpt Introduction: Delving into the intricate realm of type coercion, Herbert's insights offer invaluable guidance for Rust developers grappling with the complexities of data type conversions: Gain insights into the nuances of type coercion, a fundamental aspect of programming languages, and its potential pitfalls, drawing parallels with numerical computation surprises. Explore how Go and Rust tackle inadvertent type coercion, prioritizing program integrity by making it challenging to assign values between incompatible types. ## Ep. 3: Ensuring Data Integrity in Rust: Battling Overflow and Underflow DevFeed: [Ep. 3: Ensuring Data Integrity in Rust: Battling Overflow and Underflow]() Original publisher: [Read original article]() Published: 2024-04-29T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Rust](), [integrity](), [Programming](), [Software]() Tags: [code](), [errors](), [insights](), [integrity](), [memory-handling](), [memory-safety](), [programming](), [programming-languages](), [rust](), [safety-concerns](), [software](), [software-development]() ### AI overview This episode explains integer overflow and underflow, including their causes, examples, and potential effects in software. It focuses on how Rust's static analysis and checked arithmetic operations help developers detect or handle these issues and support code integrity. ### Source excerpt Introduction: Delving into the critical issues of overflow and underflow, Herbert's insights offer valuable takeaways for Rust developers: Rust's static analysis capabilities enable early detection and prevention of overflow and underflow errors, allowing developers to address potential issues before they manifest in runtime environments. Through Rust's emphasis on safety and correctness, developers can leverage built-in mechanisms to handle overflow and underflow situations gracefully, reducing the likelihood of software crashes and unexpected behavior. ## Making Twig Macros Work Like Functions DevFeed: [Making Twig Macros Work Like Functions]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2023-07-14T18:38:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Programming](), [Development](), [reusable code](), [Code]() Tags: [functions](), [insights](), [just](), [languages](), [learn](), [like](), [macros](), [make](), [manipulate](), [programming](), [programming-languages](), [return](), [returning](), [reusable-code](), [twig](), [value](), [values]() ### AI overview A tutorial on making Twig macros return values that can be manipulated like function results. It demonstrates a sales-calculation macro, whitespace control, and returning a value for further computations such as sales tax. ### Source excerpt Learn how to make Twig macros return values you can manipulate, just like functions in other programming languages ## A Practical Core Subset of Regular Expressions DevFeed: [A Practical Core Subset of Regular Expressions]() Original publisher: [Read original article]() Published: 2023-07-11T00:00:00Z Content type: tutorial Language: en Sources: [Tim Kellogg]() Topics: [Programming](), [Code]() Tags: [complexity](), [languages](), [portable](), [programming-languages](), [regex]() ### AI overview This tutorial presents a core subset of regular expressions that is intended to be easier to understand and remember. It explains why regex can be useful, notes that shortcuts add complexity, and introduces character sets, repetition, groups, and operators. ### Source excerpt Regex gets a bad reputation for being very complex. That's fair, but I also think that if you focus on a certain core subset of regex, it's not that hard. Most of the complexity comes from various "shortcuts" that are hard to remember. If you ignore those, the language itself is fairly small and portable across programming languages. ## Fully bootstrapping Java from source in Wolfi DevFeed: [Fully bootstrapping Java from source in Wolfi]() Original publisher: [Read original article]() Published: 2023-06-02T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Java](), [openjdk](), [supply-chain-security](), [chainguard](), [Compiler](), [Programming](), [gcc]() Tags: [bootstrapping](), [chainguard](), [chainguard-images](), [compiler](), [distribution](), [eclipse-compiler-for-java](), [gcc](), [gnu-linux](), [java](), [jdk](), [linux](), [openjdk](), [programming](), [programming-languages](), [provenance](), [security](), [software](), [software-supply-chain](), [software-supply-chain-security](), [supply-chain-security](), [wolfi]() ### AI overview Chainguard describes how it is fully bootstrapping Java from source in Wolfi. The process builds a chain of OpenJDK packages with provenance extending from source code to final binary packages, using GNU Classpath, GNU Compiler for Java, and the Eclipse Compiler for Java to overcome historical bootstrapping dependencies. ### Source excerpt Learn how Chainguard engineers created a chain of OpenJDK packages to provide full provenance from pure source code for the entire Java ecosystem in Wolfi. ## 26 programming languages in 25 days, Part 2: Reflections on language design DevFeed: [26 programming languages in 25 days, Part 2: Reflections on language design]() Original publisher: [Read original article]() Published: 2022-12-31T19:36:56Z Content type: opinion Language: en Sources: [Matt Might]() Topics: [Programming language](), [Functional programming](), [Programming](), [Data structures](), [Advent of Code]() Tags: [advent-of-code](), [algorithms](), [algorithms-and-data-structures](), [functional](), [programming](), [programming-languages]() ### AI overview The author reflects on completing Advent of Code 2022 with 26 programming languages in 25 days. They found that functional techniques, algorithms, and data structures generally mattered more than language performance, while language design choices such as syntax, typing, and purity affected readability, debugging, and development speed in different puzzle contexts. ### Source excerpt I recently wrote about completing Advent of Code 2022 using a different programming language (or two) every day for 25 days. That note focused on the strategy, tactics and logistics involved in using 26 languages in 25 days without saying much about the languages or the experience itself. Using so many languages in such a short span provided insight into tradeoffs in language design. Here are my two high-level reflections from the experience: Good program design in the first part of each puzzle - especially more functional techniques and abstractions - tended to make the second part easier. So, in general, functional languages seemed to have the advantage in the puzzles. Using better algorithms and data structures was more important than having a "faster" programming language. There was never a time where rewriting in another language felt like the right way to get better performance. Read on for more specific reflections on language design. Click here to read the rest of the article ## If Programming Languages Were Futurama Characters DevFeed: [If Programming Languages Were Futurama Characters]() Original publisher: [Read original article]() Published: 2022-05-10T02:28:32Z Content type: opinion Language: en Sources: [Signs of Triviality]() Topics: [Programming language](), [Programming]() Tags: [languages](), [programming](), [programming-languages]() ### AI overview An article invites readers to map their favorite or least favorite programming language to a Futurama Planet Express crew member according to the language's characteristics. ### Source excerpt Map your (least) favorite programming language to your favorite Planet Express crew member based on its characteristics. ## Haskell 102 Lecture Notes DevFeed: [Haskell 102 Lecture Notes]() Original publisher: [Read original article]() Published: 2022-05-08T00:00:00Z Content type: tutorial Language: en Sources: [Romes' Musings]() Topics: [Haskell](), [Functional programming](), [Programming]() Tags: [code](), [function](), [functional-programming](), [haskell](), [programming](), [programming-languages](), [types]() ### AI overview Lecture notes introducing Haskell function types, currying, partial application, higher-order functions, laziness, recursion, recursive data structures, and type classes. ### Source excerpt Contents 1 Functions Types, Currying, Partial application, Higher-order functions 2 Laziness 3 Recursion: Inductive Method 4 Recursive data structures 5 Type Classes 6 Type Classes Kinds, Constraints 1 Functions Types, Currying, Partial application, Higher-order functions All functions have a type, the function type: length :: [a] -> Int length [] = 0 length (x:xs) = 1 + length xs The same way we think about the Either type constructor, and about the tuple type constructor (,), we can think about the function type type constructor (the arrow ->). They are all type constructors that take two arguments. data Either a b = Left a | Right b data (,) a b = (a, b) -- pseudo code data (->) a b = a -> b -- pseudo code This means that the (->) type constructor, when applied to two types a and b, creates a new type a -> b, where a is the input type and b the return type. This beggets the question, what is the type of a function that takes two arguments? There are two ways to define multi-argument functions. The first would be to think about functions that receive multiple arguments in a tuple. prepend :: (Char, String) -> String prepend (c, str) = c:str You could even use it like this prepend('h', "ello"), which somewhat resembles the imperative style function call. The second option is to have a function take one argument a, and return a function that takes another argument b and only then returns c. prepend :: Char -> (String -> String) prepend c = (\str -> c:str) And this is the most common way to have multi-argument functions in functional programming languages. In Haskell, thinking about two argument functions and functions that return functions is really the same thing. The most common way of writing the two argument function prepend in Haskell, read "prepend is a function that takes two arguments of type Char and String and returns String", would be prepend :: Char -> String -> String prepend c str = c:str The (Char, String) -> String version is said to be an uncurried ## Writing a WebAssembly Service in TinyGo for Wagi and Spin DevFeed: [Writing a WebAssembly Service in TinyGo for Wagi and Spin]() Original publisher: [Read original article]() Author: Matt Butcher Published: 2022-04-16T19:39:08Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [WebAssembly](), [Go Language](), [Programming]() Tags: [build](), [go](), [programming](), [programming-languages](), [webassembly]() ### AI overview This post describes building a small WebAssembly service with TinyGo, using Wagi and Spin. ### Source excerpt Of the growing list of WebAssembly capable programming languages, Go is one of our favorites. In this post, we build a real (but tiny) service with TinyGo. [Next page]()