The Dempster Dumpster had a standard form factor, so that the forks of a Dempster Dumpmaster truck could pick it up and dump it into the back.[1] The patents have expired, so now anyone can make compatible rubbish bins and trucks. The standard form factor lives on for compatibility with the installed base. Properly, the term "Dumpster" refers only to containers compatible with that system.
There's also the Dempster Dinosaur, for when a Dumpster just isn't big enough.[2] That form factor is called a "roll off".
The Dempster brothers solved the problem of collecting, lifting, packing, and moving a lot of trash without hand labor, and dominated the industry for decades. Dempster, the company, seems not to have survived. The "Dumpster" trademark was allowed to lapse. From the USPTO:
DUMPSTER (EXPIRED)
CONTAINERS FOR RECEIVING, TRANSPORTING, AND DUMPING MATERIALS OF VARIOUS
KINDS-NAMELY, REFUSE, TRASH, GARBAGE, SCRAP, DIRT, AND ROCKS.
FIRST USE: 1936-09-01.
In Dutch, we call it a container. Yes, the English word is used by the Dutch to refer to the rubbish bin we all have outside of our houses. They're all the same style too pretty much: hard plastic (not sure which type) and all pick-uppable by the garbage collectors. Though they do come in different volume sizes.
I mean I know that doesn't replace that name to your ears now, but if that word was never made up others would have been used instead, as they do in some other anglophone corners of the world.
Amusingly, I'm in the reverse situation: loving working in Haskell and reeally want to try Rust but I just don't have the time.
For what it's worth, Haskell can be compiled to code that's quite fast. Somewhat unfortunately, the difference between GHC's vanilla output and its speed-optimized output can be quite vast, which I think gives the impression that the language or a given program is necessarily slow.
Apple's T&Cs are so long because they usually show you like 6 different documents, most of which aren't even in regard to iTunes. (Google does this too.)
It depends on how you've packaged your application. Technically, yes, the user needs NW.js to run your application, but you can ship with NW.js if you like (it's just one fat executable). When NW.js is run, it looks for a NW.js app to run in the working directory, so all the user needs to do is run the NW.js binary you provided and it will launch your app.
> That's going to break so quickly here in Boston.
Depends on what you mean by "break". In Boston, you might just get, epic, hour-long pong battles. Seriously, the pedestrian signal situation in Boston is so haphazard you could hardly make it worse by introducing experiments like this.
I don't know, I always found the perl and zsh man pages to be rather pleasant. They were sprawling, sure, but having long ago given up on brevity, they have no fear of meticulously describing how a feature or flag works. And they're just man pages, so you don't need to read the manual-for-the-manual first like I always find myself doing when I'm forced to use info.
Between Bob's army and insipid comments rising to the top, the comments sections of a lot of interesting, community oriented channels became useless (more so, even, than before). If nobody is actually looking at the comments section, then it doesn't really make technical sense to keep it as it is - it's just busy work for their engineers.
So it makes sense then for them to either attempt further fixes, or, in true Google fashion, simply remove the feature altogether.
I don't know about the rest of G+, but since the integration, I've been unable to comment on YouTube videos with my G+ account, something that worked fine before. I'd certainly call that "not usable".
I too couldn't leave comments. It took me awhile to figure out it was because I was blocking third party cookies. Apparently the new G+ comments on YouTube rely on them.
Google Translate actually doesn't do a terrible job on the article text (it's not perfect, but it's understandable). It does kind of mess-up the English in the email though.
