transition

config.toml

@@ -1,10 +1,10 @@
 baseURL = "/"
 languageCode = "en-us"
-title = "nilstriebs blog"
+title = "Noratrieb's blog"
 theme = "terminal"
 
 [author]
-name = "Nilstrieb"
+name = "Noratrieb"
 
 [params]
 contentTypeName = "posts"
@@ -12,4 +12,4 @@ themeColor = "orange"
 centerTheme = true
 
 [params.logo]
-logoText = "nilstriebs blog"
+logoText = "noratrieb's blog"

content/posts/box-is-a-unique-type.md

@@ -1,8 +1,8 @@
 +++
 title = "Box Is a Unique Type"
 date = "2022-07-23"
-author = "Nilstrieb"
-authorTwitter = "@Nilstrieb"
+author = "Noratrieb"
+authorTwitter = "@Noratrieb"
 tags = ["rust", "unsafe code"]
 keywords = ["box", "noalias"]
 description = "About better aliasing semantics for `Box<T>`"
@@ -218,7 +218,7 @@ that can bring clear performance wins (for `noalias` on `&mut T`, those were   m
 future?** For the latter, there is no simple answer. For the former, there is. `rustc` has [_no_ performance improvements](https://github.com/rust-lang/rust/pull/99527) 
 from being compiled with `noalias` on `Box<T>`, but this isn't really representative since rustc mostly uses arenas instead of box internally.
 
-I have also benchmarked a few crates from the ecosystem with and without noalias on box, and the [results](https://gist.github.com/Nilstrieb/9a0751fb9fd1044a30ab55cef9a7d335)
+I have also benchmarked a few crates from the ecosystem with and without noalias on box, and the [results](https://gist.github.com/Noratrieb/9a0751fb9fd1044a30ab55cef9a7d335)
 were inconclusive. (At the time of writing, only regex-syntax, tokio, and syn have been benchmarked.) regex-syntax showed no changes. Tokio showed a few improvements without noalias
 which is very weird, so maybe the benchmarks aren't really good or something else was going on. And syn tended towards minor regressions without noalias, but the benchmarks had high
 jitter so no real conclusion can be reached from this either, at least in my eyes, but I don't have a lot of experience with benchmarks. Therefore, I would love for more people

content/posts/item-patterns-and-struct-else.md

@@ -1,8 +1,8 @@
 +++
 title = "Item Patterns And Struct Else"
 date = "2023-03-17"
-author = "Nilstrieb"
-authorTwitter = "@Nilstrieb"
+author = "Noratrieb"
+authorTwitter = "@Noratrieb"
 tags = ["rust", "language-design"]
 keywords = ["design"]
 description = "Bringing more expressiveness to our items"
@@ -95,7 +95,7 @@ This doesn't sound too bad. This is where the executed code resides. But it come
 
 # Items and sadness
 
-Items have a hard life. They are the parents of everything important. `struct`, `enum`, `const`, `mod`, `fn`, `union`, `global_asm` are all things we use daily, yet their grammar is very limited. ("free the items" was an alternative blog post title, although "freeing" generally remains a concern of [my C style guide](https://nilstrieb.github.io/nilstrieb-c-style-guide-edition-2/)).
+Items have a hard life. They are the parents of everything important. `struct`, `enum`, `const`, `mod`, `fn`, `union`, `global_asm` are all things we use daily, yet their grammar is very limited. ("free the items" was an alternative blog post title, although "freeing" generally remains a concern of [my C style guide](https://noratrieb.github.io/nilstrieb-c-style-guide-edition-2/)).
 
 
 For example, see the following code where we declare a few constants.

content/posts/the-inevitable-doom.md

@@ -1,8 +1,8 @@
 +++
 title = "The Inevitable Doom"
 date = "2024-01-13"
-author = "Nilstrieb"
-authorTwitter = "@Nilstrieb"
+author = "Noratrieb"
+authorTwitter = "@Noratrieb"
 tags = ["story"]
 keywords = ["story"]
 description = "A short story about AI"

static/CNAME

@@ -1 +0,0 @@
-blog.nilstrieb.dev