gram

From README for Tetris on CHIP-8 (1991). We should bring back sending feature request in an envelope with $5 attached.

#chip8

Today I got some time to find out why my #zsh takes a noticeably long time to start. The offender was #nvm. As I removed it, the time got down from 450ms to 60ms.

To time startup of zsh vs bash:

$ for i in $(seq 1 10); do /usr/bin/time bash -i -c exit; done

$ for i in $(seq 1 10); do /usr/bin/time zsh -i -c exit; done

To find how long each plugin takes at startup, add `zmodload zsh/zprof` at the top of `~/.zshrc` and `zprof` at the bottom.

#linux #nodejs #bash

@ShinNoNoir There are also #LFE (Lisp-Flavored Erlang) :lfe: and #Gleam, both are nice languages running on BEAM.

@raiderrobert

Wrestling with #DjangoRestFramework to make an adapter serializer that uses #pydantic for validation.

DRF embodies all the worst things about Java-style OOP. There are base classes, mixins, attributes that must not be used before you call a specific methods, nothing is documented, and, of course, not annotated. Even drf-stubs project that supposed to annotate DRF is full of Any. And then we also stuck with pydantic v1 where you can't have custom serializers.

What a day.

What are your favorite #corecursive (or another similar IT #podcast) episodes? I have a 10h flight ahead, and all I'm going to have there is an ipod.

@aohorodnyk @ede I came here to say that. #Taskfile syntax is very similar to the examples in bkn, so it might be a good inspiration.

And there is nothing wrong about reinventing things. It's fun, you can a lot along the way, and maybe you can even make something better and be an inspiration for someone else. Keep going!

@warrickball @pyodide I use pyodide to run a whole bunch of things. For example:

IDE for drawing #svg images with #python:
http://svg.orsinium.dev/

#Flake8 with plugins:
https://wps.orsinium.dev/

@mgorny You can use #flit to produce sdist distributions with autogenerated setup.py:

https://flit.pypa.io/en/stable/cmdline.html#cmdoption-flit-build-setup-py

#python

The previous post with the hashtag #litestar is me praising it's sqlalchemy integration. Oh irony.

Last week I decided to pick #litestar instead of #fastapi for a new #python microservice and I already regret this decision. I can't make DB rollbacks work in tests because the test client runs the server in a separate thread with its own event loop. And it feels like I'm the first one doing it and there is no community to help.

I learned a valuable lesson: don't underestimate the importance of community. Sometimes, it's better to go with mainstream. Especially for commercial projects.

@python_discussions That's not true. You need to specify `__all__` in `__init__.py` (and other facades) so that #mypy, #flake8, and #ruff know that these packages are imported to be exported. Then flake8 and ruff won't report unused import and mypy will allow reexports from the module.

#python

@glowrocks Django is still very much alive and I, unfortunately, work with it daily at my job. It didn't age well, though. The support for asyncio is still quite rough, support for typing is third-party (see django-stubs) and painful, and it hides too many things (the ORM makes it too easy to make bad requests). The modern most hyped web framework is #fastapi and I personally found #litestar (ex #starlite) quite nice (better #sqlalchemy integration).