Pagwin/new_blog
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

some future notes written to partially retract stupid statements

Browse source
This commit is contained in:
Pagwin 2025-05-26 16:32:14 -04:00
parent 3905b719c0
commit c30aea7451
3 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
posts/mineflayer_why.md
View file

@ -5,6 +5,10 @@ date: 2021-01-10
draft: false
tags: []
---
**Future pagwin note: this post is rather immature, I'm keeping it up mostly for historical record, in hindsight I shouldn't have written it.
Either I should've made pull request(s) to improve mineflayer or shut the fuck up.**
## Preface
Given I'm gonna be complaining about [mineflayer](https://github.com/PrismarineJS/mineflayer) you may be wondering why I don't roll with something else given my complaints. The problem with that is that there is nothing else to my knowledge or at least nothing else high level, not even in other languages. There probably is and I just didn't look hard enough but oh well. Also I would've built up my own thing from scratch but reverse engineering/reimplementing a network protocol without official docs and without even unofficial docs if you're trying to do stuff with older versions is kinda hard and if you wanna see how far I got then you can look at the [repo with my work](https://github.com/Pagwin-Fedora/McProtocolLearning) and I refused to work with the slightly lower level(relative to mineflayer) [node minecraft protocol](https://github.com/PrismarineJS/node-minecraft-protocol)(made by the same person) because if I'm using someone else's work I may as well go all the way to the highest level
## Why?

2
posts/rust_type_hiccups.md
View file

@ -48,6 +48,8 @@ Nope
## So what was the other hiccup?
Future Pagwin note: it turns out that solving this is [really hard](https://hackmd.io/@BoxyUwU/BJ6_bfmD0#Why-does-generic_const_exprs-not-work)
Oh yeah, there was a separate hiccup. Yeah that hiccup came from me trying to do SI-derived units via const generics, my minimum viable product version looked something like this
```rs
struct Measure<const km:i16, const sec:i16, const kg:i16>{

2
posts/serenity_why.md
View file

@ -10,6 +10,8 @@ draft: false
tags: []
---
**Future pagwin note: this post is rather immature, I'm keeping it up mostly for historical record, in hindsight I shouldn't have written it.**
This is the second blog article I've written dissing on how a library does something, the [first time](/blog/mineflayer_why) being effectively "Mineflayer doesn't do things the way I want it to and that annoys me". This article will probably follow in that tradition but unlike the Mineflayer one where I would've been inconvenienced to do what I want with Serenity I need to make my code potentially unsound to do what I want.
## What is Serenity?