Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Building a Text Editor for a Digital-First Newsroom

open.nytimes.com

Post reply on HN
Print view View original

61–70 of 176 posts

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

#61

Post by tedmiston »

venning wrote: post #4

Data Warning: 100 MB. Viewing the header illustration for more than a few seconds crashes my iPad Safari tab. Scrolling until it is off the viewport prevents this. EDIT: Dev Tools reports 74.8 MB transferred with an ad blocker. The illustration is a single 69.2 MB gif. EDIT: 101 MB in total when you scroll to the bottom. Three more gifs: 18.1 MB, 7.1 MB, 4.7 MB.

Instapaper Text view reduces it to a slightly more reasonable 41 MB.

https://www.instapaper.com/text?u=https%3A%2F%2Fopen.nytimes...

(This may require a free Instapaper account to view.)

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

#62

Post by tedmiston »

slig wrote: post #17
lambda wrote: post #8

Earlier quoted context omitted.

Why are they gifs instead of mp4s? Yikes. Also, since they are screenshots without a lot of movement, they really should compress better than that even as gifs.

Maybe because they're using Medium, and Medium doesn't have that option. Why the biggest newspaper in America can't run their own hosted blog is a bigger question.

> Maybe because they're using Medium, and Medium doesn't have that option.

> Why the biggest newspaper in America can't run their own hosted blog is a bigger question.

Kind of ironic given that the post is about building their custom web-based text editor... I wonder if they use it to draft their posts for Medium too.

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

#63

Post by zawerf »

manigandham wrote: post #5

Cool, but it's yet another case of re-engineering the same thing. (edit: its not entirely new). Splitting editors into an abstracted structure for finer control over data and presentation is something that's been done for a decade now in various text editors. Medium and Basecamp started similar projects and there's Mobiledoc which is trying to standardize the format. It'd be nice if all this effort focused on a singl…

It might be helpful to update your list with some feature comparisons. For example:

Quill vs (CKEditor and TinyMCE, Draft, ProseMirror, Trix): https://quilljs.com/guides/comparison-with-other-rich-text-e...

Slate vs (Draft, ProseMirror, Quill): https://github.com/ianstormtaylor/slate#why

I personally went with Slate because I needed first-class React support but not as low level as Draft.

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

#64

Post by tedmiston »

JetSpiegel wrote: post #44
kzrdude wrote: 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

On iOS, the app Unobstruct is a lifesaver for these.

https://itunes.apple.com/us/app/unobstruct/id1255281426?mt=8

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

#65

Post by tedmiston »

Phrodo_00 wrote: post #19

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.

Not sure why you're getting downvoted. This appears to be an evolution of WYSIWYG tools to me, which I wouldn't categorize as a text editor either — more like a word processor.

FWIW ProseMirror does not bill itself as a text editor:

> An ideal content editor ... bridg[ing] the gap between Markdown text editing and classical WYSIWYG editors.

> It does this by implementing a WYSIWYG-style editing interface for documents more constrained and structured than plain HTML...

from https://prosemirror.net

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

#66

Post by [deleted] »

tedmiston wrote: post #61
venning wrote: post #4

Data Warning: 100 MB. Viewing the header illustration for more than a few seconds crashes my iPad Safari tab. Scrolling until it is off the viewport prevents this. EDIT: Dev Tools reports 74.8 MB transferred with an ad blocker. The illustration is a single 69.2 MB gif. EDIT: 101 MB in total when you scroll to the bottom. Three more gifs: 18.1 MB, 7.1 MB, 4.7 MB.

Instapaper Text view reduces it to a slightly more reasonable 41 MB. https://www.instapaper.com/text?u=https%3A%2F%2Fopen.nytimes... (This may require a free Instapaper account to view.)

[deleted]

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

#67

Post by sugarpile »

albertsun wrote: post #50
AJRF wrote: post #36

I'd love to work for this engineering team. Their tech blog and github is full of interesting projects.

We're hiring! You should apply! https://nytimes.wd5.myworkdayjobs.com/Tech/job/New-York-NY/S...

Any backend openings? I've been looking to move into frontend work more but don't think my experience is there yet.

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

#68

Post by acdha »

slig wrote: post #58
skybrian wrote: post #51

Earlier quoted context omitted.

I think Hacker News does a better job of this, and so here we are.

On some cases, agreed. But most content posted on Medium doesn't end up here.

Or it is but never gets upvoted enough for most people to see it.

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

#69

Post by evrydayhustling »

tedmiston wrote: post #65
Phrodo_00 wrote: post #19

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.

Not sure why you're getting downvoted. This appears to be an evolution of WYSIWYG tools to me, which I wouldn't categorize as a text editor either — more like a word processor. FWIW ProseMirror does not bill itself as a text editor: > An ideal content editor ... bridg[ing] the gap between Markdown text editing and classical WYSIWYG editors. > It does this by implementing a WYSIWYG-style editing interface for document…

Every comment that remotely questions this article is getting downvoted, rather than discussed. Lame.
Post reply on HN