txarli/txarli.dev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch 'main' of https://github.com/cassidoo/blahg

Browse Source
This commit is contained in:
Cassidy Williams
2024-01-19 15:35:11 -06:00
parent 7d28c7f6d9 1f06123445
commit 7718725393
2 changed files with 43 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/posts/annoyed-at-react.md
View File

@@ -1,10 +1,12 @@
---
layout: "../layouts/BlogPost.astro"
title: "Kind of annoyed at React"
layout: ../layouts/BlogPost.astro
title: Kind of annoyed at React
slug: annoyed-at-react
description: "Just a little ranty rant about my fave JS library, ya know."
added: "Jan 13 2024"
tags: [technical, musings]
description: 'Just a little ranty rant about my fave JS library, ya know.'
tags:
- technical
- musings
added: 2024-01-13T00:00:00.000Z
---
I'm kind of annoyed at the state of React lately. I still use it regularly, and am somewhat friendly with the folks that work on it still, and it's the first library I reach for, but... it's just gotten too confusing and frustrating.
@@ -13,6 +15,6 @@ Not to boast but I like... really know React. I've used it for almost a decade.
I feel like the lack of understanding comes from not communicating properly with the community (both educational content and also transparency about what/how/etc things are being built), and it frustrates me.
It's frustrating to see that there hasn't been a release [since June 2022](https://github.com/facebook/react/releases/tag/v18.2.0). It's frustrating that the core team all spouted "use a framework!" with React 18 and then most of them left their jobs to join [a company that owns a large React framework] and [that framework] seems to use Canary releases rather than the one that's stable and out in the world (and it seems like a "cool kid" monopoly). It's frustrating that they took _so long_ to write new documentation (and the folks writing them weren't properly supported) that if you look up "React documentation" the new docs aren't even the first result. It's frustrating that there's [two Reacts](https://overreacted.io/the-two-reacts/) now (not that there shouldn't be, but that it's not clear/an easily understandable mental model for most people). It's frustrating that diversity efforts [visibly took a backseat](https://twitter.com/rachelnabors/status/1586772024252583936) with React leadership and there's just not as many voices from a variety of different people anymore.
It's frustrating to see that there hasn't been a release [since June 2022](https://github.com/facebook/react/releases/tag/v18.2.0). It's frustrating that the core team all spouted "use a framework!" with React 18 and then most of the vocal ones left their jobs to join \[a company that owns a large React framework] and \[that framework] seems to use Canary releases rather than the one that's stable and out in the world (and it seems like a "cool kid" monopoly). It's frustrating that they took *so long* to write new documentation (and the folks writing them weren't properly supported) that if you look up "React documentation" the new docs aren't even the first result. It's frustrating that there's [two Reacts](https://overreacted.io/the-two-reacts/) now (not that there shouldn't be, but that it's not clear/an easily understandable mental model for most people). It's frustrating that diversity efforts [visibly took a backseat](https://twitter.com/rachelnabors/status/1586772024252583936) with React leadership and there's just not as many voices from a variety of different people anymore.
Bleh, anyway. I really didn't mean for this to be a negative nancy post. I've harped on the React team's communication before and I do think they've gotten a bit better. And again, I still reach for React when I want to build something somewhat complex, I just... wish I were happier about it when I do. I'm optimistic for the future. Kind of.

35
src/posts/base-css.md Normal file
View File

@@ -0,0 +1,35 @@
---
layout: ../layouts/BlogPost.astro
title: Base CSS for your text-based pages
slug: base-css
description: >-
Sometimes the defaults your web browser gives you aren't very cute. Here's a
lil snippet I use to fix that.
tags:
- technical
added: 2024-01-19T07:56:14.460Z
---
If you don't want to deal with styling a mostly text-based HTML document, plop these lines in and it'll look good:
```css
html {
font-family: 'Helvetica Neue', 'Helvetica', 'Arial', sans-serif;
font-size: 1.3em;
max-width: 40rem;
padding: 2rem;
margin: auto;
line-height: 1.5rem;
}
```
I use this for a bunch of projects where I just need some plain ol' styling that is better than the defaults (and that I can easily add to), like [AI Ipsum](https://ai-ipsum.app/) and [W-9 Crafter](https://github.com/cassidoo/w9-crafter).
You can save [cass.run/basecss](https://cass.run/basecss) if you want a quick link to the snippet, and here's a little demo of what it looks like:
<p class="codepen" data-height="300" data-theme-id="light" data-default-tab="result" data-slug-hash="YzgVYWV" data-editable="true" data-user="cassidoo" style="height: 300px; box-sizing: border-box; display: flex; align-items: center; justify-content: center; border: 2px solid; margin: 1em 0; padding: 1em;">
<span>See the Pen <a href="https://codepen.io/cassidoo/pen/YzgVYWV">
Cassidy's base CSS demo</a> by Cassidy (<a href="https://codepen.io/cassidoo">@cassidoo</a>)
on <a href="https://codepen.io">CodePen</a>.</span>
</p>
<script async src="https://cpwebassets.codepen.io/assets/embed/ei.js"></script>