Inlining Critical #CSS: Does It Make Your Website Faster? "Learn what critical CSS is, how to inline it to improve page load #performance, and understand the trade-offs before implementing it on your website." www.debugbear.com/blog/critica...
Inlining Critical CSS: Does It Make Your Website Faster? | DebugBear
Learn what critical CSS is, how to inline it to improve page load performance, and understand the trade-offs before implementing it on your website.
www.debugbear.com
November 7, 2025 at 6:03 PM
Inlining Critical #CSS: Does It Make Your Website Faster? "Learn what critical CSS is, how to inline it to improve page load #performance, and understand the trade-offs before implementing it on your website." www.debugbear.com/blog/critica...
Why I like and keep working on Rust
October 16, 2025 at 11:52 PM
Why I like and keep working on Rust
The new version of my #BinaryNinja plugin Obfuscation Analysis (v1.2) adds recursive function inlining in the decompiler.
It collapses call-heavy code into a single function; analysis, constant propagation, DCE and other analyses work across boundaries.
github.com/mrphrazer/ob...
It collapses call-heavy code into a single function; analysis, constant propagation, DCE and other analyses work across boundaries.
github.com/mrphrazer/ob...
October 11, 2025 at 3:27 PM
The new version of my #BinaryNinja plugin Obfuscation Analysis (v1.2) adds recursive function inlining in the decompiler.
It collapses call-heavy code into a single function; analysis, constant propagation, DCE and other analyses work across boundaries.
github.com/mrphrazer/ob...
It collapses call-heavy code into a single function; analysis, constant propagation, DCE and other analyses work across boundaries.
github.com/mrphrazer/ob...
Are you streaming into your Lakehouse?
Traditional formats suffered with the “many small files” problem — OLAP engines merge them reactively with long jobs. ⏳
DuckLake takes a proactive path: Data Inlining + async flush to parquet while always keeping data queryable ⚡
Traditional formats suffered with the “many small files” problem — OLAP engines merge them reactively with long jobs. ⏳
DuckLake takes a proactive path: Data Inlining + async flush to parquet while always keeping data queryable ⚡
September 29, 2025 at 2:13 PM
Are you streaming into your Lakehouse?
Traditional formats suffered with the “many small files” problem — OLAP engines merge them reactively with long jobs. ⏳
DuckLake takes a proactive path: Data Inlining + async flush to parquet while always keeping data queryable ⚡
Traditional formats suffered with the “many small files” problem — OLAP engines merge them reactively with long jobs. ⏳
DuckLake takes a proactive path: Data Inlining + async flush to parquet while always keeping data queryable ⚡
If you don’t put some effort into memory management, generated code size, dyn traits and disabling inlining where it helps code layout, using Rust won’t make your system faster than the version written in a language with a GC and/or JIT.
September 15, 2025 at 11:42 PM
If you don’t put some effort into memory management, generated code size, dyn traits and disabling inlining where it helps code layout, using Rust won’t make your system faster than the version written in a language with a GC and/or JIT.
We have special troll-mcyoung passes in the compiler.
I might wonder if that is some sort of a NOP-encoding, for inlining (we mark inlines with NOPs), but otherwise that's puzzling.
I might wonder if that is some sort of a NOP-encoding, for inlining (we mark inlines with NOPs), but otherwise that's puzzling.
March 20, 2025 at 10:05 PM
We have special troll-mcyoung passes in the compiler.
I might wonder if that is some sort of a NOP-encoding, for inlining (we mark inlines with NOPs), but otherwise that's puzzling.
I might wonder if that is some sort of a NOP-encoding, for inlining (we mark inlines with NOPs), but otherwise that's puzzling.
can we get const enum inlining back
Today we're thrilled to announce our effort to port the TypeScript compiler and language service to native code, gaining a 10x speed boost in build times and editor responsiveness!
devblogs.microsoft.com/typescript/t...
devblogs.microsoft.com/typescript/t...
A 10x Faster TypeScript - TypeScript
Embarking on a native port of the existing TypeScript compiler and toolset to achieve a 10x performance speed-up.
devblogs.microsoft.com
March 11, 2025 at 3:37 PM
can we get const enum inlining back
Fwiw shaderfrog is a code editor, you still write raw GLSL, you can see the source code by double clicking red or green nodes in the link above. Connecting nodes is like importing the other shader as a module, and inlining its main function. “Hybrid” graph and code editing
March 11, 2025 at 1:35 AM
Fwiw shaderfrog is a code editor, you still write raw GLSL, you can see the source code by double clicking red or green nodes in the link above. Connecting nodes is like importing the other shader as a module, and inlining its main function. “Hybrid” graph and code editing
I maybe do with a little less reposts but honestly don't mind inlining replies and including the original post. Kinda gives a little flavor, gives you a little tactical-network-awareness (TAN)
June 2, 2023 at 4:21 PM
I maybe do with a little less reposts but honestly don't mind inlining replies and including the original post. Kinda gives a little flavor, gives you a little tactical-network-awareness (TAN)
i forgot to mention the abbreviated syntax! for anyone reading, yes! you can skip curly braces if you're just returning the result of the first statement. it's really nice, especially for inlining.
January 12, 2025 at 3:21 PM
i forgot to mention the abbreviated syntax! for anyone reading, yes! you can skip curly braces if you're just returning the result of the first statement. it's really nice, especially for inlining.
i still think it's wild that there's no standard way to induce icache pressure in microbenchmarks.
this is probably one of the most common systemic errors in microbenchmarks (more inlining will almost always improve a microbenchmark, but will thrash icache in a real application)
this is probably one of the most common systemic errors in microbenchmarks (more inlining will almost always improve a microbenchmark, but will thrash icache in a real application)
May 27, 2025 at 2:34 PM
i still think it's wild that there's no standard way to induce icache pressure in microbenchmarks.
this is probably one of the most common systemic errors in microbenchmarks (more inlining will almost always improve a microbenchmark, but will thrash icache in a real application)
this is probably one of the most common systemic errors in microbenchmarks (more inlining will almost always improve a microbenchmark, but will thrash icache in a real application)
Context Transference One of the hardest refactorings to get right is the balance between extract and inlining of functions. Often people struggle to understand why sometimes when they "do the right thing" and extract a function, their code quality feels...
| Details | Interest | Feed |
| Details | Interest | Feed |
Origin
dev.to
May 30, 2025 at 8:41 AM
A Clang regression related to switch statements and inlining Discussion
A Clang regression related to switch statements and inlining
nicula.xyz
February 21, 2025 at 6:00 AM
A Clang regression related to switch statements and inlining Discussion
so I've been cooking how no code would actually be distributed. the psycho thing you would do is compile it to go and check that in, and now it's an ordinary package. there is one large issue though: how does cross-module inlining work?!
February 12, 2025 at 8:41 AM
so I've been cooking how no code would actually be distributed. the psycho thing you would do is compile it to go and check that in, and now it's an ordinary package. there is one large issue though: how does cross-module inlining work?!
Inlining in the Glasgow Haskell Compiler: empirical investigation and improvement. ~ Celeste Hollenbeck. era.ed.ac.uk/bitstream/ha... #Haskell #FunctionalProgramming
July 24, 2025 at 10:28 AM
Inlining in the Glasgow Haskell Compiler: empirical investigation and improvement. ~ Celeste Hollenbeck. era.ed.ac.uk/bitstream/ha... #Haskell #FunctionalProgramming
But if we inline it every place, we'll have non-unique symbol names. Therefore the compiler and linker normally ignore it because the definitions of the inlining ought to be all the same. Linker should be able to pick any copy. But if we have an evil twin... :( #bangbangcon
January 13, 2025 at 11:35 AM
But if we inline it every place, we'll have non-unique symbol names. Therefore the compiler and linker normally ignore it because the definitions of the inlining ought to be all the same. Linker should be able to pick any copy. But if we have an evil twin... :( #bangbangcon
Oh neat! We see that embedded Rust sometimes, but it's usually a timing thing (debug is like 100x slower), or a resource thing (no inlining means a ton more stack usage, which can overflow and cause fun Bonus Behavior).
That had to be fun to debug tho
That had to be fun to debug tho
February 9, 2024 at 6:52 PM
Oh neat! We see that embedded Rust sometimes, but it's usually a timing thing (debug is like 100x slower), or a resource thing (no inlining means a ton more stack usage, which can overflow and cause fun Bonus Behavior).
That had to be fun to debug tho
That had to be fun to debug tho
NEVERMIND
false alarm
turns out it's even faster without all the factoring i did, just by inlining the functions qwq
false alarm
turns out it's even faster without all the factoring i did, just by inlining the functions qwq
February 10, 2025 at 6:52 AM
NEVERMIND
false alarm
turns out it's even faster without all the factoring i did, just by inlining the functions qwq
false alarm
turns out it's even faster without all the factoring i did, just by inlining the functions qwq
If you use node v23, the wasm version should already be faster than the JS version (I see 6.5 vs 7.5s) while on v22 they are about the same speed.
The speedup is caused by inlining being enabled for wasm by default now. (To see the effect, " node --no-experimental-wasm-inlining ..." disables it.)
The speedup is caused by inlining being enabled for wasm by default now. (To see the effect, " node --no-experimental-wasm-inlining ..." disables it.)
November 17, 2024 at 10:31 PM
If you use node v23, the wasm version should already be faster than the JS version (I see 6.5 vs 7.5s) while on v22 they are about the same speed.
The speedup is caused by inlining being enabled for wasm by default now. (To see the effect, " node --no-experimental-wasm-inlining ..." disables it.)
The speedup is caused by inlining being enabled for wasm by default now. (To see the effect, " node --no-experimental-wasm-inlining ..." disables it.)
but now you can't use box<T> as a field in T because now the layout of box<T> depends on T. which I guess means an extra type parameter to explicitly disable inlining. but now that's a separate type... so it cant interop with other box<T> values...
February 24, 2025 at 11:30 PM
but now you can't use box<T> as a field in T because now the layout of box<T> depends on T. which I guess means an extra type parameter to explicitly disable inlining. but now that's a separate type... so it cant interop with other box<T> values...
I didn't want to believe it at first. I thought that compilers were above and beyond more intelligent than I ever way. And then I figured out that, aside from inlining and replacing mathematical expressions (LEA instead of MUL, MUL instead of DIV) they're really fugging stupid.
March 27, 2025 at 5:07 AM
I didn't want to believe it at first. I thought that compilers were above and beyond more intelligent than I ever way. And then I figured out that, aside from inlining and replacing mathematical expressions (LEA instead of MUL, MUL instead of DIV) they're really fugging stupid.
If it worked through TS and re-exports this would get most of the value of TS const enum inlining but for all scalar values.
July 27, 2025 at 12:33 PM
If it worked through TS and re-exports this would get most of the value of TS const enum inlining but for all scalar values.
Yes! Very much so.
Inlining multiple different CSS files into a single file changes how that CSS will behave. For example url's to images for backgrounds. Or duplicate and cyclical imports of CSS files.
With at-sheet it could be possible to make a CSS bundler that behaves correctly in all cases
Inlining multiple different CSS files into a single file changes how that CSS will behave. For example url's to images for backgrounds. Or duplicate and cyclical imports of CSS files.
With at-sheet it could be possible to make a CSS bundler that behaves correctly in all cases
April 27, 2025 at 6:21 AM
Yes! Very much so.
Inlining multiple different CSS files into a single file changes how that CSS will behave. For example url's to images for backgrounds. Or duplicate and cyclical imports of CSS files.
With at-sheet it could be possible to make a CSS bundler that behaves correctly in all cases
Inlining multiple different CSS files into a single file changes how that CSS will behave. For example url's to images for backgrounds. Or duplicate and cyclical imports of CSS files.
With at-sheet it could be possible to make a CSS bundler that behaves correctly in all cases
R2R + Jit issue when inlining intrinsic methods (115429) https://github.com/dotnet/runtime/issues/115429
R2R + Jit issue when inlining intrinsic methods · Issue #115429 · dotnet/runtime
Based on a discussion in the open PR, when an intrinsic is JIT'd an AV occurs later in CEEInfo::getArgType when it calls GetModule(sig->scope) which calls GetDynamicResolver(scope)->GetDynamicMetho...
github.com
May 9, 2025 at 5:42 PM
R2R + Jit issue when inlining intrinsic methods (115429) https://github.com/dotnet/runtime/issues/115429