This was a response to a Hacker News comment asking me what I've been up to since 2010. I'm posting it here since HN rejects it with "that comment is too long." I suppose that's fair, since this ended up being something of an autobiography.
--
What happened after 2010?
using DimensionalData
using GeoData# Functions to be extended
"""
gridcoordinates(::Gridtype,x)
Hey everyone - this is not just a one off thing, there are likely to be many other modules in your dependency trees that are now a burden to their authors. I didn't create this code for altruistic motivations, I created it for fun. I was learning, and learning is fun. I gave it away because it was easy to do so, and because sharing helps learning too. I think most of the small modules on npm were created for reasons like this. However, that was a long time ago. I've since moved on from this module and moved on from that thing too and in the process of moving on from that as well. I've written way better modules than this, the internet just hasn't fully caught up.
@broros
otherwise why would he hand over a popular package to a stranger?
If it's not fun anymore, you get literally nothing from maintaining a popular package.
One time, I was working as a dishwasher in a restu
rasterio.Env.options does not accurately represent the current state
of the environemnt:
import rasterio as rio
with rio.Env(option='whatever') as env:
print("env.options", env.options, )
print("")
print("rio.env._env.options", rio.env._env.options)
| C:\Users\Ismael | |
| λ julia | |
| _ | |
| _ _ _(_)_ | By greedy hackers for greedy hackers. | |
| (_) | (_) (_) | Documentation: http://docs.julialang.org | |
| _ _ _| |_ __ _ | Type "?help" for help. | |
| | | | | | | |/ _' | | | |
| | | |_| | | | (_| | | Version 0.5.0 (2016-09-19 18:14 UTC) | |
| _/ |\__'_|_|_|\__'_| | Official http://julialang.org/ release | |
| |__/ | x86_64-w64-mingw32 |
In most programming languages, most functions are synchronous: a call to the function does all of its business in the same thread of execution. For functions meant to retrieve data, this means the data can be returned by calls to the function.
For an asynchronous function, a call to the function triggers business in some other thread, and that business (usually) does not complete until after the call returns. An asynchronous function that retrieves data via another thread cannot directly return the data to the caller because the data is not necessarily ready by the time the function returns.
In a sense, asynchronous functions are infectious: if a function foo calls an asynchronous function to conclude its business, then foo itself is asynchronous. Once you rely upon an asynchronous function to do your work, you cannot somehow remove the asynchronicity.
When the business initiated by an asynchronous function completes, we may want to run some code in response, so the code run
This list of resources is all about acquring and processing aerial imagery. It's generally broken up in three ways: how to go about this in Photoshop/GIMP, using command-line tools, or in GIS software, depending what's most comfortable to you. Often these tools can be used in conjunction with each other.
