# imperative Published articles for imperative. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Chrome 144's Element: Declarative Location Access DevFeed: [Chrome 144's Element: Declarative Location Access]() Original publisher: [Read original article]() Author: ratneshmaurya2311@gmail.com (Ratnesh Maurya) Published: 2026-02-24T00:00:00Z Content type: article Language: en Sources: [Ratn Labs]() Topics: [Chrome](), [HTML](), [Web Development]() Tags: [chrome](), [declarative](), [geolocation](), [html](), [imperative](), [location](), [privacy](), [web-development]() ### AI overview This article describes Chrome 144's new HTML element for declarative, user-driven location access. It explains that the element can simplify geolocation access, improve privacy, and replace imperative navigator.geolocation calls. ### Source excerpt Learn how Chrome 144's new HTML element simplifies location access, improves privacy, and replaces imperative navigator.geolocation calls with a declarative, user-driven approach. ## Using Fleet 1.19's AI Assistant to Convert Kotlin Between Imperative and Functional Styles DevFeed: [Using Fleet 1.19's AI Assistant to Convert Kotlin Between Imperative and Functional Styles]() Original publisher: [Read original article]() Published: 2023-06-10T13:12:44Z Content type: article Language: en Sources: [maiatoday]() Topics: [coding style](), [Kotlin](), [Functional programming](), [Artificial Intelligence](), [coding](), [Code](), [Advent of Code]() Tags: [advent-of-code](), [ai](), [ai-assistant](), [code](), [coding-style](), [doggerel](), [fleet](), [functional](), [functional-programming](), [imperative](), [kotlin](), [word-games]() ### AI overview The article experiments with Fleet 1.19's integrated AI assistant by converting Kotlin code for the Advent of Code 2022 Day 10 puzzle between imperative and functional styles, comparing the results, and generating poetry. ### Source excerpt Once upon a time I admit. I have a penchant for word games and weird segues. So I will tell you what this post is about off the bat. You can skip to the code, I won't be offended. Fleet 1.19 was released this week with an integrated AI assistant. I took it for a spin and used it to convert Kotlin code from imperative style to functional and back again. I used some Kotlin code, which solves the Advent of Code 2022 Day 10 puzzle. I had written the solution in two styles and I had the AI assistant do the same conversion and compared the code. And then I played around and generated some poetry. Follow links at your peril, there are rabbit holes, it might make you late or change the size of your free time. Segue the first of many Oh you are still here! You didn't jump to the code starts here section? Why am I doing this? A long time ago, I read a lot of Lewis Caroll, Alice in Wonderland. In one scene Alice talks to the Mock Turtle. He sings a song about sea creatures dancing. When the first language translators appeared on the scene, Altavisa babelfish or perhaps it was the early Google Translate, I converted passages from Alice in Wonderland to French and then back again to see what the machines could do. The Mock Turtle was transformed into an Imitation Tortoise. In this way the reference to the original mock turtle soup was lost in translation. In a roundabout way I was wondering what would be uncovered or lost if I used the AI assistant for some translations in coding style. Couplets of doggerel My trusty and non emotional assistant had no opinion on Lewis Caroll but it made this for me. A definition of functional programming style in rhyming couplets: Functional programming's way, treats functions as the play. Immutable states they use, side effects they refuse. Declarative code is their choice, with functions, they rejoice. Nested functions map, filter, reduce, a clean, elegant code they produce. Compare this with the imperative version: Imperative code, step by st ## Four of a Kotlin Kind at I code Java 2022 conference DevFeed: [Four of a Kotlin Kind at I code Java 2022 conference]() Original publisher: [Read original article]() Published: 2022-10-14T08:30:41Z Content type: article Language: en Sources: [maiatoday]() Topics: [Kotlin](), [Code](), [Software]() Tags: [code](), [concepts](), [conference](), [declarative](), [functional](), [imperative](), [java](), [kotlin](), [object-oriented](), [pitfalls](), [talk](), [tips](), [traces]() ### AI overview The article introduces a talk about Kotlin's support for imperative, declarative, functional, and object-oriented programming. It highlights tips, guidelines, pitfalls, definitions, software history, and how Kotlin supports these concepts. ### Source excerpt I shared my talk titled Imperative, Declarative, Object oriented, functional: Four of a Kotlin Kind at the I code Java conference. The abstract: Is Kotlin a functional language? Yes, but... Is it object oriented? Yes, but... Looking at four concepts: imperative, declarative, functional and object oriented How does Kotlin make it easy to use either or all at the same time. This talk contains: Some useful Kotlin tips, some guidelines and pitfalls for the four concepts, traces of definitions and software history. After listening to this talk you will understand what these concepts are, what each is good for and how they are supported by the Kotlin language. You can see the talk here ## Functional Lifestyles Training DevFeed: [Functional Lifestyles Training]() Original publisher: [Read original article]() Author: Peter Norvig Published: 2023-04-03T23:19:47.031000Z Content type: opinion Language: en Sources: [Peter Norvig]() Topics: [functions](), [exceptions](), [Haskell]() Tags: [concurrent](), [exceptions](), [functional](), [imperative](), [input](), [lambda](), [lazy](), [mapping](), [state]() ### AI overview A humorous interview presents functional programming concepts as a gym's personalized fitness program. It uses puns involving folds, lambda lifting, free variables, evaluation strategies, data structures, monads, input/output, exceptions, immutability, and functions. ### Source excerpt Some heavy lambda lifting could get you in better functional shape. ## Declaring the Future of Programming DevFeed: [Declaring the Future of Programming]() Original publisher: [Read original article]() Published: 2011-01-09T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [Programming](), [syntax](), [SQL](), [C](), [C++](), [Compiler]() Tags: [c](), [c-plus-plus](), [compiler](), [declarative](), [imperative](), [programming](), [programming-languages](), [sql]() ### AI overview The article argues that programming languages have gradually favored declarative syntax over imperative instructions and predicts that this trend will continue. It contrasts machine code, assemblers, C and C++ with SQL, where programmers describe the desired result while the database system determines how to produce it. ### Source excerpt Programming languages have developed significantly over the past several decades. I hypothesize that this development has tended more towards declarative syntax than imperative. The future of programming languages will only become more declarative in the years to come.In the beginning was machine code. Programmers wrote programs by stringing together arcane byte codes of instructions and parameters. Programs were getting pretty hard to read so they made assemblers so you could write instructions in plain text, complete with comments. An assembler program would process the source code and turn each instruction into it's equivalent machine code. This is imperative programming at its most pure state.When the first C compiler was written it immediately became popular because the programmer only had to declare what should happen in the program and the compiler would generate the necessary machine code to make that happen. Hence why you can write a C program that can be compiled for Linux, Windows and Mac with zero changes to the source code. However, C and C++ are still imperative languages in most other aspects because the thought process is still very much a "do this, now do this, now do this" algorithmic sequence of instructions.Query LanguagesThe hallmark of declarative languages thoughout history is probably SQL (referring strictly to set operations here). In SQL you describe the result set and let the DBMS decide the best way to produce that result set. For instance, consider this query:select p.FirstName, p.LastName, a.AccountNamefrom Person pinner join Account aon p.PersonId = a.ResponsiblePersonwhere a.IsActive = 1order by p.FirstName, p.LastNameFirst we describe the columns that we want (this actually happens last, if you want to be technical). In the from clause we say what tables we want information from and specify how we want them matched up using the on clause of the join. In the where clause we specify what criteria for the rows that we want to show and i