scottmac

100% this ^

The initial cost of the Gizmo was around the same as an iPad but the long term maintenance cost was significantly less.

Every building at Facebook probably has a couple of hundred of these devices between reception, building maps, room tools, monitoring dashboards and video conference controllers.

Gizmo was from the group I worked with at Facebook. This was almost entirely from a "How can we make it easier for people to collaborate". 2 is the closest reason :)

They were multi functional:

- Room Check-in devices (replacing Nexus 7s)

- Building Maps (replacing mac-minis)

- Reception Check-in (replacing iPads)

- Employee Dashboards (replacing mac-minis)

- Video conference control panels (replacing the cisco device)

The advantages they had were:

- Single SKU for IT Operations

- Pulled down a fresh image on each boot and had no state which made IT and security happier

- Could join the correct VLAN via 802.11x, the key lived on the TPM chip which made security happy

- Powered via PoE allowed remote restarts

It stopped deleting and started archiving back in 2016/2017 when Dex was merged with the Wiki.

I worked on the wiki at a large company, we had several problems but came up with a few changes.

- A wiki reaper that would reap docs that hadn't been updated in more than 1 year. We'd give people 1 month to action.

- In search, older pages were weighted lower than newer pages.

- Pages had "team" owners rather than individuals.

- Teams would get a monthly digest of their top viewed pages and lowest viewed pages to encourage updates.

- Star rating for pages 1 through 5, would feed into above digest.

Wikis grow organically but need active curating.

Stripe | Software Engineer (Type System)| San Francisco, CA / Seattle, WA / Remote | Full Time

Stripe has built and rolled out the first version of a static type system for Ruby to improve our ability to maintain and extend Stripe’s large and growing codebase. We need to extend the type checker, incorporate types into more of our code base, and create more of the tooling that the type checker enables.

We’re looking for people with a strong background in and interest in building language processing tools such as type checkers, semantic analysers, compilers, or IDEs. The ideal candidate will have a mix of technical expertise in language processing, a passion for solving developer experience problems, and a pragmatic ability to ship results iteratively. Code base is modern C++.

https://stripe.com/jobs/positions/type-system-and-tooling-en...

I work at Facebook and have been involved in the Hiphop for PHP project for the past few years.

We have our own VM written and it isn't based on the JVM.

Bytecode: https://github.com/facebook/hiphop-php/blob/master/doc/bytec...

Code: https://github.com/facebook/hiphop-php/tree/master/src/runti...

It's just CentOS

It's a hardware issue with the x87 instruction set,

http://gcc.gnu.org/ml/gcc/2003-08/msg01195.html is a good explanation.

The copying from the 80-bit register to the 64-bit memory cell is causing the result to be corrupted. When we use volatile it tells the compiler not to apply the optimisation which in this case was putting it in a register.

I've fixed this now in all the PHP branches.

http://svn.php.net/viewvc/?view=revision&revision=307095