The guy who coded the initial version of BackRub, the first version of Google Search, but left before the company formed. TODO how did he meet Largey Brage? Why did he leave Google?
In 1997 he cofounded eGroups, a mailing list management website, together with the mysterious Carl Victor Page, Jr., Larry Page's older brother. eGroups was sold to Yahoo! in 2000 for $432m, just before the Dot-com bubble burst.
As of 2021 his net worth was of "only" $1b, even though his original Google shares would have been worth $13b. He must have sold too much too early to do other cool stuff. archive.ph/IgkMI:Did Largey give him this nice deal as a way to thank him for helping start the company, or was it just that they had no big hopes and $800 seemed right? youtu.be/pmXDtTD6vQY?t=146 suggests the stocks were part of his compensation for 3 months of coding work. Also mentioned at: nypost.com/2021/08/20/google-founder-created-revenge-site-against-estranged-wife
When Mr. Page and Mr. Brin founded Google in 1998, Mr. Hassan bought 160,000 shares for $800. When Google went public in 2004, the shares were worth more than $200 million. The shares, now in Google’s parent company, Alphabet, would be valued at more than $13 billion today [2021].
In 2001, Scott married a Vietnamese chick called Allison Huynh from university and they had three children.
In 2004 he tried strike a $20 million[ref] post-nuptial after Google went public, which she declined, so things were already crappy back then.
Then, during the divorce, Scott even created a revenge website for her as well. He's so petty! Down as of 2024 of course. There are only some weird redirect archives now: web.archive.org/web/20210915000000*/https://allisonhuynh.com redirecting to sites.google.com/view/allisonhuynhcom
The divorce is covered in several major outlets:
- www.dailymail.co.uk/news/article-9912929/Billionaire-investor-helped-launch-Google-accused-divorce-terrorism-bitter-break-up.html
- www.nytimes.com/2021/08/20/technology/Scott-Hassan-Allison-Huynh-divorce.html
- www.cnbctv18.com/technology/who-is-scott-hassan-the-google-founder-accused-of-divorce-terrorism-10543641.htm
- www.forbes.com/sites/jilliandonfro/2020/02/28/suitable-technologies-bankruptcy-filing-scott-hassan-allison-huynh/
To be fair, he did work on a lot of cool stuff after BackRub for which he deserves credit, not the least the company that created the Robot Operating System, which is a cool sounding open source project, which is awesome. But this divorce story is so damning! He should just own up to it, split the cash, and move on... The fact that the Google money came from an investment before marriage likely complicates things.
The fact that he does not have a Wikipedia page as of 2022 is mind blowing, especially after divorce details. Maybe Ciro Santilli will create it one day. Just no patience now. OK, done it June 2022: en.wikipedia.org/wiki/Scott_Hassan let's see if it lasts. The page lasted but ended up being Ciro Santilli's first edit war, how exciting:
- December 2022: an anonymous user with IP from California removed divorce details and google share ownership details, both of which had a New York Times source: www.nytimes.com/2021/08/20/technology/Scott-Hassan-Allison-Huynh-divorce.html. Discussion at: en.wikipedia.org/wiki/Talk:Scott_Hassan#Divorce_details_removed_as_%22poorly_sourced_material%22_by_anonymous_user_even_though_they_had_a_source_from_the_New_York_Times It feels exactly like the type of thing Scott would have done himself. And he possibly inadvertently exposed his real IP in doing so: 24.6.226.102. It is pingable, but Nmap analysis shows nothing of interest.
- June 2024: another partial revert removing the juicy divorce details by user named "ReversingWrongs". The username choice so incredibly cute and naive it makes Ciro wonder if this is from some woman that loves him (mother, child, new partner?) rather than just a Hassan sockpuppet. OK, perhaps with en.wikipedia.org/wiki/Wikipedia:Biographies_of_living_persons#People_who_are_relatively_unknown the divorce has to be left out? It's always impossible to decide with those wikipedia things. What you can say, is not necessarily what people want to read about, even when it is incredibly well source.
Looking a the history, he just kept revealing different IPs and continuously reverting, which other people put back in. Another of his IPs:There is also an interesting edit from 2600:1700:5470:5c50:7566:9580:1b60:ab41 which mentions without source the little known factso it could be Hassan adding some actually good and interesting information to the article. That one however also has an edit to en.wikipedia.org/wiki/Ernest_Nagel so maybe it's not him.
after working at Washington University's Medical Libraries Group (having been recruited out of SUNY Buffalo for the summer).
Screenshot of allisonhuynh.com by the Daily Mail
. Source. The most comprehensive list is the amazing curated and commented list of quantum algorithms as of 2020.
He was at Fairchild. That place was nuts.
Theories of Quantum Matter by Austen Lamacraft The Elastic Chain Position Fluctuations by 
Ciro Santilli 37 Updated 2025-05-13 +Created 1970-01-01
Ciro Santilli 37 Updated 2025-05-13 +Created 1970-01-01Webpack is like a magic hydra that can eat any type of file and bundle it into a single output: .js, .ts, .ccs, .scss, .jsx, .tsx,
require, import, import css from .js, it doesn't matter at all, it just digests all into the same dump.When it works, you are just left in awe and with a single Js file. When it doesn't, you're fucked and have to debug for several hours.
Demos under: webpack/. To run all of them by default:To easily make changes and reload the .js output live let this run on a terminal:
cd webpack/min
npm install
npm run build
xdg-open index.htmlnpx webpack watchExamples:
- webpack/min: minimal hello world. Doesn't do much, just copies
index.jstodist/index.js. - webpack/require:
requireandimportdemo. Both work from the same file.dist/index.jsnow contains all of:notindex.jsnotindex2.js- Lodash, a common third-party helper library specified in the package.json and installed with npm
- webpack/node: produce Node.js output, as opposed to the default web output. To test it run:Achieved simply with:
npm run build node dist/index.jsas documented at: webpack.js.org/concepts/targets/target: 'node'Fatman in Robin, - webpack/sequelize: attempts at getting Sequelize to work with webpack. It's just not supported by Sequelize:
Pinned article: ourbigbook/introduction-to-the-ourbigbook-project
Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
Intro to OurBigBook
. Source. We have two killer features:
- topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculusArticles of different users are sorted by upvote within each article page. This feature is a bit like:
- a Wikipedia where each user can have their own version of each article
- a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
Figure 1. Screenshot of the "Derivative" topic page. View it live at: ourbigbook.com/go/topic/derivativeVideo 2. OurBigBook Web topics demo. Source. - local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
- to OurBigBook.com to get awesome multi-user features like topics and likes
- as HTML files to a static website, which you can host yourself for free on many external providers like GitHub Pages, and remain in full control
Figure 2. You can publish local OurBigBook lightweight markup files to either OurBigBook.com or as a static website.
Figure 3. Visual Studio Code extension installation.
Figure 5. . You can also edit articles on the Web editor without installing anything locally. Video 3. Edit locally and publish demo. Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension. 
- Infinitely deep tables of contents:
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact