# editor Published articles for editor. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Inertia DevTools Now Available for Firefox DevFeed: [Inertia DevTools Now Available for Firefox]() Original publisher: [Read original article]() Author: Paul Redmond Published: 2026-09-17T02:28:55Z Content type: release Language: en Sources: [Laravel]() Topics: [Firefox](), [Browser Extension](), [developer tooling](), [Chrome](), [vs-code](), [phpstorm]() Tags: [chrome-extension](), [devtools](), [editor](), [extension](), [features](), [firefox](), [news](), [panel](), [phpstorm](), [vs-code]() ### AI overview Inertia DevTools is now available as an official Firefox extension with feature parity with the Chrome extension. It records Inertia visits and exposes props, request and response details, routes, controller actions, and page state in a Firefox DevTools panel. Sensitive fields are redacted, and recorded data remains on the local machine. ### Source excerpt Inertia DevTools, the panel for inspecting Inertia.js visits and props, is now on Firefox with the same features as the Chrome extension. The post Inertia DevTools Now Available for Firefox appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ## New Bug-Fix Releases Are Available for MPS Versions 2026.1.1, 2025.3.2, 2025.2.4, and 2025.1.4 DevFeed: [New Bug-Fix Releases Are Available for MPS Versions 2026.1.1, 2025.3.2, 2025.2.4, and 2025.1.4]() Original publisher: [Read original article]() Author: Vaclav Pech Published: 2026-09-16T20:06:31Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [JetBrains MPS](), [releases](), [version](), [jetbrains]() Tags: [2](), [2025](), [2026](), [3](), [agent](), [agents](), [bug](), [changes](), [create](), [development](), [diagnostics](), [editor](), [improvements](), [major](), [manipulate](), [mps](), [practical](), [release](), [releases](), [updates](), [version]() ### AI overview JetBrains has released bug-fix updates for MPS versions 2026.1.1, 2025.3.2, 2025.2.4, and 2025.1.4. The MPS 2026.1.1 update includes improvements to the Projectional Agent Toolkit, editor context, diagnostics, agent guidance, and test execution. ### Source excerpt We've released updates for multiple major MPS versions that fix several issues. DOWNLOAD MPS 2026.1.1 Check out all the updates in each particular version below: MPS 2026.1.1 The Projectional Agent Toolkit receives several practical improvements that allow agents to: See and invoke intentions and quick-fixes on individual nodes. Manipulate NodeAttributes, PropertyAttributes, and others. Create copies [...] ## Vim: por qué merece la pena frente a nano DevFeed: [Vim: por qué merece la pena frente a nano]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-01T13:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Vim](), [POSIX](), [Unix]() Tags: [alpine](), [distro](), [editor](), [posix](), [unix](), [vim]() ### AI overview A practical Spanish tutorial explaining why Vim is worth learning instead of nano. It covers how to exit, save, undo, and redo, then argues that Vim is widely available on Unix systems because vi is required by POSIX. It also discusses BusyBox, Alpine, and Vim's modes. ### Source excerpt Vim parece complicado pero no lo es: aprende a salir, moverte y editar con lo mínimo imprescindible, sin miedo y sin memorizar todo de golpe. ## An Update on the FreeBSD Journal: New Editor, New Format DevFeed: [An Update on the FreeBSD Journal: New Editor, New Format]() Original publisher: [Read original article]() Author: Florine Kamdem Published: 2026-07-29T20:16:39Z Content type: news Language: en Sources: [FreeBSD Foundation]() Topics: [Computing](), [browser](), [Website](), [pdf]() Tags: [blog](), [browser](), [editor](), [format](), [freebsd](), [pdf](), [software](), [update](), [website]() ### AI overview The FreeBSD Journal has appointed Matt Slaybaugh as its new editor and is moving to a browser-based-only format without downloadable PDFs. The journal will remain quarterly, free, and guided by its editorial and advisory boards. ### Source excerpt We have a couple of updates to share about the FreeBSD Journal. A New Editor Please join us in welcoming Matt Slaybaugh as the Journal's new editor. Matt brings years of editorial and content management experience, including his ongoing work with the Association for Computing Machinery (ACM), and he's already hard at work on upcoming [...] The post An Update on the FreeBSD Journal: New Editor, New Format first appeared on FreeBSD Foundation. ## DeveloperHub Introduces a New Editor for More Reliable Documentation Authoring DevFeed: [DeveloperHub Introduces a New Editor for More Reliable Documentation Authoring]() Original publisher: [Read original article]() Author: Zaid Daba'een Published: 2026-06-30T09:47:09Z Content type: release Language: en Sources: [DeveloperHub.io]() Topics: [Documentation](), [Tool](), [formatting](), [render]() Tags: [commands](), [docs](), [documentation](), [editor](), [engineering](), [features](), [google](), [image](), [inside](), [model]() ### AI overview DeveloperHub has rebuilt its editor around a single document model. The new editor is designed to preserve saved formatting, improve undo and redo, handle pasted content more faithfully, and provide tools such as slash commands, link controls, an image library, variable and glossary pickers, blocks within lists, and keyboard-focused editing. ### Source excerpt We rebuilt the DeveloperHub editor from the ground up. Here is what is new, and why it makes writing and maintaining your documentation noticeably better. ## 22 UX improvements to the web editor DevFeed: [22 UX improvements to the web editor]() Original publisher: [Read original article]() Author: Dmytro Tovstokoryi Published: 2026-05-04T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [User experience (UX)](), [Web](), [Documentation]() Tags: [docs](), [editor](), [ux](), [ux-improvements](), [web]() ### AI overview Mintlify describes 22 UX improvements to its web editor, including visual diffs, PR title and description generation, improved drag-and-drop editing, grouped block operations, block conversion, a redesigned slash menu, and inline emoji suggestions. ### Source excerpt A round-up of the UX improvements coming to Mintlify's web editor. ## Introducing the collaborative editor built for teams and agents DevFeed: [Introducing the collaborative editor built for teams and agents]() Original publisher: [Read original article]() Author: Hahnbee Lee Published: 2026-04-29T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [Git](), [GitHub](), [developer tooling]() Tags: [announcements](), [browser](), [collaboration](), [editor](), [git](), [teams](), [workflow]() ### AI overview Mintlify introduces a collaborative editor that combines browser-based WYSIWYG editing, live collaboration, and git synchronization. It supports contributors beyond engineering while preserving a git-native workflow for developer users. ### Source excerpt A new editing experience that brings live collaboration, git sync, and WYSIWYG editing into one workflow for your whole team. ## Comparing Cypress cy.prompt, Cypress Studio, and Hand-Coded Tests DevFeed: [Comparing Cypress cy.prompt, Cypress Studio, and Hand-Coded Tests]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-04-28T04:00:00Z Content type: comparison Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Testing](), [coding](), [Visual Studio Code]() Tags: [ai](), [coding](), [command](), [copilot](), [cypress](), [editor](), [next](), [process](), [prompt](), [selectors](), [test](), [testing](), [vs]() ### AI overview The article compares three ways to create a Cypress login test: hand-coding in VSCode, using cy.prompt, and recording actions with Cypress Studio. In the author's test, hand-coding worked reliably, while cy.prompt produced failures and code that needed manual cleanup, and Cypress Studio inserted unwanted assertions and missed recommended selectors and negative assertions. ### Source excerpt Cypress-the-company is putting a lot of effort behind its cy.prompt command (which I recreated ## 5 things you didn't know you could do in the Mintlify web editor DevFeed: [5 things you didn't know you could do in the Mintlify web editor]() Original publisher: [Read original article]() Author: Peri Langlois Published: 2026-04-13T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [Visual Studio Code](), [MDX](), [Artificial Intelligence](), [browser](), [Git](), [Code]() Tags: [ai](), [best-practices](), [browser](), [code](), [docs](), [editor](), [git](), [how-to](), [markdown](), [web]() ### AI overview This article presents five Mintlify web editor features that help teams create, edit, review, and reorganize documentation in the browser without relying on an IDE, Git commands, or deployment pipelines. It highlights suggesting mode with comments, navigation restructuring, inline AI, live preview, and visual/Markdown switching. ### Source excerpt The Mintlify web editor can do more than you think, here are five features that make it easy for your whole team to contribute to docs. ## The Data Structures Behind Text Editors: Gap Buffers, Piece Tables, Ropes, and CRDTs DevFeed: [The Data Structures Behind Text Editors: Gap Buffers, Piece Tables, Ropes, and CRDTs]() Original publisher: [Read original article]() Published: 2026-04-05T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Data structures](), [distributed-systems]() Tags: [data-structures](), [delete](), [distributed-systems](), [editor](), [file](), [insert](), [memory](), [search](), [syntax-highlighting]() ### AI overview This tutorial explains how text editors represent document buffers in memory. It compares gap buffers, piece tables, ropes, and CRDTs, focusing on the trade-offs among insertion, deletion, reading, cursor movement, memory efficiency, latency, and multi-user concurrency. ### Source excerpt Open a text editor, type a character, and it appears on screen. That single keystroke triggers a surprisingly deep question: how does the editor represent your document in memory so that insertions, deletions, and cursor movements all feel instant, even on a file with millions of lines... ## Workflow-as-code: orchestration in pure code DevFeed: [Workflow-as-code: orchestration in pure code]() Original publisher: [Read original article]() Author: Ruben Fiszel Published: 2026-04-03T00:00:00Z Content type: release Language: en Sources: [Windmill Blog]() Topics: [Orchestration](), [Code](), [Python](), [TypeScript](), [Concurrency](), [Error Handling]() Tags: [architecture](), [code](), [concurrency](), [editor](), [error-handling](), [execution](), [launch-week](), [orchestration](), [parallelism](), [python](), [releases](), [typescript](), [version-control](), [workflow](), [workflows]() ### AI overview Windmill introduces workflow-as-code, allowing complex workflows to be defined in TypeScript or Python. The system uses checkpointing and replay, runs tasks as separate jobs, supports parallelism and fault tolerance, and releases workers while workflows wait. ### Source excerpt Introducing workflow-as-code: define complex workflows in TypeScript or Python with checkpointing, parallelism, and fault tolerance built in. ## A Claude Skill to Generate Professional App Store Screenshots ❤🔥 DevFeed: [A Claude Skill to Generate Professional App Store Screenshots ❤🔥]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2026-03-23T15:20:56Z Content type: opinion Language: en Sources: [Effective Android]() Topics: [Claude Code](), [App](), [Code]() Tags: [app](), [claude-code](), [editor](), [screenshots]() ### AI overview The author presents a Claude Code skill that generates production-ready screenshots for apps and deploys them to an online editor for iteration. The skill also works with other code agents that support skills. ### Source excerpt I built a Claude Code skill that generates production ready screenshots for your app and deploys them to a powerful online editor so you can iterate as much as you want. ## I love building apps. Designing App Store screenshots not that much 😅 DevFeed: [I love building apps. Designing App Store screenshots not that much 😅]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2026-01-22T18:30:52Z Content type: opinion Language: en Sources: [Effective Android]() Topics: [App](), [Development](), [Artificial Intelligence]() Tags: [ai](), [app](), [building-products](), [design](), [developers](), [drag-and-drop](), [editor](), [generation](), [subscriptions](), [templates]() ### AI overview A developer describes building a drag-and-drop product for creating polished App Store and Play Store screenshots. The product evolved from a personal tool into a public platform with templates, multiple screen ratios, AI-powered generation, automatic internationalization, subscriptions, and free templates. ### Source excerpt Most developers don't have a designer eye, and that's completely okay. ## Guía práctica de systemd en Linux DevFeed: [Guía práctica de systemd en Linux]() Original publisher: [Read original article]() Author: Alois Published: 2026-01-11T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [systemd](), [Linux](), [boot]() Tags: [boot](), [drop-in](), [editor](), [file](), [linux](), [service](), [systemd]() ### AI overview A practical guide to systemd on Linux covering unit types, socket activation, service state and startup configuration, masking, custom services, and drop-in overrides. ### Source excerpt Guía práctica de systemd: unidades service, timer y socket, targets de arranque, enable vs start, mask/unmask y overrides con systemctl edit. ## Haskell Debugger for GHC 9.14 DevFeed: [Haskell Debugger for GHC 9.14]() Original publisher: [Read original article]() Published: 2026-01-07T00:00:00Z Content type: tutorial Language: en Sources: [Romes' Musings]() Topics: [debugging](), [Haskell](), [Neovim](), [Visual Studio Code](), [Protocol (disambiguation)](), [GitHub Issues]() Tags: [bytecode](), [crashes](), [debugger](), [debugging](), [editor](), [haskell](), [issue](), [performance](), [protocol](), [vscode]() ### AI overview This article announces that the Haskell Debugger is ready for GHC 9.14 and explains how to install it and configure editors through the Debug Adapter Protocol. It covers VSCode and Neovim integration, project-based session configuration, robustness goals, current limitations, and planned callstack and multithreading support. ### Source excerpt This post was first published inline to the Haskell Discourse, where there was some discussion about the debugger: 1 The Haskell Debugger for GHC 9.14 The Haskell Debugger is ready to use with GHC-9.14! The installation, configuration, and talks can be found in the official website. The tl;dr first step is installing the debugger: $ ghc --version # MUST BE GHC 9.14 The Glorious Glasgow Haskell Compilation System, version 9.14.1 $ cabal install haskell-debugger \ --allow-newer=base,time,containers,ghc,ghc-bignum,template-haskell \ --enable-executable-dynamic # ON WINDOWS, DO NOT PASS --enable-executable-dynamic ... $ ~/.local/bin/hdb --version # VERIFY IT'S THE LATEST! Haskell Debugger, version 0.11.0.0 The second step is configuring your editor to use the debugger via the Debug Adapter Protocol (DAP). - For VSCode, install the haskell debugger extension. - For Neovim, install nvim-dap and configure it for haskell-debugger - For other editors, consult your DAP documentation and let others know how! Bug reports and discussions are welcome in the haskell-debugger issue tracker. My MuniHac 2025 talk also walks through the installation, usage, and design of the debugger. Do note much has been improved since the talk was given, and much more will still improve. 1.1 A little bit more info The debugger work is sponsored by Mercury. It's the project in which I've spent most of my full working days (for almost a full year now), with the invaluable help from my team at Well-Typed. The debugger is meant to work both on trivial files and on large and complex codebases1. It is a GHC application so all features are supported. Like HLS, it also uses hie-bios to automatically configure the session based on your cabal or stack project. Robustness is a main goal of the debugger. If anything doesn't work, or if you have performance issues, or something crashes, please don't hesitate to submit a bug. We've got a small but respectable testsuite, and have tested performance by debugging G ## Designing a Website with Experimental DOM Effects and AI-Created Tools DevFeed: [Designing a Website with Experimental DOM Effects and AI-Created Tools]() Original publisher: [Read original article]() Author: James Long Published: 2025-12-03T12:00:00Z Content type: opinion Language: en Sources: [James Long]() Topics: [Document Object Model (DOM)](), [Artificial Intelligence](), [Website](), [procedural flowers]() Tags: [ai](), [animation](), [design](), [editor](), [tools](), [website]() ### AI overview The author reflects on an experimental website redesign built around warped DOM elements, explaining that the visual concept became too distracting from the site's purpose of presenting readable content. They describe simplifying the design and using AI to create animation and drawing tools during the process. ### Source excerpt Over a week ago, I had a thought: "I'm gonna make my website cool." I really love visual exploration. But there's a problem: given no constraints, it's so easy to get wrapped up into a one idea and go too far down that path. Here's what happened: I found a cool trick to "warp" real DOM elements. I took this approach to the extreme and tried to build my whole site around it. Here was one early version: I still really like this. It feels like my personal messy desk that that world can see. But that's also a problem: it's too messy. The hardest part about design is executing it in a way that doesn't detract from the original need. It still needs to fulfill the original requirement. In this case, the requirement is I should be able to quickly write content for you to read. I spent almost a week working on this before realizing this approach just fundamentally detracted from the experience too much. Maybe a better designer could have figured out how to execute this better. For now, I ripped it out and implemented what you see in ONE HOUR. It's time to focus on content again. I left my in-progress work up so you can see it on this page. (I also wrote this up as a thread which has a few more details & videos) This is my favorite part of the design by far. I made the demo videos into little polaroid pictures. These are real videos that are playing! They animate in like a paper would, and there's a nice paper-like interaction on hover, and you can drag them around: (I wrote some notes when implementing this: https://jlongster.com/slicing-up-a-video) I learned a ton throughout this process. The biggest thing was I used AI to create design tools on the fly. For example, I create a full animation keyframe editor that let me create keyframes of the warped DOM nodes, and then a runtime player plays these keyframes to make the animation: I installed the perfect-freehand library and created a live animation drawing tool. You can press record, draw stuff on the screen, and stop reco ## ScreenshotWhale Generates App Store Screenshots with a Layer-Based Editor and Automatic Localization DevFeed: [ScreenshotWhale Generates App Store Screenshots with a Layer-Based Editor and Automatic Localization]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2025-09-16T16:36:22Z Content type: article Language: en Sources: [Effective Android]() Topics: [App](), [Artificial Intelligence](), [Vibe coding](), [Figma](), [Internationalization (i18n)](), [Cloud](), [User Experience]() Tags: [ai](), [android](), [app](), [app-store](), [building](), [cloud](), [code](), [coding](), [editor](), [export](), [figma](), [i18n](), [ios](), [languages](), [phones](), [templates]() ### AI overview The article introduces ScreenshotWhale, a cloud-based service for creating app store screenshots. It offers a Figma-style layer-based editor, templates, support for Android and iOS device formats, and automatic internationalization during export. The product is in its initial stages and is presented as seeking user feedback. ### Source excerpt Some words for the people who joined the newsletter these days. ## Launching ScreenshotWhale.com 🐋 DevFeed: [Launching ScreenshotWhale.com 🐋]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2025-09-13T15:03:52Z Content type: release Language: en Sources: [Effective Android]() Topics: [App](), [Android](), [iOS](), [Internationalization (i18n)](), [export](), [Cloud]() Tags: [android](), [app](), [cloud](), [editor](), [export](), [i18n](), [image](), [ios](), [layer](), [screenshots](), [templates]() ### AI overview ScreenshotWhale has launched as a cloud-based tool for creating app screenshots. It includes an online editor, templates, multilingual export, support for iOS and Android form factors, a mirror feature, app store layout settings, and layered editing. ### Source excerpt The wait is over, screenshotwhale is live today 🎉 ## Lexxy: A new rich text editor for Rails DevFeed: [Lexxy: A new rich text editor for Rails]() Original publisher: [Read original article]() Author: Jorge Manrubia Published: 2025-09-04T17:00:00Z Content type: release Language: en Sources: [37signals Dev]() Topics: [Rails](), [Framework]() Tags: [editor](), [rails](), [rich](), [trix]() ### AI overview 37signals introduces Lexxy, a new rich text editor for Rails Action Text based on Meta's Lexical framework. The early beta adds Markdown support, semantic HTML, real-time code syntax highlighting, configurable prompts, attachment previews, and integration with Action Text and Active Storage. ### Source excerpt A better Action Text. ## Features to consider when choosing a documentation editor DevFeed: [Features to consider when choosing a documentation editor]() Original publisher: [Read original article]() Author: Zaid Daba'een Published: 2024-10-13T19:01:46Z Content type: article Language: en Sources: [DeveloperHub.io]() Topics: [Documentation](), [formatting](), [Syntax Highlighting]() Tags: [2025](), [blocks](), [collaboration](), [customizable](), [documentation](), [editor](), [features](), [formatting](), [images](), [search](), [syntax-highlighting](), [technical](), [version-control]() ### AI overview This article explains how technical writers can evaluate documentation editors. It discusses formatting options, blocks and custom elements, multimedia embedding, collaboration tools, version control, and search functionality. ### Source excerpt Selecting the right documentation editor is essential for technical writers. Look for features like advanced formatting, customizable blocks, version control, and powerful search functionality. These tools enhance collaboration and ensure your documentation is clear, accessible, and easy to manage. ## Doctave Studio 2.0 Beta: The editor for technical writing and docs-as-code DevFeed: [Doctave Studio 2.0 Beta: The editor for technical writing and docs-as-code]() Original publisher: [Read original article]() Author: Doctave Team Published: 2024-10-08T05:00:00Z Content type: release Language: en Sources: [Doctave - Build beautiful developer portals with docs-as-code]() Topics: [Documentation](), [Tooling](), [Markdown](), [OpenAPI Specification](), [CI/CD]() Tags: [announce](), [assets](), [auto-complete](), [beta](), [blog](), [ci-cd](), [components](), [docs](), [docs-as-code](), [editor](), [real-time](), [technical-writing]() ### AI overview Doctave announces the public beta of Doctave Studio 2.0, an editor for technical writing and docs-as-code. The beta includes a modern editor, real-time Markdown and OpenAPI previews, auto-complete for links and assets, and inline Markdown error reporting. ### Source excerpt We're excited to announce that Doctave Studio 2.0 is now available in public beta! Doctave Studio is a new editor for technical writing and docs-as-code, and we're excited to share it with you. Want to see it in action? Here's a quick introductory video of Doctave Studio 2.0: If you just want to see how to participate in the beta, you can jump straight to the end of this post Why build a new editor? One of the biggest issues with docs-as-code is inconsistent tooling. While there are great tools out there (like Vale), it's really hard to create a great authoring environment for docs-as-code. Getting spell check, broken links checking, auto-complete, and more configured is often too complex or time consuming, that lots of authors live without these tools. This problem is compounded when you have multiple authors collaborating on the same documentation. One will have a spell checker configured, one will have auto-complete configured, another doesn't have a broken links checker. The lack of a common authoring system causes friction, confusion, and ultimately raises the barrier for contributions. And after all that, you still need to set up these same checks in your CI/CD pipeline! This is what we set out to solve with Doctave Studio 2.0. We've already made it easy to host, version, and review docs-as-code projects with our existing product. Now we're taking the next logical step and improving the docs-as-code authoring experience. What's in the Doctave Studio 2.0 beta? Today we're launching Doctave Studio 2.0 into beta with a few key features: A new, modern editor with a focus on the authoring experience Real-time previews of your content as you type (Markdown and OpenAPI!) Powerful auto-complete for your links, assets, and components Great error-reporting inline in your Markdown Let's see some of these in action! Real-time previews The right-side panel in Doctave Studio is dedicated to a real-time preview window. It shows you what your content will look like once publi ## Zed Code Editor as an Atom reincarnation DevFeed: [Zed Code Editor as an Atom reincarnation]() Original publisher: [Read original article]() Author: Tom Published: 2024-03-19T00:00:00Z Content type: opinion Language: en Sources: [Tomasz Gągor]() Topics: [Code](), [Rust](), [configuration]() Tags: [atom-reincarnation](), [code](), [configuration](), [customization](), [editor](), [macos](), [macos-code-editor](), [rust](), [rust-code-editor](), [speed](), [tools](), [zed](), [zed-code-editor](), [zed-configuration](), [zed-vs-atom]() ### AI overview The author compares Zed with Atom and VS Code, describing Zed as a Rust-built editor focused on speed. They find it promising as an Atom-like editor but not yet a replacement for their customized VS Code setup. ### Source excerpt Discover how Zed, a fast and efficient code editor built in Rust, aims to recapture the essence of Atom, with a focus on speed and customization. ## My Mac Dev Setup and Favorite Tools DevFeed: [My Mac Dev Setup and Favorite Tools]() Original publisher: [Read original article]() Author: Chris Hager Published: 2024-01-12T00:00:00Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [Development](), [Tool](), [Command-line interface](), [Shell](), [Terminal](), [backups](), [passwords](), [Homebrew](), [Package Management](), [Encryption](), [App](), [Obsidian]() Tags: [backup](), [csv](), [database](), [dev](), [dev-setup](), [developer-setup](), [editor](), [encryption](), [homebrew](), [iterm2](), [mac](), [macos](), [setup](), [tools]() ### AI overview A practical guide to setting up a Mac for software development, covering system security, backups, password management, developer tools, favorite applications, terminal use, and keyboard shortcuts. ### Source excerpt How I setup and use my computer and tools for development. I wrote this mostly as a guide for myself, for the next time I setup a computer, and hope it might be useful to others too. I'd love to hear your thoughts, ideas and additional tips in the comments below! Related: How I setup my Terminal and Bash. Contents Mac setup General system setup Favorite apps Keyboard shortcuts Application shortcuts Arranging windows Browser Terminal & Shell Docker for Node. ## Taking the Language Server Protocol one step further DevFeed: [Taking the Language Server Protocol one step further]() Original publisher: [Read original article]() Published: 2023-12-19T00:00:00Z Content type: article Language: en Sources: [Garnix Blog]() Topics: [Protocol (disambiguation)](), [configuration](), [Microsoft]() Tags: [configuration](), [editor](), [flexibility](), [microsoft](), [protocol]() ### AI overview The article examines Microsoft's Language Server Protocol, noting that it supports diversity among text editors but lacks flexibility for project-specific configuration. ### Source excerpt Microsoft's LSP is great for text-editor diversity, but it is severely lacking in flexibility for project-specific configuration. [Next page]()