1,213 karma · joined December 13, 2011
Fun unrelated anecdote: someone was showing off their concurrent Node.js web scraper and as requests piled up, it was apparent that it could handle no more than 5 concurrent requests. Why? The HTTP library's internal concurrency limit defaulted to 5.
The only thing that seems to be missing from the !!Con transcripts are timestamps. I'm not familiar with Plover so it might already be a feature, but being able to output one of the standard subtitle formats (SubRip, timed text, SSA) would make remuxing an MP4/MKV of each talk with subtitles much easier.
You'd of course need to install the software on your outside server that will forward packets for you, but a DO droplet would be great for that. It'd also work for the case where your router is your server and you shift between wired and wireless.
I think Google's enterprise pricing was targeted towards, say, a long-haul trucking company or a corporate GIS department where the viewers are just some managerial or analyst staff. In cases like that, if they charged the same rates as they did for CraigsPinSquare, they'd make a few pennies. Thus, the solution would be to discriminate pricing between high-volume consumer-facing usage and low-volume internal "enterprise" usage, especially since internal "enterprise" usage wouldn't give Google Maps much publicity.
Google decided that we fell in the "enterprise" bucket, and enterprise sales typically involves private negotiations with pricing. It's very possible that we got wildly different pricing than other companies.
We're still open to using Google products in general, but OSM is more fun.
For example, many cities in OSM have virtually perfect address geocoding because some random person pestered their local government to openly release a dump of addresses and their coordinates, whereas Google is just guessing at house numbers.
If anybody comes close, it'd probably be one of the big mapping companies. An armchair OSM contributor can map out a whole city without leaving the desk, but street-level imagery requires systematically visiting each street.
Unfortunately, the default renderer doesn't know how to draw a line of "man_made=conveyor_belt"...
The superfluous obtuse complexity that node.js forces is what's keeping ninja programmers like us employed. If we don't keep switching to strange new things every few years, our wages will stagnate as there's less separating our rock-star tech from lower-salaried uncool "enterprise" software.
Being able to manually manage continuations rather than using a language that does it for us is a high barrier that keeps us in demand, the same way that having to manage memory manually keeps people from becoming C programmers. Losing this edge is not something we should encourage.
Just imagine - if all of these "learn to code" programs actually work, the market will be flooded with new programmers. Thankfully, if we make sure that they only learn easy things like Python, we can continue to convince the world that things like Node.js and MongoDB are the future. While the rest of the world is still catching up on basics like Python and Postgres, we'll be one step ahead of them.
People questioning Node.js like this more and more are a sign that we need to find the next hotness and move there if/when node.js sinks. If we can convince people to build more things in the next hotness, then we can get in early before the masses pick up on it, ensuring that we can maintain our spendy lifestyles and free lunches in SF.
(/s)
So I go to Hoogle, and search for "[a] -> [b] -> [(a, b)]". First result is "zip".
Or I want to get only the things in a list that satisfy a predicate, but I'm suffering from nominal amnesia. I type in "(a -> Bool) -> [a] -> [a]" and Hoogle lets me know that I meant to write "filter".
[1] http://www.haskell.org/hoogle/?hoogle=%28a+-%3E+Bool%29+-%3E...
There are hardly any services like what MapBox and CloudMade have. The closest seem to be the various consultancies that will design and host a map for you.
It's tough to compare the two - each has services that the other doesn't (aerial imagery, routing, geocoding, etc.) so you might end up with an implementation that cobbles together things from both.
[0] http://open.mapquest.com/ [1] Well, check the terms at http://developer.mapquest.com/web/products/open/map
I wrote a prototype proxy in Go that can split network traffic over two Internet connections using some hacked-together tun code[0] and everything happens in userspace.
I think it's because PHP has a much larger surface area of questionable decisions to attack. When your core language is very, very small (e.g. Scheme), you have less to criticize, but when PHP has everything and the kitchen sink, plus a lack of an overarching philosophy or standard, plus a broken core developers community, it simply generates many more hatable things.
Overwhelmed with all of the responses I've gotten so far - unfortunately I don't have an HR department to handle these, so it's just me going through everything and might take me a few days to reply. Thanks!
* Mobile apps - especially iOS, Android, and possibly some jQuery Mobile + Phonegap work
* Web frontend - we're hoping to do more UI work on a PHP/jQuery interface
* Node.js - potentially looking for a dev on a Node.js backend
DoubleMap is a leader in real-time transit technology that puts real-time transit information at the fingertips of transit agencies and riders. We have several different software solutions that handle receiving, processing, and sending real-time geospatial data, and we use a variety of open-source technologies and languages.
We are based in Indiana, USA, and we welcome domestic and international remote workers.
Email if you're interested in working with us - our domain is doublemap.com, and my mailbox is "eric" at that domain.
This way, interesting Scheme programs can be written without using the small JavaScript stack.
It uses an infinite loop that's broken out of by throwing an exception. There are also some other tricks that it uses to allow other things to happen on the page while it runs your program.
One thing to note is that the UC-Logic pens use a different tech than Wacom's -- they require a battery inside the pen. And it looks like they still don't have tilt senstivity. But at that price...
What gp described just seems inefficient in general.
Things like the syntax of pattern-matching and datatypes I'd repeatedly Google for until I remembered, but relatively speaking it wasn't a huge time sink. The things that I did burn time on were things like getting types right inside monads, various other type-theory things, and cabal quirks.
I hope this cheatsheet helps people get started with Haskell, but my gut feeling is that the bigger hurdles will need another cheatsheet.