Live data from Hacker News

The Most Dangerous Writing App

maebert.github.io

181–190 of 193 posts

Re: The Most Dangerous Writing App

#181
post #4

This reminds me of early versions of Microsoft Word. Edit: And more generally, DOS, FAT and CHKDSK. You never knew, when there was a power interruption -- or when the system just crashed for whatever mysterious reason -- just how bad it would be. NTFS was such an improvement.

How does NTFS fix the save problem? I thought this auto-save thing was introduced in MacOS first few years ago...

Re: The Most Dangerous Writing App

#182
post #4

This reminds me of early versions of Microsoft Word. Edit: And more generally, DOS, FAT and CHKDSK. You never knew, when there was a power interruption -- or when the system just crashed for whatever mysterious reason -- just how bad it would be. NTFS was such an improvement.

How does NTFS fix the save problem? I thought this auto-save thing was introduced in MacOS first few years ago...

NTFS fixed the file system corruption issue.

As I vaguely recall, it typically went like this. You're editing some document. Something bad happens, and the system goes down. You reboot, and get the CHKDSK prompt. If you cancel out, sometimes your document is corrupted. If you run CHKDSK, sometimes your document is entirely gone. Unless you've been saving a revision history.

Re: The Most Dangerous Writing App

#184
post #94

Earlier quoted context omitted.

TIL the name pilcro; thanks!

Apologies to all I have mislead! It's actually spelt "Pilcrow". https://en.wikipedia.org/wiki/Pilcrow . ¶

So I looked, and found:

> Scribes would often leave space before paragraphs to allow rubricators to draw the pilcrow. With the introduction of the printing press, space before paragraphs was still left for rubricators to draw by hand; however, rubricators could not draw fast enough for printers and often would leave the beginnings of the paragraphs as blank. This is how the indent before paragraphs was created.

Amazing. Had no clue.

Re: The Most Dangerous Writing App

#185
post #4

This reminds me of early versions of Microsoft Word. Edit: And more generally, DOS, FAT and CHKDSK. You never knew, when there was a power interruption -- or when the system just crashed for whatever mysterious reason -- just how bad it would be. NTFS was such an improvement.

I can remember Word on SCO Xenix from around '89 or so which I don't think was particularly unstable.

Now I am really surprised. I knew that Xenix was a Unix that belonged to Microsoft, but I didn't know Word worked on a Unix. And I didn't know that Xenix was bought by SCO later. Looked up wikipedia on Xenix [0], and there are a lot of interesting facts in there, that for me put some aspects of the PC and Unix history in new lights. For example:

"Microsoft hopes that XENIX will become the preferred choice for software production and exchange", the company stated in 1981.[8] Microsoft referred to its own MS-DOS as its "single-user, single-tasking operating system",[31] and advised customers that wanted multiuser or multitasking support to buy XENIX.[31][32] It planned to over time improve MS-DOS so it would be almost indistinguishable from single-user XENIX, or XEDOS, which would also run on the 68000, Z8000, and LSI-11; they would be upwardly compatible with XENIX, which BYTE in 1983 described as "the multi-user MS-DOS of the future".[33][34] Microsoft's Chris Larson described MS-DOS 2.0's XENIX compatibility as "the second most important feature".[35] His company advertised DOS and XENIX together, listing the shared features of its "single-user OS" and "the multi-user, multi-tasking, UNIX-derived operating system", and promising easy porting between them.

AT&T started selling System V,[37] however, after the breakup of the Bell System. Microsoft, believing that it could not compete with UNIX's developer, decided to abandon XENIX. The decision was not immediately transparent, which led to the term vaporware.[38] It agreed with IBM to develop OS/2,[4] and the XENIX team (together with the best MS-DOS developers)[citation needed] was assigned to that project. In 1987, Microsoft transferred ownership of XENIX to SCO in an agreement that left Microsoft owning slightly less than 20% of SCO (this amount prevented both companies from having to disclose the exact amount in the event of a SCO IPO). When Microsoft eventually lost interest[clarification needed] in OS/2 as well, the company based its further high-end strategy on Windows NT."

[0] https://en.wikipedia.org/wiki/Xenix

Re: The Most Dangerous Writing App

#186

There is a whole tradition of these apps. Perhaps you have heard of "Write or Die" or the countless variations? https://v2.writeordie.com https://writingstreak.io http://writtenkitten.co And, yes, the most dangerous writing app. The idea is that it is easier to edit once done, so it is important to get everything out quickly and then go back and edit. Edit: Someone should come up with an Atom plugin that does the sam…

https://writingstreak.io/ shows me the following in Firefox:

Warning: Potential Security Risk Ahead

Firefox detected an issue and did not continue to writingstreak.io. The website is either misconfigured or your computer clock is set to the wrong time.

It’s likely the website’s certificate is expired, which prevents Firefox from connecting securely. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details.

Re: The Most Dangerous Writing App

#187
what will happen if I stop writing? will something happen? Oh it is possible to have capital letters! That's neat. I like how it presents itself, almost no distraction, you are typing on an empty page, the cursor being red is a nice touch too.

Very nice idea. Now I get it. As soon as I stop writing the text starts to get blurry! Very nice! Well, I like it, because I am using a similar technique when I am very stressed and need to get some air off my chest. I have this VIM mode that will put the font color the same as the background color, which means that you cannot see what you type. This will force you to type the same way as you speak, because it is impossible to correct words, to go back, delete. So you have to type the way you speak. Which is in a way just like talking, but without having the need to talk with someone else. At the same time it allows you to write everything in a public place, where other people can see your screen. They will probably think that you are crazy, or that they got some problem with their vision, because they cannot see anything. But you do not care and continue typing. And after some time you realize that typing blindly as well helps you to formulate your sentence before you type it.

Well, now the 5 minutes are over, it was a nice experience, but I like my VIM s0u7-mode better

Re: The Most Dangerous Writing App

#188

Earlier quoted context omitted.

It's not an age thing I don't think. I'm 22 and after I finish any tiny section of code I format it and then save. I don't know why, it's just habit now

Yeah, but do you save several times before you're finished that tiny section?

Several times? No, just saving once is sufficient.

Re: The Most Dangerous Writing App

#190
post #75

Earlier quoted context omitted.

I think everyone older than 30 does. I also have the habit of pressing it more than one time, every time I press it. I'm not even be sure that save will really save.

Is this an age thing? I do the exact same thing. Every time I stop typing I hit ctrl-s between 2-5 times. I don't eve think about it anymore. My kids are getting to the age where they are doing projects on a computer and I'm constantly telling them to "save early, save often." I guess it's some form of PTSD from computing in the 90's.

It definitely is! My company recently connected Office to OneDrive, which means everything saves automatically. I still find myself saving after every paragraph.
Post reply on HN