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

171–176 of 176 posts

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

#171

Post by geofft »

parvenu74 wrote: post #137
geofft wrote: post #87

Earlier quoted context omitted.

Can we leave the Slashdot-quality trolling about licensing back in the previous millennium where it belongs? There are, of course, successful projects licensed under the GPL and AGPL (Linux comes to mind), many of which have for-profit businesses; there are plenty of people with different priorities about what "REAL freedom" is. And calling the licenses that match their priorities "herpes licenses" is unlikely to con…

Trolling aside, the freedom allowed to not show all of your cards that MIT/MSD/Apache allows is better for business, and if the app is essential to their business then they will contribute fixes back upstream. An example is Juniper and their myriad contributions to FreeBSD. This allows Juniper to pull down upstream updates without it being a complete goat-rope to integrate with their own secret sauce code; if Juniper…

That shows that it is better for some businesses, which no one disputes. For other businesses, the compulsion for others to share their work results in a better product, and tbeir profit motives are more aligned with a better product in an absolute sense than being better than competitors, and so being compelled to release source is a worthwhile tradeoff for everyone else doing so too.

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

#172

Post by djhartman »

mdigan wrote: post #146
djhartman wrote: post #144

Earlier quoted context omitted.

Don't suppose you'd consider remote candidates?

NYT is remote friendly, but most engineers are based in NYC. Wirecutter ( https://thewirecutter.com/ ) is owned by The New York Times and is fully remote: https://nytimes.wd5.myworkdayjobs.com/Wirecutter

Thanks :D! I love Wirecutter, didn't know they were fully remote.

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

#173

Post by dang »

youpassbutter wrote: post #149
mattberkowitz wrote: post #141

Earlier quoted context omitted.

I'm an engineer on our CMS team and as Albert mentioned we're currently seeking both back-end and front-end team members. We're not opposed to hiring skilled developers that don't have deep experience the specific language or frameworks we use. There's also always the option of joining the back-end and transitioning over time to a more front-end role. If you're interested, I'm happy to answer any questions or connect…

A CMS team? Christ, no wonder NYTimes is losing money.

Could you please not post unsubstantive comments to HN?

https://news.ycombinator.com/newsguidelines.html

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

#174

Post by maccard »

thomastjeffery wrote: post #162
maccard wrote: post #116

Earlier quoted context omitted.

Not all languages are created equal. While yes a developer with years of experience in python may have lots of transferable skills to other languages, my team arent going to hire someone for a mid level/senior position without a good knowledge of c++

> Not all languages are created equal No language is inherently "better" than another. They are each useful for specific cases, and understanding more languages means understanding their contextual strengths and weaknesses.

Apologies, I didn't mean to imply that C++ was better (or worse) than any language, just that it's not the same as others.

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

#175

Post by pier25 »

iamcasen wrote: post #159
marijn wrote: post #47

Earlier quoted context omitted.

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.)

Hey there, Just wanted to offer some feedback. Prosemirror's docs are woefully incomplete. The way controls are added is extremely confusing. Why do we need some node module called "prose-mirror-example-setup" ? I know I'd personally prefer being able to add all the markup and style for the editor, and then just use prosemirror underneath the hood for state management. Another thing that I found quite difficult, was…

I agree the docs are obtuse, and implementing features is hard, but document state is not saved as markdown. The whole point of PM is to separate content from prsentation.

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

#176

Post by pier25 »

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…

Mobiledoc document format, while abstracted, is heavily based on html. ProseMirror completely abstracts content from prsentation.
Post reply on HN