# idea Published articles for idea. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Logpoints Walkthrough DevFeed: [Logpoints Walkthrough]() Original publisher: [Read original article]() Author: Igor Kulakov Published: 2026-09-16T14:14:04Z Content type: tutorial Language: en Sources: [The JetBrains Blog]() Topics: [IntelliJ IDEA](), [debug](), [debugging](), [gRPC](), [Java](), [2026.2]() Tags: [2026-2](), [bug](), [client](), [command-line](), [debug](), [debugger](), [debugging](), [debugging-tools](), [idea](), [intellij](), [intellij-idea](), [java](), [kotlin](), [logpoints]() ### AI overview This walkthrough explains how to use logpoints in IntelliJ IDEA to investigate a bug in a gRPC client-server example that returns incorrect discount values. It covers reproducing the issue, attaching the debugger to the server, and observing program behavior without suspending execution, including improvements in IntelliJ IDEA 2026.2. ### Source excerpt Modern development tools, especially IntelliJ IDEA, have such comprehensive debugging support that for virtually any niche use case, there is a specialized tool for the job. This can make it hard to know where to begin. If you are new to debugging tools and want the biggest return on your learning investment, the best feature [...] ## Behind the Scenes: How the OpenTelemetry Plugin Maps Your Microservices in Real-Time DevFeed: [Behind the Scenes: How the OpenTelemetry Plugin Maps Your Microservices in Real-Time]() Original publisher: [Read original article]() Author: Egor Klimov Published: 2026-09-16T12:34:47Z Content type: article Language: en Sources: [The JetBrains Blog]() Topics: [OpenTelemetry](), [Microservices](), [observability](), [telemetry](), [Traces](), [ide]() Tags: [all-things-web](), [backstage](), [environment-variables](), [goland](), [ide](), [idea](), [intellij-idea](), [intellij-platform](), [jetbrains](), [microservices](), [observability](), [opentelemetry](), [performance-optimization](), [plugin-development](), [plugin-highlights](), [plugins](), [pycharm](), [research](), [rider](), [telemetry](), [traces](), [webstorm]() ### AI overview This article explains how the JetBrains OpenTelemetry Plugin generates a service map from runtime telemetry. It describes using logs, metrics, and especially standardized trace spans to visualize how microservices communicate, along with the plugin's lightweight local OpenTelemetry backend. ### Source excerpt We've all been there: you join a new project, and the first thing you ask for is the architecture diagram. You're handed a diagram that looks great, but after a week of debugging, you realize it's six months out of date. Service A hasn't talked to Service B since the spring, and there's a new [...] ## The Evolution of WSL Support in JetBrains IDEs DevFeed: [The Evolution of WSL Support in JetBrains IDEs]() Original publisher: [Read original article]() Author: Kristina Pchelintseva Published: 2026-09-09T10:39:49Z Content type: article Language: en Sources: [The JetBrains Blog]() Topics: [IntelliJ IDEA](), [Processes]() Tags: [2026-2](), [architecture](), [debug](), [ecosystem](), [engineering](), [ide](), [idea](), [intellij-idea](), [intellij-platform](), [linux](), [phpstorm](), [remote-development](), [support](), [webstorm](), [windows](), [wsl]() ### AI overview JetBrains describes its evolution of WSL integration and recommends Native mode from version 2026.2. In this mode, supported IDEs remain Windows applications while an agent in WSL handles project files and processes. ### Source excerpt JetBrains IDEs have worked with WSL for many years, and over time, several ways of using it have emerged across our products. Depending on the entry point, the IDE could rely on a different underlying architecture, leading to a different experience. Starting with the 2026.2 release, there is one recommended entry point. In IntelliJ IDEA, [...] ## Loop engineering: stop prompting, start looping DevFeed: [Loop engineering: stop prompting, start looping]() Original publisher: [Read original article]() Author: Anthony Viard Published: 2026-09-08T16:00:00Z Content type: article Language: en Sources: [Postman Blog]() Topics: [Loop Engineering](), [AI Agent](), [AI-assisted coding](), [API]() Tags: [2026](), [agent](), [agentic](), [agents](), [ai](), [ai-agents](), [ai-coding](), [api](), [api-testing](), [blog](), [code](), [coding-agents](), [developer](), [engineering](), [general](), [guide](), [idea](), [loops](), [model](), [post](), [postman-cli](), [tool](), [verify](), [work]() ### AI overview This article explains loop engineering as a way to improve AI coding agent reliability. Instead of relying on a single prompt, the system repeatedly generates code, runs it against a real API or other source of truth, verifies the result, and decides whether to stop or continue. The article distinguishes this outer verification loop from the inner ReAct tool-use cycle and presents a reproducible setup for allowing an agent to correct its own mistakes. ### Source excerpt Stop prompting your AI agent, start looping. A guide to loop engineering: wire a real API call in as the oracle so generated code stops guessing. The post Loop engineering: stop prompting, start looping appeared first on Postman Blog. ## This Week in Spring - September 8th, 2026 DevFeed: [This Week in Spring - September 8th, 2026]() Original publisher: [Read original article]() Author: joshlong Published: 2026-09-08T00:00:00Z Content type: article Language: en Sources: [Spring]() Topics: [Artificial Intelligence](), [Large Language Model](), [Electron](), [App](), [IntelliJ IDEA]() Tags: [ai](), [applications](), [article](), [batch](), [boot](), [cloud](), [event-driven](), [idea](), [intellij](), [intellij-idea](), [java](), [linux](), [llm](), [llms](), [microservices](), [oauth](), [reactive](), [serverless](), [spring](), [spring-ai](), [spring-boot](), [video](), [web-applications](), [windows]() ### AI overview This weekly Spring roundup highlights Spring AI content about running LLMs in the JVM and locally, building a Spring AI starter for agents.md, and improving tool use. It also covers Spring Boot and JavaFX desktop applications, native images, Spring Security OAuth clients, secure application images, external configuration, Spring Cloud AWS, and a Spring Boot Analyzer. ### Source excerpt Bonjour a tout le monde! Welcome to another rip-roarin' installment of This Week in Spring! It's a fabulous and fun day here in Paris, France, as I wait to board the train to Amsterdam for the IntelliJ IDEA conference! It's going to be amazing. We've got another incredible week's roundup to dive into, so let's do it! I feel like some of the best content over the past several months in this weekly roundup has been Craig Walls' Spring AI Recipes section. Fantastic stuff! This latest one looks at running an LLM in-JVM This is a nice article on using vertical slices in Spring Boot on Solodev.sk, by Dominik. Well done! Another amazing installment from Craig Walls, this one looking at running against local LLMs My friend and colleague DaShaun Carter talks about his Spring AI starter for agents.md Craig also has this lovely post on efficient tool use in Spring AI Last week, I did two videos on using Spring Boot, JavaFX, GraalVM native images, and Spring Security (and PKCE) to build native, lightning-fast, dynamic, efficient, reusable desktop applications that run well on Mac, Windows, and Linux, and look amazing, while taking small fractions of the RAM of a similar Electron-based application. Here's the first one, showing how to use Spring Boot and JavaFX together, so that you get the component model, event dispatch subsystem, internationalization, lifecycle management, and, of course, the entire and very rich ecosystem of Spring components and can use them to manage JavaFX components, too. We also look at native image compilation. Here's the second video, which looks at using Spring Security's OAuth client in the context of a desktop application, which can not, by definition, hold a client secret. In last week's installment of A Bootiful Podcast, I was delighted to chat with BellSoft's Catherine Edelveis about trusted and secure images for your Spring Boot applications This is a nice post on managing external configurations with Spring Cloud Config A nice recap of some of ## Java Weekly, Issue 659 DevFeed: [Java Weekly, Issue 659]() Original publisher: [Read original article]() Author: baeldung Published: 2026-08-15T10:23:09Z Content type: article Language: en Sources: [Baeldung]() Topics: [Programming](), [intellij-platform](), [Model Context Protocol](), [elasticsearch]() Tags: [elasticsearch](), [github](), [gradle](), [idea](), [java](), [mcp](), [netflix](), [no-ads](), [no-after-post](), [no-before-post](), [no-optins](), [programming](), [releases](), [security](), [weekly-review](), [weekly-review-no-ads-no-after-post-no-before-post-no-optins]() ### AI overview Java Weekly, Issue 659 is a roundup of Java ecosystem reading, including MCP server evolution, Project Valhalla, JVM security, DuckDB, HTTP extension design, AI features in IntelliJ IDEA, webinars, and software releases. ### Source excerpt Equality in Java is evolving. The post Java Weekly, Issue 659 first appeared on Baeldung. ## Brainstorming with ChatGPT DevFeed: [Brainstorming with ChatGPT]() Original publisher: [Read original article]() Published: 2026-04-10T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [ChatGPT](), [Frameworks]() Tags: [chatgpt](), [how-to](), [idea](), [learn](), [openai-academy](), [themes](), [work]() ### AI overview This article explains how to use ChatGPT as a structured thought partner for brainstorming. It covers generating options, organizing ideas into themes, pressure-testing plans, applying constraints, and moving from broad exploration to evaluation and an actionable plan. ### Source excerpt Learn how to use ChatGPT to brainstorm ideas, organize thinking, and turn rough concepts into structured, actionable plans. ## New Blog Post: Some Silly Z3 Scripts I Wrote DevFeed: [New Blog Post: Some Silly Z3 Scripts I Wrote]() Original publisher: [Read original article]() Author: Hillel Wayne Published: 2026-02-23T16:49:10Z Content type: article Language: en Sources: [Newsletter feed for Hillel Wayne's Newsletter]() Topics: [Code](), [Math and Logic](), [Script]() Tags: [blog-post](), [code](), [idea]() ### AI overview The author announces a new blog post containing Z3 scripts and discusses its mathematical examples, including total operations, arrays, quantifiers, and an unsuccessful attempt to encode Goldbach's conjecture as an SMT problem. ### Source excerpt Now that I'm not spending all my time on Logic for Programmers, I have time to update my website again! So here's the first blog post in five months: Some Silly Z3 Scripts I Wrote. Normally I'd also put a link to the Patreon notes but I've decided I don't like publishing gated content and am going to wind that whole thing down. So some quick notes about this post: Part of the point is admittedly to hype up the eventual release of LfP. I want to start marketing the book, but don't want the marketing material to be devoid of interest, so tangentially-related-but-independent blog posts are a good place to start. The post discusses the concept of "chaff", the enormous quantity of material (both code samples and prose) that didn't make it into the book. The book is about 50,000 words... and considerably shorter than the total volume of chaff! I don't think most of it can be turned into useful public posts, but I'm not entirely opposed to the idea. Maybe some of the old chapters could be made into something? Coming up with a conditioned mathematical property to prove was a struggle. I had two candidates: a == b * c => a / b == c, which would have required a long tangent on how division must be total in Z3, and a != 0 => some b: b * a == 1, which would have required introducing a quantifier (SMT is real weird about quantifiers). Division by zero has already caused me enough grief so I went with the latter. This did mean I had to reintroduce "operations must be total" when talking about arrays. I have no idea why the array example returns 2 for the max profit and not 99999999. I'm guessing there's some short circuiting logic in the optimizer when the problem is ill-defined? One example I could not get working, which is unfortunate, was a demonstration of how SMT solvers are undecidable via encoding Goldbach's conjecture as an SMT problem. Anything with multiple nested quantifiers is a pain. ## How I'm Using Agents for Development - January 2026 DevFeed: [How I'm Using Agents for Development - January 2026]() Original publisher: [Read original article]() Author: Sam Edwards Published: 2026-01-07T16:23:40Z Content type: opinion Language: en Sources: [Handstand Sam]() Topics: [Development](), [Claude](), [IntelliJ IDEA](), [ide](), [context window](), [Compose](), [GUI](), [YAML](), [Test automation]() Tags: [agents](), [claude](), [code](), [compose](), [context-window](), [development](), [gui](), [ide](), [idea](), [intellij](), [intellij-idea](), [junit](), [review](), [test-automation](), [updates](), [yaml]() ### AI overview A developer describes using agents with IntelliJ IDEA, Firebender, and Claude Sonnet 4.5 across Trailblaze projects. The article explains a Research, Plan, Implement workflow, including incremental commits, progress handoffs when the context window fills, refactoring, UI test automation, and building a Compose-based YAML editor. ### Source excerpt I'm currently sitting here with Intellij IDEA IDE open with 3 workspaces (different clones of the Trailblaze project). In each one of them I'm using Firebender with the Claude Sonnet 4.5 model. As I'm writing this I just toggled back over to IDE and made sure all my agents are still running. I've been hesitant [...] ## Announcing OpenAI Grove Cohort 2 DevFeed: [Announcing OpenAI Grove Cohort 2]() Original publisher: [Read original article]() Published: 2026-01-02T10:00:00Z Content type: news Language: en Sources: [OpenAI News]() Topics: [OpenAI](), [Artificial Intelligence](), [API]() Tags: [ai](), [api](), [applications](), [building](), [community](), [company](), [idea](), [models](), [openai](), [tools]() ### AI overview OpenAI Grove Cohort 2 is a five-week program for individuals at the beginning of their company-building journey, including those who are still exploring ideas. Participants receive mentorship from OpenAI technical leaders and researchers, workshops, office hours, community support, access to OpenAI tools and models before general availability, and resources intended to accelerate their progress. The cohort is expected to include approximately fifteen participants. ### Source excerpt Applications are now open for OpenAI Grove Cohort 2, a 5-week founder program designed for individuals at any stage, from pre-idea to product. Participants receive $50K in API credits, early access to AI tools, and hands-on mentorship from the OpenAI team. ## Building a better First Draft for designers DevFeed: [Building a better First Draft for designers]() Original publisher: [Read original article]() Author: Noah Levin Published: 2024-09-24T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [FIRST](), [Figma](), [Artificial Intelligence](), [AI Models](), [OpenAI](), [amazon]() Tags: [accelerate](), [ai](), [ai-models](), [amazon](), [analysis](), [building](), [components](), [design](), [design-systems](), [feature](), [figma](), [generate](), [gpt](), [idea](), [launch](), [libraries](), [library](), [models](), [production](), [testing]() ### AI overview Figma is reintroducing its Make Designs feature under the name First Draft in limited beta. First Draft uses off-the-shelf AI models, including OpenAI's GPT-4 and Amazon Titan, together with design-system context and user prompts to select, arrange, and customize components into an initial design. The update adds a choice of four libraries after Figma disabled the original feature because its generated mocks too closely resembled existing apps. ### Source excerpt We're reintroducing our Make Designs feature with some key improvements, including a new name--First Draft--to better reflect our goal of giving designers another way to get started. ## Immutable URLs can simplify deployments DevFeed: [Immutable URLs can simplify deployments]() Original publisher: [Read original article]() Published: 2024-03-14T00:00:00Z Content type: article Language: en Sources: [Garnix Blog]() Topics: [hash]() Tags: [deployments](), [hash](), [idea](), [simplify]() ### AI overview The article explores making URLs immutable and suggests that this approach could improve and simplify deployments. ### Source excerpt What happens if we make URLs immutable? A somewhat unusual idea that can substantially improve and simplify deployments. ## Getting Started with Compose for Web DevFeed: [Getting Started with Compose for Web]() Original publisher: [Read original article]() Author: Gustavo Fão Valvassori Published: 2023-12-01T21:34:32Z Content type: tutorial Language: en Sources: [Touchlab]() Topics: [compose-for-web](), [Compose](), [Kotlin](), [multiplatform](), [IntelliJ IDEA](), [Gradle](), [HTML](), [Canvas]() Tags: [canvas](), [coding](), [community](), [compose](), [compose-for-web](), [development](), [engineering](), [getting-started](), [gradle](), [how-to](), [html](), [idea](), [inclusive](), [introduction](), [kotlin](), [multiplatform](), [software](), [ui](), [webdev]() ### AI overview A beginner tutorial on building web applications with Compose for Web and Kotlin. It introduces the JS + HTML and Wasm + Canvas runtimes, explains their components and experimental status, and outlines project setup using IntelliJ IDEA, Kotlin Multiplatform, Compose, JavaScript source sets, dependencies, and an HTML entry page. ### Source excerpt If you are a Kotlin developer like me, you are probably very excited about Jetpack Compose. It's a modern UI toolkit for developing apps, and with the great work from JetBrains, it's becoming a really interesting solution. As a mobile developer, I've never gone in the weeds on how to properly develop sites with HTML, CSS, and JS. My closest experience was with React Native back in 2018. But now, with Compose, using a Kotlin DSL, I feel comfortable on doing this. Compose Runtime and Component Library Before creating a project and start coding, it's important to have a small introduction to Compose runtimes. As of now, Compose has two different runtimes on the web: JS + HTML Wasm + Canvas They both use the Compose Runtime underneath, but they use different components. Long story short: The HTML version will have HTML composable components (like H1, P, Span, Input, Div, etc.) The Canvas version will have similar components as the Android version as it uses SKIA to draw on the Canvas. Both of them are experimental. Note that choosing how you want to build your application will impact on possible code-sharing with native if this is what you want. For this series of posts, I'll use the HTML version and I will be able to explore more the web components. Creating the project Now that we know what runtime/components we want to use, we need to create a project. My first idea was to use the KMP project wizard, but unfortunately, the Web target is not available as an option for now. As a workaround, I had to create a new clean project using IntelliJ IDEA and add the dependencies manually. Using a clean template you will reduce the amount of code that needs to be removed/updated to make the project work. But if you prefer to use any other IDE/Template, feel free to do so and share your experience with us later :) With that, the configuration is completed with a few extra lines: Change the Kotlin plugin from JVM to MULTIPLATFORM Add the Compose plugin Declare JS source-sets Impor ## Conditional API Responses For JavaScript vs. HTML Forms DevFeed: [Conditional API Responses For JavaScript vs. HTML Forms]() Original publisher: [Read original article]() Author: Austin Published: 2023-01-03T15:31:38Z Content type: tutorial Language: en Sources: [Back End - Austin Gil]() Topics: [Nuxt.js](), [API](), [Back end](), [HTTP](), [JavaScript](), [Forms]() Tags: [api](), [back-end](), [backend](), [building](), [coding](), [development](), [edge-compute](), [how-to](), [html](), [http](), [idea](), [javascript](), [js](), [programming](), [software](), [web-development]() ### AI overview A tutorial on detecting whether an HTTP request came from an HTML form or JavaScript in a Nuxt.js backend API. It explains returning redirects for form submissions and JSON for JavaScript requests, supporting progressive enhancement when JavaScript fails. ### Source excerpt Learn how to build backend APIs that support progressive enhancement by detecting if a request was submitted with HTML forms or JavaScript. ## Investigation of a Gradle and IntelliJ IDEA Memory Leak DevFeed: [Investigation of a Gradle and IntelliJ IDEA Memory Leak]() Original publisher: [Read original article]() Author: Pierre-Yves Ricau Published: 2022-10-12T17:26:46Z Content type: tutorial Language: en Sources: [Py's blog]() Topics: [Gradle](), [Memory Leaks](), [IntelliJ IDEA](), [Java](), [Graphs]() Tags: [garbage-collection](), [gc](), [gradle](), [graph](), [idea](), [intellij](), [java](), [leak](), [memory](), [memory-leak](), [performance]() ### AI overview A team investigation examines a Gradle process memory leak during project import in IntelliJ IDEA. The article describes heap analysis using dominator trees, pending finalization, and paths from GC roots. ### Source excerpt 👋 Hi, this is P.Y., I work as an Android Engineer at Block. This article shares a team investigation by Tony Robalik, Pablo Baxter, Roger Hu and myself into a recent Gradle / IntelliJ memory leak. O ## Good ideas stick DevFeed: [Good ideas stick]() Original publisher: [Read original article]() Author: Amber Bravo Published: 2022-04-21T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma]() Tags: [feature](), [figma](), [idea](), [prototyping]() ### AI overview The article describes Figma's 24-hour April Fun Day feature that let Figma and FigJam users decorate files with digital washi tape. It explains the feature's inspiration from a community suggestion and connects the digital experience to the history, functionality, and creative uses of physical washi tape. ### Source excerpt A brief history of washi tape, and why we think it's the perfect experience to digitize. ## Making Kotlin Constant-Expression Analysis Useful in IntelliJ IDEA DevFeed: [Making Kotlin Constant-Expression Analysis Useful in IntelliJ IDEA]() Original publisher: [Read original article]() Author: tagir\_valeev (JetBrains) Published: 2021-11-02T10:18:04Z Content type: article Language: ru Sources: [JetBrains RU]() Topics: [IntelliJ IDEA](), [Kotlin](), [Java]() Tags: [idea](), [intellij](), [intellij-idea](), [java](), [kotlin](), [tag-9ec75300b635](), [tag-c5a1967375ea]() ### AI overview The article discusses the development of constant-expression inspection for Kotlin in IntelliJ IDEA 2021.3. The inspection reuses the Java analyzer's data-flow analysis to identify expressions that always evaluate to the same value, while reducing warnings that are technically correct but unhelpful in normal code. ### Source excerpt Одна из проблем статического анализа в том, что его легко сделать умнее, чем надо. В результате он начинает выдавать предупреждения в таком коде, который человеку кажется нормальным. И так и хочется сказать анализатору "Отстань, зануда! Сильно умный что ли?" Я в очередной раз почувствовал вкус всего этого, когда работал над поиском константных выражений для Kotlin. Ранее такой анализ был для Java, но для Kotlin он впервые появится только в следующей версии IntelliJ IDEA 2021.3. Инспекция базируется на анализе потока данных и находит в коде выражения, которые всегда равны одному и тому же. Изначально такая инспекция на Java сообщала только о логических выражениях, которые всегда равны true или false. Потом мы осторожно расширили её, и она стала сообщать ещё и о выражениях, которые всегда равны null или 0. Было решено проделать тот же путь для Kotlin. Читать дальше -> ## Test as Text в IntelliJ IDEA DevFeed: [Test as Text в IntelliJ IDEA]() Original publisher: [Read original article]() Author: Razmik (JetBrains) Published: 2021-08-31T14:53:37Z Content type: tutorial Language: ru Sources: [JetBrains RU]() Topics: [IntelliJ IDEA](), [Agile](), [test](), [Markdown]() Tags: [agile](), [idea](), [intellij](), [intellij-idea](), [markdown](), [tag-34905ba5ce2c](), [tag-532d1762d470](), [tag-7bc388df28ed](), [tag-e34f6dec12c4](), [test]() ### AI overview This tutorial explains how Agile teams can manage test cases in IntelliJ IDEA using a Test Management plugin and a Test as Text or Test as Code workflow. Test cases are stored as Markdown-based .t.md files in version control alongside project code, enabling synchronization with automated tests, change history review, and collaborative development. ### Source excerpt Test as Text в IntelliJ IDEA - коротко о том, как мы видим управление чеклистами и тестовыми сценариями в agile командах. Читать далее ## Что в коробке? Обзор свежего релиза Toolbox App 1.21 DevFeed: [Что в коробке? Обзор свежего релиза Toolbox App 1.21]() Original publisher: [Read original article]() Author: dievsky (JetBrains) Published: 2021-07-15T09:12:02Z Content type: release Language: ru Sources: [JetBrains RU]() Topics: [App](), [ide](), [IntelliJ IDEA](), [PyCharm](), [rider](), [webstorm](), [Android Studio](), [Google]() Tags: [android-studio](), [app](), [eap](), [google](), [ide](), [idea](), [install](), [intellij](), [intellij-idea](), [jetbrains](), [mac](), [pycharm](), [rider](), [toolbox](), [toolbox-app](), [update](), [webstorm]() ### AI overview This Russian-language release overview explains JetBrains Toolbox App, which manages JetBrains IDEs and Android Studio. It describes installing, updating, rolling back, and maintaining multiple tool versions, and highlights name-based filtering in version 1.21. ### Source excerpt Если вы еще не знаете, что такое Toolbox App, то этот пост для вас, потому что мы сейчас расскажем. А если вы -- один из 800 тысяч наших пользователей, то этот пост тем более для вас, потому что в новой версии много интересного, а еще она быстрее работает и меньше кушает. Что в коробке? ## Language Injections in Android Studio / IntelliJ IDEA 💉 DevFeed: [Language Injections in Android Studio / IntelliJ IDEA 💉]() Original publisher: [Read original article]() Author: Rebecca Franks Published: 2021-01-20T09:19:12Z Content type: tutorial Language: en Sources: [Rebecca Franks - @riggaroo]() Topics: [Android Studio](), [Syntax Highlighting](), [ide](), [IntelliJ IDEA](), [SQL](), [glsl](), [Kotlin]() Tags: [android](), [android-studio](), [glsl](), [ide](), [idea](), [intellij-idea](), [kotlin](), [language-injection](), [opengl](), [sql](), [studio](), [syntax-highlighting]() ### AI overview This tutorial explains how language injection in Android Studio and IntelliJ IDEA enables embedded code such as SQL or GLSL to receive syntax highlighting, validation, suggestions, and separate-editor support. It also describes using annotations and the GLSL Support Plugin for Kotlin string literals. ### Source excerpt Android Studio is a powerful IDE with a multitude of features that I'll probably never discover. However, when I do discover a feature of the IDE that I've been dreaming about, I get irrationally excited about it (and often times write a blog post such as this one). One feature that really piqued my interest [...] The post Language Injections in Android Studio / IntelliJ IDEA 💉 appeared first on Rebecca Franks - @riggaroo. ## TAYFA Built a No-Code Website Builder in Seven Days DevFeed: [TAYFA Built a No-Code Website Builder in Seven Days]() Original publisher: [Read original article]() Published: 2020-12-02T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [No-code]() Tags: [accelerate](), [customer](), [growth](), [idea](), [no-code](), [work]() ### AI overview A case study about Tayfa building a no-code website builder in seven days, progressing from an idea to a paying customer in less than 30 days, with Supabase helping companies accelerate growth and streamline work. ### Source excerpt See how Tayfa went from idea to paying customer in less than 30 days. ## Почему JetBrains не напишет легковесную IDE DevFeed: [Почему JetBrains не напишет легковесную IDE]() Original publisher: [Read original article]() Published: 2020-05-23T15:16:18Z Content type: opinion Language: ru Sources: [Tonsky Стой под стрелой]() Topics: [ide](), [jetbrains](), [Sublime Text](), [Android Studio](), [Vim](), [vs-code](), [Java](), [Syntax Highlighting]() Tags: [android-studio](), [ide](), [idea](), [java](), [jetbrains](), [livejournal](), [syntax-highlighting](), [tag-5e1c061eda96](), [tag-c40b78a8c8a6](), [tag-d16a2c26554f](), [tag-e3028c5e0ab2](), [vim](), [vs-code]() ### AI overview The author argues that a lightweight IDE cannot exist because IDE features such as navigation, refactoring, debugging, and run configurations must understand the entire project. Build systems, frameworks, and integrations make that project-wide understanding inherently complex. The discussion draws on the author's experience with JetBrains IDEs, Java tooling, and Android Studio, while noting a personal preference for lightweight editors. ### Source excerpt Еще в 2011 я публично отказался от ИДЕ и так с тех пор и живу: TextMate, Vim, Sublime, LightTable, VS Code, снова Sublime. И вот год назад я устроился в JetBrains. Нет, мое отношение не поменялось: я все еще считаю, что в ИДЕ программировать не надо. У меня на столе усердно копится папочка Annoying IDE(A), а Джаву и Котлин я все так же пишу в Sublime Text. Поменялось вот что. Раньше я думал, что IDE это такие цитадели зла, что их специально делают сложными и неудобными, ну или не специально, а просто сил не хватает сделать аккуратными и легковесными. Могли бы, да не смогли. Сейчас, посмотрев на Idea, и на Java-тулинг, и на Android Studio, я понимаю, что это принципиальное противоречие: в самой идее IDE заложена сложность, кривость и неудобство. Легковесная IDE не может существовать, потому что мир вокруг сложен. Давайте подумаем, что ИДЕ нам дает. Syntax highlighting, Go to definition, Find usages, Show hierarchy, Structural rename, и допустим Run configurations, то есть возможность все это как-то запускать (в том числе и под дебаггером). Все это сами по себе вполне легковесные функции, так-то. Легко представить их чисто интерфейсно в, скажем, в Vim или VS Code, ничего принципиально сложного или развесистого они в себе не несут. Так в чем же проблема? Проблема в том, что чтобы они работали, нужно вот прям все-все знать о проекте в целом. Язык программирования, допустим, маленький и фиксированный, с ним просто. Поэтому Syntax highlighting, для которого дальше одного файла смотреть не нужно, есть в самых легковесных редакторах. А вот как проект настроен и как билдится, вот тут-то адок и начинается. Миллионы билд-систем, некоторые из которых императивные и тюринг-полные, два миллионна фреймворков, миллион в квадрате интеграций, все это кривое, косое, уникальное, как блядь снежинка, общается друг с другом не пойми как, пишет файлы, теряет файлы, не видит очевидного, лезет куда не нужно, зависит друг от друга, ломается и занимается при этом довольно тривиальными вещами, ## Java 9 Flow API: switching threads DevFeed: [Java 9 Flow API: switching threads]() Original publisher: [Read original article]() Author: David Karnok (noreply@blogger.com) Published: 2017-09-21T10:49:00Z Content type: tutorial Language: en Sources: [Akarnokd - Advanced RxJava]() Topics: [Java](), [Java 9](), [API](), [reactive](), [Concurrency](), [Concurrent Programming]() Tags: [asynchronous](), [executor](), [executorservice](), [flow](), [flow-api](), [idea](), [intellij](), [java](), [java-9](), [jvm](), [main-thread](), [observeon](), [publisher](), [thread](), [threading](), [threads]() ### AI overview This tutorial explains how to switch execution between threads in reactive flows using Java 9's Flow API. It compares embedding thread switching in operators with a separate observeOn stage, then outlines an observeOn implementation based on Executor, asynchronous boundaries, bounded queues, and request management. ### Source excerpt Introduction Ensuring certain computations happen on the right thread, usually off the main thread, is a very common development task when dealing with reactive flows. When building up tools for Java 9's Flow API, one can decide to add this thread-switching support to each operator directly - see the range() operator from the start of the series -, or have a standalone stage for this purpose. This is a tradeoff. Inlining thread switching avoids bogging down the source thread like the thread-stealing behavior of most of the queue-drain approach presented so far. A separate operator allows better composition and may even allow working with exotic asynchrony-providing components. The observeOn operator In Java, threading support is provided via the Executor, ExecutorService and ScheduledExecutorService-based API. Executor is is the most basic one of them which only provides a single execute(Runnable) method. This allows creating an Executor from a lambda: Executor trampoline = Runnable::run; Executor swing = SwingUtilities::invokeLater; Executor pool = ForkJoinPool.commonPool(); As the least common denominator, we'll use Executor in defining our observeOn operator: public static Flow.Publisher observeOn( Flow.Publisher source, Executor exec, int prefetch) { return new ObserveOnPublisher<>(source, exec, prefetch); } Crossing an asynchronous boundary requires the temporary storage of an event until the other side can pick it up. The queue-drain approach can provide a nice bounded queue we can size with prefetch. In addition, the so-called stable-prefetch request management (shown in the mapFilter operator before) allows minimizing the overhead of requesting more items. First, let's see the skeleton of the operator's main Flow.Subscriber implementation: static final class ObserveOnSubscriber implements Flow.Subscriber, Flow.Subscription, Runnable { final Flow.Subscriber downstream; final Executor exec; final int prefetch; final Queue queue; F ## Droidcon App! - Kevin Galligan DevFeed: [Droidcon App! - Kevin Galligan]() Original publisher: [Read original article]() Published: 2017-07-14T16:00:38Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Android](), [App](), [Development](), [Kotlin](), [RxJava](), [Mobile]() Tags: [android](), [architecture](), [built-by-touchlab](), [community](), [database](), [idea](), [kotlin](), [libraries](), [mobile](), [mobile-dev](), [networking](), [rxjava](), [thoughts]() ### AI overview The article describes a planned modernization of the Droidcon Android app, including migration from older Kotlin, libraries, architectures, and Retrofit v1. The authors discuss moving to Room or SQLDelight, using RxJava 2 for non-persisted tasks, retaining a persisted queue for offline support, and adopting new architecture components while exploring compatibility with iOS through Doppl. ### Source excerpt We're gearing up to have our 4th year of Droidcon NYC! Keep an eye on the Droidcon example app. We'll be modifying a few things over the next few weeks. [Next page]()