willhoyle

- Here's the thing nobody tells you about fitting singularities

- But here's the part that should unsettle you

- And the uncomfortable answer is: it's already happening.

- The labor market isn't adjusting. It's snapping.

I was evaluating various Python async http frameworks and landed on a similar stack:

- attrs/cattrs for models - starlette+uvicorn for HTTP/websocket - validation I’m still on the fence about. I’ll see how far I get with the built in validators offered by attrs. I use voluptuous at work and generally like the DX but it’s in maintenance mode.

This is purely personally preference, I’m sure devs using fastapi+pydantic are more productive in the long run. It almost feels like I’m hand rolling my own fastapi implementation but at the same time I don’t want to be too locked in to frameworks like that.

Ive been burnt by magic frameworks that do too much behind the scenes and there’s something nice about fully understanding what’s going on when you hand stitch libraries yourself.

For some reason I kept getting extreme slowdowns/laggy behaviour when using neovim.

I’ve seen this thread: https://github.com/tmux/tmux/issues/353

I tried everything in the thread and still end up with a laggy terminal. For now I just use iterm2 with tabs but I miss my tmux.

On my personal Linux laptop, I never encounter the same lag with the same setup.

My thinking is that logging food is annoying (weighing and tracking food you ate). I want to make a more fluid way of just selecting recipes or food and encourage a more scalable/intuitive way of eating.

Looks like a cool project you’ve built there.

Hope they can improve, might give it another go once I have time.

The 7 repos are gone now and a k8s cluster has replaced the swarm service. Deployments are a bit easier to manage now. It's still such slow development process to add a simple API endpoint, especially if that API has to call other DAOs. It's crazy because I feel like it's completely normalized here that dev work takes 300% longer than it should for simple features.

I’ve had pretty decent success using this library.

I’m genuinely curious what simple site would cause a 30+ minute build? Is it just one of those things that grow over time?

I’m sure there’s other aspects I’m missing which make this a bad idea but there’s something that doesn’t feel right about people owning 2-3 homes while others can’t get on the property ladder.

You have to compile a previous commit from the repo because the experimental implementation of quic was removed according to this issue: https://github.com/nodejs/node/pull/37067

Not sure when we can expect it to come back. You can just feel the pain in those comments. All that hard work.

Also, thanks for not calling the website offsideSornot.com ;)

I'm always reminded of https://xkcd.com/927/ when another UI framework pops up. Do all libraries do things just differently enough to warrant a completely new library or can the implementation details be abstracted to some core lib (maybe even a web spec).

On the other hand, maybe I'm wrong and HeadlessUI ends up being that GenericUI lib.

I often wonder whether we need yet another UI framework implementation? I touched on this in my post a couple days ago: https://williamhoyle.ca/blog/2021/vue-has-too-many-ui-framew...

To summarize:

We have 20+ UI frameworks written in Vue. Surely there's enough common ground/code to combine the implementation details for all these common components. For example, OP mentioned the complexities of implementing a modal with some corner cases for 'ESC' behaviour. This is a universal concept whether you're using WidgetUI or TailwindUI. How many times are we going to re-implement a modal/button/dialog/menu?

We have to learn another set of APIs, props, component names, etc... Of course, no one is forcing us to use this. But it seems like we're going in circles re-implementing the same UI patterns over and over again.

I wish we could standardize on a library. Imagine just pulling in GenericUI and sprinkling in your CSS of choice (e.g. tailwindCSS, Bulma, Material, etc...).

I'm a Vue guy, but I think my argument still stands for the React ecosystem.

I thought SSR support was pretty good in Quasar? https://quasar.dev/quasar-cli/developing-ssr/ssr-frequently-...

There’s 3 dedicated buttons for paired Bluetooth devices (fn + 1,2,3) and hitting them just pairs to the device. And you can reassign a button to another device by holding fn+1,2,3.

When you turn it on it pairs to the last device it was paired to.

It’s an animated series that takes place inside the human body. I’ve been meaning to watch it myself. It’s supposed to be pretty accurate.