diff options
| author | Ashelyn Rose <git@tempest.dev> | 2023-05-08 02:17:40 -0600 |
|---|---|---|
| committer | Ashelyn Rose <git@tempest.dev> | 2023-05-08 02:17:40 -0600 |
| commit | 880cfbeb74546056feab63ed6e92a10c0dbaf2c3 (patch) | |
| tree | 33c7429bd5b1b968d74c74a4b7fbf0aa072111f7 /posts | |
| parent | 885d95d889633e312567d891831d74d9e120e5b8 (diff) | |
New layout, uses nextjs
Diffstat (limited to 'posts')
| -rw-r--r-- | posts/01_04_2023-advent-of-wasm.html | 123 | ||||
| -rw-r--r-- | posts/07_29_2022-on-communities-and-trust.html | 107 | ||||
| -rw-r--r-- | posts/08_01_2022-thoughts-on-neovim.html | 109 | ||||
| -rw-r--r-- | posts/index.html | 42 |
4 files changed, 0 insertions, 381 deletions
diff --git a/posts/01_04_2023-advent-of-wasm.html b/posts/01_04_2023-advent-of-wasm.html deleted file mode 100644 index 4f707a6..0000000 --- a/posts/01_04_2023-advent-of-wasm.html +++ /dev/null @@ -1,123 +0,0 @@ -<!DOCTYPE html> -<html> - <head> - <title>Advent of Wasm</title> - <link rel="stylesheet" href="/resources/style.css"/> - <meta name="viewport" content="width=device-width, initial-scale=1"> - </head> - <body> - <nav> - <a href="/">Home</a> - <a href="/about.html">About</a> - <a href="/posts/">Posts</a> - </nav> - <h1> - Advent of Wasm - <span class="subtitle">Now with 87% more pain</span> - </h1> - - <p> - So the last few years I have done Advent of Code off and on. Sometimes - I have tried to learn a new language, other times I was just trying to - beat my dad each evening. This year though, this year I don't know what - I was thinking. - </p> - - <p> - It was several weeks after everyone else had started, I had largely written - it off for the year - I was not up for it. Until a terrible idea crossed - my mind. - </p> - - <p> - Like an intrusive thought, my mind asked: "Well you've been wanting to do - something in web assembly for a while right? How bad could it be?" - </p> - - <br/> - - <p> - Turns out I was definitely not ready for this. - </p> - - <h2>So what was so hard about it?</h2> - - <p> - More than anything else, I forgot how much you need to do by hand to do - any sort of assembly. The first day saw me spending several hours just - on some loader code to pass the puzzle input in from JS, call a wasm - function, and then read back the result. - </p> - - <p> - Next was a few functions for reading numbers out of the wasm memory buffer, - parsing them from ascii, etc. The core read loop was not too tricky, but - the bit that took far longer than it had any reason to was converting my - answer back to ascii and shoving it into an output area. - </p> - - <p> - Really none of it was surprising, and none of it <em><strong>*should*</strong></em> - have been that hard ... it's just been a while since this Javascript girl - has written truly low-level code. - </p> - - <p> - To make matters worse I got hard-core distracted by the non-wasm part of - my wasm project. After the first day I returned to my stub JS loader and - expanded it into a little wasm explorer. - </p> - - <p> - I added a code view, syntax highlighting, auto-loaded my puzzle inputs, - even made a janky little dynamic list that would automatically pick up - new days' solutions as I added them to the repo without needing me to - touch the loader page each day. - </p> - - <p> - In the end I'm really quite proud of it, I will absolutely be reusing - this setup for future years, and you should - <a href="https://aoc2022.tempest.dev/" target="_blank">check it out</a> - if you haven't already ... but for wanting to challenge myself with - something new I was doing a lot of the same-old. - </p> - - <p> - Ultimately I got through 3 days before giving up jusst because every - step along the way involved <em><strong>*so much*</strong></em> extra - code. I may come back to some of the puzzles later, but for now I'm - kind of happy with what I did, and I don't feel like I need to prove - myself by doing more. I was doing it for fun, and so I stopped when - it stopped being fun. - </p> - - <h2>Tips if you want to get into writing wasm by hand?</h2> - - <p> - Uhh ... maybe consider don't? - </p> - - <p> - Jokes aside: do a throwaway project or two so you get used to passing - data into and out of wasm, whatever parsing you're going to do, etc. - </p> - - <p> - Do everything in your power to make sure you can focus on the actual - wasm part of your project, because (at least if you're anything like - me) it's easy to get sidetracked with all that. - </p> - - <p> - With that said: I had fun. Doing new things is always a treat, so if - you're looking for something new to try definitely consider giving - webassembly a look. - </p> - - <footer> - <a href="https://git.tempest.dev/ashe/tempest.dev">Site Source</a> - <a href="/pay-transparency.html">Pay Transparency</a> - </footer> - </body> -</html> diff --git a/posts/07_29_2022-on-communities-and-trust.html b/posts/07_29_2022-on-communities-and-trust.html deleted file mode 100644 index 4aef9ae..0000000 --- a/posts/07_29_2022-on-communities-and-trust.html +++ /dev/null @@ -1,107 +0,0 @@ -<!DOCTYPE html> -<html> - <head> - <title>On Communities and Trust</title> - <link rel="stylesheet" href="/resources/style.css"/> - <meta name="viewport" content="width=device-width, initial-scale=1"> - </head> - <body> - <nav> - <a href="/">Home</a> - <a href="/about.html">About</a> - <a href="/posts/">Posts</a> - </nav> - <h1> - On Communities and Trust - <span class="subtitle">Some thoughts on the VRChat security update</span> - </h1> - - <p> - So we've had the VRChat Security Update for a few days now, and while I'm - not the most prolific VR community member, I have heard a fair bit of - discourse about the update. This update has been a polarizing one to say - the least, with users excited for the new features that were and will soon - be added, others decrying the performance issues they have now from Easy - Anti-Cheat, and still others still unable to play due to missing - accessibility features they previously would have gotten via mods. - </p> - - <p> - Overall, my personal concerns about update itself have been resolved: - although I used to run into issues with EAC crashing when hardware - virtualization was enabled, that seem to no longer be the case, and I - personally haven't even seen a performance hit. I was not - using any mod features, and the changes in the most recent beta - certainly a welcome addition to my experience. - </p> - - <p> - However, I do still have some broader community concerns about how the - update was announced and rolled out, as well as how the VRChat team seems - to be handling this whole scenario as if they're only playing public - opinion damage control. - </p> - - <p> - Regardless of their official policy or any amount of discouragement - towards mods for VRChat, the fact of the matter is that a large portion - of their community relied on mods to add accessibility, performance, or - comfort features to the game. While I have to acknowledge that the VRC - team has added some of these features back into the game since blocking - mods, the fact that they needed to reprioritize these features (as they - have been pretty clear about in their updates) shows us that they had - no interest in adding these features until they faced public backlash. - </p> - - <p> - You might think that a reasonable development team (if they wanted to - reduce the use of mods for their game) might look at the sizable portion - of their community using mods for this sort of enhancement, - and come to the conclusion "clearly there is need for these features, - let's reduce the need for mods by implementing those features". But instead the - VRChat team decided to actively make their game worse for those people instead. - Disabling comments on Steam further indicates that they knew this would - be disliked by the community ahead of time, but chose to do it anyways. - </p> - - <p> - Listen, VRChat team - what sort of conclusions am I supposed to draw about - your priorities here?!? Improving the game experience for your most - vulnerable players doesn't make the roadmap, but pushing an ineffective - solution to a problem <b>against the angry backlash of your community</b> - makes the cut? - </p> - - <p> - So yeah . . . I guess in one sense, the game is fine. It's getting new features, more are - on the horizon, the community feels like they've been listened to. - </p> - - <p> - But in another sense, the security update has made it incredibly clear - that the VRChat team either does not care, or did not think to consider - how their priorities would affect large portions of their community. - </p> - - <p> - Social games grow and shrink with their communities. Regardless of technical - decisions, updates, or anything else, if large portions of the community - leave or can no longer join, then VRChat will no longer be the same game - (and it will be worse for it). With the latest changes and how they've - handled the community response, I just can't convince myself that the team remembers - this. - </p> - - <p> - In that regard, I feel that even more than the actual removal of features - they have violated our trust - and unless this newfound responsiveness to - the needs of their players sticks around longer than it takes to clean up - their PR mess, I personally am hesitant to forgive them. - </p> - - <footer> - <a href="https://git.tempest.dev/ashe/tempest.dev">Site Source</a> - <a href="/pay-transparency.html">Pay Transparency</a> - </footer> - </body> -</html> diff --git a/posts/08_01_2022-thoughts-on-neovim.html b/posts/08_01_2022-thoughts-on-neovim.html deleted file mode 100644 index 183902a..0000000 --- a/posts/08_01_2022-thoughts-on-neovim.html +++ /dev/null @@ -1,109 +0,0 @@ -<!DOCTYPE html> -<html> - <head> - <title>Thoughts on Neovim</title> - <link rel="stylesheet" href="/resources/style.css"/> - <meta name="viewport" content="width=device-width, initial-scale=1"> - </head> - <body> - <nav> - <a href="/">Home</a> - <a href="/about.html">About</a> - <a href="/posts/">Posts</a> - </nav> - <h1> - Thoughts on Neovim - <span class="subtitle">Who even needs an IDE anyways?</span> - </h1> - - <h2>Why I'm using Neovim</h2> - - <p> - When I first started coding in high school and then later in early - college I used to jump around between editors a lot more than I do today. - I used Notepad++, then Visual Studio, briefly Netbeans, then Atom. - </p> - - <p> - But since settling into frontend web development I've stayed with VSCode - for a very long time. I liked it because it was straightforward to get - started with, but versatile enough to extend for other languages. - Between various jobs and projects I used it for Javascript, Java, C#, - Rust, and C - and it did admirably at pretty much all of these. - </p> - - <p> - But about a year ago I saw that VSCode had a Neovim plugin, and I was - intrigued. I'd wanted to get more familiar with Vim beyond the basic - hjkl navigation, and this seemed like a great way to do that! - </p> - - <p> - So for the last year and change I've had the - <a target="_blank" href="https://marketplace.visualstudio.com/items?itemName=asvetliakov.vscode-neovim">vscode-neovim</a> - plugin installed, and I've been really enjoying it! - </p> - - <p> - I quickly fell in love with visual block mode, or the "delete N words" - commands. They're just so handy I suddenly felt like they were missing - if I needed to edit code any other way! - </p> - - <p> - But over the weekend I made the jump from using Neovim inside VSCode to - using it more or less on its own. I saw a video that mentioned the - AstroNvim configuration framework and Neovide, and decided "yeah, I think - I want to try that", and a few days later . . . here we are. - </p> - - <h2>How is it going?</h2> - - <p> - Overall, surprisingly well. - </p> - - <p> - The AstroNvim config I'm using already had NeoTree set up which is - very nice. I've figured out how to get ESLint and Prettier configured - for work, rust-analyzer installed for my own projects, I've been poking - at themes over and over again, and honestly . . . I'm really liking this. - </p> - - <p> - Getting Neovide to connect to a VM over the network was relatively - straightforward, I love how easy it is to drop my config into git and - keep it synced between computers, and finally having proper mouse support - (which I never could get sorted out with my terminal) is a pretty big - game changer for when I'm just reading code. - </p> - - <p> - Also, I'd be lying if I said that I didn't love the smooth scrolling and - cursor animation. I am a simple girl after all. - </p> - - <h2>Should you try replacing your IDE?</h2> - - <p> - That is a tricky question to answer. - </p> - - <p> - I was comfortable spending some time experimenting with this because I - already had decent familiarity with Vim and had been using Neovim - specifically for a while. If you don't have any similar experience, - the learning curve is going to be pretty steep. - </p> - - <p> - But hey - if you're looking for a challenge, you'll definitely learn - a lot. - </p> - - <footer> - <a href="https://git.tempest.dev/ashe/tempest.dev">Site Source</a> - <a href="/pay-transparency.html">Pay Transparency</a> - </footer> - </body> -</html> diff --git a/posts/index.html b/posts/index.html deleted file mode 100644 index 05beb66..0000000 --- a/posts/index.html +++ /dev/null @@ -1,42 +0,0 @@ -<!DOCTYPE html> -<html> - <head> - <title>Posts</title> - <link rel="stylesheet" href="/resources/style.css"/> - <meta name="viewport" content="width=device-width, initial-scale=1"> - </head> - <body> - <nav> - <a href="/">Home</a> - <a href="/about.html">About</a> - <a href="/posts/">Posts</a> - </nav> - <h1> - Posts - </h1> - <h2>2023</h2> - <ul class="posts"> - <li> - <span>January 4</span> - <a href="/posts/01_04_2023-advent-of-wasm.html">Retrospect: Advent of Wasm</a> - </li> - </ul> - - <h2>2022</h2> - <ul class="posts"> - <li> - <span>August 1</span> - <a href="/posts/08_01_2022-thoughts-on-neovim.html">Thoughts on Neovim</a> - </li> - <li> - <span>July 29</span> - <a href="/posts/07_29_2022-on-communities-and-trust.html">On Communities and Trust</a> - </li> - </ul> - - <footer> - <a href="https://git.tempest.dev/ashe/tempest.dev">Site Source</a> - <a href="/pay-transparency.html">Pay Transparency</a> - </footer> - </body> -</html> |