Yes, but not accidentally. You should press an [Edit] button which would take you to another URL to edit the page.
The problem occurs when someone accidentally drags things around, or has the wrong window open when typing in text and you end up with "ls" and "exit" scattered randomly throughout the doc.
.. okay it’s mostly a misfeature because it’s the exact same input gesture as selecting text, but you have to remember that there is text selected / ensure that no text has been inadvertently selected.
Another case where making the user remember things can cause a problem is hybrid cars, where the driver needs to know the state of the hybrid battery because the responsiveness of the brakes and acceleration change depending on it.
the same thing would happen in word/google docs/etc
Is it really such a foreign concept that people want a dedicated editing-focused mode whose source is published into the final wiki page for viewing? Is this not how basically all tools worked pre-Notion?
Do they? Then export your documents to an immutable website. That's why those options exist. Personally I don't want that. I want to edit my content fast and the hybrid-solution doesn't bother me. So we are talking here about a conflict of interest, not an anti-pattern. And solutions for this already exist, maybe they should just advertised more prominently?
> I want to differentiate content editing and content viewing much the same way in software development you edit source code which is then built into an immutable read-only artifact.
I don't read the compiled artifact, I use it, which is very different from what we are talking here. A more equal example would be reading code on github or reading in a code editor.
We want to serve people who've used apps like those with their preferred writing experience.
If Notion had to be everything-editable-by-default, make it so that changes need to be explicitly committed and saved, much the same way one would do with Git. Otherwise it becomes impossible to track down these kinds of accidental mutations to the document, much less even realize that they have occurred.
On that note, I'm increasingly considering making my Emacs open all files read-only by default. When coding, I'm usually viewing many more individual documents than I end up actually editing - and multiple times a day, I end up accidentally typing (and then immediately deleting - muscle memory, this) a character into some file I was reading - and causing a spike in CPU usage, as the Language Server tries to reprocess the change. $deity forbid I do this in a widely-used header file - if I'm not quick with undo, LSP will churn through dozens of translation units before it realizes the edits were reverted.
This is not a big deal - usually just the cooling fans spinning up for a few seconds, and the editor (or whole system) getting slightly less responsive. It's just that the "slightly less responsive" part is really jarring.
Spitballing bad ideas somewhere in the ball park of what could be prototyped: - Editing locked by default and locked whenever a clear non editing action occurs. Editing unlocked by right swipe, double click, enter key or something similar. Editing unlocked by looking at the text cursor.
A little editor/reader toggle button would go a long way here.
But for a lot of people that never do that, that's hard, the more closer edit mode is to reality to easier it is to understand what it will look like and the less brainpower it takes the creator. But yeah in some cases with notion the difference between read and edit mode is not significantly indicated.
There's a certain sort of worker that really leans into that as their version of "easy async collaboration" but is actually just putting the burden on the recipients to make sense of the author's journey and thought process, instead of putting more effort into more-infrequent-but-more-curated updates.
I want to be able to open a document in read-only mode. Otherwise, while just navigating through pages or reading content, it's far too easy to accidentally add text to a block by pressing anything on the keyboard, or move things around with an accidental drag of the mouse.
I've been reprimanded several times for errant edits to company wiki pages because of this...