Isn't it more of a style decision where if your team rebases, and practices clean code discipline, and excellence is a habit rather than an enforcement — the signals visibly emit in `status`.
Most committers don't really understand remotes, much less rebasing.
The second half of the post essentially describes low/high context social dynamics.
Outside of linguistucs, I've seen it applied as a concept of social group inclusion and mobility. Eg. America is a low context society — if you mess up you can move across town. Other cultures that are high context, your family will be shunned for generations with no hope of success.
You lost me at, "XML is not that bad if you are already doing <x>". Verbosity is insane, attribute vs element freedom induces crowd madness. But I do love the data-visiting parts, why can't they somehow get that into Markdown.
Crabs in a bucket is probably the bandit left triangle, people competing by dragging others down.
Flaizers are the lower left quadrant, what original author refers to as "stupid" — causing harm to themselves and others with no benefit for any parties.
My "main" org file is 21k lines, it's no problem at all. My laptop is from 2017 or something.
I do sometimes work on files that are 300k lines (don't ask), and while it's mostly fine, once in a while I'll try to use some less common operation that's not very optimized and have to abort it (e.g. don't try to magit-blame that file). But stuff like searching, scrolling, editing, syntax highlighting are all fast.
If I have to open files >100M I sometimes open them in `fundamental-mode`, which turns off syntax highlighting.
For truly large files (gigabytes), there is the `vlf` (Very Large File) package, which doesn't load it all into memory at once, but still lets you search, scroll and even M-x occur (sort of like grep, but more integrated and editable).
Note that this is on Emacs 31 (there have been some major perf improvements in the last three or so releases, and more is coming with the new garbage collector)
In earlier days there were issues with very long lines; these have partly been mitigated in later releases; on the one hand by faster internals, but also a new builtin package `so-long` that can notice very long lines, default 10k bytes, where Emacs probably should give up syntax highlighting etc. to remain snappy.
I finally made the switch to vim when I was working on a really large frontend template that consisted of the same massive repeated block where a small portion of each was different based on a condition.
There was a lot of search and replace, and emacs started dogging it really hard on like the 10th condition block.
Not these days. Native Compilation made emacs a faster and there have been a lot of other changes. In fundamental-mode, emacs can handle really large files. When opening files literally, it's even faster. I have this 104k line org-mode file and it's reasonably responsive. Reverting it takes a while, but the UI does not hang while the buffer is being formatted according to the mode.
I use a mid tier laptop CPU (6C12T). Emacs is snappy. Compared to what it's like now, it was glacial in 2019.
In general, no... but also maybe yes. It's usually fine, but you may get extra unlucky in specific situations with specific major modes.
I've always found line length the biggest problem. Emacs has never done a fantastic job of handling long lines. If truncated, you can't see most of the content; if not truncated, the performance gets worse with length, and visual-line-mode (essential for dealing with non-truncated long lines IMO) doesn't make it any better.
Performance with large numbers of mostly shortish lines is ok. I've had no serious problems loading 2+ GByte log files (average line length <200 chars) in literal mode. The general performance suggests that Emacs isn't really tuned for editing enormous files, but I've never found things so bad as to be worth switching text editor over.
No, but that’s not really relevant, my point is more that all buffers should be windows across all applications.
Emacs for me gets slow when syntax highlighting is on and I navigate to a very long line, text-mode does not have highlighting or the slowness. Most emacs slowness is caused by bad plugins, which if you report may be fixed by developers.
It's like Rumshpringa for TODO apps. Everyone wants to rebel from the old norms and go do something different, only to end up returning to the reliability, clarity and comfort of a good pen and pocket notebook.
Big fan of the Rite-In-Rain notebooks, myself, and Fisher Space Pen's Cap-o-matic.
> Big fan of the Rite-In-Rain notebooks, myself, and Fisher Space Pen's Click-o-matic.
I carry this combo everywhere I go. Way less friction than taking out my phone, unlocking, and suffering the horrible experience of typing something on a virtual keyboard.
I do enjoy the looks I get from friends and family sometimes, as they all expect me to be high tech everywhere in my life but I'm probably one of the most low-tech people outside of work.
Interestingly enough, this just shows how different people like and hate different things. I personally can’t stand writing with a pen, and am very fluent and fast with a virtual keyboard and would never describe the experience as horrible. I’m writing this on one right now, and it’s great.
I also don’t want to carry an extra thing in my pocket when I already have a phone.
I prefer A4, but yeah. I adopted something roughly based on Bullet Journal about 6 or 7 years ago and now on my 4th book.
There's something about manually writing and copying over TODOs to the next month that makes you really question if you still need to do it, and if you do, gives you a reminder that you still haven't done it.
I use a few basic markers copied from standard bullet journal, which work well as a dot can be promoted to all the others. A dash "-" for informational stuff, a centre dot "·" for a task, which turns into a slash "/" for partially done or a cross "X" for done, ">" if I carry it forward to the next month and "<" if I copy it into the future log (I have pages at the front for about 4 years of future events, 3 months per page). I also have a leftmost column for the date when something needs to be done or for meetings/events.
Surprisingly, even when doing a whole page of notes on something, it's not excessive to leave an inch margin, and sometimes you want to star a key point or attach an action point market.
I've got really used to this way of journaling, and appreciate the ability to do different things, like calendar views - such as 36 week views with one page for weekends and the other for mid week - which are great for planning holidays, weekends and significant events.
I never really got into the monthly reflection aspect, but I do like doing that around end of year and other inflection points through the year.
> There's something about manually writing and copying over TODOs to the next month that makes you really question if you still need to do it, and if you do, gives you a reminder that you still haven't done it.
This is also key for me. Striking through an item that's on my list for some time and that I just decided doesn't matter feels just as good as marking some item as done. Undecided items indeed go to the next list, and just the act of writing down the same item on a new list forces you to reconsider it.
List done? Timestamp it and throw it in the archive box.
If there's really a hyperlink I need, I might e-mail it to myself, add it to a text file in an appropriate place in the appropriate project, leave the tab open in my browser, or just do the task now.
But IMHO none of that is related to the todo list, which is stuff like "7 · Fred's birthday". It's about remembering things that I need/want to do, and in a way that's tactile and I can reflect on it whether I'm using the computer or not, not trying to maintain a knowledge base of everything.
I recently tried out Task Warrior for tasks and this is why I switched back to Obsidian + DataView.
Forgetting to check TW is the big reason it didn't work, but the secondary reason is that I take a lot dev logs on context and the `annotate` command is too clumsy to be practical for that.
I like the idea of a CLI tool for todos, but it needs to integrate with my notes.
A4 maxi. surprised to find this here - and yea, you can 1) take photo 2) easily index later via vision llm types cheap now etc even local (99% time never do, essence of todo lists ie ack wont ever need to index most items)
If we're being fair here then this must be the place to list the problems with the note card/pad system. For me, I ultimately settled on using a GitHub repo of todo lists w markdown as my solution, viewable on desktop & mobile.
The problems with a physical note card system are:
- I have to use the computer & mobile phone to enter and receive all my work, so it makes sense to consolidate the todo list(s) into those systems, instead of adding a third one. Having to remember to keep a physical bundle near me all the time, with a working pen, feels clunky.
- My handwriting is messy and this causes various problems. I can't really read it at a glance; longer messages take longer to decode; something about the non-uniformity of it also throws me off. I don't relish the thought of consulting a pile of my handwriting multiple times in an hour.
- I frequently cross off old items and add and/or modify new items. This is very easily done with a text file but sounds like a mess with note cards: keeping the empty cards around, scratching off or erasing existing ones, etc. With GitHub's commit history, I can even get a holistic view of how it's changed over the day, not possible with physical cards.
- A LOT of the value of my system comes from being able to view past days todo lists, to see what's getting done and what isn't; I do this daily. Obviously keeping up w/today's tasks stretches the physical card system to its limits; extending that to the past 7 days sounds like a nightmare.
I do this. I love good old fashioned pen and paper.
I've tried, many many times to use digital for both Todos and note taking and nothing ever stuck. Even tried using an iPad with GoodNotes & the Apple Pencil. Pen and paper is the only thing that has ever worked for me still. Plus I enjoy the physical sensation of writing things down physically, with a really nice pen and a high quality notebook.
So I always keep a notebook open on my desk, I intermix Todos and notes on sort of a "daily page" format, and I also carry a little field notes flip pad notebook with me everywhere I go. On the go it's also, oddly enough, less friction to write in my field notes book than it is to take out my phone, unlock it, and suffer through the horrible experience of typing anything out on a virtual keyboard.
OCR is readily available everywhere now so digitizing your handwritten notes, if you have to, is trivial.
Even so, I feel that much of the point of writing things down in the first place is to put the information into the mind (where the subconscious mind can work with it and do its jobs) and, ultimately, so you won't need to be reminded about it later.
Most committers don't really understand remotes, much less rebasing.
reply