statenjason

Aider as a non-agentic coding tool strikes a nice balance on the efficiency vs effectiveness front. Using tree-sitter to create a repo map of the repository means less filesystem digging. No MCP, but shell commands mean it can use utilities I myself am familiar with. Combined with Cerebras as a provider, the turnaround on prompts is instant; I can stay involved rather than waiting on multiple rounds of tool calls. It's my go-to for smaller scale projects.

I use gen.nvim[1] with for small tasks, like “write a type definition for this JSON” .

Running locally avoids the concern of sending IP or PII to third parties.

[1] https://github.com/David-Kunz/gen.nvim

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.

[1] https://github.com/Orange-OpenSource/hurl/issues/1723

[2] https://docs.usebruno.com/bru-language-samples.html

I use both.

Restic for various machines to hourly backup on a local server. Rclone to sync those backups to S3 daily.

Keeps the read/write ops lower, restores faster, and limits to a single machine with S3 access.

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.

Drew DeVault has a decent write up on Alpine that’s worth a read. https://drewdevault.com/2021/05/06/Praise-for-Alpine-Linux.h...

https://outline.com/qNDss4

That loaded fast.

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?

Makes me wonder if anyone suggested Ever Given "do a barrel roll"[1]

[1] https://www.google.com/search?q=do+a+barrel+roll

For another hackable smartwatch, see the PineTime.

https://pine64.com/product/pinetime-dev-kit

First thing that came to mind was in one of the "Postgres-backend" projects like Hasura[1], Postgraphile[2], or PostgREST[3].

[1] https://github.com/hasura/graphql-engine/

[2] https://www.graphile.org/postgraphile/

[3] https://postgrest.org

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!

Have you looked at Nim? Python-like syntax, compiles to C, and a considerably sized stdlib (http, parsing, channels)

https://nim-lang.org/

Displaying a loading spinner in under 50ms while waiting for a 500ms request to complete doesn't necessarily build a strong relationship.

SPAs can start off with the good intention of being low-latency and responsive. But when you're backed by a web server, you still have to account for it though optimistic rendering, prefetching, and loading states. Getting it right can be an excellent UX, but it's easy to get very wrong.

What is Nix?

Nix is a powerful package manager for Linux and other Unix systems that makes package management reliable and reproducible. It provides atomic upgrades and rollbacks, side-by-side installation of multiple versions of a package, multi-user package management and easy setup of build environments.

What is NixOS?

NixOS is a Linux distribution with a unique approach to package and configuration management. Built on top of the Nix package manager, it is completely declarative, makes upgrading systems reliable, and has many other advantages.

[1] https://nixos.org/

Opening in React devtools shows a number of hints[1]. "React Native Style Editor" section. "View" components with numeric "style" props. And the classname prefixes "css-" and "r-" match the generated identifiers from react-native-web[2].

[1] https://imgur.com/lFUvL7P

[2] https://github.com/necolas/react-native-web/blob/45f94eb43da...

This strong sign of the confidence Twitter has in React Native for Web[1]. In 2017, Nicolas Gallagher gave a talk[2] about why it was used for mobile.twitter.com.

[1] https://github.com/necolas/react-native-web

[2] https://www.youtube.com/watch?v=tFFn39lLO-U

If the light goes on, then it's too late.

The Redistricting Game[1] is an interesting approach to teaching about how gerrymandering works.

[1] http://redistrictinggame.org/game/launchgame.php

Good to see that it's using knex for queries. Many node ORMs dumb every database down to a Mongo-like object hash.

AWS offers a BAA with some services

https://aws.amazon.com/compliance/hipaa-compliance/#What_Ser...?

You can run a bridge, but then it's another machine to set up and maintain. How are security and Chrome updates handled? A cron job? What if that fails? Suddenly the simple Chromebook is more complex.

I wouldn't mind running that hack myself, but there's no way I'd drop it on someone who couldn't debug if something went wrong.

I've suggested ChromeOS to family members that use facebook, email, and limited spreadsheets. Ultimately, I backtracked when they asked about printing. Telling them they have to buy a new printer that's Cloud Print compatible is a tough sell, especially if they've purchased one within the last year.

I have found that Chrome Boxes are excellent machines for demoing web products at tradeshows. Cheap, relatively hardened, fast enough, and sync bookmarks and settings.

Check out Lua Missions[1] for a quick tour of basic Lua.

[1] https://github.com/kikito/lua_missions

I'm not seeing a 1.4 entry in the changelog. What's the deal?

Edit: They force pushed to master to remove the release due to issues on OSX

https://github.com/iojs/io.js/issues/932#issuecomment-760480...

We started using dokku just before 0.2.0 released for hosting our apps. One place it initially lacked was process management. If you wanted anything outside of your 'web' process in your Procfile, you were out of luck. I wrote a couple plugins[1][2] to handle that.

It worked alright for single sever deployments. When attempting to scale to a multi-server setup, dokku wasn't the right choice. I went down the rabbit hole of docker orchestration on top of CoreOS, but eventually backed out to go with Cloud66[3].

[1] https://github.com/statianzo/dokku-shoreman [2]: https://github.com/statianzo/dokku-supervisord [3]: https://www.cloud66.com/

Thanks for the great documentation. It makes lapis stand out from just some weekend project.

Was it the one from 2012? The video is available on infoq.

http://www.infoq.com/presentations/Y-Combinator

Really excited if they offer service between SLC and Provo

We use it for event storage in the event sourced parts of our app.

For the rest of our data, we're currently migrating off of Mongo to Postgres due to an experience similar to the OP's.

Sound still works