morgancmartin
Joined 9 years ago
Joined 9 years ago
Personally, as a long-time magit user, I'm not sure I see any reason to make the switch. Can anyone more familiar with GitLens (possibly the author) provide any commentary on its differences with magit's blame functionality?
AFAICT, the only difference seems to be that the commits simply show on line selection instead of all at once, but there may be more going on here than I am noticing at first glance.
On the other hand, I am a huge proponent of Spacemacs. It's technically just a custom Emacs config, but it is a significant enough departure from the base functionality that it is managed as its own project.
It brings Vim keybindings (as well as an improved package management system and a bunch of other stuff) to Emacs in a very intuitive and seamless way. That way you get access to the very rich Emacs ecosystem, as well as the endless potential for customization, all with the, IMO, superior text editing experience of Vim.
I've tried VSCode, and it doesn't hold a candle to Spacemacs IMO.
I do occasionally envy some of the goodies the VSCode ecosystem benefits from, however. In particular the new Github Codespaces, for example. Still not enough to make me leave Spacemacs though.
I should also note, I've attempted OOP in TS and it wasn't pretty. It is much more suited to a functional style IME, although I will concede I have seen some open source projects that use it in a Java-esque OOP style presumably to good effect. Personally it wasn't my cup of tea.
They look like really well done apps, congrats on (kind of) exiting the rat race!
Essentially, I see it as a meta-indicator, a way of making decisions in situations where I don't have all of the information.
Another way to look at it would be through the lens of game theory. Game theory is absolutely a field of some consequence, and it's all about relative positioning of agents in a system and their likely intentions after factoring in the likely intentions of their peers.
In a word, you might describe this type of analysis as simply, "wisdom." I find it to be of particular value in entrepreneurship.
I think it would be pretty neat to include metadata in the calculation of the voting power metric as well. Such as how each subscriber votes in relation to other subscribers and assign a higher score to those who vote inline with the community. The goal being to optimize for those subscribers who embody the spirit of the community. Of course that brings up issues of echo chambers but other kinds of metadata could be factored in to offset that too. I would have to think on it for a while to come up with something I felt was as meritocratic as possible.
EDIT: And the book by the same author, Refactoring UI, is also a fantastic primer on the philosophy behind Tailwind.
It's not nearly as fast as "proper" swimming but I'm sure I could keep it up approximately as long as I could walk. Maybe even longer. It makes for a great option in dangerous situations, and is likely a good fundamental technique to teach anyone just learning.
It is a bottom up approach to state. Everything is modeled as atoms. Atoms can be defined in any module and are accessed by simply exporting/importing from/to the module. Simply call the useAtom hook and you're now using that state atom.
Under the covers it is scoped via a top-level React context, I believe.
Atom derivation, read/write, async, it's all there. It also hooks into a lot of other popular state libs like redux, XState, Zustand and many others.
I much prefer it to Redux because there is zero boilerplate and extremely flexible. It can be easy to hang yourself with all the extra rope it gives you if you aren't careful though.