jmarcher
That being said, I think you are mostly thinking about the aspect ratio of ultra-wide monitors in general. It's a matter of preference, but I will take an ultra wide (>= 40in) any day over two regular 16/9 monitors. I end up having my main window in the middle 40% with two other windows on the side at 30%.
> They seem optimally designed to ensure that you'll have glare on your screen no matter how you position it in any kind of well lit environment.
I guess the workaround (with any monitor, really) is to ensure that the light sources are not behind you.
The kids particularly enjoyed the moments where you have to exchange subassemblies: "I need this from 'popcorn'!" "I need this from 'astronaut'".
When the kids got tired, subsequent steps were assigned to me as if nothing had happened. I am guessing there's a DAG of tasks (to build subassemblies), and the tasks just get picked up by individual participants.
10/10
It's exciting for the future, though!
MVG did a great overview of it: https://www.youtube.com/watch?v=r5twUkvYFpA
https://support.apple.com/en-ca/guide/mac-help/mchlp2711/mac
Oh, I don't want to play Pokémon games, but every few hours, I am given the controller and told to beat the boss with a team composed of 6 low-level Pikachus and zero healing items.
Your dream is probably a ~50in 8K TV (with RGB pattern if you are on macOS), but curved. I don't know if that will ever exist.
Personally, I found that with a bigger 16:9, I would not use the top and bottom of the screen. When I "downgraded" to a 40in ultra-wide, there was not much difference in the space I was using.
I would love a large-ish ultra-wide with > 160ppi. One day, maybe, that being said, by that time those things will exist and be reasonably priced, my eyes might not be able to appreciate the difference.
My son loves Lego Mario and the app. He'll even go through the building instructions of kits he doesn't have just to see how they are built. The instructions in the app are super clear, animated, and the model can be rotated at any step to check whether the real-life model is correctly built.
Going back to paper instructions after using the app is a pain.
If I were to use a TV, it would be an OLED. That being said, the subpixel layout is not great: https://pcmonitors.info/articles/qd-oled-and-woled-fringing-...
1. helm-ag <pattern> # the search results are updated as you type 2. helm-ag-edit # edit the search result as regular text. Use multi-cursors, macros, whatever. 3. helm-ag-edit-save # commits the changes to the affected files
All those commands have keybindings, so it's pretty fast. I'll often open up Emacs just to do that and then go back to my JetBrains IDE.
When people ask me which tool I use to manage my dotfiles, I tell them about this little-known tool called `git`. ;)
Side note: I use an shell alias instead, but it's pretty much the same.
`alias home="git --work-tree=$HOME --git-dir=$HOME/.files.git"`
[1] https://helpguide.sony.net/dc/1910/v1/en/contents/TP00028862...
https://raphlinus.github.io/xi/2020/06/27/xi-retrospective.h...
Which points to https://xi-editor.io/docs/rope_science_00.html
Technical solution wise, sharing credentials via 1password or bitwarden is probably the most straightforward approach IMHO.
e.g: LayerX + cmd + shift + 9 to rebuild a file. There are much worse offenders I am sure.
I do have my MacBooks cooking themselves in my backpack every so often too.
Basically, every MacBook's I had in the past > 10 years ended with that issue.
Mystery solved!
For example, I ended up writing this to integrate diagrams and Sphinx. https://github.com/j-martin/sphinx-diagrams
Similarly there's https://pypi.org/project/sphinxcontrib-plantuml/ and https://mermaid-js.github.io/mermaid/#/ (among other similar tools).