mpalme

Posts like these are the reason I come here. Kudos!

Perhaps people still reading the rather long blog article?

> [...] rule that will trigger xscreensaver to lock the screen every time any USB drive is removed

Link cams are a marvel of engineering.

Thy operate on a simple concept of trisecting a cam lobe so that, as the device is retracted, the cam unfolds and permits an amazing range for a unit of its size.

http://www.omegapac.com/itemdetail.php?id=1&secid=9

But in any case, it will be helpful for other newcomers to Rust because they are likely to run into the same challenges.

"Imagine the kinds of amazing new software that could be created in alternative cultural environments."

It's in development according to https://status.modern.ie/webrtcobjectrtcapi?term=webrt

I was surprised that the PHP database access layer doesn't throw an error and aborts the transaction (like the other DAL I know would do).

> So if Martin Fowler says that it is possible to use a service locator instead of DI in unit testing, then who are you to argue otherwise?

There are good arguments against a service locator - one of them is presented here: http://blog.ploeh.dk/2010/02/03/ServiceLocatorisanAnti-Patte...

Another argument again the service locator pattern is this: If you ask the locator for a service which has dependencies you have to resolve those dependencies yourself. So you need to know about the specific implemntation of this service interface which defeats the purpse. If you work around that, you end up with something that is pretty close to a DI container.

The main benefit seems to be that it's based on a Firebase backend and updates in realtime.

The problem es essentially to map from an indiscrete space to a discrete one. The solution that comes into my mind is a simple sweep-line algorithm:

1. Take all the start x-coordinates of a buildings (=start events).

2. Take all the end x-coodinates of the buildings (=end events).

3. Sort all the events the by the value of the coordinate.

4. Now walk over all the events and keep count of how many there currently are (or in this case: how high the building is) by adding one for a start event and substracting one for a end event.

http://en.wikipedia.org/wiki/Sweep_line_algorithm

Another idea: sunken ships. Comes in handy if a server is down.

Meta note: this is what journalism can look like today. Made for the web first, not for the paper. Visualizations that are actually insightful - and most importantly a well researched story.

The title is slightly misleading - In fact the compilers have been available before as part of the .NET Framework (or Windows SDK) and are most likely sitting on your windows machine (try c:\Windows\Microsoft.NET\Framework\v2.0.50727\csc.exe).