Live data from Hacker News

Building a Text Editor for a Digital-First Newsroom

open.nytimes.com

41–50 of 176 posts

Re: Building a Text Editor for a Digital-First Newsroom

#41
post #22

Earlier quoted context omitted.

69 MB gif - isn't that called a video? I thought we had different formats for that.

What I find amazing is that it's that large despite only being two bits of color depth, and it's extremely short and low framerate. Where the hell did all that filesize come from?

Screen-grabber?

Re: Building a Text Editor for a Digital-First Newsroom

#42
post #3
post #2

> If you’re like most people in America, you use a text editor nearly every day. Filter bubble detected.

The author does not say "work in a text editor", only "use". Considering she's including text editors on mobile devices, which the majority of America will utilize today, that's not a particularly bold statement.

Disagree. Paragraph context and examples made it clear she is discussing a dedicated text editor, not something embedded in e.g. your SMS app.

Can't imagine why parent is getting downvotes - it's an important point, and doesn't seek to invalidate the whole piece.

Re: Building a Text Editor for a Digital-First Newsroom

#43
post #32

This isn't even a test editor. It's closer to a web publishing tool. The article also didn't talk about the normal text editor challenges like the way the text is stored in memory and modified.

Agreed. I carry the personal view that when someone says "text editor" they are implicitly implying plain text. As such the leading paragraph of the article makes me twinge a little when "text editor" is used rather than "word processor". The article then continues on to describe the editor which sounds very much like a WYSIWYG editor. Indeed ProseMirror[1] homepage says the following. ProseMirror tries to bridge the…

What would you call Adobe Indesign?

Re: Building a Text Editor for a Digital-First Newsroom

#44
post #37

Earlier quoted context omitted.

Organizations use Medium instead of their own platforms to try to create a sort of social signalling--like, "this is not the usual old-school BS you'd expect from us--this is cool design or tech content." Whether that actually works is up for debate...

Medium has already turned around to just be uncool and pushing stupid bars and buttons in front of the text. So they are late to the party.

https://daringfireball.net/linked/2011/03/06/dickbar

Re: Building a Text Editor for a Digital-First Newsroom

#45
post #43
post #32

Earlier quoted context omitted.

Agreed. I carry the personal view that when someone says "text editor" they are implicitly implying plain text. As such the leading paragraph of the article makes me twinge a little when "text editor" is used rather than "word processor". The article then continues on to describe the editor which sounds very much like a WYSIWYG editor. Indeed ProseMirror[1] homepage says the following. ProseMirror tries to bridge the…

What would you call Adobe Indesign?

It's a digital publishing system.

Re: Building a Text Editor for a Digital-First Newsroom

#46
post #37

Earlier quoted context omitted.

Medium has already turned around to just be uncool and pushing stupid bars and buttons in front of the text. So they are late to the party.

https://daringfireball.net/linked/2011/03/06/dickbar

I've had this vague sense all year that someone gave it a term and wrote a post on it and I read it, but it never reached the level of consciousness where I'd actually look it up. Thanks for pointing the way.

Re: Building a Text Editor for a Digital-First Newsroom

#47
post #13

I've invested in Mobiledoc (mostly because it was for two ember apps) and it's mostly been fine, but is there any reason why I shouldn't be moving to ProseMirror? Seems to be a lot more powerful and have things like collaborative editing and track changes as well.

Just my experience: I had a rough time with ProseMirror trying to use it before it was released. It didn't use modern JS modules for a long time, the source code was a mess as far as I could tell, and JavaScript variable errors would surface with every version. Maybe the author has overcome these issues, but I'd be inclined to go with a different editor. Also, ProseMirror's architecture is extremely close to DraftJS,…

Yeah thanks for dropping some deeply outdated impressions in here. (Also not even fair—the code was never a mess and at the time it wasn't clear how ES modules would be used so using CommonJS was a completely reasonable choice.)

Re: Building a Text Editor for a Digital-First Newsroom

#49
post #13

I've invested in Mobiledoc (mostly because it was for two ember apps) and it's mostly been fine, but is there any reason why I shouldn't be moving to ProseMirror? Seems to be a lot more powerful and have things like collaborative editing and track changes as well.

ProseMirror requires a certain willingness to work with strict data flow and immutable data structures, and to cobble together a loose set of small modules before you have something user-friendly, but if you can handle that I think it's a safe bet at this point. (Disclaimer: I wrote it, and am heavily biased.)
Post reply on HN