pyppeteer VS b-decoded

The latest version of Pyppeteer, i.e., 1.0.2, can also be installed by executing pip3 install -U git+https://github.com/pyppeteer/pyppeteer@dev on the terminal.

Having async baked into Python both as a keyword and standard library has vastly opened up the number of use cases async will be used in where it is appropriate, one of my favorite libraries pyppeteer would have not existed in the easy nice way it can be used without asyncio: https://github.com/pyppeteer/pyppeteer

Yes, this is scraping. You need a legit new cookie issued by the site. The solution is to automate the going to get the cookies part. The most straight forward way to do this is probably using a headless browser through something like Selenium or pyppeteer.

Last I checked, pyppeteer wasn't a thing anymore, and I haven't tried Playwright but if it has a headless mode, thats what you want so you don't have a browser open.

pip install -U git+https://github.com/pyppeteer/pyppeteer@dev

The normal Puppeteer package is JavaScript, but I do see that there's a Python port called pyppeteer. I can't vouch for it specifically, but I imagine it's similarly easy to use as the JS version.

Just use b

I use b

I used to believe this but i don't anymore.

From https://github.com/tlack/b-decoded

Arthur is famous for his very dense programming style. Most C programmers would scream when seeing this code.

In his view (and others in the terse scene), it is much better to have everything in your application readable on the screen at once than to have great names for things or a lot of white space to comfort the first timer reader.

To them, once you've sufficiently studied that screen or two of code, you can understand all of it at the same time. If it's spread out over thousands of files, it's very difficult to understand all of it, which leads to bugs, unnecessary abstraction, and the need for advanced tooling just to work with your own project's code.

He wants to see the code "all at once" so he can understand all of its behavior without paging around and shifting his focus to another tab, window, etc. To get there he makes a lot of tradeoffs in terms of the code formatting and naming conventions. He also, in b, creates a dense set of interlocking macros and abstractions that can make the code very hard to follow.

Critics and the uninitiated say that his code is like old school modem line noise: random punctuation intermixed with bits of understandable code. I would suggest that he's actually quite careful with the abstractions he chooses and they are actually not always the most dense, highly compressed code structures available to him. He chooses wisely and his code rewards deep study.

Interview with Arthur Whitney: https://queue.acm.org/detail.cfm?id=1531242

Here's some links relating to this style of code that you may find useful:

https://docs.google.com/document/d/1W83ME5JecI2hd5hAUqQ1BVF3...

https://github.com/tlack/b-decoded

https://chat.stackexchange.com/rooms/90748/conversation/ngn-...

They're not 1.5 paragraphs per line, but enough to give a taste of the implementation style.

I could write a whole compiler in that time.

Here is a link: https://github.com/tlack/b-decoded