sam/blog
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

init

Browse source
This commit is contained in:
sam 2024-12-02 02:33:20 +01:00
commit 6109bae0a5
Signed by: sam
GPG key ID: B4EF20DDE721CAA1
25 changed files with 2294 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
.gitmodules vendored Normal file
View file

@ -0,0 +1,3 @@
[submodule "themes/hugo-bearblog"]
path = themes/hugo-bearblog
url = https://github.com/janraasch/hugo-bearblog.git

0
.hugo_build.lock Normal file
View file

438
LICENSE Normal file
View file

@ -0,0 +1,438 @@
Attribution-NonCommercial-ShareAlike 4.0 International
=======================================================================
Creative Commons Corporation ("Creative Commons") is not a law firm and
does not provide legal services or legal advice. Distribution of
Creative Commons public licenses does not create a lawyer-client or
other relationship. Creative Commons makes its licenses and related
information available on an "as-is" basis. Creative Commons gives no
warranties regarding its licenses, any material licensed under their
terms and conditions, or any related information. Creative Commons
disclaims all liability for damages resulting from their use to the
fullest extent possible.
Using Creative Commons Public Licenses
Creative Commons public licenses provide a standard set of terms and
conditions that creators and other rights holders may use to share
original works of authorship and other material subject to copyright
and certain other rights specified in the public license below. The
following considerations are for informational purposes only, are not
exhaustive, and do not form part of our licenses.
Considerations for licensors: Our public licenses are
intended for use by those authorized to give the public
permission to use material in ways otherwise restricted by
copyright and certain other rights. Our licenses are
irrevocable. Licensors should read and understand the terms
and conditions of the license they choose before applying it.
Licensors should also secure all rights necessary before
applying our licenses so that the public can reuse the
material as expected. Licensors should clearly mark any
material not subject to the license. This includes other CC-
licensed material, or material used under an exception or
limitation to copyright. More considerations for licensors:
wiki.creativecommons.org/Considerations_for_licensors
Considerations for the public: By using one of our public
licenses, a licensor grants the public permission to use the
licensed material under specified terms and conditions. If
the licensor's permission is not necessary for any reason--for
example, because of any applicable exception or limitation to
copyright--then that use is not regulated by the license. Our
licenses grant only permissions under copyright and certain
other rights that a licensor has authority to grant. Use of
the licensed material may still be restricted for other
reasons, including because others have copyright or other
rights in the material. A licensor may make special requests,
such as asking that all changes be marked or described.
Although not required by our licenses, you are encouraged to
respect those requests where reasonable. More considerations
for the public:
wiki.creativecommons.org/Considerations_for_licensees
=======================================================================
Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
Public License
By exercising the Licensed Rights (defined below), You accept and agree
to be bound by the terms and conditions of this Creative Commons
Attribution-NonCommercial-ShareAlike 4.0 International Public License
("Public License"). To the extent this Public License may be
interpreted as a contract, You are granted the Licensed Rights in
consideration of Your acceptance of these terms and conditions, and the
Licensor grants You such rights in consideration of benefits the
Licensor receives from making the Licensed Material available under
these terms and conditions.
Section 1 -- Definitions.
a. Adapted Material means material subject to Copyright and Similar
Rights that is derived from or based upon the Licensed Material
and in which the Licensed Material is translated, altered,
arranged, transformed, or otherwise modified in a manner requiring
permission under the Copyright and Similar Rights held by the
Licensor. For purposes of this Public License, where the Licensed
Material is a musical work, performance, or sound recording,
Adapted Material is always produced where the Licensed Material is
synched in timed relation with a moving image.
b. Adapter's License means the license You apply to Your Copyright
and Similar Rights in Your contributions to Adapted Material in
accordance with the terms and conditions of this Public License.
c. BY-NC-SA Compatible License means a license listed at
creativecommons.org/compatiblelicenses, approved by Creative
Commons as essentially the equivalent of this Public License.
d. Copyright and Similar Rights means copyright and/or similar rights
closely related to copyright including, without limitation,
performance, broadcast, sound recording, and Sui Generis Database
Rights, without regard to how the rights are labeled or
categorized. For purposes of this Public License, the rights
specified in Section 2(b)(1)-(2) are not Copyright and Similar
Rights.
e. Effective Technological Measures means those measures that, in the
absence of proper authority, may not be circumvented under laws
fulfilling obligations under Article 11 of the WIPO Copyright
Treaty adopted on December 20, 1996, and/or similar international
agreements.
f. Exceptions and Limitations means fair use, fair dealing, and/or
any other exception or limitation to Copyright and Similar Rights
that applies to Your use of the Licensed Material.
g. License Elements means the license attributes listed in the name
of a Creative Commons Public License. The License Elements of this
Public License are Attribution, NonCommercial, and ShareAlike.
h. Licensed Material means the artistic or literary work, database,
or other material to which the Licensor applied this Public
License.
i. Licensed Rights means the rights granted to You subject to the
terms and conditions of this Public License, which are limited to
all Copyright and Similar Rights that apply to Your use of the
Licensed Material and that the Licensor has authority to license.
j. Licensor means the individual(s) or entity(ies) granting rights
under this Public License.
k. NonCommercial means not primarily intended for or directed towards
commercial advantage or monetary compensation. For purposes of
this Public License, the exchange of the Licensed Material for
other material subject to Copyright and Similar Rights by digital
file-sharing or similar means is NonCommercial provided there is
no payment of monetary compensation in connection with the
exchange.
l. Share means to provide material to the public by any means or
process that requires permission under the Licensed Rights, such
as reproduction, public display, public performance, distribution,
dissemination, communication, or importation, and to make material
available to the public including in ways that members of the
public may access the material from a place and at a time
individually chosen by them.
m. Sui Generis Database Rights means rights other than copyright
resulting from Directive 96/9/EC of the European Parliament and of
the Council of 11 March 1996 on the legal protection of databases,
as amended and/or succeeded, as well as other essentially
equivalent rights anywhere in the world.
n. You means the individual or entity exercising the Licensed Rights
under this Public License. Your has a corresponding meaning.
Section 2 -- Scope.
a. License grant.
1. Subject to the terms and conditions of this Public License,
the Licensor hereby grants You a worldwide, royalty-free,
non-sublicensable, non-exclusive, irrevocable license to
exercise the Licensed Rights in the Licensed Material to:
a. reproduce and Share the Licensed Material, in whole or
in part, for NonCommercial purposes only; and
b. produce, reproduce, and Share Adapted Material for
NonCommercial purposes only.
2. Exceptions and Limitations. For the avoidance of doubt, where
Exceptions and Limitations apply to Your use, this Public
License does not apply, and You do not need to comply with
its terms and conditions.
3. Term. The term of this Public License is specified in Section
6(a).
4. Media and formats; technical modifications allowed. The
Licensor authorizes You to exercise the Licensed Rights in
all media and formats whether now known or hereafter created,
and to make technical modifications necessary to do so. The
Licensor waives and/or agrees not to assert any right or
authority to forbid You from making technical modifications
necessary to exercise the Licensed Rights, including
technical modifications necessary to circumvent Effective
Technological Measures. For purposes of this Public License,
simply making modifications authorized by this Section 2(a)
(4) never produces Adapted Material.
5. Downstream recipients.
a. Offer from the Licensor -- Licensed Material. Every
recipient of the Licensed Material automatically
receives an offer from the Licensor to exercise the
Licensed Rights under the terms and conditions of this
Public License.
b. Additional offer from the Licensor -- Adapted Material.
Every recipient of Adapted Material from You
automatically receives an offer from the Licensor to
exercise the Licensed Rights in the Adapted Material
under the conditions of the Adapter's License You apply.
c. No downstream restrictions. You may not offer or impose
any additional or different terms or conditions on, or
apply any Effective Technological Measures to, the
Licensed Material if doing so restricts exercise of the
Licensed Rights by any recipient of the Licensed
Material.
6. No endorsement. Nothing in this Public License constitutes or
may be construed as permission to assert or imply that You
are, or that Your use of the Licensed Material is, connected
with, or sponsored, endorsed, or granted official status by,
the Licensor or others designated to receive attribution as
provided in Section 3(a)(1)(A)(i).
b. Other rights.
1. Moral rights, such as the right of integrity, are not
licensed under this Public License, nor are publicity,
privacy, and/or other similar personality rights; however, to
the extent possible, the Licensor waives and/or agrees not to
assert any such rights held by the Licensor to the limited
extent necessary to allow You to exercise the Licensed
Rights, but not otherwise.
2. Patent and trademark rights are not licensed under this
Public License.
3. To the extent possible, the Licensor waives any right to
collect royalties from You for the exercise of the Licensed
Rights, whether directly or through a collecting society
under any voluntary or waivable statutory or compulsory
licensing scheme. In all other cases the Licensor expressly
reserves any right to collect such royalties, including when
the Licensed Material is used other than for NonCommercial
purposes.
Section 3 -- License Conditions.
Your exercise of the Licensed Rights is expressly made subject to the
following conditions.
a. Attribution.
1. If You Share the Licensed Material (including in modified
form), You must:
a. retain the following if it is supplied by the Licensor
with the Licensed Material:
i. identification of the creator(s) of the Licensed
Material and any others designated to receive
attribution, in any reasonable manner requested by
the Licensor (including by pseudonym if
designated);
ii. a copyright notice;
iii. a notice that refers to this Public License;
iv. a notice that refers to the disclaimer of
warranties;
v. a URI or hyperlink to the Licensed Material to the
extent reasonably practicable;
b. indicate if You modified the Licensed Material and
retain an indication of any previous modifications; and
c. indicate the Licensed Material is licensed under this
Public License, and include the text of, or the URI or
hyperlink to, this Public License.
2. You may satisfy the conditions in Section 3(a)(1) in any
reasonable manner based on the medium, means, and context in
which You Share the Licensed Material. For example, it may be
reasonable to satisfy the conditions by providing a URI or
hyperlink to a resource that includes the required
information.
3. If requested by the Licensor, You must remove any of the
information required by Section 3(a)(1)(A) to the extent
reasonably practicable.
b. ShareAlike.
In addition to the conditions in Section 3(a), if You Share
Adapted Material You produce, the following conditions also apply.
1. The Adapter's License You apply must be a Creative Commons
license with the same License Elements, this version or
later, or a BY-NC-SA Compatible License.
2. You must include the text of, or the URI or hyperlink to, the
Adapter's License You apply. You may satisfy this condition
in any reasonable manner based on the medium, means, and
context in which You Share Adapted Material.
3. You may not offer or impose any additional or different terms
or conditions on, or apply any Effective Technological
Measures to, Adapted Material that restrict exercise of the
rights granted under the Adapter's License You apply.
Section 4 -- Sui Generis Database Rights.
Where the Licensed Rights include Sui Generis Database Rights that
apply to Your use of the Licensed Material:
a. for the avoidance of doubt, Section 2(a)(1) grants You the right
to extract, reuse, reproduce, and Share all or a substantial
portion of the contents of the database for NonCommercial purposes
only;
b. if You include all or a substantial portion of the database
contents in a database in which You have Sui Generis Database
Rights, then the database in which You have Sui Generis Database
Rights (but not its individual contents) is Adapted Material,
including for purposes of Section 3(b); and
c. You must comply with the conditions in Section 3(a) if You Share
all or a substantial portion of the contents of the database.
For the avoidance of doubt, this Section 4 supplements and does not
replace Your obligations under this Public License where the Licensed
Rights include other Copyright and Similar Rights.
Section 5 -- Disclaimer of Warranties and Limitation of Liability.
a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
c. The disclaimer of warranties and limitation of liability provided
above shall be interpreted in a manner that, to the extent
possible, most closely approximates an absolute disclaimer and
waiver of all liability.
Section 6 -- Term and Termination.
a. This Public License applies for the term of the Copyright and
Similar Rights licensed here. However, if You fail to comply with
this Public License, then Your rights under this Public License
terminate automatically.
b. Where Your right to use the Licensed Material has terminated under
Section 6(a), it reinstates:
1. automatically as of the date the violation is cured, provided
it is cured within 30 days of Your discovery of the
violation; or
2. upon express reinstatement by the Licensor.
For the avoidance of doubt, this Section 6(b) does not affect any
right the Licensor may have to seek remedies for Your violations
of this Public License.
c. For the avoidance of doubt, the Licensor may also offer the
Licensed Material under separate terms or conditions or stop
distributing the Licensed Material at any time; however, doing so
will not terminate this Public License.
d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
License.
Section 7 -- Other Terms and Conditions.
a. The Licensor shall not be bound by any additional or different
terms or conditions communicated by You unless expressly agreed.
b. Any arrangements, understandings, or agreements regarding the
Licensed Material not stated herein are separate from and
independent of the terms and conditions of this Public License.
Section 8 -- Interpretation.
a. For the avoidance of doubt, this Public License does not, and
shall not be interpreted to, reduce, limit, restrict, or impose
conditions on any use of the Licensed Material that could lawfully
be made without permission under this Public License.
b. To the extent possible, if any provision of this Public License is
deemed unenforceable, it shall be automatically reformed to the
minimum extent necessary to make it enforceable. If the provision
cannot be reformed, it shall be severed from this Public License
without affecting the enforceability of the remaining terms and
conditions.
c. No term or condition of this Public License will be waived and no
failure to comply consented to unless expressly agreed to by the
Licensor.
d. Nothing in this Public License constitutes or may be interpreted
as a limitation upon, or waiver of, any privileges and immunities
that apply to the Licensor or You, including from the legal
processes of any jurisdiction or authority.
=======================================================================
Creative Commons is not a party to its public
licenses. Notwithstanding, Creative Commons may elect to apply one of
its public licenses to material it publishes and in those instances
will be considered the “Licensor.” The text of the Creative Commons
public licenses is dedicated to the public domain under the CC0 Public
Domain Dedication. Except for the limited purpose of indicating that
material is shared under a Creative Commons public license or as
otherwise permitted by the Creative Commons policies published at
creativecommons.org/policies, Creative Commons does not authorize the
use of the trademark "Creative Commons" or any other trademark or logo
of Creative Commons without its prior written consent including,
without limitation, in connection with any unauthorized modifications
to any of its public licenses or any other arrangements,
understandings, or agreements concerning use of licensed material. For
the avoidance of doubt, this paragraph does not form part of the
public licenses.
Creative Commons may be contacted at creativecommons.org.

14
README.md Normal file
View file

@ -0,0 +1,14 @@
# oooh shiny blog
blog made with [hugo](https://gohugo.io/).
## commands
- `hugo server --buildDrafts`: run a dev server
- `hugo`: build the site
yeah that's it
## license
see the LICENSE file or [the creative commons site](https://creativecommons.org/licenses/by-nc-sa/4.0/) for details. basically: use and edit my work for whatever non-commercial thing you want, just attribute me and use the same license for your edited version.

5
archetypes/default.md Normal file
View file

@ -0,0 +1,5 @@
+++
date = '{{ .Date }}'
draft = true
title = '{{ replace .File.ContentBaseName "-" " " | title }}'
+++

13
content/_index.md Normal file
View file

@ -0,0 +1,13 @@
+++
title = "Home"
+++
heya, i'm sam! this is my attempt at a blog which i will _definitely_ update often, trust me.
i deliberately don't really have a public online presence, but you can find me here:
- codeberg: https://codeberg.org/u1f320/ (git)
- forgejo: https://code.vulpine.solutions/sam (self-hosted git)
- pronouns.cc: https://pronouns.cc/@sam (i made this site!)
###### _vulpine problems require vulpine solutions_

3
content/blog/_index.md Normal file
View file

@ -0,0 +1,3 @@
+++
title = "Blog"
+++

39
content/blog/go-panics-are-fundamentally-flawed.md Normal file
View file

@ -0,0 +1,39 @@
+++
title = "go's panics are fundamentally flawed"
date = "2024-11-05"
+++
_(alternative title: `panic()` considered harmful)_
## errors, how do they work anyway?
errors in Go programs are represented by values. when calling a function that may return an error, it'll return `(T, error)`, and you can handle the error the same way you would any other value.
(note: the `(T, error)` syntax doesn't imply Go has tuples, because it doesn't. functions can just return multiple values.)
now, this approach does have some problems. Go lets you ignore the error very easily, by using the discard operator `_` rather than assigning it to a variable. it's also extremely verbose--anyone who has used Go a substantial amount has written `if err != nil { return err }` a thousand times. both of these issues are fixable, though: the compiler could emit a warning or an error (heh) when discarding an error value, and new syntax could be introduced to bubble errors up more easily.
## panic! at the goroutine
what _isn't_ fixable, though, is the panic system. any function, no matter its signature, can call `panic()` at any point, with any value. as soon as it's called, the call stack unwinds all the way to `main()` and the program crashes. a function doesn't have to indicate that it can do this. in fact, it _can't_, except in a documentation comment.
you can catch panics with a call to `recover()`. you _can't_ put this below a function that might panic, though, you have to use `defer` _before_ the panic happens. `recover()` will return the value passed to `panic()`, or no value if no function panicked. (ironically, `recover()` _also_ doesn't return an error, or even a boolean, when nothing panicked. you check if the return value is `nil` instead.)
this is basically a worse version of `try { } catch { }` in other languages. you can't guarantee that the value returned by `recover()` is an error, it can be _any_ type. it moves error recovery away from the source of the error. and, of course, it's inconsistent: the `(T, error)` pattern lulls you into a false sense of security, making you think that you handled all possible errors in your application, when surprise! it can always panic.
## how this could be fixed
simple: remove `panic()` entirely. all functions that panic now must instead return an error, and the caller must _handle_ that error. now when a function doesn't return an error type, you _know_ it can't ever crash your program! problem solv--
oh. the language itself panics quite a bit as well. trying to access a slice index that doesn't exist, trying to assign to a `nil` map, dereferencing a `nil` pointer, trying to write to a map from multiple goroutines simultaneously, and more can all cause panics. that requires a little more thought.
well, here we go:
- slice indexing could simply _also_ return a `(T, error)`, or at least `(T, bool)`, at all times, unless the index is known to exist at compile time. this would be extremely annoying in the current version of the language, but would be fine if a more streamlined way of bubbling errors up was added, such as borrowing Rust's `?` operator.
- `nil` maps should be removed entirely. every map is strongly typed to begin with, and there is no practical difference between a `nil` map and an empty one. in my mind, the current behaviour is the language exposing an implementation detail (distinguishing between `nil` and empty maps) for no real reason.
- similarly to slices, accessing a pointer could also return `(T, error)`. borrowing C#'s `?` operator to streamline accessing deeply nested values would help here. alternatively, do away with pointers entirely and replace it with a system similar to Rust's `Option<T>` type.
- i'm not entirely sure how to handle maps in multiple goroutines. the easy solution would be to wrap every single map in a `sync.RWMutex`, but this would massively slow down single-threaded programs, which is why [the developers decided against doing this in the first place](https://go.dev/doc/faq#atomic_maps). maybe assigning to a map could return a boolean, with `false` meaning the write failed because another goroutine wrote to it at the same time. that's not a perfect solution, though.
but really, the biggest problem with panics is that all of the decisions surrounding them are set in stone, forever. Go intends to never release 2.0, which is understandable: they don't want a repeat of the Python 2 to 3 transition. but it also means the language can never truly grow past some of its faults.
luckily, this is all just a thought experiment. if i want a more reasonable error handling system, there are so many other languages to choose from. such as c#--`System.NullReferenceException` ...oh, never mind.

11
content/blog/hello-world.md Normal file
View file

@ -0,0 +1,11 @@
+++
title = "hello world!"
date = "2024-11-04"
+++
oh hey, it's the stereotypical "hello world" post. look at me! i copy pasted a hugo tutorial!
turns out making a blog is really difficult, and not for technical reasons. it's just really hard to actually write things consistently.
i can't promise anything in that regard--expect this site to get about one post a year, and that's _if_ i actually remember it exists.
until then though, have fun reading the one rant i've already written. hope you like go because if not, it probably isn't for you!

44
content/blog/rust-is-good-just-not-for-me.md Normal file
View file

@ -0,0 +1,44 @@
+++
title = "rust is good, just not for me"
date = "2024-12-02"
+++
Rust is the big new[^1] thing in just about every programming niche. web frameworks? of course there's a Rust one! in fact, there's dozens of them. command line tools? good luck finding one that _isn't_ written in Rust these days. databases? oops, all Rust!
all of this carcinisation[^2] has me feeling kind of left out, though. you see, i've never really vibed with Rust: i have tried it multiple times, even building a handful of (unfinished, naturally) projects with it, but i always bounce off of it eventually. for a long time, i attributed this to Rust just not being what it's hyped up to be, that it's actually a lot worse than everyone says it is, but... it really isn't. it _is_ a good programming language. a great one, in fact! i want to dig a little deeper into _why_ i, personally, don't vibe with it. (not very deep, mind you, because self-reflection is difficult as _hell_)
## it's too low-level
starting off with the big one: **Rust is a systems language.** while it _also_ works very well for web development, command line tools, and other software, it's not what it was designed for. it was designed for scenarios where you can (and often need to!) squeeze as much performance as possible out of a system, where a garbage collector on its own would already not fit into the device's memory, and where a string taking up any more space than its literal bytes is unacceptable.
meanwhile, when _i_ used Rust, i just wrapped everything in an `Arc<RwMutex<T>>`[^3] and called it a day, because i _don't_ care about performance all that much. HTTP and database latency already destroy any optimization i could do to the business logic, so why even bother?
## i was constantly fighting the compiler
i'll admit it: i didn't really go out of my way to learn Rust. like every other language i've used, i just jumped in headfirst and started trying to rewrite my silly little programs into the silly little crab language. **this was a mistake.**
Rust's compiler is its strongest suit: it catches bugs that no C or C++ compilers can even _imagine_ exist, and its borrow checker seems like dark magic at times. but what makes the compiler great for experienced Rust users makes it an absolute _pain_ for people learning the language. other languages let you throw code at the wall and see what sticks; Rust won't even let your code compile unless it works perfectly. this makes my learning process a lot more difficult, and as such, i never really learned more advanced Rust.
## macros are magic, but not the good kind
macros are _extremely_ powerful. many of the libraries i was using heavily relied on them--some, like `sqlx` (no relation to `sqlx`, the Go library[^4]) are entirely built around them. they're also a nightmare to reason with as an inexperienced rustacean.
i'm used to being able to ctrl-click on a function invocation to go directly to its implementation in other languages--Go, C#, and even Python all do this (well, as long as the Python package has type annotations, and you're not relying on external ones). this just doesn't work with macros, because the code is generated at compile time. it felt like i was feeding input into a black box and praying that whatever came out on the other side worked[^5].
### types for days
somewhat related to macros: some libraries like [axum](https://github.com/tokio-rs/axum) generate _ridiculously_ long type names, which, while funny, are impossible to actually parse. this didn't make debugging my code any easier.
## conclusion, i guess
i don't really have any conclusion to draw from writing this. i guess my learning process just doesn't mesh with how Rust works, and that's why i bounced off of it.
i definitely think it's worth thinking about this for _any_ language--or any other _tool_ in general, even--that you dislike. it's honestly kind of depressing to be extremely negative about things without being able to articulate _why_. i'm sure i've annoyed plenty of friends by complaining about Rust or any other tool they like.
in fact, i should write a post like this for every language i dislike! Go, Elixir, maybe even PHP--well, maybe not that last one. it's been so long since i last used it that i'm sure all my problems with it have been fixed at this point.
[^1]: please ignore that it's been stable for over 9 years.
[^2]: [everything seems to evolve into crabs these days.](https://en.wikipedia.org/wiki/Carcinisation)
[^3]: wait a second, does that mean i just used a reference-counting garbage collector?
[^4]: `sqlx`, the Rust library that converts database rows to strongly typed structs using reflection magic (macros), not to be confused with `sqlx`, the Go library that converts database rows to strongly typed structs using reflection magic (the reflection package). they are somehow completely unrelated.
[^5]: this is, coincidentally, why i don't use LLMs.

16
hugo.toml Normal file
View file

@ -0,0 +1,16 @@
baseURL = "https://blog.vulpine.solutions/"
languageCode = "en-gb"
title = "vulpine solutions"
author = "sam"
theme = "hugo-bearblog"
enableRobotsTXT = true
copyright = "sam, CC-BY-SA 4.0"
disableKinds = ["taxonomy"]
ignoreErrors = ["error-disable-taxonomy"]
[params]
description = "vulpine problems require vulpine solutions"
title = "vulpine solutions"
dateFormat = "Jan 2, 2006"
favicon = "favicon.png"

234
public/404.html Normal file
View file

@ -0,0 +1,234 @@
<!DOCTYPE html>
<html lang="en-gb">
<head>
<meta http-equiv="X-Clacks-Overhead" content="GNU Terry Pratchett" />
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<link rel="shortcut icon" href="https://blog.vulpine.solutions/favicon.png" />
<title>404</title>
<meta name="title" content="404 Page not found" />
<meta name="description" content="vulpine problems require vulpine solutions" />
<meta name="keywords" content="" />
<meta property="og:url" content="https://blog.vulpine.solutions/404.html">
<meta property="og:site_name" content="vulpine solutions">
<meta property="og:title" content="404 Page not found">
<meta property="og:description" content="vulpine problems require vulpine solutions">
<meta property="og:locale" content="en_gb">
<meta property="og:type" content="website">
<meta name="twitter:card" content="summary">
<meta name="twitter:title" content="404 Page not found">
<meta name="twitter:description" content="vulpine problems require vulpine solutions">
<meta itemprop="name" content="404 Page not found">
<meta itemprop="description" content="vulpine problems require vulpine solutions">
<meta name="referrer" content="no-referrer-when-downgrade" />
<style>
body {
font-family: Verdana, sans-serif;
margin: auto;
padding: 20px;
max-width: 720px;
text-align: left;
background-color: #fff;
word-wrap: break-word;
overflow-wrap: break-word;
line-height: 1.5;
color: #444;
}
h1,
h2,
h3,
h4,
h5,
h6,
strong,
b {
color: #222;
}
a {
color: #3273dc;
}
.title {
text-decoration: none;
border: 0;
}
.title span {
font-weight: 400;
}
nav a {
margin-right: 10px;
}
textarea {
width: 100%;
font-size: 16px;
}
input {
font-size: 16px;
}
content {
line-height: 1.6;
}
table {
width: 100%;
}
img {
max-width: 100%;
}
code {
padding: 2px 5px;
background-color: #f2f2f2;
}
pre code {
color: #222;
display: block;
padding: 20px;
white-space: pre-wrap;
font-size: 14px;
overflow-x: auto;
}
div.highlight pre {
background-color: initial;
color: initial;
}
div.highlight code {
background-color: unset;
color: unset;
}
blockquote {
border-left: 1px solid #999;
color: #222;
padding-left: 20px;
font-style: italic;
}
footer {
padding: 25px;
text-align: center;
}
.helptext {
color: #777;
font-size: small;
}
.errorlist {
color: #eba613;
font-size: small;
}
ul.blog-posts {
list-style-type: none;
padding: unset;
}
ul.blog-posts li {
display: flex;
}
ul.blog-posts li span {
flex: 0 0 130px;
}
ul.blog-posts li a:visited {
color: #8b6fcb;
}
@media (prefers-color-scheme: dark) {
body {
background-color: #333;
color: #ddd;
}
h1,
h2,
h3,
h4,
h5,
h6,
strong,
b {
color: #eee;
}
a {
color: #8cc2dd;
}
code {
background-color: #777;
}
pre code {
color: #ddd;
}
blockquote {
color: #ccc;
}
textarea,
input {
background-color: #252525;
color: #ddd;
}
.helptext {
color: #aaa;
}
}
</style>
</head>
<body>
<header><a href="/" class="title">
<h2>vulpine solutions</h2>
</a>
<nav><a href="/">Home</a>
<a href="/blog">Blog</a>
</nav>
</header>
<main>
<h1>404</h1>
<h2>ʕノ•ᴥ•ʔノ ︵ ┻━┻</h2>
</main>
<footer>Made with <a href="https://github.com/janraasch/hugo-bearblog/">Hugo ʕ•ᴥ•ʔ Bear</a>
</footer>
</body>
</html>

BIN
public/blog.tar.gz Normal file
View file

Binary file not shown.

288
public/blog/go-panics-are-fundamentally-flawed/index.html Normal file
View file

@ -0,0 +1,288 @@
<!DOCTYPE html>
<html lang="en-gb">
<head>
<meta http-equiv="X-Clacks-Overhead" content="GNU Terry Pratchett" />
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<link rel="shortcut icon" href="https://blog.vulpine.solutions/favicon.png" />
<title>go&#39;s panics are fundamentally flawed | vulpine solutions</title>
<meta name="title" content="go&#39;s panics are fundamentally flawed" />
<meta name="description" content="(alternative title: panic() considered harmful)
errors, how do they work anyway?
errors in Go programs are represented by values. when calling a function that may return an error, it&rsquo;ll return (T, error), and you can handle the error the same way you would any other value.
(note: the (T, error) syntax doesn&rsquo;t imply Go has tuples, because it doesn&rsquo;t. functions can just return multiple values.)
now, this approach does have some problems. Go lets you ignore the error very easily, by using the discard operator _ rather than assigning it to a variable. it&rsquo;s also extremely verbose&ndash;anyone who has used Go a substantial amount has written if err != nil { return err } a thousand times. both of these issues are fixable, though: the compiler could emit a warning or an error (heh) when discarding an error value, and new syntax could be introduced to bubble errors up more easily." />
<meta name="keywords" content="" />
<meta property="og:url" content="https://blog.vulpine.solutions/blog/go-panics-are-fundamentally-flawed/">
<meta property="og:site_name" content="vulpine solutions">
<meta property="og:title" content="go&#39;s panics are fundamentally flawed">
<meta property="og:description" content="(alternative title: panic() considered harmful)
errors, how do they work anyway? errors in Go programs are represented by values. when calling a function that may return an error, it’ll return (T, error), and you can handle the error the same way you would any other value.
(note: the (T, error) syntax doesn’t imply Go has tuples, because it doesn’t. functions can just return multiple values.)
now, this approach does have some problems. Go lets you ignore the error very easily, by using the discard operator _ rather than assigning it to a variable. it’s also extremely verbose–anyone who has used Go a substantial amount has written if err != nil { return err } a thousand times. both of these issues are fixable, though: the compiler could emit a warning or an error (heh) when discarding an error value, and new syntax could be introduced to bubble errors up more easily.">
<meta property="og:locale" content="en_gb">
<meta property="og:type" content="article">
<meta property="article:section" content="blog">
<meta property="article:published_time" content="2024-11-05T00:00:00+00:00">
<meta property="article:modified_time" content="2024-11-05T00:00:00+00:00">
<meta name="twitter:card" content="summary">
<meta name="twitter:title" content="go&#39;s panics are fundamentally flawed">
<meta name="twitter:description" content="(alternative title: panic() considered harmful)
errors, how do they work anyway? errors in Go programs are represented by values. when calling a function that may return an error, it’ll return (T, error), and you can handle the error the same way you would any other value.
(note: the (T, error) syntax doesn’t imply Go has tuples, because it doesn’t. functions can just return multiple values.)
now, this approach does have some problems. Go lets you ignore the error very easily, by using the discard operator _ rather than assigning it to a variable. it’s also extremely verbose–anyone who has used Go a substantial amount has written if err != nil { return err } a thousand times. both of these issues are fixable, though: the compiler could emit a warning or an error (heh) when discarding an error value, and new syntax could be introduced to bubble errors up more easily.">
<meta itemprop="name" content="go&#39;s panics are fundamentally flawed">
<meta itemprop="description" content="(alternative title: panic() considered harmful)
errors, how do they work anyway? errors in Go programs are represented by values. when calling a function that may return an error, it’ll return (T, error), and you can handle the error the same way you would any other value.
(note: the (T, error) syntax doesn’t imply Go has tuples, because it doesn’t. functions can just return multiple values.)
now, this approach does have some problems. Go lets you ignore the error very easily, by using the discard operator _ rather than assigning it to a variable. it’s also extremely verbose–anyone who has used Go a substantial amount has written if err != nil { return err } a thousand times. both of these issues are fixable, though: the compiler could emit a warning or an error (heh) when discarding an error value, and new syntax could be introduced to bubble errors up more easily.">
<meta itemprop="datePublished" content="2024-11-05T00:00:00+00:00">
<meta itemprop="dateModified" content="2024-11-05T00:00:00+00:00">
<meta itemprop="wordCount" content="779">
<meta name="referrer" content="no-referrer-when-downgrade" />
<style>
body {
font-family: Verdana, sans-serif;
margin: auto;
padding: 20px;
max-width: 720px;
text-align: left;
background-color: #fff;
word-wrap: break-word;
overflow-wrap: break-word;
line-height: 1.5;
color: #444;
}
h1,
h2,
h3,
h4,
h5,
h6,
strong,
b {
color: #222;
}
a {
color: #3273dc;
}
.title {
text-decoration: none;
border: 0;
}
.title span {
font-weight: 400;
}
nav a {
margin-right: 10px;
}
textarea {
width: 100%;
font-size: 16px;
}
input {
font-size: 16px;
}
content {
line-height: 1.6;
}
table {
width: 100%;
}
img {
max-width: 100%;
}
code {
padding: 2px 5px;
background-color: #f2f2f2;
}
pre code {
color: #222;
display: block;
padding: 20px;
white-space: pre-wrap;
font-size: 14px;
overflow-x: auto;
}
div.highlight pre {
background-color: initial;
color: initial;
}
div.highlight code {
background-color: unset;
color: unset;
}
blockquote {
border-left: 1px solid #999;
color: #222;
padding-left: 20px;
font-style: italic;
}
footer {
padding: 25px;
text-align: center;
}
.helptext {
color: #777;
font-size: small;
}
.errorlist {
color: #eba613;
font-size: small;
}
ul.blog-posts {
list-style-type: none;
padding: unset;
}
ul.blog-posts li {
display: flex;
}
ul.blog-posts li span {
flex: 0 0 130px;
}
ul.blog-posts li a:visited {
color: #8b6fcb;
}
@media (prefers-color-scheme: dark) {
body {
background-color: #333;
color: #ddd;
}
h1,
h2,
h3,
h4,
h5,
h6,
strong,
b {
color: #eee;
}
a {
color: #8cc2dd;
}
code {
background-color: #777;
}
pre code {
color: #ddd;
}
blockquote {
color: #ccc;
}
textarea,
input {
background-color: #252525;
color: #ddd;
}
.helptext {
color: #aaa;
}
}
</style>
</head>
<body>
<header><a href="/" class="title">
<h2>vulpine solutions</h2>
</a>
<nav><a href="/">Home</a>
<a href="/blog">Blog</a>
</nav>
</header>
<main>
<h1>go&#39;s panics are fundamentally flawed</h1>
<p>
<i>
<time datetime='2024-11-05' pubdate>
Nov 5, 2024
</time>
</i>
</p>
<content>
<p><em>(alternative title: <code>panic()</code> considered harmful)</em></p>
<h2 id="errors-how-do-they-work-anyway">errors, how do they work anyway?</h2>
<p>errors in Go programs are represented by values. when calling a function that may return an error, it&rsquo;ll return <code>(T, error)</code>, and you can handle the error the same way you would any other value.</p>
<p>(note: the <code>(T, error)</code> syntax doesn&rsquo;t imply Go has tuples, because it doesn&rsquo;t. functions can just return multiple values.)</p>
<p>now, this approach does have some problems. Go lets you ignore the error very easily, by using the discard operator <code>_</code> rather than assigning it to a variable. it&rsquo;s also extremely verbose&ndash;anyone who has used Go a substantial amount has written <code>if err != nil { return err }</code> a thousand times. both of these issues are fixable, though: the compiler could emit a warning or an error (heh) when discarding an error value, and new syntax could be introduced to bubble errors up more easily.</p>
<h2 id="panic-at-the-goroutine">panic! at the goroutine</h2>
<p>what <em>isn&rsquo;t</em> fixable, though, is the panic system. any function, no matter its signature, can call <code>panic()</code> at any point, with any value. as soon as it&rsquo;s called, the call stack unwinds all the way to <code>main()</code> and the program crashes. a function doesn&rsquo;t have to indicate that it can do this. in fact, it <em>can&rsquo;t</em>, except in a documentation comment.</p>
<p>you can catch panics with a call to <code>recover()</code>. you <em>can&rsquo;t</em> put this below a function that might panic, though, you have to use <code>defer</code> <em>before</em> the panic happens. <code>recover()</code> will return the value passed to <code>panic()</code>, or no value if no function panicked. (ironically, <code>recover()</code> <em>also</em> doesn&rsquo;t return an error, or even a boolean, when nothing panicked. you check if the return value is <code>nil</code> instead.)</p>
<p>this is basically a worse version of <code>try { } catch { }</code> in other languages. you can&rsquo;t guarantee that the value returned by <code>recover()</code> is an error, it can be <em>any</em> type. it moves error recovery away from the source of the error. and, of course, it&rsquo;s inconsistent: the <code>(T, error)</code> pattern lulls you into a false sense of security, making you think that you handled all possible errors in your application, when surprise! it can always panic.</p>
<h2 id="how-this-could-be-fixed">how this could be fixed</h2>
<p>simple: remove <code>panic()</code> entirely. all functions that panic now must instead return an error, and the caller must <em>handle</em> that error. now when a function doesn&rsquo;t return an error type, you <em>know</em> it can&rsquo;t ever crash your program! problem solv&ndash;</p>
<p>oh. the language itself panics quite a bit as well. trying to access a slice index that doesn&rsquo;t exist, trying to assign to a <code>nil</code> map, dereferencing a <code>nil</code> pointer, trying to write to a map from multiple goroutines simultaneously, and more can all cause panics. that requires a little more thought.</p>
<p>well, here we go:</p>
<ul>
<li>slice indexing could simply <em>also</em> return a <code>(T, error)</code>, or at least <code>(T, bool)</code>, at all times, unless the index is known to exist at compile time. this would be extremely annoying in the current version of the language, but would be fine if a more streamlined way of bubbling errors up was added, such as borrowing Rust&rsquo;s <code>?</code> operator.</li>
<li><code>nil</code> maps should be removed entirely. every map is strongly typed to begin with, and there is no practical difference between a <code>nil</code> map and an empty one. in my mind, the current behaviour is the language exposing an implementation detail (distinguishing between <code>nil</code> and empty maps) for no real reason.</li>
<li>similarly to slices, accessing a pointer could also return <code>(T, error)</code>. borrowing C#&rsquo;s <code>?</code> operator to streamline accessing deeply nested values would help here. alternatively, do away with pointers entirely and replace it with a system similar to Rust&rsquo;s <code>Option&lt;T&gt;</code> type.</li>
<li>i&rsquo;m not entirely sure how to handle maps in multiple goroutines. the easy solution would be to wrap every single map in a <code>sync.RWMutex</code>, but this would massively slow down single-threaded programs, which is why <a href="https://go.dev/doc/faq#atomic_maps">the developers decided against doing this in the first place</a>. maybe assigning to a map could return a boolean, with <code>false</code> meaning the write failed because another goroutine wrote to it at the same time. that&rsquo;s not a perfect solution, though.</li>
</ul>
<p>but really, the biggest problem with panics is that all of the decisions surrounding them are set in stone, forever. Go intends to never release 2.0, which is understandable: they don&rsquo;t want a repeat of the Python 2 to 3 transition. but it also means the language can never truly grow past some of its faults.</p>
<p>luckily, this is all just a thought experiment. if i want a more reasonable error handling system, there are so many other languages to choose from. such as c#&ndash;<code>System.NullReferenceException</code> &hellip;oh, never mind.</p>
</content>
<p>
</p>
</main>
<footer>Made with <a href="https://github.com/janraasch/hugo-bearblog/">Hugo ʕ•ᴥ•ʔ Bear</a>
</footer>
</body>
</html>

267
public/blog/hello-world/index.html Normal file
View file

@ -0,0 +1,267 @@
<!DOCTYPE html>
<html lang="en-gb">
<head>
<meta http-equiv="X-Clacks-Overhead" content="GNU Terry Pratchett" />
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<link rel="shortcut icon" href="https://blog.vulpine.solutions/favicon.png" />
<title>hello world! | vulpine solutions</title>
<meta name="title" content="hello world!" />
<meta name="description" content="oh hey, it&rsquo;s the stereotypical &ldquo;hello world&rdquo; post. look at me! i copy pasted a hugo tutorial!
turns out making a blog is really difficult, and not for technical reasons. it&rsquo;s just really hard to actually write things consistently.
i can&rsquo;t promise anything in that regard&ndash;expect this site to get about one post a year, and that&rsquo;s if i actually remember it exists.
until then though, have fun reading the one rant i&rsquo;ve already written. hope you like go because if not, it probably isn&rsquo;t for you!" />
<meta name="keywords" content="" />
<meta property="og:url" content="https://blog.vulpine.solutions/blog/hello-world/">
<meta property="og:site_name" content="vulpine solutions">
<meta property="og:title" content="hello world!">
<meta property="og:description" content="oh hey, it’s the stereotypical “hello world” post. look at me! i copy pasted a hugo tutorial!
turns out making a blog is really difficult, and not for technical reasons. it’s just really hard to actually write things consistently. i can’t promise anything in that regard–expect this site to get about one post a year, and that’s if i actually remember it exists.
until then though, have fun reading the one rant i’ve already written. hope you like go because if not, it probably isn’t for you!">
<meta property="og:locale" content="en_gb">
<meta property="og:type" content="article">
<meta property="article:section" content="blog">
<meta property="article:published_time" content="2024-11-04T00:00:00+00:00">
<meta property="article:modified_time" content="2024-11-04T00:00:00+00:00">
<meta name="twitter:card" content="summary">
<meta name="twitter:title" content="hello world!">
<meta name="twitter:description" content="oh hey, it’s the stereotypical “hello world” post. look at me! i copy pasted a hugo tutorial!
turns out making a blog is really difficult, and not for technical reasons. it’s just really hard to actually write things consistently. i can’t promise anything in that regard–expect this site to get about one post a year, and that’s if i actually remember it exists.
until then though, have fun reading the one rant i’ve already written. hope you like go because if not, it probably isn’t for you!">
<meta itemprop="name" content="hello world!">
<meta itemprop="description" content="oh hey, it’s the stereotypical “hello world” post. look at me! i copy pasted a hugo tutorial!
turns out making a blog is really difficult, and not for technical reasons. it’s just really hard to actually write things consistently. i can’t promise anything in that regard–expect this site to get about one post a year, and that’s if i actually remember it exists.
until then though, have fun reading the one rant i’ve already written. hope you like go because if not, it probably isn’t for you!">
<meta itemprop="datePublished" content="2024-11-04T00:00:00+00:00">
<meta itemprop="dateModified" content="2024-11-04T00:00:00+00:00">
<meta itemprop="wordCount" content="87">
<meta name="referrer" content="no-referrer-when-downgrade" />
<style>
body {
font-family: Verdana, sans-serif;
margin: auto;
padding: 20px;
max-width: 720px;
text-align: left;
background-color: #fff;
word-wrap: break-word;
overflow-wrap: break-word;
line-height: 1.5;
color: #444;
}
h1,
h2,
h3,
h4,
h5,
h6,
strong,
b {
color: #222;
}
a {
color: #3273dc;
}
.title {
text-decoration: none;
border: 0;
}
.title span {
font-weight: 400;
}
nav a {
margin-right: 10px;
}
textarea {
width: 100%;
font-size: 16px;
}
input {
font-size: 16px;
}
content {
line-height: 1.6;
}
table {
width: 100%;
}
img {
max-width: 100%;
}
code {
padding: 2px 5px;
background-color: #f2f2f2;
}
pre code {
color: #222;
display: block;
padding: 20px;
white-space: pre-wrap;
font-size: 14px;
overflow-x: auto;
}
div.highlight pre {
background-color: initial;
color: initial;
}
div.highlight code {
background-color: unset;
color: unset;
}
blockquote {
border-left: 1px solid #999;
color: #222;
padding-left: 20px;
font-style: italic;
}
footer {
padding: 25px;
text-align: center;
}
.helptext {
color: #777;
font-size: small;
}
.errorlist {
color: #eba613;
font-size: small;
}
ul.blog-posts {
list-style-type: none;
padding: unset;
}
ul.blog-posts li {
display: flex;
}
ul.blog-posts li span {
flex: 0 0 130px;
}
ul.blog-posts li a:visited {
color: #8b6fcb;
}
@media (prefers-color-scheme: dark) {
body {
background-color: #333;
color: #ddd;
}
h1,
h2,
h3,
h4,
h5,
h6,
strong,
b {
color: #eee;
}
a {
color: #8cc2dd;
}
code {
background-color: #777;
}
pre code {
color: #ddd;
}
blockquote {
color: #ccc;
}
textarea,
input {
background-color: #252525;
color: #ddd;
}
.helptext {
color: #aaa;
}
}
</style>
</head>
<body>
<header><a href="/" class="title">
<h2>vulpine solutions</h2>
</a>
<nav><a href="/">Home</a>
<a href="/blog">Blog</a>
</nav>
</header>
<main>
<h1>hello world!</h1>
<p>
<i>
<time datetime='2024-11-04' pubdate>
Nov 4, 2024
</time>
</i>
</p>
<content>
<p>oh hey, it&rsquo;s the stereotypical &ldquo;hello world&rdquo; post. look at me! i copy pasted a hugo tutorial!</p>
<p>turns out making a blog is really difficult, and not for technical reasons. it&rsquo;s just really hard to actually write things consistently.
i can&rsquo;t promise anything in that regard&ndash;expect this site to get about one post a year, and that&rsquo;s <em>if</em> i actually remember it exists.</p>
<p>until then though, have fun reading the one rant i&rsquo;ve already written. hope you like go because if not, it probably isn&rsquo;t for you!</p>
</content>
<p>
</p>
</main>
<footer>Made with <a href="https://github.com/janraasch/hugo-bearblog/">Hugo ʕ•ᴥ•ʔ Bear</a>
</footer>
</body>
</html>

281
public/blog/index.html Normal file
View file

@ -0,0 +1,281 @@
<!DOCTYPE html>
<html lang="en-gb">
<head>
<meta http-equiv="X-Clacks-Overhead" content="GNU Terry Pratchett" />
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<link rel="shortcut icon" href="https://blog.vulpine.solutions/favicon.png" />
<title>Blog | vulpine solutions</title>
<meta name="title" content="Blog" />
<meta name="description" content="vulpine problems require vulpine solutions" />
<meta name="keywords" content="" />
<meta property="og:url" content="https://blog.vulpine.solutions/blog/">
<meta property="og:site_name" content="vulpine solutions">
<meta property="og:title" content="Blog">
<meta property="og:description" content="vulpine problems require vulpine solutions">
<meta property="og:locale" content="en_gb">
<meta property="og:type" content="website">
<meta name="twitter:card" content="summary">
<meta name="twitter:title" content="Blog">
<meta name="twitter:description" content="vulpine problems require vulpine solutions">
<meta itemprop="name" content="Blog">
<meta itemprop="description" content="vulpine problems require vulpine solutions">
<meta itemprop="datePublished" content="2024-12-02T00:00:00+00:00">
<meta itemprop="dateModified" content="2024-12-02T00:00:00+00:00">
<meta name="referrer" content="no-referrer-when-downgrade" />
<link rel="alternate" type="application/rss+xml" href="https://blog.vulpine.solutions/blog/index.xml" title="vulpine solutions" />
<style>
body {
font-family: Verdana, sans-serif;
margin: auto;
padding: 20px;
max-width: 720px;
text-align: left;
background-color: #fff;
word-wrap: break-word;
overflow-wrap: break-word;
line-height: 1.5;
color: #444;
}
h1,
h2,
h3,
h4,
h5,
h6,
strong,
b {
color: #222;
}
a {
color: #3273dc;
}
.title {
text-decoration: none;
border: 0;
}
.title span {
font-weight: 400;
}
nav a {
margin-right: 10px;
}
textarea {
width: 100%;
font-size: 16px;
}
input {
font-size: 16px;
}
content {
line-height: 1.6;
}
table {
width: 100%;
}
img {
max-width: 100%;
}
code {
padding: 2px 5px;
background-color: #f2f2f2;
}
pre code {
color: #222;
display: block;
padding: 20px;
white-space: pre-wrap;
font-size: 14px;
overflow-x: auto;
}
div.highlight pre {
background-color: initial;
color: initial;
}
div.highlight code {
background-color: unset;
color: unset;
}
blockquote {
border-left: 1px solid #999;
color: #222;
padding-left: 20px;
font-style: italic;
}
footer {
padding: 25px;
text-align: center;
}
.helptext {
color: #777;
font-size: small;
}
.errorlist {
color: #eba613;
font-size: small;
}
ul.blog-posts {
list-style-type: none;
padding: unset;
}
ul.blog-posts li {
display: flex;
}
ul.blog-posts li span {
flex: 0 0 130px;
}
ul.blog-posts li a:visited {
color: #8b6fcb;
}
@media (prefers-color-scheme: dark) {
body {
background-color: #333;
color: #ddd;
}
h1,
h2,
h3,
h4,
h5,
h6,
strong,
b {
color: #eee;
}
a {
color: #8cc2dd;
}
code {
background-color: #777;
}
pre code {
color: #ddd;
}
blockquote {
color: #ccc;
}
textarea,
input {
background-color: #252525;
color: #ddd;
}
.helptext {
color: #aaa;
}
}
</style>
</head>
<body>
<header><a href="/" class="title">
<h2>vulpine solutions</h2>
</a>
<nav><a href="/">Home</a>
<a href="/blog">Blog</a>
</nav>
</header>
<main>
<content>
<ul class="blog-posts">
<li>
<span>
<i>
<time datetime='2024-12-02' pubdate>
Dec 2, 2024
</time>
</i>
</span>
<a href="https://blog.vulpine.solutions/blog/rust-is-good-just-not-for-me/">rust is good, just not for me</a>
</li>
<li>
<span>
<i>
<time datetime='2024-11-05' pubdate>
Nov 5, 2024
</time>
</i>
</span>
<a href="https://blog.vulpine.solutions/blog/go-panics-are-fundamentally-flawed/">go&#39;s panics are fundamentally flawed</a>
</li>
<li>
<span>
<i>
<time datetime='2024-11-04' pubdate>
Nov 4, 2024
</time>
</i>
</span>
<a href="https://blog.vulpine.solutions/blog/hello-world/">hello world!</a>
</li>
</ul>
<small>
<div>
</div>
</small>
</content>
</main>
<footer>Made with <a href="https://github.com/janraasch/hugo-bearblog/">Hugo ʕ•ᴥ•ʔ Bear</a>
</footer>
</body>
</html>

34
public/blog/index.xml Normal file
View file

@ -0,0 +1,34 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Blog on vulpine solutions</title>
<link>https://blog.vulpine.solutions/blog/</link>
<description>Recent content in Blog on vulpine solutions</description>
<generator>Hugo</generator>
<language>en-gb</language>
<copyright>sam, CC-BY-SA 4.0</copyright>
<lastBuildDate>Mon, 02 Dec 2024 00:00:00 +0000</lastBuildDate>
<atom:link href="https://blog.vulpine.solutions/blog/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>rust is good, just not for me</title>
<link>https://blog.vulpine.solutions/blog/rust-is-good-just-not-for-me/</link>
<pubDate>Mon, 02 Dec 2024 00:00:00 +0000</pubDate>
<guid>https://blog.vulpine.solutions/blog/rust-is-good-just-not-for-me/</guid>
<description>&lt;p&gt;Rust is the big new&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; thing in just about every programming niche. web frameworks? of course there&amp;rsquo;s a Rust one! in fact, there&amp;rsquo;s dozens of them. command line tools? good luck finding one that &lt;em&gt;isn&amp;rsquo;t&lt;/em&gt; written in Rust these days. databases? oops, all Rust!&lt;/p&gt;&#xA;&lt;p&gt;all of this carcinisation&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt; has me feeling kind of left out, though. you see, i&amp;rsquo;ve never really vibed with Rust: i have tried it multiple times, even building a handful of (unfinished, naturally) projects with it, but i always bounce off of it eventually. for a long time, i attributed this to Rust just not being what it&amp;rsquo;s hyped up to be, that it&amp;rsquo;s actually a lot worse than everyone says it is, but&amp;hellip; it really isn&amp;rsquo;t. it &lt;em&gt;is&lt;/em&gt; a good programming language. a great one, in fact! i want to dig a little deeper into &lt;em&gt;why&lt;/em&gt; i, personally, don&amp;rsquo;t vibe with it. (not very deep, mind you, because self-reflection is difficult as &lt;em&gt;hell&lt;/em&gt;)&lt;/p&gt;</description>
</item>
<item>
<title>go&#39;s panics are fundamentally flawed</title>
<link>https://blog.vulpine.solutions/blog/go-panics-are-fundamentally-flawed/</link>
<pubDate>Tue, 05 Nov 2024 00:00:00 +0000</pubDate>
<guid>https://blog.vulpine.solutions/blog/go-panics-are-fundamentally-flawed/</guid>
<description>&lt;p&gt;&lt;em&gt;(alternative title: &lt;code&gt;panic()&lt;/code&gt; considered harmful)&lt;/em&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;errors-how-do-they-work-anyway&#34;&gt;errors, how do they work anyway?&lt;/h2&gt;&#xA;&lt;p&gt;errors in Go programs are represented by values. when calling a function that may return an error, it&amp;rsquo;ll return &lt;code&gt;(T, error)&lt;/code&gt;, and you can handle the error the same way you would any other value.&lt;/p&gt;&#xA;&lt;p&gt;(note: the &lt;code&gt;(T, error)&lt;/code&gt; syntax doesn&amp;rsquo;t imply Go has tuples, because it doesn&amp;rsquo;t. functions can just return multiple values.)&lt;/p&gt;&#xA;&lt;p&gt;now, this approach does have some problems. Go lets you ignore the error very easily, by using the discard operator &lt;code&gt;_&lt;/code&gt; rather than assigning it to a variable. it&amp;rsquo;s also extremely verbose&amp;ndash;anyone who has used Go a substantial amount has written &lt;code&gt;if err != nil { return err }&lt;/code&gt; a thousand times. both of these issues are fixable, though: the compiler could emit a warning or an error (heh) when discarding an error value, and new syntax could be introduced to bubble errors up more easily.&lt;/p&gt;</description>
</item>
<item>
<title>hello world!</title>
<link>https://blog.vulpine.solutions/blog/hello-world/</link>
<pubDate>Mon, 04 Nov 2024 00:00:00 +0000</pubDate>
<guid>https://blog.vulpine.solutions/blog/hello-world/</guid>
<description>&lt;p&gt;oh hey, it&amp;rsquo;s the stereotypical &amp;ldquo;hello world&amp;rdquo; post. look at me! i copy pasted a hugo tutorial!&lt;/p&gt;&#xA;&lt;p&gt;turns out making a blog is really difficult, and not for technical reasons. it&amp;rsquo;s just really hard to actually write things consistently.&#xA;i can&amp;rsquo;t promise anything in that regard&amp;ndash;expect this site to get about one post a year, and that&amp;rsquo;s &lt;em&gt;if&lt;/em&gt; i actually remember it exists.&lt;/p&gt;&#xA;&lt;p&gt;until then though, have fun reading the one rant i&amp;rsquo;ve already written. hope you like go because if not, it probably isn&amp;rsquo;t for you!&lt;/p&gt;</description>
</item>
</channel>
</rss>

295
public/blog/rust-is-good-just-not-for-me/index.html Normal file
View file

@ -0,0 +1,295 @@
<!DOCTYPE html>
<html lang="en-gb">
<head>
<meta http-equiv="X-Clacks-Overhead" content="GNU Terry Pratchett" />
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<link rel="shortcut icon" href="https://blog.vulpine.solutions/favicon.png" />
<title>rust is good, just not for me | vulpine solutions</title>
<meta name="title" content="rust is good, just not for me" />
<meta name="description" content="Rust is the big new1 thing in just about every programming niche. web frameworks? of course there&rsquo;s a Rust one! in fact, there&rsquo;s dozens of them. command line tools? good luck finding one that isn&rsquo;t written in Rust these days. databases? oops, all Rust!
all of this carcinisation2 has me feeling kind of left out, though. you see, i&rsquo;ve never really vibed with Rust: i have tried it multiple times, even building a handful of (unfinished, naturally) projects with it, but i always bounce off of it eventually. for a long time, i attributed this to Rust just not being what it&rsquo;s hyped up to be, that it&rsquo;s actually a lot worse than everyone says it is, but&hellip; it really isn&rsquo;t. it is a good programming language. a great one, in fact! i want to dig a little deeper into why i, personally, don&rsquo;t vibe with it. (not very deep, mind you, because self-reflection is difficult as hell)" />
<meta name="keywords" content="" />
<meta property="og:url" content="https://blog.vulpine.solutions/blog/rust-is-good-just-not-for-me/">
<meta property="og:site_name" content="vulpine solutions">
<meta property="og:title" content="rust is good, just not for me">
<meta property="og:description" content="Rust is the big new1 thing in just about every programming niche. web frameworks? of course there’s a Rust one! in fact, there’s dozens of them. command line tools? good luck finding one that isn’t written in Rust these days. databases? oops, all Rust!
all of this carcinisation2 has me feeling kind of left out, though. you see, i’ve never really vibed with Rust: i have tried it multiple times, even building a handful of (unfinished, naturally) projects with it, but i always bounce off of it eventually. for a long time, i attributed this to Rust just not being what it’s hyped up to be, that it’s actually a lot worse than everyone says it is, but… it really isn’t. it is a good programming language. a great one, in fact! i want to dig a little deeper into why i, personally, don’t vibe with it. (not very deep, mind you, because self-reflection is difficult as hell)">
<meta property="og:locale" content="en_gb">
<meta property="og:type" content="article">
<meta property="article:section" content="blog">
<meta property="article:published_time" content="2024-12-02T00:00:00+00:00">
<meta property="article:modified_time" content="2024-12-02T00:00:00+00:00">
<meta name="twitter:card" content="summary">
<meta name="twitter:title" content="rust is good, just not for me">
<meta name="twitter:description" content="Rust is the big new1 thing in just about every programming niche. web frameworks? of course there’s a Rust one! in fact, there’s dozens of them. command line tools? good luck finding one that isn’t written in Rust these days. databases? oops, all Rust!
all of this carcinisation2 has me feeling kind of left out, though. you see, i’ve never really vibed with Rust: i have tried it multiple times, even building a handful of (unfinished, naturally) projects with it, but i always bounce off of it eventually. for a long time, i attributed this to Rust just not being what it’s hyped up to be, that it’s actually a lot worse than everyone says it is, but… it really isn’t. it is a good programming language. a great one, in fact! i want to dig a little deeper into why i, personally, don’t vibe with it. (not very deep, mind you, because self-reflection is difficult as hell)">
<meta itemprop="name" content="rust is good, just not for me">
<meta itemprop="description" content="Rust is the big new1 thing in just about every programming niche. web frameworks? of course there’s a Rust one! in fact, there’s dozens of them. command line tools? good luck finding one that isn’t written in Rust these days. databases? oops, all Rust!
all of this carcinisation2 has me feeling kind of left out, though. you see, i’ve never really vibed with Rust: i have tried it multiple times, even building a handful of (unfinished, naturally) projects with it, but i always bounce off of it eventually. for a long time, i attributed this to Rust just not being what it’s hyped up to be, that it’s actually a lot worse than everyone says it is, but… it really isn’t. it is a good programming language. a great one, in fact! i want to dig a little deeper into why i, personally, don’t vibe with it. (not very deep, mind you, because self-reflection is difficult as hell)">
<meta itemprop="datePublished" content="2024-12-02T00:00:00+00:00">
<meta itemprop="dateModified" content="2024-12-02T00:00:00+00:00">
<meta itemprop="wordCount" content="810">
<meta name="referrer" content="no-referrer-when-downgrade" />
<style>
body {
font-family: Verdana, sans-serif;
margin: auto;
padding: 20px;
max-width: 720px;
text-align: left;
background-color: #fff;
word-wrap: break-word;
overflow-wrap: break-word;
line-height: 1.5;
color: #444;
}
h1,
h2,
h3,
h4,
h5,
h6,
strong,
b {
color: #222;
}
a {
color: #3273dc;
}
.title {
text-decoration: none;
border: 0;
}
.title span {
font-weight: 400;
}
nav a {
margin-right: 10px;
}
textarea {
width: 100%;
font-size: 16px;
}
input {
font-size: 16px;
}
content {
line-height: 1.6;
}
table {
width: 100%;
}
img {
max-width: 100%;
}
code {
padding: 2px 5px;
background-color: #f2f2f2;
}
pre code {
color: #222;
display: block;
padding: 20px;
white-space: pre-wrap;
font-size: 14px;
overflow-x: auto;
}
div.highlight pre {
background-color: initial;
color: initial;
}
div.highlight code {
background-color: unset;
color: unset;
}
blockquote {
border-left: 1px solid #999;
color: #222;
padding-left: 20px;
font-style: italic;
}
footer {
padding: 25px;
text-align: center;
}
.helptext {
color: #777;
font-size: small;
}
.errorlist {
color: #eba613;
font-size: small;
}
ul.blog-posts {
list-style-type: none;
padding: unset;
}
ul.blog-posts li {
display: flex;
}
ul.blog-posts li span {
flex: 0 0 130px;
}
ul.blog-posts li a:visited {
color: #8b6fcb;
}
@media (prefers-color-scheme: dark) {
body {
background-color: #333;
color: #ddd;
}
h1,
h2,
h3,
h4,
h5,
h6,
strong,
b {
color: #eee;
}
a {
color: #8cc2dd;
}
code {
background-color: #777;
}
pre code {
color: #ddd;
}
blockquote {
color: #ccc;
}
textarea,
input {
background-color: #252525;
color: #ddd;
}
.helptext {
color: #aaa;
}
}
</style>
</head>
<body>
<header><a href="/" class="title">
<h2>vulpine solutions</h2>
</a>
<nav><a href="/">Home</a>
<a href="/blog">Blog</a>
</nav>
</header>
<main>
<h1>rust is good, just not for me</h1>
<p>
<i>
<time datetime='2024-12-02' pubdate>
Dec 2, 2024
</time>
</i>
</p>
<content>
<p>Rust is the big new<sup id="fnref:1"><a href="#fn:1" class="footnote-ref" role="doc-noteref">1</a></sup> thing in just about every programming niche. web frameworks? of course there&rsquo;s a Rust one! in fact, there&rsquo;s dozens of them. command line tools? good luck finding one that <em>isn&rsquo;t</em> written in Rust these days. databases? oops, all Rust!</p>
<p>all of this carcinisation<sup id="fnref:2"><a href="#fn:2" class="footnote-ref" role="doc-noteref">2</a></sup> has me feeling kind of left out, though. you see, i&rsquo;ve never really vibed with Rust: i have tried it multiple times, even building a handful of (unfinished, naturally) projects with it, but i always bounce off of it eventually. for a long time, i attributed this to Rust just not being what it&rsquo;s hyped up to be, that it&rsquo;s actually a lot worse than everyone says it is, but&hellip; it really isn&rsquo;t. it <em>is</em> a good programming language. a great one, in fact! i want to dig a little deeper into <em>why</em> i, personally, don&rsquo;t vibe with it. (not very deep, mind you, because self-reflection is difficult as <em>hell</em>)</p>
<h2 id="its-too-low-level">it&rsquo;s too low-level</h2>
<p>starting off with the big one: <strong>Rust is a systems language.</strong> while it <em>also</em> works very well for web development, command line tools, and other software, it&rsquo;s not what it was designed for. it was designed for scenarios where you can (and often need to!) squeeze as much performance as possible out of a system, where a garbage collector on its own would already not fit into the device&rsquo;s memory, and where a string taking up any more space than its literal bytes is unacceptable.</p>
<p>meanwhile, when <em>i</em> used Rust, i just wrapped everything in an <code>Arc&lt;RwMutex&lt;T&gt;&gt;</code><sup id="fnref:3"><a href="#fn:3" class="footnote-ref" role="doc-noteref">3</a></sup> and called it a day, because i <em>don&rsquo;t</em> care about performance all that much. HTTP and database latency already destroy any optimization i could do to the business logic, so why even bother?</p>
<h2 id="i-was-constantly-fighting-the-compiler">i was constantly fighting the compiler</h2>
<p>i&rsquo;ll admit it: i didn&rsquo;t really go out of my way to learn Rust. like every other language i&rsquo;ve used, i just jumped in headfirst and started trying to rewrite my silly little programs into the silly little crab language. <strong>this was a mistake.</strong></p>
<p>Rust&rsquo;s compiler is its strongest suit: it catches bugs that no C or C++ compilers can even <em>imagine</em> exist, and its borrow checker seems like dark magic at times. but what makes the compiler great for experienced Rust users makes it an absolute <em>pain</em> for people learning the language. other languages let you throw code at the wall and see what sticks; Rust won&rsquo;t even let your code compile unless it works perfectly. this makes my learning process a lot more difficult, and as such, i never really learned more advanced Rust.</p>
<h2 id="macros-are-magic-but-not-the-good-kind">macros are magic, but not the good kind</h2>
<p>macros are <em>extremely</em> powerful. many of the libraries i was using heavily relied on them&ndash;some, like <code>sqlx</code> (no relation to <code>sqlx</code>, the Go library<sup id="fnref:4"><a href="#fn:4" class="footnote-ref" role="doc-noteref">4</a></sup>) are entirely built around them. they&rsquo;re also a nightmare to reason with as an inexperienced rustacean.</p>
<p>i&rsquo;m used to being able to ctrl-click on a function invocation to go directly to its implementation in other languages&ndash;Go, C#, and even Python all do this (well, as long as the Python package has type annotations, and you&rsquo;re not relying on external ones). this just doesn&rsquo;t work with macros, because the code is generated at compile time. it felt like i was feeding input into a black box and praying that whatever came out on the other side worked<sup id="fnref:5"><a href="#fn:5" class="footnote-ref" role="doc-noteref">5</a></sup>.</p>
<h3 id="types-for-days">types for days</h3>
<p>somewhat related to macros: some libraries like <a href="https://github.com/tokio-rs/axum">axum</a> generate <em>ridiculously</em> long type names, which, while funny, are impossible to actually parse. this didn&rsquo;t make debugging my code any easier.</p>
<h2 id="conclusion-i-guess">conclusion, i guess</h2>
<p>i don&rsquo;t really have any conclusion to draw from writing this. i guess my learning process just doesn&rsquo;t mesh with how Rust works, and that&rsquo;s why i bounced off of it.</p>
<p>i definitely think it&rsquo;s worth thinking about this for <em>any</em> language&ndash;or any other <em>tool</em> in general, even&ndash;that you dislike. it&rsquo;s honestly kind of depressing to be extremely negative about things without being able to articulate <em>why</em>. i&rsquo;m sure i&rsquo;ve annoyed plenty of friends by complaining about Rust or any other tool they like.</p>
<p>in fact, i should write a post like this for every language i dislike! Go, Elixir, maybe even PHP&ndash;well, maybe not that last one. it&rsquo;s been so long since i last used it that i&rsquo;m sure all my problems with it have been fixed at this point.</p>
<div class="footnotes" role="doc-endnotes">
<hr>
<ol>
<li id="fn:1">
<p>please ignore that it&rsquo;s been stable for over 9 years.&#160;<a href="#fnref:1" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:2">
<p><a href="https://en.wikipedia.org/wiki/Carcinisation">everything seems to evolve into crabs these days.</a>&#160;<a href="#fnref:2" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:3">
<p>wait a second, does that mean i just used a reference-counting garbage collector?&#160;<a href="#fnref:3" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:4">
<p><code>sqlx</code>, the Rust library that converts database rows to strongly typed structs using reflection magic (macros), not to be confused with <code>sqlx</code>, the Go library that converts database rows to strongly typed structs using reflection magic (the reflection package). they are somehow completely unrelated.&#160;<a href="#fnref:4" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:5">
<p>this is, coincidentally, why i don&rsquo;t use LLMs.&#160;<a href="#fnref:5" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
</ol>
</div>
</content>
<p>
</p>
</main>
<footer>Made with <a href="https://github.com/janraasch/hugo-bearblog/">Hugo ʕ•ᴥ•ʔ Bear</a>
</footer>
</body>
</html>

BIN
public/favicon.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 12 KiB

252
public/index.html Normal file
View file

@ -0,0 +1,252 @@
<!DOCTYPE html>
<html lang="en-gb">
<head>
<meta name="generator" content="Hugo 0.139.2">
<meta http-equiv="X-Clacks-Overhead" content="GNU Terry Pratchett" />
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<link rel="shortcut icon" href="https://blog.vulpine.solutions/favicon.png" />
<title>Home | vulpine solutions</title>
<meta name="title" content="Home" />
<meta name="description" content="vulpine problems require vulpine solutions" />
<meta name="keywords" content="" />
<meta property="og:url" content="https://blog.vulpine.solutions/">
<meta property="og:site_name" content="vulpine solutions">
<meta property="og:title" content="Home">
<meta property="og:description" content="heya, i’m sam! this is my attempt at a blog which i will definitely update often, trust me.
i deliberately don’t really have a public online presence, but you can find me here:
codeberg: https://codeberg.org/u1f320/ (git) forgejo: https://code.vulpine.solutions/sam (self-hosted git) pronouns.cc: https://pronouns.cc/@sam (i made this site!) vulpine problems require vulpine solutions">
<meta property="og:locale" content="en_gb">
<meta property="og:type" content="website">
<meta name="twitter:card" content="summary">
<meta name="twitter:title" content="Home">
<meta name="twitter:description" content="heya, i’m sam! this is my attempt at a blog which i will definitely update often, trust me.
i deliberately don’t really have a public online presence, but you can find me here:
codeberg: https://codeberg.org/u1f320/ (git) forgejo: https://code.vulpine.solutions/sam (self-hosted git) pronouns.cc: https://pronouns.cc/@sam (i made this site!) vulpine problems require vulpine solutions">
<meta itemprop="name" content="Home">
<meta itemprop="description" content="heya, i’m sam! this is my attempt at a blog which i will definitely update often, trust me.
i deliberately don’t really have a public online presence, but you can find me here:
codeberg: https://codeberg.org/u1f320/ (git) forgejo: https://code.vulpine.solutions/sam (self-hosted git) pronouns.cc: https://pronouns.cc/@sam (i made this site!) vulpine problems require vulpine solutions">
<meta itemprop="datePublished" content="2024-12-02T00:00:00+00:00">
<meta itemprop="dateModified" content="2024-12-02T00:00:00+00:00">
<meta itemprop="wordCount" content="51">
<meta name="referrer" content="no-referrer-when-downgrade" />
<link rel="alternate" type="application/rss+xml" href="https://blog.vulpine.solutions/index.xml" title="vulpine solutions" />
<style>
body {
font-family: Verdana, sans-serif;
margin: auto;
padding: 20px;
max-width: 720px;
text-align: left;
background-color: #fff;
word-wrap: break-word;
overflow-wrap: break-word;
line-height: 1.5;
color: #444;
}
h1,
h2,
h3,
h4,
h5,
h6,
strong,
b {
color: #222;
}
a {
color: #3273dc;
}
.title {
text-decoration: none;
border: 0;
}
.title span {
font-weight: 400;
}
nav a {
margin-right: 10px;
}
textarea {
width: 100%;
font-size: 16px;
}
input {
font-size: 16px;
}
content {
line-height: 1.6;
}
table {
width: 100%;
}
img {
max-width: 100%;
}
code {
padding: 2px 5px;
background-color: #f2f2f2;
}
pre code {
color: #222;
display: block;
padding: 20px;
white-space: pre-wrap;
font-size: 14px;
overflow-x: auto;
}
div.highlight pre {
background-color: initial;
color: initial;
}
div.highlight code {
background-color: unset;
color: unset;
}
blockquote {
border-left: 1px solid #999;
color: #222;
padding-left: 20px;
font-style: italic;
}
footer {
padding: 25px;
text-align: center;
}
.helptext {
color: #777;
font-size: small;
}
.errorlist {
color: #eba613;
font-size: small;
}
ul.blog-posts {
list-style-type: none;
padding: unset;
}
ul.blog-posts li {
display: flex;
}
ul.blog-posts li span {
flex: 0 0 130px;
}
ul.blog-posts li a:visited {
color: #8b6fcb;
}
@media (prefers-color-scheme: dark) {
body {
background-color: #333;
color: #ddd;
}
h1,
h2,
h3,
h4,
h5,
h6,
strong,
b {
color: #eee;
}
a {
color: #8cc2dd;
}
code {
background-color: #777;
}
pre code {
color: #ddd;
}
blockquote {
color: #ccc;
}
textarea,
input {
background-color: #252525;
color: #ddd;
}
.helptext {
color: #aaa;
}
}
</style>
</head>
<body>
<header><a href="/" class="title">
<h2>vulpine solutions</h2>
</a>
<nav><a href="/">Home</a>
<a href="/blog">Blog</a>
</nav>
</header>
<main>
<p>heya, i&rsquo;m sam! this is my attempt at a blog which i will <em>definitely</em> update often, trust me.</p>
<p>i deliberately don&rsquo;t really have a public online presence, but you can find me here:</p>
<ul>
<li>codeberg: <a href="https://codeberg.org/u1f320/">https://codeberg.org/u1f320/</a> (git)</li>
<li>forgejo: <a href="https://code.vulpine.solutions/sam">https://code.vulpine.solutions/sam</a> (self-hosted git)</li>
<li>pronouns.cc: <a href="https://pronouns.cc/@sam">https://pronouns.cc/@sam</a> (i made this site!)</li>
</ul>
<h6 id="_vulpine-problems-require-vulpine-solutions_"><em>vulpine problems require vulpine solutions</em></h6>
</main>
<footer>Made with <a href="https://github.com/janraasch/hugo-bearblog/">Hugo ʕ•ᴥ•ʔ Bear</a>
</footer>
</body>
</html>

34
public/index.xml Normal file
View file

@ -0,0 +1,34 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Home on vulpine solutions</title>
<link>https://blog.vulpine.solutions/</link>
<description>Recent content in Home on vulpine solutions</description>
<generator>Hugo</generator>
<language>en-gb</language>
<copyright>sam, CC-BY-SA 4.0</copyright>
<lastBuildDate>Mon, 02 Dec 2024 00:00:00 +0000</lastBuildDate>
<atom:link href="https://blog.vulpine.solutions/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>rust is good, just not for me</title>
<link>https://blog.vulpine.solutions/blog/rust-is-good-just-not-for-me/</link>
<pubDate>Mon, 02 Dec 2024 00:00:00 +0000</pubDate>
<guid>https://blog.vulpine.solutions/blog/rust-is-good-just-not-for-me/</guid>
<description>&lt;p&gt;Rust is the big new&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; thing in just about every programming niche. web frameworks? of course there&amp;rsquo;s a Rust one! in fact, there&amp;rsquo;s dozens of them. command line tools? good luck finding one that &lt;em&gt;isn&amp;rsquo;t&lt;/em&gt; written in Rust these days. databases? oops, all Rust!&lt;/p&gt;&#xA;&lt;p&gt;all of this carcinisation&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt; has me feeling kind of left out, though. you see, i&amp;rsquo;ve never really vibed with Rust: i have tried it multiple times, even building a handful of (unfinished, naturally) projects with it, but i always bounce off of it eventually. for a long time, i attributed this to Rust just not being what it&amp;rsquo;s hyped up to be, that it&amp;rsquo;s actually a lot worse than everyone says it is, but&amp;hellip; it really isn&amp;rsquo;t. it &lt;em&gt;is&lt;/em&gt; a good programming language. a great one, in fact! i want to dig a little deeper into &lt;em&gt;why&lt;/em&gt; i, personally, don&amp;rsquo;t vibe with it. (not very deep, mind you, because self-reflection is difficult as &lt;em&gt;hell&lt;/em&gt;)&lt;/p&gt;</description>
</item>
<item>
<title>go&#39;s panics are fundamentally flawed</title>
<link>https://blog.vulpine.solutions/blog/go-panics-are-fundamentally-flawed/</link>
<pubDate>Tue, 05 Nov 2024 00:00:00 +0000</pubDate>
<guid>https://blog.vulpine.solutions/blog/go-panics-are-fundamentally-flawed/</guid>
<description>&lt;p&gt;&lt;em&gt;(alternative title: &lt;code&gt;panic()&lt;/code&gt; considered harmful)&lt;/em&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;errors-how-do-they-work-anyway&#34;&gt;errors, how do they work anyway?&lt;/h2&gt;&#xA;&lt;p&gt;errors in Go programs are represented by values. when calling a function that may return an error, it&amp;rsquo;ll return &lt;code&gt;(T, error)&lt;/code&gt;, and you can handle the error the same way you would any other value.&lt;/p&gt;&#xA;&lt;p&gt;(note: the &lt;code&gt;(T, error)&lt;/code&gt; syntax doesn&amp;rsquo;t imply Go has tuples, because it doesn&amp;rsquo;t. functions can just return multiple values.)&lt;/p&gt;&#xA;&lt;p&gt;now, this approach does have some problems. Go lets you ignore the error very easily, by using the discard operator &lt;code&gt;_&lt;/code&gt; rather than assigning it to a variable. it&amp;rsquo;s also extremely verbose&amp;ndash;anyone who has used Go a substantial amount has written &lt;code&gt;if err != nil { return err }&lt;/code&gt; a thousand times. both of these issues are fixable, though: the compiler could emit a warning or an error (heh) when discarding an error value, and new syntax could be introduced to bubble errors up more easily.&lt;/p&gt;</description>
</item>
<item>
<title>hello world!</title>
<link>https://blog.vulpine.solutions/blog/hello-world/</link>
<pubDate>Mon, 04 Nov 2024 00:00:00 +0000</pubDate>
<guid>https://blog.vulpine.solutions/blog/hello-world/</guid>
<description>&lt;p&gt;oh hey, it&amp;rsquo;s the stereotypical &amp;ldquo;hello world&amp;rdquo; post. look at me! i copy pasted a hugo tutorial!&lt;/p&gt;&#xA;&lt;p&gt;turns out making a blog is really difficult, and not for technical reasons. it&amp;rsquo;s just really hard to actually write things consistently.&#xA;i can&amp;rsquo;t promise anything in that regard&amp;ndash;expect this site to get about one post a year, and that&amp;rsquo;s &lt;em&gt;if&lt;/em&gt; i actually remember it exists.&lt;/p&gt;&#xA;&lt;p&gt;until then though, have fun reading the one rant i&amp;rsquo;ve already written. hope you like go because if not, it probably isn&amp;rsquo;t for you!&lt;/p&gt;</description>
</item>
</channel>
</rss>

2
public/robots.txt Normal file
View file

@ -0,0 +1,2 @@
User-Agent: *
Sitemap: https://blog.vulpine.solutions/sitemap.xml

20
public/sitemap.xml Normal file
View file

@ -0,0 +1,20 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
<url>
<loc>https://blog.vulpine.solutions/blog/</loc>
<lastmod>2024-12-02T00:00:00+00:00</lastmod>
</url><url>
<loc>https://blog.vulpine.solutions/</loc>
<lastmod>2024-12-02T00:00:00+00:00</lastmod>
</url><url>
<loc>https://blog.vulpine.solutions/blog/rust-is-good-just-not-for-me/</loc>
<lastmod>2024-12-02T00:00:00+00:00</lastmod>
</url><url>
<loc>https://blog.vulpine.solutions/blog/go-panics-are-fundamentally-flawed/</loc>
<lastmod>2024-11-05T00:00:00+00:00</lastmod>
</url><url>
<loc>https://blog.vulpine.solutions/blog/hello-world/</loc>
<lastmod>2024-11-04T00:00:00+00:00</lastmod>
</url>
</urlset>

BIN
static/favicon.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 12 KiB

1
themes/hugo-bearblog Submodule

@ -0,0 +1 @@
Subproject commit efc24bc5e95f0ccb88051e1a7d95e8a1404e953e