aardvark179

61 ms·

751.
by aardvark179 15y ago
The OS maps are lovely, and interesting for some of the subtle detail they include. I noticed recently (while using an OS map as a background raster for some much more detailed data) that the roads on the 1:25000 and 1:50000 scale maps are
752.
by aardvark179 15y ago
Quite a lot of published maps pass through Illustrator or similar at some stage for careful human retouching and intervention. For larger scale (quantity, not map scale) stuff then you tend to have a source data set containing the raw geosp
753.
by aardvark179 15y ago
It was more than that, you wrote your entire UI in NeWS's Postscript-with-knobs on, and communicated asynchronously with the server side of your app. Think of writing a desktop app as a tiny web-server with the UI in a browser, only all the
754.
by aardvark179 15y ago
This is true, but has to be thought through very carefully in multithreaded environments where another thread might remove an object from a collection, causing it to be deleted while you're still looking at it. Safe looping then requires lo
755.
by aardvark179 15y ago
Ah right, those are going to make things fun. :-) I think in your position I'd write a compiler, but keep the AST associated with the byte code and back off to an interpreter if the AST is modified, maybe recompile after enough calls withou
756.
by aardvark179 15y ago
Looking at that project page is there a reason you went for an interpreter rather than compiling to JVM byte code directly? Obviously it's a little harder if you're targeting JVMs <v7 as you don't have invokeDynamic to play with, but mo