# runtime

Published articles for runtime.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## PHPStan custom rules

DevFeed: [PHPStan custom rules](<https://devfeed.tech/articles/phpstan-custom-rules-39472.md>)

Original publisher: [Read original article](<https://akrabat.com/phpstan-custom-rules/>)

Author: Rob

Published: 2026-03-03T11:00:00Z

Content type: tutorial

Language: en

Sources: [Rob Allen](<https://devfeed.tech/sources/rob-allen.md>)

Topics: [PHP](<https://devfeed.tech/topics/php.md>), [Exception](<https://devfeed.tech/topics/exception.md>), [Code](<https://devfeed.tech/topics/code.md>), [phpstorm](<https://devfeed.tech/topics/phpstorm.md>)

Tags: [autocomplete](<https://devfeed.tech/tags/autocomplete.md>), [class](<https://devfeed.tech/tags/class.md>), [code](<https://devfeed.tech/tags/code.md>), [container](<https://devfeed.tech/tags/container.md>), [exception](<https://devfeed.tech/tags/exception.md>), [extension](<https://devfeed.tech/tags/extension.md>), [php](<https://devfeed.tech/tags/php.md>), [phpstorm](<https://devfeed.tech/tags/phpstorm.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [settings](<https://devfeed.tech/tags/settings.md>)

### AI overview

This tutorial explains how a PHPStan custom rule can detect references to unavailable PHP classes. It also describes configuring PhpStorm to limit autocomplete to extensions used by the application.

### Source excerpt

Recently I discovered that this code passed our PHPStan level 10 checks: use http\Exception\InvalidArgumentException; // ... throw new InvalidArgumentException; I was surprised as http\Exception\InvalidArgumentException is not a class in our system. While cooling, I discovered that there's an http PHP extension and it appears that PHPStan has a stub for this which means that it accepts it as existing even if it doesn't. What we think happened is that I wrote throw new InvalidArgumentException; and... continue reading.

## Inside Go - Part 3: Garbage Collection

DevFeed: [Inside Go - Part 3: Garbage Collection](<https://devfeed.tech/articles/inside-go-part-3-garbage-collection-39765.md>)

Original publisher: [Read original article](<https://furkankolcu.com/post/inside-go-part-3-garbage-collection>)

Author: Furkan Kolcu

Published: 2025-09-16T14:30:04Z

Content type: tutorial

Language: en

Sources: [Furkan Kolcu - Software Engineer Blog](<https://devfeed.tech/sources/furkan-kolcu-software-engineer-blog.md>)

Topics: [Go Language](<https://devfeed.tech/topics/go-language.md>), [Algorithms](<https://devfeed.tech/topics/algorithms.md>)

Tags: [algorithm](<https://devfeed.tech/tags/algorithm.md>), [garbage-collection](<https://devfeed.tech/tags/garbage-collection.md>), [go](<https://devfeed.tech/tags/go.md>), [go-garbage-collector](<https://devfeed.tech/tags/go-garbage-collector.md>), [gogc](<https://devfeed.tech/tags/gogc.md>), [golang](<https://devfeed.tech/tags/golang.md>), [inside-go](<https://devfeed.tech/tags/inside-go.md>), [performance](<https://devfeed.tech/tags/performance.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [technology](<https://devfeed.tech/tags/technology.md>)

### AI overview

This tutorial explains the evolution of Go's garbage collector from stop-the-world pauses to mostly concurrent collection. It introduces tri-color marking, explains the purpose of write barriers, and indicates that it will cover GOGC tuning.

### Source excerpt

How Go's GC grew from full pauses to mostly concurrent, what the tri-color algorithm does, why write barriers matter, and how to tune GC with GOGC without shooting yourself in the foot are how we will walk through in this part.

## 重新思考 Go：了解程序在线上是如何运行的

DevFeed: [重新思考 Go：了解程序在线上是如何运行的](<https://devfeed.tech/articles/go-40988.md>)

Original publisher: [Read original article](<https://blog.joway.io/posts/golang-rethink-program-in-realworld/>)

Author: Joway

Published: 2024-12-10T00:00:00Z

Content type: article

Language: zh

Sources: [Random Thoughts](<https://devfeed.tech/sources/random-thoughts.md>)

Topics: [Go Language](<https://devfeed.tech/topics/go-language.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [cpu](<https://devfeed.tech/topics/cpu.md>), [cgroups](<https://devfeed.tech/topics/cgroups.md>), [Linux](<https://devfeed.tech/topics/linux.md>)

Tags: [cgroups](<https://devfeed.tech/tags/cgroups.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [go](<https://devfeed.tech/tags/go.md>), [golang](<https://devfeed.tech/tags/golang.md>), [k8s](<https://devfeed.tech/tags/k8s.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mechanical-sympathy](<https://devfeed.tech/tags/mechanical-sympathy.md>), [quota](<https://devfeed.tech/tags/quota.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [tech](<https://devfeed.tech/tags/tech.md>), [waiting](<https://devfeed.tech/tags/waiting.md>)

### AI overview

This article examines how Go programs run in production environments, focusing on the relationship between Kubernetes CPU quotas, physical CPU availability, cgroups, and Go's GOMAXPROCS setting. It explains that CPU quota limits aggregate execution time, while available parallelism can depend on the host's physical cores and the program's design. It also introduces scheduling latency and the factors that affect the computing resources a Go service actually receives.

### Source excerpt

重新思考 Go 系列：这个系列希望结合工作中在 Go 编程与性能优化中遇到过的问题，探讨 Go 在语言哲学、底层实现和现实需求三者之间关系与矛盾。 前言 过去一段时间，在大量的线上服务 case study 过程中，逐步深入了解了如今的业务 Go 进程是如何在一系列繁杂的基础设施之上运行的。有些表现在意料之中，也有一些出乎意料的发现。

## Weak Learning, Boosting, and the AdaBoost algorithm

DevFeed: [Weak Learning, Boosting, and the AdaBoost algorithm](<https://devfeed.tech/articles/weak-learning-boosting-and-the-adaboost-algorithm-40383.md>)

Original publisher: [Read original article](<https://www.jeremykun.com/2015/05/18/boosting-census/>)

Published: 2015-05-18T09:00:00Z

Content type: tutorial

Language: en

Sources: [Jeremy Kun](<https://devfeed.tech/sources/jeremy-kun.md>)

Topics: [Algorithm](<https://devfeed.tech/topics/algorithm.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [algorithm](<https://devfeed.tech/tags/algorithm.md>), [better](<https://devfeed.tech/tags/better.md>), [boosting](<https://devfeed.tech/tags/boosting.md>), [classification](<https://devfeed.tech/tags/classification.md>), [distribution](<https://devfeed.tech/tags/distribution.md>), [efficiently](<https://devfeed.tech/tags/efficiently.md>), [function](<https://devfeed.tech/tags/function.md>), [learner](<https://devfeed.tech/tags/learner.md>), [learning](<https://devfeed.tech/tags/learning.md>), [models](<https://devfeed.tech/tags/models.md>), [number](<https://devfeed.tech/tags/number.md>), [pac-learning](<https://devfeed.tech/tags/pac-learning.md>), [re](<https://devfeed.tech/tags/re.md>), [runtime](<https://devfeed.tech/tags/runtime.md>)

### AI overview

This article introduces learning models in the context of Probably Approximately Correct (PAC) learning and compares the usual PAC model with weak PAC learning. It explains that weak learning requires accuracy only slightly better than random guessing and states that weak and strong learning are equivalent.

### Source excerpt

When addressing the question of what it means for an algorithm to learn, one can imagine many different models, and there are quite a few. This invariably raises the question of which models are "the same" and which are "different," along with a precise description of how we're comparing models. We've seen one learning model so far, called Probably Approximately Correct (PAC), which espouses the following answer to the learning question:

## Static and extern keywords in C

DevFeed: [Static and extern keywords in C](<https://devfeed.tech/articles/static-and-extern-keywords-in-c-40742.md>)

Original publisher: [Read original article](<https://radek.io/posts/static-and-extern-keywords-in-c/>)

Published: 2011-09-01T00:00:00Z

Content type: tutorial

Language: en

Sources: [Radek Pazdera](<https://devfeed.tech/sources/radek-pazdera.md>)

Topics: [C](<https://devfeed.tech/topics/c.md>), [standard](<https://devfeed.tech/topics/standard.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [c](<https://devfeed.tech/tags/c.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [external](<https://devfeed.tech/tags/external.md>), [function](<https://devfeed.tech/tags/function.md>), [local-variables](<https://devfeed.tech/tags/local-variables.md>), [memory](<https://devfeed.tech/tags/memory.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [scope](<https://devfeed.tech/tags/scope.md>), [standard](<https://devfeed.tech/tags/standard.md>)

### AI overview

A tutorial explaining how the static and extern keywords in C affect linkage, storage duration, memory allocation, and visibility across scopes and compilation units. It also describes external, internal, and no linkage, along with static and automatic storage duration.

### Source excerpt

What does the C standard actually say about these?