danstewart_
I bounce around API clients a lot because the UX just never feels right, they always get in the way or start to feel clunky sooner or later.
With Yaak it feels natural, it’s clean and simple and is a joy to use.
I’m looking forward to seeing it grow and improve further.
I just hope as its feature set grows it can hold on to that simplicity. Hopefully the plugin system can be used to bridge any gaps without overloading the main app.
They have incredible defaults that can make it as simple as just running ‘git push’ but there isn’t really any magic happening, it’s all documented and configurable.
I feel it’s safer for scripts that have irreversible (or difficult to reverse) actions.
Take a look at the 3 videos here: https://solito.dev
Solito is a thin wrapper around React Native and next.js so make it easier to share as much code as possible between the website and the native apps but still have the apps actually behave like native apps.
The site is showing the correct timezone for me on safari.
Yes, Scotland is within the island of Britain but many of us (though not all) identify as Scottish, not British.
This seems to come up a lot online and I wonder what percentage of people making the corrections are actually Scottish…
I use a bash function to load the MDN page for the status:
function man-http() {
code="$1"
if [[ -z $code ]]; then
echo "Usage: man-http <status code>"
exit 0
fi
firefox "https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/$code"
}We deploy our full monolithic app to lambda (as a docker image) and then just have a wrapper entrypoint script that dispatches the request to the appropriate module and function.
There are benefits to keeping each lambda function small but we like the benefit of deploying one lambda and being able to call any function within the monolith.