Bento: Jupyter Notebooks at Meta • Hacker News Board

Re: Bento: Jupyter Notebooks at Meta

#111

Post by KaiserPro » Thu, Sep 19, 2024, 10:33 AM UTC

tru3_power wrote: post #87

extr wrote: post #58

Earlier quoted context omitted.

People probably think you’re exaggerating but it’s true. Sometimes when I would get blocked the suggestion was to “read the source code” or “submit a fix” on some far flung internal project. Huge fucking waste of time and effort, completely unserious.

No matter what, tools will be broken. Having access to the source and being able to land a diff to fix the issue is awesome imo.

> Having access to the source

Yes, thats great.

> being able to land a diff to fix the issue is awesome imo.

yes, if its a one off. but for my last project that would involve spinning up many "XFNs" (multi-team chat fests) to argue that actually they don't want to have that change because of reason x,y and z.

At which point you just give up and make a stupid fucking hack.

So much is not about engineering excellence, its about trying to get people to accept change.

Re: Bento: Jupyter Notebooks at Meta

#112

Post by KaiserPro » Thu, Sep 19, 2024, 10:35 AM UTC

ipsum2 wrote: post #61

grantsucceeded wrote: post #53

Earlier quoted context omitted.

Few companies experienced the explosive growth fb did, though many will claim to have done so. Hack made the existing codebase of php scale to insane levels while reaching escape velocity for the overall company to even attempt to transition away or shrink the php codebase, as i recall (i was an SRE, not a dev) zeus likewise.

You worked at FB, but you call yourself an SRE, not a PE? ;)

PEs are still quite new remember....

Re: Bento: Jupyter Notebooks at Meta

#113

Post by herval » Thu, Sep 19, 2024, 11:32 AM UTC

tqi wrote: post #28

JohnMakin wrote: post #23

Earlier quoted context omitted.

One of the crazier things a L4 meta colleague of mine told me, that I still don’t believe entirely, is that meta pretty much has their own fork of everything , even tools like git. is this true?

Facebook actually doesn't use git, they use mercurial ( https://graphite.dev/blog/why-facebook-doesnt-use-git ). That decision is also illustrative of why they end up forking most things - Facebook's usage patterns at the far extreme end for almost any tool, and things thats are non-issues with fewer engineers or a smaller codebase become complete blockers.

FB uses mercurial _for most things_, but like any company that size, there's teams that use git and even teams that use perforce

Re: Bento: Jupyter Notebooks at Meta

#114

Post by woadwarrior01 » Thu, Sep 19, 2024, 11:34 AM UTC

Having used both Bento and later Colaboratory, a few years ago, I think I liked the latter a lot more. Google's internal tools are usually much more polished and better-designed, perhaps because they've been around for much longer.

Re: Bento: Jupyter Notebooks at Meta

#115

Post by mkl » Thu, Sep 19, 2024, 11:36 AM UTC

chthonicdaemon wrote: post #101

quantadev wrote: post #76

The original "Block Editor" (that Jupyter modeled itself after) is the one that's now called "Quanta", and has been around for decades in various forms and incantations: https://github.com/Clay-Ferguson/quantizr I'm thinking that Jupyter might still not be "Tree Based" but that would be a heck of a leap in capability if they "fix" that.

I always thought Jupyter was based on other notebook-style interfaces like Mathematica or Maple.

Yes, but it's closer to Sage (browser and Python based).

I don't know what quantadev is thinking of, but Quanta seems totally different and not a programming notebook at all. Its README also claims "Quanta is a new kind of platform with a new kind of architecture", while quantadev claims it "has been around for decades".

Re: Bento: Jupyter Notebooks at Meta

#116

Post by mkl » Thu, Sep 19, 2024, 11:55 AM UTC

talles wrote: post #33

I wish more people used marimo, so much better than jupyter

Show HN from 8 months ago: https://news.ycombinator.com/item?id=38971966

Re: Bento: Jupyter Notebooks at Meta

#117

Post by [deleted] » Thu, Sep 19, 2024, 12:03 PM UTC

wenc wrote: post #40

lamename wrote: post #35

Earlier quoted context omitted.

IME notebooks in VS Code are even worse (but improving). Jupyter lab is faster...but that depends on how fast you prefer ;)

I have the exact opposite experience — VS Code notebooks are much snappier and are possibly the best Jupyter implementations I’ve ever used (better and more responsive than vanilla Jupyter or Jupyter labs). VS code notebooks also support LSPs with refactoring, typing etc. Black is supported. Step by step debugging is supported. Venv is built in. There are so many conveniennces in VS Code that whenever I have to use J…

[deleted]

Re: Bento: Jupyter Notebooks at Meta

#118

Post by [deleted] » Thu, Sep 19, 2024, 12:25 PM UTC

web3aj wrote: post #2

The internal tools at Meta are incredible tbh. There’s an ecosystem of well-designed internal tools that talk to each other. That was my favorite part of working there.

[deleted]

Re: Bento: Jupyter Notebooks at Meta

#119

Post by [deleted] » Thu, Sep 19, 2024, 12:25 PM UTC

[deleted]

Re: Bento: Jupyter Notebooks at Meta

#120

Post by master_crab » Thu, Sep 19, 2024, 12:35 PM UTC

quicklime wrote: post #96

master_crab wrote: post #91

Earlier quoted context omitted.

If git is blocking you, you are using it wrong. Lotta instances of people treating it as an artifact repository. Use it correctly with a branching strategy that works for your use case and it's bulletproof. Plenty of other customers with the same magnitude problems as Meta are using Git perfectly fine.

Who are the others with the same magnitude as Google and Meta’s monorepos?

No one. Because people should know better than to use monorepos. Most teams at Amazon (which works at the same scale) religiously avoided them.