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

Bento: Jupyter Notebooks at Meta

engineering.fb.com

Post reply on HN
Print view View original

71–80 of 134 posts

Re: Bento: Jupyter Notebooks at Meta

#71

Post by adolph »

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…

Killer feature of VS Code notebooks is Vim keybindings. It also manages movement between cells, so you have to be very aware of the current mode.

Re: Bento: Jupyter Notebooks at Meta

#72

Post by paddy_m »

Fraterkes wrote: post #27
Fraterkes wrote: post #26

A bit off-topic, but my problem with any notebook type of tool (ie you create a document that mixes code, the output of that code, and text/media) is that they always feel like they're meant to be these quick, off the cuff ways to present data. But when I try to use them they just feel awkward and slow. (I tried doing a jupyter notebook with the vscode plugin, and while everything was very polished, it feld like I wa…

Also I always think it's a littly sad that Jupyter was one of the best shots for Julia to get more mainstream attention, and instead the notebooks people write are basically exclusively python

Also the Julia people wrote their own notebook system called Pluto. Which is so on brand for them. It might be technically better, but they miss out on the whole jupyter ecosystem, further isolating the language.

Re: Bento: Jupyter Notebooks at Meta

#73

Post by bsimpson »

Fraterkes wrote: post #26

A bit off-topic, but my problem with any notebook type of tool (ie you create a document that mixes code, the output of that code, and text/media) is that they always feel like they're meant to be these quick, off the cuff ways to present data. But when I try to use them they just feel awkward and slow. (I tried doing a jupyter notebook with the vscode plugin, and while everything was very polished, it feld like I wa…

I've only used them in Colab, which feels a lot like a Codepen. It's a self-contained scratchpad that's easily linkable to send to others.

Re: Bento: Jupyter Notebooks at Meta

#76

Post by quantadev »

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.

Re: Bento: Jupyter Notebooks at Meta

#77

Post by hnav »

extr wrote: post #58
landedgentry wrote: post #51

Earlier quoted context omitted.

Well, you're supposed to read the code and figure it out. And if you can't, you're not good enough an engineer. According to people at Meta.

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.

Doesn't sound like your type of company tbh, the flipside is that a "serious" company will often have broken bs too except now nobody is going to look at your contribution/fix.

Re: Bento: Jupyter Notebooks at Meta

#78

Post by moandcompany »

yodsanklai wrote: post #69
moandcompany wrote: post #68

Earlier quoted context omitted.

Same as Google. Many internal tools have painful interfaces and poor or documentation because the hiring bar was high and it was acceptable to assume that the user's skill level is high enough to figure it out. That attitude becomes a bigger problem when trying to sell tools to the public (e.g. Google Cloud Platform).

As an outsider, I was always under the impression that Google had a tradition of engineering excellence (robust tools, clean and while tested code following strict guidelines), while Meta has more of a Hacker culture (move fast and break things).

Google also has traditions that created Broccoli Man: https://www.youtube.com/watch?v=3t6L-FlfeaI

Re: Bento: Jupyter Notebooks at Meta

#79

Post by 3eb7988a1663 »

sdenton4 wrote: post #24
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?

It wouldn't be terribly surprising. Forking everything provides a liiiitle bit of protection against things like the 'left pad' incident.

Left pad was from the creator pulling the code from the public source forge, not from a destructive code change.

I assume all of the big tech companies host internal mirrors of every single code dependency + tooling. Otherwise they could not guarantee that they can build all of their code.

Re: Bento: Jupyter Notebooks at Meta

#80

Post by 3eb7988a1663 »

scottyah wrote: post #54
fwip wrote: post #44

Earlier quoted context omitted.

Is it? It seems like 90% of what Netflix is (from a technical PoV), is a CDN + video playback. There's a lot more value in the content library they've negotiated and the business agreements with ISPs than there is in the software stack. Apologies if this response is delayed, 6 posts today is "too fast."

I'm not sure anyone has access to the real data, but I've had a suspicion that Netflix is able to remain a lot more profitable due to their superior tech. Cloud hosting and streaming (not to mention labor) can get very expensive, and I think while it's easier to set up nowadays (in comparison to when they started) a lot of the other companies are burning cash to try to keep up. HBO Max (just Max now?) has always had…

Surely that has more to do with having a fleet of edge nodes that mirror content close to consumers? There are only so many ways to ship video bytes across the internet. Best way to save money is to move fewer bytes.
Post reply on HN