elliotf

To offer a contrasting viewpoint, I don't have openwrt as my router, but only have openwrt APs, because it's the best and cheapest way to have VLAN support in my APs, keeping iot and guest VLANs separate from my main network.

The "fire upon the deep" series describes zones where the speed of light differs, causing deserts from which escape is difficult, did to the slow speed at which ships must travel.

Chrome is also adding bizarre ux choices on mobile. The tipping point for me was nested tabs (tab groups) with no way to disable them. I've been a happy Android Firefox user since then.

I also want to be able to tell _why_ which is why I dislike working on codebases that squash commmits. Too many times I've done a blame to see why a change was made, and it's a giant (> 10) list of commit messages. Oftentimes, the macro description of what was going on does not help me with the line-level detail.

Also, in case it helps you in the future, `blame -wC` is what I use when doing blame; it ignores whitespace changes and tracks changes across files (changes happened before a rename, for example.)

I don't know about this project, but I have used tmate.io (self hosted ssh server) for almost seven years for remote pairing, using vim inside of tmate.

Compared to vscode: when sharing the terminal, you don't need to worry about following the other person's cursor or them following yours, as there is only one cursor.

You don't need to worry about telling them what dukes you are opening, as there is only one editor.

You also don't need to worry about registering for an account, as (at least with tmate) it's simply an ssh connection for the remote person.

It is the only way I've found that allows for effective remote pairing. There are a number of downsides, but it is a wonderful tool.

That's really neat! Is the source of the path generator available anywhere?

I have not! Thank you!

I love svelte on the personal/toy projects I've tried it on, but does someone have an example of a large-ish svelte codebase with an example of a testing pattern that they've found works?

Using mithril/vue/react, there are assertions you can make about how a given action will modify the state, and given some state, how that state will be rendered.

I've not found a good way to make assertions on the behavior of code without resorting to poking through the DOM and dealing with asynchronous behaviors.

Very true and likely, also considering how short the terms are, but emacs is in clear decline. Perhaps it's just become so easy to use, no one needs to search for anything anymore?

The difference being having a more positive/helpful/constructive mindset.

With "how might it work" you're proposing solutions to the potential "why will it fail" problems rather than dumping more obstacles in the way.

"this will work if we do X because it will fail if Y"

vs

"this isn't going to work because Y"

I think the prior would be a more pleasant experience.

Agreed. I bought a Samsung (UN40JU6700) 4k60p curved monitor for ~$800 and it works reasonably well. There are some quirks using a TV as a monitor and I was a little nervous about the screen quality, but it's worked well so far. Also, it's a TV.

edit: I especially like that the DPI is the same as a 27" 2560x1440 monitor.

I think the point of the post is valid: it can be hard to work with a schemaless datastore. I think Cassandra is the only one you listed that supports type enforcements.