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

21–30 of 176 posts

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

#21

Post by [deleted] »

lambda wrote: post #11
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…

This is discussing one that you already had on your list; ProseMirror. In fact, you've had it on the list since 2015: https://gist.github.com/manigandham/65543a0bc2bf7006a487/429... This is talking about using ProseMirror to build some more features into their CMS, but it sounds like more of just a use of ProseMirror rather than a new editor entirely.

[deleted]

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

#22

Post by sli »

twothamendment wrote: post #14
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.

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?

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

#23

Post by slig »

Analemma_ wrote: post #20
slig wrote: post #17

Earlier quoted context omitted.

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.

I'm sure they could run a hosted blog, it's probably a deliberate decision by their tech team to seem cool and hip by posting on Medium, because that's the in thing right now for developer blogs. (Note: I'm not dissing them, I know a very talented developer who works there and says he has a great team)

> because that's the in thing right now for developer blogs.

Which is bizarre. The comments section of tech blogs are a great place to discuss and ask questions, and the support for comments on Medium is abismal, looks like they deliberately made it suck.

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

#24

Post by weego »

Analemma_ wrote: post #20
slig wrote: post #17

Earlier quoted context omitted.

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.

I'm sure they could run a hosted blog, it's probably a deliberate decision by their tech team to seem cool and hip by posting on Medium, because that's the in thing right now for developer blogs. (Note: I'm not dissing them, I know a very talented developer who works there and says he has a great team)

Maybe it was a decision to not have to run and maintain unnecessary shit when they have enough to deal with with their primary products when third parties have already invented that wheel.

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

#25

Post by jstewartmobile »

jbob2000 wrote: post #9

Whew, what a gross way to over-engineer a text editor. If the NYTimes structured themselves like a dev team, they could use common sense tools to get much better results. Why is the journalist responsible for how it's presented? Wouldn't it make more sense to have some kind of product manager or designer handle this? And why is the journalist responsible for programming the look and feel of the their article? Why not…

Journalism is in the toilet, so journalists end up being one-man bands. Local Gannett paper had everyone using CRTs--in 2014!!!

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

#26

Post by ax0ar »

jbob2000 wrote: post #9

Whew, what a gross way to over-engineer a text editor. If the NYTimes structured themselves like a dev team, they could use common sense tools to get much better results. Why is the journalist responsible for how it's presented? Wouldn't it make more sense to have some kind of product manager or designer handle this? And why is the journalist responsible for programming the look and feel of the their article? Why not…

The journalist doesn't only write an article, he also structures and plans how the story is going to be presented because that's also part of the job. Hiring another person in-between the article and the journalist is like hiring an extra person to only hammer a nail when there is a construction worker to do that job already.

They develop the underlying technology to let journalists do what they want without needing to hire more employees.

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

#27

Post by ax0ar »

jstewartmobile wrote: post #25
jbob2000 wrote: post #9

Whew, what a gross way to over-engineer a text editor. If the NYTimes structured themselves like a dev team, they could use common sense tools to get much better results. Why is the journalist responsible for how it's presented? Wouldn't it make more sense to have some kind of product manager or designer handle this? And why is the journalist responsible for programming the look and feel of the their article? Why not…

Journalism is in the toilet, so journalists end up being one-man bands. Local Gannett paper had everyone using CRTs--in 2014!!!

Not true. Presenting is part of writing. It's not separate.

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

#28

Post by SippinLean »

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.

>While it may seem strange for us, a publisher, to post on Medium rather than our own platform, we are here for a simple reason: the community. Medium is where so many of our people are, so much of the product, design and development community, so we wanted to be here too.

https://open.nytimes.com/introducing-the-new-open-blog-23eba...

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

#29

Post by slig »

weego wrote: post #24
Analemma_ wrote: post #20

Earlier quoted context omitted.

I'm sure they could run a hosted blog, it's probably a deliberate decision by their tech team to seem cool and hip by posting on Medium, because that's the in thing right now for developer blogs. (Note: I'm not dissing them, I know a very talented developer who works there and says he has a great team)

Maybe it was a decision to not have to run and maintain unnecessary shit when they have enough to deal with with their primary products when third parties have already invented that wheel.

And then they end up with a 70 mb GIF because the platform has deliberately poor features.
Post reply on HN