# text Published articles for text. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users DevFeed: [Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users]() Original publisher: [Read original article]() Author: Nubank Editorial Published: 2026-09-16T14:09:16Z Content type: article Language: en Sources: [Nubank]() Topics: [Accessibility](), [Claude](), [User interface design](), [screen](), [Users](), [Development]() Tags: [accessibility](), [accessible](), [claude](), [culture-values](), [data-science-machine-learning](), [development-environment](), [engineering](), [inclusive](), [life-at-nu](), [people-with-disabilities](), [text](), [users](), [vision]() ### AI overview Nubank describes BLIND-CLAUDE.md, an instruction set that adapts Claude responses for people who primarily use screen readers or read-aloud functionality. The approach treats auditory comprehension as an engineering constraint and changes behavioral instructions without modifying Claude or adding a native accessibility feature. ### Source excerpt How a cognitively diverse IT team at Nubank, they coded screen reader-friendly rules into Claude's instructions, treating auditory comprehension as an engineering constraint The post Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users appeared first on Building Nubank. ## Introducing TIN: full-text search for Postgres DevFeed: [Introducing TIN: full-text search for Postgres]() Original publisher: [Read original article]() Author: Patrick Reynolds Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [Blog -- PlanetScale]() Topics: [Databases](), [benchmarking]() Tags: [backups](), [benchmark](), [benchmarks](), [bm25](), [engineering](), [full-text-search](), [index](), [performance](), [postgres](), [reddit](), [replication](), [search](), [text](), [wikipedia]() ### AI overview PlanetScale announces TIN, a full-text search extension for Postgres and Neki databases. The article describes supported query and matching features, transaction and update behavior, and benchmark workloads and corpora used to assess performance. ### Source excerpt TIN is a fast, full-featured, full-text search index for Postgres ## Npb: Nixpkgs PR build diff CLI inspired by nixpkgs-review DevFeed: [Npb: Nixpkgs PR build diff CLI inspired by nixpkgs-review]() Original publisher: [Read original article]() Author: samestep Published: 2026-07-21T21:09:29Z Content type: article Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [Development](), [Command-line interface]() Tags: [announcements](), [caching](), [cli](), [memory](), [parallelism](), [text]() ### AI overview A developer introduces npb, a Nixpkgs pull-request build outcome diff CLI inspired by nixpkgs-review. It compares build results before and after a change, and adds features including passthru.test inclusion, cached failures, lower memory usage, parallel Nix evaluations, reproducible report commands, and progress indicators. ### Source excerpt Hello! While reviewing Nixpkgs PRs written by myself and others, I've found it difficult to keep track of which build failures were preexisting and which are regressions introduced by the PR itself. So I built a tool called npb which produces reports that are similar to nixpkgs-review, but show both before and after, instead of just after. github.com GitHub - samestep/npb: Nixpkgs build outcome diff CLI Nixpkgs build outcome diff CLI While building this, I also included some other features I had found myself wanting previously, such as: automatically including passthru.tests caching build failures in a local database reducing memory usage of Nix evaluations speeding up Nix evaluations via parallelism giving each report a command that reproduces the same report providing progress indicators during long-running operations I hope you find it useful! Disclosure, quoting the project's README: The development of this project was AI-assisted. There is no AI-generated text in this README, npb --help, or npb's generated reports. 7 posts - 4 participants Read full topic ## PowerToys Advanced Paste supports plain text, Markdown, JSON, and file pasting DevFeed: [PowerToys Advanced Paste supports plain text, Markdown, JSON, and file pasting]() Original publisher: [Read original article]() Author: Dean Hume Published: 2026-04-28T16:15:22Z Content type: tutorial Language: en Sources: [Dean Hume]() Topics: [Microsoft PowerToys](), [JSON](), [Markdown](), [Artificial Intelligence]() Tags: [json](), [markdown](), [powertoys](), [technical-program-manager](), [text]() ### AI overview This article explains how PowerToys Advanced Paste can transform clipboard content into plain text, Markdown, JSON, or a file. It presents the tool as a way to reduce formatting cleanup and convert content between formats. ### Source excerpt PowerToys Advanced Paste transforms your clipboard - paste as plain text, Markdown, JSON, extract text from images, and reformat content with AI. ## snakes.run: rendering 100M pixels a second over ssh DevFeed: [snakes.run: rendering 100M pixels a second over ssh]() Original publisher: [Read original article]() Author: Nolen Royalty (eieiogames@gmail.com) Published: 2026-02-25T00:00:00Z Content type: article Language: en Sources: [eieio.games]() Topics: [ssh](), [Go Language](), [Back end](), [Text-based user interface](), [ASCII]() Tags: [backend](), [go](), [multiplayer](), [performance](), [pixels](), [render](), [server](), [ssh](), [terminal](), [text](), [unicode]() ### AI overview An engineering article explains how snakes.run delivers a massively multiplayer snake game over SSH. It describes server-side frame rendering, a TUI-based game architecture, bandwidth and performance work, and the use of Unicode block elements and terminal colors for smoother graphics. ### Source excerpt snakes.run is a massively multiplayer snake game that uses the Secure Snake Home (SSH) protocol. It can render 100M pixels a second. ## Gemini and Angular, Part II: Creating Generative UIs DevFeed: [Gemini and Angular, Part II: Creating Generative UIs]() Original publisher: [Read original article]() Author: Armen Vardanyan Published: 2026-01-22T13:48:08Z Content type: tutorial Language: en Sources: [Daniel Glejzner]() Topics: [Angular](), [Large Language Model](), [function calling](), [ui](), [text-generation](), [JSON](), [App]() Tags: [angular](), [article](), [code](), [function-calling](), [gemini](), [generative](), [generative-ui](), [json](), [llms](), [model](), [schemas](), [structured](), [text](), [text-generation]() ### AI overview This tutorial continues a series on LLMs and Gemini by exploring Generative UI in Angular. It describes dynamically rendering interactive Angular components from model responses, combining Gemini with Google's Nano Banana Pro image generation model, and using Angular signal forms. The article emphasizes minimizing boilerplate while balancing model capability, performance, and cost. ### Source excerpt Let's continue our journey into LLMs and Gemini! In the previous article, we moved beyond simple text generation and learned: how to force the model to speak our language using structured outputs (JSON schemas) how to connect the model to our actual code and logic using function calling ## Maintaining shadow branches for GitHub PRs DevFeed: [Maintaining shadow branches for GitHub PRs]() Original publisher: [Read original article]() Published: 2026-01-22T08:00:00Z Content type: article Language: en Sources: [MaskRay]() Topics: [GitHub](), [Pull Request](), [Vibe coding](), [Tool](), [LLVM]() Tags: [git](), [github](), [pull-request](), [text](), [tool](), [vibe-coding](), [workflow]() ### AI overview The author describes pr-shadow, a tool created with vibe coding that maintains a fast-forward-only shadow branch for GitHub pull requests. Developers can rebase, amend, or squash locally while reviewers see stable diffs and the workflow avoids force-pushing problems. ### Source excerpt I've created pr-shadow with vibe coding, a tool that maintains a shadow branch for GitHub pull requests (PR) that never requires force-pushing. This addresses pain points I described in Reflections on LLVM's switch to GitHub pull requests#Patch evolution. ## Using Stencil Templates for Code Generation in iOS Development DevFeed: [Using Stencil Templates for Code Generation in iOS Development]() Original publisher: [Read original article]() Author: CleverDevilV (hh.ru) Published: 2025-12-04T09:45:15Z Content type: tutorial Language: ru Sources: [HeadHunter RU]() Topics: [iOS](), [Swift](), [Figma](), [Kotlin](), [JSON](), [Sublime Text](), [Visual Studio Code](), [Xcode]() Tags: [figma](), [filter](), [ios](), [ios-92ecabba3495](), [join](), [kotlin](), [split](), [swift](), [tag-3383f6fe7741](), [tag-e95ee8b94dca](), [text](), [vscode](), [xcode]() ### AI overview A tutorial introducing Stencil, a template language used to automate code and file generation in iOS development. It explains the language's syntax, data structures, filters, and tags, and describes applications involving Swift, Figma-exported design-system data, analytics events, Kotlin files, JSON input, and editor support. ### Source excerpt Что любят все разработчики? Конечно, автоматизировать рутинные повторяющиеся действия! Я расскажу, как в этом может помочь язык Stencil, широко известный в узких кругах iOS-разработчиков. Читать далее ## Using JSON: json vs. jsonb, pglz vs. lz4, key optimization, parsing speed? DevFeed: [Using JSON: json vs. jsonb, pglz vs. lz4, key optimization, parsing speed?]() Original publisher: [Read original article]() Author: depesz Published: 2025-11-29T19:16:00Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [JSON](), [PostgreSQL](), [Compression](), [Optimization](), [Parsing]() Tags: [benchmark](), [compression](), [discord](), [irc](), [json](), [jsonb](), [optimization](), [parsing](), [performance](), [postgresql](), [slack](), [speed](), [text](), [uncategorized]() ### AI overview This article investigates JSON and JSONB storage in PostgreSQL, comparing pglz and LZ4 compression, storage overhead, key-name handling, and parsing speed. In the reported test, pglz compressed slightly better, while LZ4 processed 16 MB of text faster. ### Source excerpt Recently(ish) I had a conversation on one of PostgreSQL support chats (IRC, Slack, or Discord) about efficient storage of JSON data, which compression to use, which datatype. Unrelated to this, some people (at least two over the last year or so) said that they aren't sure if PostgreSQL doesn't optimize storage between columns, for example, ... Continue reading "Using JSON: json vs. jsonb, pglz vs. lz4, key optimization, parsing speed?" ## Text rendering and effects using GPU-computed distances DevFeed: [Text rendering and effects using GPU-computed distances]() Original publisher: [Read original article]() Published: 2025-11-01T17:20:06Z Content type: tutorial Language: en Sources: [The Last Static Blog RSS]() Topics: [GPU](), [signed distance functions](), [Font](), [Algorithm](), [Mobile]() Tags: [algorithm](), [code](), [compute](), [effects](), [fonts](), [gpu](), [graphics](), [math](), [mobile](), [prog](), [render](), [text]() ### AI overview This tutorial explains how to compute signed distance fields for text glyphs on the GPU. It covers extracting glyph outlines, representing lines and Bézier curves as cubics, implementing the algorithm in a shader, and the trade-offs and effects enabled by the approach. ### Source excerpt Text rendering is cursed. Anyone who has worked on text will tell you the same; whether it's about layout, bi-directional, shaping, Unicode, or the rendering itself, it's never a completely solved problem. In my personal case, I've been working on trying to render text in the context of a compositing engine for creative content. I needed crazy text effects, and I needed them to be reasonably fast, which implied working with the GPU as much as possible. The distance field was an obvious requirement because it unlocks anti-aliasing and the ability to make many great effects for basically free. In this article, we will see how to compute signed distance field on the GPU because it's much faster than doing it on the CPU, especially when targeting mobile devices. We will make the algorithm decently fast, then after lamenting about the limitations, we will see what kind of effects this opens up. Progressive build of the 'あ' glyph from the Mochiy Pop One font Extraction of glyph outlines Non-bitmap fonts contain glyphs defined by outlines made of closed sequences of lines and (quadratic or cubic) Bézier curves. Extracting them isn't exactly complicated: FreeType or ttf-parser typically expose a way to do that. For the purpose of this article, we're going to hard code the list of the Bézier curves inside the shader, but of course in a more serious setup those would be uploaded through storage buffers or similar. Using this tiny program, a glyph can be dumped as series of outlines into a fixed size array: struct Bezier { vec2 p0; // start point vec2 p1; // control point 1 vec2 p2; // control point 2 vec2 p3; // end point }; #define N 42 #define NC 2 const int glyph_A_count[2] = int[](33, 9); const Bezier glyph_A[42] = Bezier[]( Bezier(vec2( 0.365370, -0.570817), vec2( 0.374708, -0.631518), vec2( 0.332685, -0.687549), vec2( 0.339689, -0.748249)), Bezier(vec2( 0.339689, -0.748249), vec2( 0.339689, -0.748249), vec2( 0.344358, -0.764591), vec2( 0.351362, -0.771595)), Bezier(vec2 ## Meta 3D AssetGen: Generating 3D Worlds With AI DevFeed: [Meta 3D AssetGen: Generating 3D Worlds With AI]() Original publisher: [Read original article]() Author: Pascal Hartig Published: 2025-09-29T14:00:42Z Content type: article Language: en Sources: [Meta AI Research]() Topics: [3D](), [Artificial Intelligence](), [foundation-models](), [Large Language Model](), [Meta]() Tags: [3d](), [ai](), [ai-research](), [foundation](), [images](), [keynote](), [learning](), [llms](), [meta](), [meta-tech-podcast](), [ml-applications](), [model](), [podcast](), [text](), [virtual](), [virtual-reality](), [worlds]() ### AI overview A Meta Tech Podcast episode discusses AssetGen, a foundation model for 3D assets. Meta's XR Tech team explains how it was built and trained, the role of LLMs in VR, and efforts to generate complete 3D worlds from text prompts. ### Source excerpt Imagine being able to use AI to create 3D virtual worlds using prompts as easily as you can generate images. The intersection of AI and VR was one of the biggest topics at Meta Connect this year. In his keynote, Mark Zuckerberg shared his vision of a future where anyone can create virtual worlds using [...] Read More... The post Meta 3D AssetGen: Generating 3D Worlds With AI appeared first on Engineering at Meta. ## The Accessibility Problems Caused by Incorrect Text Truncation in Android Apps DevFeed: [The Accessibility Problems Caused by Incorrect Text Truncation in Android Apps]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2025-04-26T07:31:38.151000Z Content type: article Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [Android](), [User interface design](), [Font](), [Large Screen]() Tags: [accessibility](), [android](), [cognitive-load](), [text](), [users]() ### AI overview The article examines how Android apps truncate text with ellipses when it does not fit, often without a way to expand the hidden text. It argues that this can prevent users, especially those using larger font sizes or smaller displays, from accessing important labels and context. ### Source excerpt Imagine that you're in an unfamiliar location. You can see a signpost, but it's old, and most of the letters of the words have been scratched off. The names in the signs all seem similar, given the couple of letters you can see. And you need to get somewhere, but the signpost is not helping at all. You're lost. As the title gives away, I'm writing about something starting with "trun". I could be writing about the problems of trunkfish. They seem a bit lost, so the topic could be that. Or I could be writing about truncheons and the issues caused by them. But no, this time, it's about truncation, specifically when truncation has not been implemented correctly. Texts in applications are like those signs in a signpost. They most often lead to somewhere, give some instructions or necessary information, or are otherwise relevant. Texts wouldn't be in the app if they weren't meaningful. Problem of Truncation Done Wrong We have this widely spread pattern on Android, where the words are truncated with an ellipsis if they don't fit the container, without any way to expand the missing part of the text. For example, when you have a font size that is big enough, app names are truncated. The following image shows an example from accessibility settings and font size selection in Pixel: And okay, one could argue that if you install an app, you should be familiar with it and be able to recognize it even when you just get three letters from the name with the icon. But it's not that straightforward - what if it's an app you've used a year ago? Or what if you have memory issues due to something permanent or due to stress? Or any of the number of reasons why recognizing the app only with a partial name and an icon is not possible - let alone the cognitive load it creates. And it's not just the app icons; it's everywhere in the apps: The bottom navigation, buttons, links, titles... All these are places where the user would need the context of "What will happen if I press this item?" or " ## Android Accessibility Checklist DevFeed: [Android Accessibility Checklist]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2024-08-07T02:56:29.395000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [Android](), [Development](), [Website]() Tags: [accessibility](), [accessibility-guidelines](), [analysis](), [android](), [blog](), [blog-post](), [design](), [developer](), [development](), [google](), [process](), [research](), [screen](), [text]() ### AI overview This blog post presents an Android accessibility checklist developed as part of a master's thesis. It explains the checklist's research and development process, including prior research, Android accessibility guidelines, interviews with Android developers, and questionnaire feedback. The checklist has sections for checks developers can fix themselves and issues that may require broader support or significant changes. ### Source excerpt I'm studying for my second master's degree (for fun) and finished with my thesis in the spring. As part of my thesis, I developed an accessibility checklist for Android developers. While completing all the checks doesn't guarantee that your app is 100% accessible, the checklist aims to help catch many possible accessibility problems. In this blog post, I'll first share a bit about the development process and then share the checklist. If you're curious, the whole checklist with accompanying material is behind the following link: Android Accessibility Checklist. Background As mentioned, developing the checklist was part of my Master's thesis, which has been published, and you can find it from the following link: Towards More Accessible Android Applications: An Actionable Accessibility Checklist for Android Developers. I conducted the research with the help of Design Science Research (DSR). I collected material for the initial checklist from prior research and available Android accessibility guidelines, evaluated it with five interviews with Android developers, and then constructed an improved checklist. Then, I created the website with the improved checklist and collected feedback and material for the last analysis with a Google Form. I analyzed the answers from both interviews and the questionnaire with the help of content analysis. The result of the research is the Android Accessibility Checklist, or as DSR calls it, an artifact. The checklist itself consists of two sections. The first contains the checks that every Android developer should do, and the findings should be fixable by the developer. The second section includes checks that might not be fixable by the developer alone and might either require help from other functions or be a huge change. I'll explain the reasoning for some of these checks later in the blog post. Now that the work with the thesis is over, and I don't need to think about the thesis' scope anymore, I will update the page and the checklist o ## Emopoint: Extract and measure emotion from text DevFeed: [Emopoint: Extract and measure emotion from text]() Original publisher: [Read original article]() Published: 2024-06-26T09:00:00Z Content type: tutorial Language: en Sources: [Tim Kellogg]() Topics: [Large Language Model](), [Embeddings](), [Retrieval-Augmented Generation](), [Code]() Tags: [ai](), [embeddings](), [javascript](), [llms](), [python](), [rag](), [text](), [wild]() ### AI overview This tutorial explains how LLM embeddings can be used to extract emotional information from text and map it into a three-dimensional "emopoint" space. It discusses measuring emotional content in conversations and introduces embeddings, their role in retrieval-augmented generation, and their lack of directly interpretable dimensions. ### Source excerpt Can AI understand emotion? They must, ChatGPT responds to me in the appropriate tone of voice. So they certainly encode emotion. In this blog we'll dive deep into how LLMs understand emotion, as well as how to take advantage of that. ## A brief and incomplete history of modal text editors DevFeed: [A brief and incomplete history of modal text editors]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2023-08-20T00:00:00Z Content type: article Language: en Sources: [Carlos Becker]() Topics: [Vim](), [Unix](), [Programming]() Tags: [editor](), [history](), [text](), [unix](), [vim]() ### AI overview The article provides a brief, explicitly incomplete history of modal text editors, covering the author's early experiences with Turbo C and Vim before discussing Ed, Ex, and Vi. It explains modal editing and describes how Vi developed from Ex and Ed. ### Source excerpt In this post I'm going to talk about some old text editors you probably never heard of, what is modal text editing, and why people like it so much. ## tclip: A pastebin for your tailnet DevFeed: [tclip: A pastebin for your tailnet]() Original publisher: [Read original article]() Author: Xe Iaso Published: 2023-08-17T00:00:00Z Content type: article Language: en Sources: [Tailscale Community]() Topics: [tailscale]() Tags: [funnel](), [tailnet](), [tailscale](), [text](), [tsnet]() ### AI overview tclip is a Tailscale-powered pastebin for sharing text between machines or coworkers. ### Source excerpt Sometimes you need to paste text between your machines or coworkers. tclip is a Tailscale-powered pastebin that lets you do just that. ## Talk: Reimagining text fields in Compose DevFeed: [Talk: Reimagining text fields in Compose]() Original publisher: [Read original article]() Author: Zach Klippenstein Published: 2023-06-09T07:00:00Z Content type: article Language: en Sources: [Zach Klippenstein's Blog]() Topics: [Compose]() Tags: [android](), [compose](), [droidcon](), [fields](), [jetpack-compose](), [kotlin](), [talk](), [talks](), [text]() ### AI overview The article presents a talk about reimagining text fields in Compose and mentions work on a new BasicTextField. ### Source excerpt I've spent the last six months working on a new BasicTextField. Check out what we've been working on! ## How to Use GPT-4 to Create Interactive Text-Based Adventure Games DevFeed: [How to Use GPT-4 to Create Interactive Text-Based Adventure Games]() Original publisher: [Read original article]() Published: 2023-04-01T15:48:44Z Content type: tutorial Language: en Sources: [Matt Might]() Topics: [Generative AI](), [Game engine](), [Development]() Tags: [game](), [generate](), [gpt](), [how-to](), [interactive](), [make](), [save](), [text]() ### AI overview This tutorial explains how to use GPT-4 as a game engine for interactive text-based adventure games by defining a fictional universe and designing a prompt to simulate gameplay. It also describes adding a save-game feature so players can save and resume the game state. ### Source excerpt Compared to prior versions, GPT-4 is more capable at writing fiction. Combined with its advances in reasoning, this allows it to maintain a consistent state in a fictional universe as it emulates a text-based adventure game like the classic Zork. In this article, I'll explain how to convert GPT-4 into a game engine for interactive text-based adventure games with just two simple steps: Create a descriptive lore to define the universe and the player Engineer a prompt to simulate a text-based adventure game You can even add a save game feature that allows you to save the state and resume play later. While GPT-3 works with these techniques, it tends to create worlds with less coherent states and the game has shallower narratives compared to GPT-4. The backstory Figuring out how to create these games emerged from my kids' bedtime. Before they go to bed, I like to spend 15-30 minutes doing something educational and entertaining, such as: reading a book or a graphic novel; doing simple crafts like paper airplanes; asking a question on their mind and searching for the result; choosing an object to have 3D printed by morning; or writing a small program or part of a larger program. Not surprisingly, generative AI expands what you can do in 15-30 minutes! For instance, this image took about 30 minutes from start to finish, combining Midjourney to generate a base image, Lensa to do touch-ups and change the background and then DALL-E to tweak parts of it and extend the borders: The opportunities for text-based gaming turn out to the just as rich! My daughter had created a fictional universe with friends at school, complete with its own lore. So, we dropped in the lore and then asked it to act like a role-playing game in that world. We ended up spending an hour exploring this world brought to life, completing the first "quest" it had imagined for us. Click here to read the rest of the article ## Measuring the Impact of Font Grade on Text Readability DevFeed: [Measuring the Impact of Font Grade on Text Readability]() Original publisher: [Read original article]() Published: 2022-05-11T09:00:00Z Content type: article Language: en Sources: [Material.io - Material Design]() Topics: [Font]() Tags: [measuring](), [readability](), [text]() ### AI overview This article examines how font grade affects text readability. ### Source excerpt Measuring the impact font grade has on text readability ## EOF is not a character DevFeed: [EOF is not a character]() Original publisher: [Read original article]() Author: Ruslan Spivak Published: 2020-03-01T16:53:00Z Content type: tutorial Language: en Sources: [Ruslan Spivak]() Topics: [C](), [IO](), [Unix](), [ASCII](), [Streams](), [Code]() Tags: [ascii](), [blog](), [c](), [code](), [computer](), [example](), [file](), [function](), [library](), [linux](), [mac-os](), [python](), [standard-library](), [stream](), [systems](), [text](), [unix](), [value]() ### AI overview This tutorial explains that EOF in C is not a character and is not stored at the end of a file. It examines EOF in Unix I/O, its usual value of -1, and why that value cannot represent a character. ### Source excerpt I was reading Computer Systems: A Programmer's Perspective the other day and in the chapter on Unix I/O the authors mention that there is no explicit "EOF character" at the end of a file. ## GSoC 2019 - File Search (Final Report) DevFeed: [GSoC 2019 - File Search (Final Report)]() Original publisher: [Read original article]() Published: 2019-08-26T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [like](), [ReactOS](), [file](), [Windows](), [GUI](), [Regular expression]() Tags: [file](), [free](), [gsoc](), [keyboard](), [open-source](), [os](), [react](), [reactos](), [regular-expressions](), [report](), [text](), [win32](), [winapi](), [windows]() ### AI overview The article reports completed work on ReactOS's file search project, including a Start menu or keyboard shortcut launch, case-insensitive recursive searching, UTF-16 text-file support, and wildcard file-name filtering. It also notes possible future support for case-sensitive search and regular expressions. ### Source excerpt This is a summary of all the work that has been completed this summer on the file search project. All contributed code can be found in this GitHub pull request. Summary Here is a list of the main features: Quickly open it from the Start menu or with the keyboard shortcut Windows + F Search is case-insensitive and recurses all sub-folders Support for UTF-16 encoded text files File name filtering with support for wildcards " ## PostgreSQL Data Types: Text Processing DevFeed: [PostgreSQL Data Types: Text Processing]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2018-04-11T21:15:42Z Content type: tutorial Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [Regular expression](), [pattern matching](), [CSV]() Tags: [csv](), [dataset](), [functions](), [pattern-matching](), [postgresql](), [processing](), [regexp](), [regular](), [text]() ### AI overview This tutorial introduces PostgreSQL text-processing functions and operators, including string functions, aggregates, regular expressions, and regexp_split_to_table(). It also discusses text and varchar data types and demonstrates processing comma-separated and hierarchical values in a CSV dataset. ### Source excerpt Continuing our series of PostgreSQL Data Types today we're going to introduce some of the PostgreSQL text processing functions. There's a very rich set of PostgreSQL functions to process text -- you can find them all in the string functions and operators documentation chapter -- with functions such as overlay(), substring(), position() or trim(). Or aggregates such as string_agg(). There are also regular expression functions, including the very powerful regexp_split_to_table(). In this article we see practical example putting them in practice. ## Postgres hidden gems DevFeed: [Postgres hidden gems]() Original publisher: [Read original article]() Author: Map Published: 2018-01-31T20:55:56Z Content type: article Language: en Sources: [Craig Kerstiens]() Topics: [PostgreSQL](), [Database](), [Replication](), [Network Operations](), [Statistics]() Tags: [functions](), [jsonb](), [lateral](), [network-operations](), [postgres](), [postgresql](), [psql](), [replication](), [statistics](), [text](), [unicode](), [window-functions]() ### AI overview The article collects PostgreSQL features that the author and contributors consider useful or easily overlooked. It highlights capabilities including ltree, citext, date arithmetic, jsonb, lateral joins, window functions, custom foreign data wrappers, replication slots, range types, statistics, logical decoding, and psql features. ### Source excerpt Postgres has a rich set of features, even when working everyday with it you may not discover all it has to offer. In hopes of learning some new features that I didn't know about myself as well as seeing what small gems people found joy in I tweeted out to see what people came back from. The response was impressive, and rather than have it lost into ether of twitter I'm capturing some of the responses here along with some resources many of the features. @listrophy - $ brew postgresql-update database Though personally I prefer Postgres.app ;) @pat_shaugnessy - ltree Pat has a great post that walks through ltree @billyfung - citext A really handy datatype for case insensitive text @eeeebbbbrrrr - date math with intervals I couldn't agree more on this one, working with time in Postgres is the easiest time I've every had @DataMiller - The jsonb datatype and lateral joins I'd argue it's hard to claim now JSONB is a hidden gem, but lateral joins are certain a great one @ideasasylum - row_number() over(partition http://orders.site_id order by orders.created_at) Window functions are definitely a handy feature was my hidden (to me) discovery this week @franckverrot - Index access method, and custom FDWs @jonjensen0 - Set-returning functions and custom aggregate functions can be very helpful. @ascherbaum - psql -x Psql is indeed awesome and can be well tuned @Abstr_ct - The fact that the docs are fantastic and all hidden gems are actually readily available. Oh, and pl/brainfuck obviously @Halpin_IO - Subnetting and network operations @jkatz05 - Replication slots, both physical and logical. They've made setting up replication infinitely easier. And range types. Because they're awesome. @petereisentraut - Unicode table borders @_avichalp Notify/listen @simonw - The fact that GIN indices can make LIKE queries run fast even if the % isn't just at the end of the string @javisantana - it has a statistics system to plan queries that can be used by the user when accuracy does not matt ## How to Add a Text Filter to Django Admin DevFeed: [How to Add a Text Filter to Django Admin]() Original publisher: [Read original article]() Author: Haki Benita Published: 2018-01-01T22:00:00Z Content type: tutorial Language: en Sources: [Haki Benita]() Topics: [Django](), [implementation]() Tags: [articles](), [custom](), [django](), [django-admin](), [faster](), [filter](), [how-to](), [search](), [text]() ### AI overview This tutorial explains how to replace broad Django Admin search fields with custom text-based ListFilters for specific fields. The approach avoids large match-any queries and can make admin searches faster. ### Source excerpt Django Admin search fields are great, throw a bunch of fields in search_fields and Django will handle the rest. The problem with search field begins when there are too many of them. This is how we replaced Django search with text filters for specific fields, and made Django admin much faster. [Next page]()