# rewrite Published articles for rewrite. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Third-Generation GUI Builder: One Workspace for Every Form DevFeed: [The Third-Generation GUI Builder: One Workspace for Every Form]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-14T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [GUI](), [Maven](), [CSS](), [Java]() Tags: [css](), [gui](), [java](), [projects](), [rewrite]() ### AI overview Codename One has rebuilt its GUI Builder for a third generation. The new project-oriented workspace preserves guided layout while integrating Maven project structure, forms, live CSS, protected Java regions, and switching between forms. ### Source excerpt Codename One's third-generation GUI Builder keeps the guided layout work from the previous editor and rebuilds the workflow around Maven projects, live CSS, protected Java regions, and fast switching between forms. ## Migrating a Large Flow Monorepo to TypeScript DevFeed: [Migrating a Large Flow Monorepo to TypeScript]() Original publisher: [Read original article]() Author: Shawn Walton, Software Engineer Published: 2026-08-04T00:00:00Z Content type: article Language: en Sources: [Yelp]() Topics: [monorepo](), [TypeScript](), [migration](), [repo](), [Code]() Tags: [coverage](), [integrity](), [migration](), [monorepo](), [open-source](), [rewrite](), [typescript]() ### AI overview Yelp describes its gradual migration of a large Flow monorepo to TypeScript. The team chose a package-by-package approach to preserve type-checking trust and type safety while Flow and TypeScript coexisted in production, using open-source conversion tooling, custom codemods, and manual fixes. ### Source excerpt In early 2017, Webcore selected Flow as Yelp's next-generation typechecker over TypeScript. At the time there was no clear frontrunner. Flow had better support for React, better performance, and a respectable repository of types for NPM packages in flow-typed. However, a few years later the landscape had shifted, and it became clear that TypeScript was emerging as the stronger choice. TypeScript's DefinitelyTyped repo had thousands more packages than flow-typed, and many more packages shipped with built-in TypeScript headers. TypeScript also proved to be more stable over time, and limited uptake in the wider JS community made finding tools and documentation... ## Strategies for Migrating from a Monolith to Microservices DevFeed: [Strategies for Migrating from a Monolith to Microservices]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-06-23T07:55:12Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [Architecture & Design](), [microservices architecture](), [migration](), [legacy systems](), [gateway]() Tags: [api-gateway](), [architecture](), [automated](), [big-bang](), [feature-flags](), [incremental](), [legacy-systems](), [microservices](), [migration](), [monolith](), [parallel](), [rewrite](), [strategies](), [testing]() ### AI overview This tutorial outlines patterns for gradually moving from a monolithic architecture to microservices. It describes the Strangler Fig Pattern, Parallel Run Pattern, and Collaborator Pattern, covering techniques such as API gateways, incremental migration, traffic splitting, feature flags, and automated comparison testing. ### Source excerpt Top Strategies ## Improve AI output with continuous improvement DevFeed: [Improve AI output with continuous improvement]() Original publisher: [Read original article]() Author: Alexander Nohe; Dan Gruhl Published: 2026-01-13T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Artificial Intelligence](), [Chain-of-thought]() Tags: [adk](), [agentic](), [ai](), [automated](), [firebase](), [gemini](), [prompting](), [python](), [rewrite](), [verify]() ### AI overview A tutorial explains continuous improvement, a prompting strategy in which one AI generates an output and another AI critiques it before the first AI revises the result. It demonstrates the approach with ADK and LoopAgent for designing gym workouts. ### Source excerpt Learn how to improve your AI outputs to a more reliable output through continuous improvement. ## Out with the Old, In with the New: A Guide to Application Upkeep DevFeed: [Out with the Old, In with the New: A Guide to Application Upkeep]() Original publisher: [Read original article]() Author: Andres Sacco Published: 2025-12-20T03:08:59Z Content type: tutorial Language: en Sources: [Java Advent Calendar]() Topics: [Java](), [migration](), [Spring Boot](), [Microservice](), [Vulnerabilities](), [Security]() Tags: [2025](), [automatic](), [guide](), [java](), [legacy-application](), [legacy-code](), [maintainability](), [microservices](), [migration](), [rewrite](), [security](), [spring](), [spring-boot]() ### AI overview This guide explains why upgrading Java or Spring Boot applications involves more than changing a version number. It discusses migration challenges, legacy code, differing versions across microservices, and risks from outdated software, including security, compatibility, stability, and maintainability concerns. ### Source excerpt Migrating an existing application to a new version of Java or a framework such as Spring Boot involves much more than simply updating a version number in a file. Each new release of a library or language brings new features, deprecations, behavioral changes, and sometimes complete API redesigns. When legacy code is involved, these upgrades [...] The post Out with the Old, In with the New: A Guide to Application Upkeep appeared first on JVM Advent. ## \[RevEng\] Toy decompiler DevFeed: [\[RevEng\] Toy decompiler]() Original publisher: [Read original article]() Published: 2025-11-16T23:00:00Z Content type: article Language: en Sources: [Dennis Yurichev]() Topics: [Assembly](), [Code](), [Compiler](), [Python](), [C](), [gcc]() Tags: [assembly](), [c](), [code](), [compiler](), [experimental](), [gcc](), [python](), [rewrite]() ### AI overview This article describes a toy decompiler for Xilinx MicroBlaze assembly. It manually and programmatically rewrites chains of addk and rsubk instructions into multiplication expressions, using Python regular expressions and tests, then discusses limitations including GCC optimization and the experimental nature of the implementation. ### Source excerpt [RevEng] Toy decompiler ## The rewrite dilemma in software engineering DevFeed: [The rewrite dilemma in software engineering]() Original publisher: [Read original article]() Author: Mike Yerou Published: 2025-11-06T12:10:38Z Content type: opinion Language: en Sources: [Rock and Null]() Topics: [Software Engineering](), [Refactoring](), [Software]() Tags: [engineering](), [rewrite](), [software](), [software-engineering](), [thoughts]() ### AI overview The article examines the trade-offs of rewriting existing software. It argues that accumulated fixes, edge-case handling, testing, and historical knowledge can make a messy system stable, so improving working code may be wiser than starting over. ### Source excerpt Rewriting software can be tempting, but understanding the hidden value of accumulated fixes and system stability is key to making the right decision. ## Ten years of Overcast: A new foundation DevFeed: [Ten years of Overcast: A new foundation]() Original publisher: [Read original article]() Author: Marco Arment Published: 2024-07-16T12:57:40Z Content type: article Language: en Sources: [Marco.org]() Topics: [App](), [iOS](), [Playback](), [Streaming]() Tags: [accessible](), [app](), [apple](), [faster](), [launch](), [navigation](), [new-features](), [playback](), [privacy](), [redesign](), [rewrite](), [shortcuts](), [storage](), [streaming](), [sync]() ### AI overview Overcast has launched a substantial rewrite and redesign of most of its iOS app for its tenth anniversary. The update improves responsiveness, reliability, accessibility, navigation, and controls, while retaining most features and the existing audio engine. Streaming has been replaced by downloading episodes before playback, and several missing features are planned to return. ### Source excerpt Today, on the tenth anniversary of Overcast 1.0, I'm happy to launch a complete rewrite and redesign of most of the iOS app, built to carry Overcast into the next decade -- and hopefully beyond. Like podcasts better than blog posts? Listen to ATP #596 for more! What's new Much faster, more responsive, more reliable, and more accessible. Modern design, optimized for easily-reached controls on today's phone sizes. Improvements throughout, such as undoing large seeks, new playlist-priority options, easier navigation, and more. What's not Most features. Overcast is still Overcast! The audio engine. It's the best part of Overcast, and still leads the industry in sound quality, silence skipping, and volume normalization. (More soon!) The business. I'm still a one-person operation, with no funding or external ownership, serving only my customers. My principles. I always want to make the best podcast app, and I'll never disrespect your time, attention, or privacy. What's gone Streaming. Most big podcasts now use dynamic ad insertion, which causes bugs and problems for streaming playback.1 Downloading episodes completely before they begin playback is much more reliable. Tapping a non-downloaded episode will now open the playback screen, download it, then start playback. It works similarly to the way streaming did before, but playback begins after the download completes, not after a portion of it is buffered. On today's fast networks, this usually only takes a few extra seconds. And in the near future, I'll be adding smarter options and more control over selective downloading of episodes to further improve the experience for people who don't automatically download every episode. What's next The last few missing features from the old app, such as Shortcuts support, storage management, and OPML. These are absent now, but will return soon. More options for downloading and deleting episodes. Upgrading the Apple Watch app to the new, faster sync engine. (The Watch app is currently ## Open-sourcing our progress on Tailwind CSS v4.0 DevFeed: [Open-sourcing our progress on Tailwind CSS v4.0]() Original publisher: [Read original article]() Published: 2024-03-06T16:30:00Z Content type: release Language: en Sources: [Tailwind CSS Blog]() Topics: [Tailwind CSS](), [CSS](), [Rust](), [TypeScript](), [Parsing](), [PostCSS](), [Web platform]() Tags: [build](), [compatibility](), [css](), [developer-experience](), [experimental](), [features](), [framework](), [open](), [parsing](), [performance](), [pipeline](), [plugins](), [release](), [rewrite](), [rust](), [syntax](), [tailwind](), [typescript](), [web-platform]() ### AI overview Tailwind CSS announces the first public v4.0.0-alpha of its rewritten Oxide engine. The release focuses on faster builds, a smaller installed footprint, Rust-based performance improvements while retaining a TypeScript core, a custom parser, and integrated CSS processing through Lightning CSS. ### Source excerpt We just tagged the first public v4.0.0-alpha so you can start experimenting with it and help us get to a stable release later this year. ## Why Zed rewrote its GPUI UI framework from version 1 to version 2 DevFeed: [Why Zed rewrote its GPUI UI framework from version 1 to version 2]() Original publisher: [Read original article]() Author: Thorsten Ball Published: 2024-01-23T00:00:00Z Content type: opinion Language: en Sources: [Zed Industries - Blog]() Topics: [Framework](), [ui]() Tags: [framework](), [interviews](), [rewrite](), [ui]() ### AI overview An editorialized interview with Zed co-founders Nathan, Max, and Antonio about the team's multi-month rewrite of the GPUI framework from version 1 to version 2. They discuss why GPUI 1 had to change, the risks and organization of the rewrite, and the value of revisiting a system after learning from its first version. ### Source excerpt Thorsten interviews co-founders Nathan, Max, Antonio in his first week at Zed about the rewrite from GPUI1 to GPUI2 ## MLIR -- Canonicalizers and Declarative Rewrite Patterns DevFeed: [MLIR -- Canonicalizers and Declarative Rewrite Patterns]() Original publisher: [Read original article]() Published: 2023-09-20T08:00:00Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [Code](), [C++](), [Development]() Tags: [c-plus-plus](), [canonicalization](), [compilers](), [complex-numbers](), [declarative](), [deprecated](), [maintenance](), [mathematics](), [mlir](), [polynomials](), [primer](), [programming](), [rewrite](), [tablegen](), [test]() ### AI overview This tutorial explains how to implement general canonicalization patterns in MLIR. It covers both C++ canonicalizers and declarative rewrite rules in TableGen, including an identity-based polynomial rewrite and its testing considerations. ### Source excerpt Table of Contents In a previous article we defined folding functions, and used them to enable some canonicalization and the sccp constant propagation pass for the poly dialect. This time we'll see how to add more general canonicalization patterns. The code for this article is in this pull request, and as usual the commits are organized to be read in order. Why is Canonicalization Needed? MLIR provides folding as a mechanism to simplify an IR, which can result in simpler, more efficient ops (e. ## The Verse Calculus: a Core Calculus for Functional Logic Programming DevFeed: [The Verse Calculus: a Core Calculus for Functional Logic Programming]() Original publisher: [Read original article]() Published: 2022-12-12T16:23:17Z Content type: article Language: en Sources: [Lambda the Ultimate]() Topics: [Programming](), [Math and Logic]() Tags: [draft](), [functional](), [lambda-calculus](), [languages](), [logic](), [paper](), [programming](), [rewrite](), [semantics]() ### AI overview The draft paper introduces the Verse calculus (VC), a core calculus for functional logic programming. Its main contribution is a small-step rewrite semantics that enables reasoning about VC programs through successive rewrites, as with lambda calculus. The authors note that the design is still a work in progress and that the current rewrite rules may not be confluent. ### Source excerpt The Verse Calculus: a Core Calculus for Functional Logic Programming https://simon.peytonjones.org/assets/pdfs/verse-conf.pdf LENNART AUGUSTSSON, Epic Games, Sweden JOACHIM BREITNER KOEN CLAESSEN, Epic Games, Sweden RANJIT JHALA, Epic Games, USA SIMON PEYTON JONES, Epic Games, United Kingdom OLIN SHIVERS, Epic Games, USA/li> TIM SWEENEY, Epic Games, USA Functional logic languages have a rich literature, but it is tricky to give them a satisfying semantics. In this paper we describe the Verse calculus, VC, a new core calculus for functional logical programming. Our main contribution is to equip VC with a small-step rewrite semantics, so that we can reason about a VC program in the same way as one does with lambda calculus; that is, by applying successive rewrites to it. This draft paper describes our current thinking about Verse. It is very much a work in progress, not a finished product. The broad outlines of the design are stable. However, the details of the rewrite rules may well change; we think that the current rules are not confluent, in tiresome ways. (If you are knowledgeable about confluence proofs, please talk to us!)We are eager to enagage in a dialogue with the community. Please do write to us. ## Apollo iOS Client 1.0 with improved code generation DevFeed: [Apollo iOS Client 1.0 with improved code generation]() Original publisher: [Read original article]() Author: John Vajda Published: 2022-10-03T16:49:21Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [Code generation](), [iOS](), [Swift](), [GraphQL](), [SDK](), [Development]() Tags: [apollo](), [code-generation](), [command-line](), [configuration](), [developers](), [graphql](), [ios](), [maintenance](), [mobile](), [npm](), [performance](), [refactoring](), [rewrite](), [sdk](), [swift](), [tests](), [tooling](), [typescript](), [validation]() ### AI overview Apollo announces Apollo iOS Client 1.0, which replaces its previous TypeScript-based code-generation tooling with a Swift rewrite. The release describes improvements including reduced dependencies, faster performance, simpler configuration, smaller and less complex generated code, improved data validation, and better support for testing generated models. ### Source excerpt As developers, we all know code generation can save us a ton of time, but can also be a pain point if the generated code needs to be refactored. When it works as expected code generation provides us with: productivity, simplification, portability, and consistency. When it doesn't work as expected we experience consistency issues and code maintenance overhead. ## Reasons a company considers replacing its backend technology stack DevFeed: [Reasons a company considers replacing its backend technology stack]() Original publisher: [Read original article]() Published: 2020-05-10T00:00:00Z Content type: opinion Language: en Sources: [Saagar Jha]() Topics: [Back end](), [Latency](), [Compiler]() Tags: [backend](), [garbage-collection](), [latency](), [rewrite]() ### AI overview A company describes considering a replacement for its backend technology stack. The stated concerns include latency spikes associated with garbage collection and difficulty hiring developers for its existing language. ### Source excerpt When $FAMOUS_COMPANY launched in 2010, it ran on a single server in $TECHBRO_FOUNDER's garage. Since then, we've experienced explosive VC-funded growth and today we have hundreds of millions of daily active users (DAUs) from all around the globe accessing our products from our mobile apps and on $famouscompany.com. We've since made a couple of panic-induced changes to our backend to manage our technical debt (usually right after a high-profile outage) to keep our servers from keeling over. Our existing technology stack has served us well for all these years, but as we seek to grow further it's clear that a complete rewrite of our application is something which will somehow prevent us from losing two billion dollars a year on customer acquisition. ## Camera Kit Rewrite DevFeed: [Camera Kit Rewrite]() Original publisher: [Read original article]() Author: Shai Almog Published: 2019-04-29T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Android](), [Library](), [JavaScript](), [Web]() Tags: [android](), [camera](), [camera2](), [javascript](), [library](), [rewrite](), [web]() ### AI overview The article describes a rewrite of Codename One's low-level camera support. After compatibility and stability problems with Android Camera Kit, the implementation moved to Golden Eye while retaining the existing cn1lib name. The library also gained partial support for the JavaScript port and web applications, with a mostly unchanged API. ### Source excerpt The native low level camera API on Android is a disaster. It's often cited as one of the worst API's on Android. To make matters worse there are two separate API's Camera and Camera2 (yes really). You need to use Camera2 where it's available but that means no support for older devices. To solve this we picked the Android Camera Kit library when we started building our low level camera support. This proved to be a mistake. ## Five tips to get your code base in shape DevFeed: [Five tips to get your code base in shape]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2019-02-20T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Code](), [legacy](), [Development](), [test](), [App]() Tags: [architecture](), [blogs](), [bugs](), [code](), [development](), [legacy](), [legacy-code](), [refactor](), [refactoring](), [rewrite](), [software-engineering](), [test](), [tips]() ### AI overview This tutorial offers five tips for improving a legacy codebase. It advises against rewriting everything, emphasizes frequent releases and testing, and discusses the risks of complexity, insufficient testing, bugs, and delayed user value. ### Source excerpt Are you living the dream? Is your code so clean it makes your eyes just tear a little? Can't think of anything you would still like to refactor? ## Understanding Fragment Transactions and Back Navigation DevFeed: [Understanding Fragment Transactions and Back Navigation]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2017-12-18T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Transactions](), [navigation](), [App](), [implementation]() Tags: [android](), [app](), [blogs](), [events](), [fragment](), [fragments](), [implementation](), [login](), [navigation](), [rewrite](), [screen](), [transactions]() ### AI overview This tutorial investigates unexpected Android Fragment behavior when login-related Fragment transactions interact with back navigation. It explains that the transaction manager saves executed transactions rather than the Fragments themselves, which can leave multiple Fragments visible after navigating back. ### Source excerpt Do Fragment transactions and back navigation have no more secrets for you? Well then you should try to solve the mystery in this post, where a Fragment (literally) came to haunt us... ## How we got rid of 5k lines of our bash release process DevFeed: [How we got rid of 5k lines of our bash release process]() Original publisher: [Read original article]() Author: Olaf Gladis Follow Published: 2017-10-16T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [releases](), [Scripting, bash](), [Development](), [Server]() Tags: [bash](), [development](), [devops](), [legacy](), [load-balancer](), [open-source](), [redis](), [release](), [release-engineering](), [rewrite](), [server]() ### AI overview A trivago engineer describes replacing a fragile Bash-based release process. The article covers OPcache warmup failures, manual server recovery, and the legacy deployment tool's maintenance, validation, coupling, and testing problems. ### Source excerpt When I joined trivago a year ago we had problems with our releases. Read how we were able to switch from our bash release process to a new one. ## Knowing when to delete code DevFeed: [Knowing when to delete code]() Original publisher: [Read original article]() Author: Miguel Angel Quiñones Published: 2016-08-16T20:04:04Z Content type: opinion Language: en Sources: [Miguel Quinones]() Topics: [Code](), [Development](), [Application Development](), [Refactoring](), [Software]() Tags: [code](), [development](), [legacy-code](), [refactor](), [refactoring](), [regression](), [rewrite](), [tests]() ### AI overview An opinion article about deciding when to delete code in long-term projects. It discusses short-lived application code, how evolving products can make code legacy, and the trade-off between refactoring and rewriting, favoring small refactorings over large rewrites. ### Source excerpt Much of the literature and writing related to sofware development focuses on the creation, new ideas, fresh ideas and things to improve in your next project. But when is it a good moment to delete the old stuff in an long term project? Here's my short rant about this; I recently deleted a chunk of code in my current project and just felt I wanted to write my thoughts. Short-lived code Working on application development field, it is very normal that some code is very short lived. If you're looking to build systems and generic components then you're generally out of luck. Most Application code is generally short lived. In my opinion we just need to know how to deal with it. Products evolve, ideas and markets change, and the code implementing those concepts has to change to reflect the direction of an application. If your code doesn't closely relate or express the domain of your application, you're bound to have design problems, miscomunication and likely many bugs. Application code is very likely to become legacy in a very short time. That time might be even less than 1 or 2 years. Legacy code There isn't consensus on what makes code reach the dreaded legacy status. The definition has changed since it's first introduction, and nowadays we generally consider legacy the code that we didn't write. See the wikipedia entry: ...source code inherited from someone else and source code inherited from an older version of the software Or another definition: Michael Feathers introduced a definition of legacy code as code without tests, which reflects the perspective of legacy code being difficult to work with in part due to a lack of automated regression tests Many programmers generally call legacy code anything that they didn't write. While this is a very harsh treament of somebody's effort and time, it will mean that your code will become legacy in very short time as well. Refactoring vs Rewriting Legacy code is often mentioned when refactoring. The effort of writing some piece o ## 7th European Lisp Symposium DevFeed: [7th European Lisp Symposium]() Original publisher: [Read original article]() Published: 2014-05-04T22:00:00Z Content type: opinion Language: en Sources: [Dimitri Fontaine]() Topics: [Lisp](), [Common Lisp](), [Programming language](), [Python](), [Programming]() Tags: [language](), [lightning](), [lisp](), [modern](), [programming](), [programming-language](), [python](), [rewrite](), [switching](), [talk]() ### AI overview A lightning talk at the 7th European Lisp Symposium discusses rewriting pgloader from Python in Common Lisp. The stated motivation was wanting a modern programming language. ### Source excerpt A lightning talk about pgloader and why I chose to rewrite it enterily, switching from Python to Common Lisp. TL;DR -- I wanted a Modern Programming Language. ## Nginx - przydatne rewrite'y i różne sztuczki DevFeed: [Nginx - przydatne rewrite'y i różne sztuczki]() Original publisher: [Read original article]() Author: Tom Published: 2013-09-09T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [nginx](), [HTTP]() Tags: [http](), [linux](), [nginx](), [request](), [rewrite]() ### AI overview A Polish tutorial collecting practical Nginx rewrite and redirect configurations. It explains how query-string handling works, why a trailing question mark can prevent duplicated parameters, how to optimize rewrite rules, and how to redirect domains with HTTP 301 responses. ### Source excerpt Polubiłem Nginx'a i wykorzystuję go na coraz więcej sposobów. Kilka rzeczy udało mi się całkiem fajnie w nim skonfigurować i postanowiłem zebrać te przykłady by następnym razem gdy postanowię do nich sięgnąć nie musieć wertować konfigów po serwerach 😃 Słowo wstępu Niektóre rewrite'y kończą się znakiem ? - czemu? Otóż Nginx próbuje automatycznie dodawać parametry na końcu przepisanego adresu. Jeśli jednak wykorzystamy zmienną $request_uri to ona sama w sobie zawiera już parametry zapytania (czyli to co w URI znajduje się po znaku ?) i właśnie dodanie pytajnika tuż za tą zmienną powoduje że argumenty nie są dublowane. ## Raking Podspecs DevFeed: [Raking Podspecs]() Original publisher: [Read original article]() Author: Keith Smiley Published: 2013-01-04T19:09:00Z Content type: article Language: en Sources: [Keith Smiley]() Topics: [Ruby](), [rubygems](), [Objective-C](), [pull-requests]() Tags: [code](), [dependency](), [libraries](), [lint](), [objective-c](), [pull-requests](), [repo](), [rewrite](), [ruby](), [rubygems](), [tool](), [tools](), [travis]() ### AI overview The article describes automating CocoaPods podspec linting across multiple Ruby versions with rbenv and a Rakefile. ### Source excerpt I spend a decent amount of time these days helping maintain the CocoaPods specs repo by managing pull requests and issues. CococaPods is an awesome dependency manager similar to Rubygems for Objective-C projects. Unfortunately a lot of submitted podspecs haven't been correctly formatted or they're missing required information. CocoaPods has an awesome build in command pod spec lint that allows you to make sure the spec is valid and complete. Understandably people who are new to CocoaPods trying to submit their libraries are unaware of this awesome tool. Therefore when I look through the pull requests, I like to lint them myself (CocoaPods does utilize Travis but unfortunately it can't do everything). Since CocoaPods supports multiple versions of Ruby (1.8.7 and 1.9.3) to be complete ideally you'd lint them on both versions. Tools like RVM and rbenv(my tool of choice) make it easy to quickly switch between different versions of Ruby using .rvmrc and .rbenv-version respectively. As you can probably assume I wanted to automate this. So I wrote a quick Rakefile to do this for me. #!/usr/bin/env rake # NOTE: Must be using rbenv 4.0 to use `system` and `.ruby-version` ## Set your preferred ruby versions $V18 = 'system' $V19 = '1.9.3-p385' $RBENV = '.ruby-version' # The gem to use $GEM = 'cocoapods' task :default => :lint task :c => :clean desc "Lint podspecs on multiple versions of ruby with rbenv" task :lint do if Dir.glob('*.podspec').count < 1 puts "No podspecs in #{ Dir.pwd }" exit end existed = versionFileExists? if existed old_version = currentVersion end # Loop through all podspecs Dir.glob('*.podspec').each do |file| # Loop through ruby versions 2.times do |x| version = x == 0 ? $V18 : $V19 writeVersion(version) puts "Linting #{ file } on Ruby version #{ currentVersion }" puts lint(file) end end # If the dotfile already existed rewrite the original code if existed writeVersion(old_version) else File.delete($RBENV) if versionFileExists? end end desc "Delete all pod ## mod\_rewrite - wymuszenie małych liter w adresie URL DevFeed: [mod\_rewrite - wymuszenie małych liter w adresie URL]() Original publisher: [Read original article]() Author: Tom Published: 2012-09-25T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [Mod\_rewrite]() Tags: [apache](), [linux](), [mod-rewrite](), [rewrite]() ### AI overview The article explains how to use Apache mod_rewrite to force lowercase URLs. It describes why case differences can cause requests to map to nonexistent directories and presents a tolower map with redirection for URLs containing uppercase letters. ### Source excerpt Co prawda adresy URL pozwalają na stosowanie zarówno dużych jak i małych liter ale różne systemy mogą je różnie obsługiwać i może się trafić sytuacja, w której nie zechcemy by np. duże litery w ogóle pojawiały się w adresach URL. Doskonały przykład to mój niedawny wpis: Apache: ograniczenie dostępu dla zalogowanych użytkowników z mod_rewrite i mod_auth_basic . Zachodzi tam sytuacja, w której katalog użytkownika jest jego loginem małymi literami (bądź dużymi - jak kto woli), a użytkownik wpisując login może użyć zarówno małych jak i dużych liter i tutaj zaczyna się jazda. Można użyć modyfikatora NC (no case), ale to wpłynie tylko na porównania - przepisanie ścieżki na nazwę podaną przez usera (z dużymi i małymi literami) przekieruje do katalogu, którego nie ma (bo jest katalog tylko małymi/dużymi). ## Apache: ograniczenie dostępu dla zalogowanych użytkowników z mod\_rewrite i mod\_auth\_basic DevFeed: [Apache: ograniczenie dostępu dla zalogowanych użytkowników z mod\_rewrite i mod\_auth\_basic]() Original publisher: [Read original article]() Author: Tom Published: 2012-09-09T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [Mod\_rewrite](), [.NET Framework]() Tags: [apache](), [auth](), [debian](), [linux](), [login](), [mod-rewrite](), [rewrite](), [security](), [user]() ### AI overview This Polish tutorial explains how to use Apache mod_rewrite with mod_auth_basic to redirect authenticated users to directories named after their logins and prevent access to other users' directories. It describes comparing the URI login with the REMOTE_USER value using RewriteRule and RewriteCond backreferences. ### Source excerpt Niedawno trafiłem na ciekawy problem w mod_rewrite - by przekierowywać użytkowników logujących się jednym z modułów mod_auth_basic do dedykowanych im katalogów, równocześnie blokując dostęp do katalogów innych użytkowników. Nie brzmi to jakoś strasznie ale problem okazał się być całkiem nietrywialnym. Teoretyczne rozwiązanie sprowadzało się do wyszukania loginu użytkownika ze ścieżki URI i porównania z nazwą użytkownika ze zmiennej %{REMOTE_USER} - jeśli wartości się różnią to Forbidden. Ale szybko okazało się że w RewriteCond zmienne z dopasowań można podstawiać tylko w pierwszym parametrze i że o ile można RewriteCond'y połączyć wyrażeniami logicznymi typu AND/OR to nie ma możliwości porównania czy dopasowania z kolejnych RewriteCond'ów są identyczne. Po kilku dniach szperania w dokumentacji i różnych tutorialach udało mi się trafić na jedną wartościową wskazówkę ale tej stronki już nie ma, więc opiszę problem dla potomnych. [Next page]()