I tried Hurl after Insomnia went the way of Postman. The highlights you list were the strong drivers for testing it out. Where Hurl fell short was composing requests. Example: X.hurl response has authToken. Y.hurl uses authToken. Z.hurl uses authToken. There's no import ability[1], so you've got to use other tooling to copy X.hurl into Y.hurl and Z.hurl.
Ultimately settled on Bruno. It's backed by readable text files[2] as well. The CLI works for scripting. And the GUI is familiar enough that I've managed to convert Postman holdouts at my dayjob.
I migrated to Alpine for my laptop this year after an extended attempt of NixOS.
For development, I’ve found I’m more productive in that I don’t go down the rabbit hole of finding the “Nix way” of using a language/tool.
The speed of apk is refreshing for my older machine, and APKBUILDs are intuitive after my past experience with Arch PKGBUILD.
Also, seeing the network request for background gradients takes me back to an era of CSS I don't miss. Anyone remember the hacks for drop shadows and rounded corners?
> Anyone remember the hacks for drop shadows and rounded corners?
Originally it was kinda simple: just a 3x3 <table> with stretched images in the outer cells, then <div>-itis. Fortunately we rarely needed 9 nested <div> elements - a common trick was to create a 2000x2000px-sized PNG containing the top-left, top, and left-edge border and then another for the other side and make that a background image - the only problem was the lack of support for transparency and how IE would get PNG colors wrong for some reason until IE8 unless you altered the gamma ( https://salman-w.blogspot.com/2011/03/png-color-problem-in-i... )
And that was around the time the CMS was really getting mainstream (instead of Frontpage). So then you had to go digging through a million templates trying to wrap the right thing with your 3x3 table.
It was fun breaking sites with XSS vulnerabilities (i.e. most of them) where entering </table> into an unsanitized user-content editor would break the entire website layout.
https://imgur.com/a/vb6h0IF - complete with the "legitimate interest" checks that basically say "we see you'd rather not be stalked, we'd like to stalk you anyway". Never click "reject all" if you actually want to opt out of all tracking, always go to the options screen or what-ever they call it because "reject all" usually means "reject all except for those that claim legitimate interest" (i.e. not even remotely rejecting all).
If you are not in the EU, you just get all the tracking without even being asked (instead of being asked but any negative response somehow worked around).
Each of those chevrons when clicked lists the hundreds of partners that you are potentially being followed around by. They make it painful to opt out (impossible to permenantly opt out but of course easy to permanently opt in, accidentally or otherwise) though this design is not as egregious as many I've seen as it gives an opt-out-all click for "legitimate interest". Some sites ("powered by Admiral" - I'm looking at you, well actually I'm not as you are collecting in the list of sites blocked at the network DNS level here) make you click a separate option off for every. single. one. of. the. many. many. many. many. many. 3rd parties.
No guessing needed. You only get them in the EU because the EU government decided to stand with people not wanting to be tracked everywhere and other governments have not (yet?) gone that way.
California has enacted some relevant policy in that direction, but IIRC it does not require consent in the same way the EU legislation does.
I guess someone's got rich^W an okay business offering CCPaaS: Cookie Consent Popup as a Service.
I remember looking up some tourist destination and reading a few travel blogs about it, the cookie consent popups of the different sites looked identical
Yes, PineTime is another low cost and cheaper open smart watch alternative (USD$25) but based on Nordic SoC nRF52832, check the previous PineTime discussions on HN:
Benjie, one of the PostGraphile creators, has a good talk [1] advocating for database-driven development.
OTOH, having dug into PostGraphile a bit, I personally wouldn't advocate for pushing so much backend logic into the DB.
Like, if you decide to do auth and TOTP in the DB, you'll end up implementing it in PL/pgSQL. Writing core security logic in a less-familiar language feels like it adds risk.
Also, for smaller projects your backend is often just a single server, so moving auth in into the DB doesn't save you from managing distributed state.
Right, except if my backend is in JS, there's a cognitive cost to adding another language to the stack.
I could use plv8, but there's a more subtle preference here for JS to wrap SQL, rather than the reverse (plus tooling is less convenient, e.g. if you're writing Typescript).
exactly! this is the ecosystem that I'm a part of that inspired me to build this :)
I do agree about making sure you have experience writing PL/pgSQL and would also add that you should make sure you have a good test-driven environment when writing code in the db.
Came here to recommend "Fall; Or, Dodge in Hell" as well. I recently finished it. While Stephenson can get long-winded, it was a thought provoking story around how brain simulation is received by the world.
Will check out Bobiverse. Thanks for the recommendation!
Running locally avoids the concern of sending IP or PII to third parties.
[1]: https://github.com/David-Kunz/gen.nvim