| progress... |
[Jul. 19th, 2009|09:01 pm] |
http://www.club.cc.cmu.edu/~mds2/js_play/calculator.html
cool.
Some side comments ( inane details ) ( mini rant )
Finally: I'm a graphics programmer at heart. I'm not going to be satisfied with this until I know enough ugly DOM tricks to actually get real sprite-based graphics working. It must be possible, since both "Google Maps" and "Google StreetView" work this way.... ...huh, I wonder if I could cheat and look at these... |
|
|
| Baiting the PL people |
[Jul. 12th, 2009|09:50 pm] |
I have several questions I'd like to ask the PL people out there (and really, anyone else who feels like giving their own answers, as I'm mostly soliciting opinions, scenarios and what-ifs rather than "facts"). I am posting them here because I would like to see some degree of lively debate. Anyway, here goes:
- Given how much the "standard programming languages we use" have changed over the years, and that many of the industry standard scripting languages today were based on research languages like Self, Smalltalk, Lisp, etc., what present-day research languages and features of present-day research languages do you see inspiring the industry-standard languages of tomorrow?
- Of the standard "functional favorites" (Haskell, SML, OCaml), which do you see used the most often for industrial CS applications? (I mean, come on, I know there is a small minority of people who do this) Which would you like to see used for industrial CS applications and why? Are some better suited and/or more widely used for web / mobile / other application domain?
- JCreed once had a post about the things he'd learned in programming that seemed silly at first and later turned out to be of fundamental importance. The list begin with things like "commenting your code" and "strong type systems" and ended with pieces of mathematical logic I'd never heard of and didn't understand. Of the things PL people deal with that I don't yet know or understand, which do you think are the most important/fundamental/general/practical? i.e., if I had a choice, which should I learn first?
Thanks.
P.S. This was all inspired by learning JavaScript... ...I shit you not. |
|
|
| Cool |
[Jul. 12th, 2009|02:12 am] |
Javascript...
I seem to have the basics down although I probably just used them to create a godawful bad UI...
I'm also guessing that for most of the things people use it for, they just end up copying one of a bunch of standard pieces of code...
... also what the hell is with firefox doing image scaling by point sampling. |
|
|
| CS etc |
[Jul. 11th, 2009|03:59 am] |
I'm slowly getting the impression that the field I knew of as "computer science" when I was an undergrad (remember when the undergraduate catalog listed a "scientific computing track"? CS majors don't do that shit anymore) is slowly schisming into a bunch of only-tangentially-related fields.
This frustrates me as I feel I should be able to work in all of them (okay, so I accept that I can't understand programming languages theory without an entirely different sort of math degree from the one I have) but its quite clear that only some skills from any given field will cross over into other ones.
I made a comment about wanting to catch up on "web programming" (actually a serious discipline now) in an earlier post, but even fields like "graphics and robotics" that should be quite close in many ways present this problem. For instance, 5 years of writing control algorithms and simulators for robot swarms has left me oddly unemployable in computer graphics. (I'm probably going to relearn this from the ground up sometime in the next 5 years, and its probably going to change a couple times as "graphics" starts to mean "shared virtual environments over something resembling modern web protocols" and phrases like "augmented reality" move from "things you name your research lab" to "things your mobile phone startup has to do")
I guess this is partly exacerbated by the fact that I did grad school in something most people don't really consider computer science. "Robotics" is only in the CS departments at a few schools (oddly the ones considered the best in robotics) and the conferences I go to are mostly populated by mechanical, electrical and chemical engineers, with the odd mathematician.
Also, dude, vision. That stuff keeps turning over faster than anyone but a vision PhD can keep track of. They seem to be able to do wonderful things with it though.
Oh yeah, and systems? My first 5 years in industry, the little bit of OS I'd managed to absorb was incredibly useful for writing graphics applications that ran on a single desktop. Now I'm kicking myself for not taking networks instead. It seems networks and databases are now the useful parts of systems, and knowing those would be well worth the trade for "only having a 15-213 level understanding of OS" Shit, there's totally going to be networks inside our computers, and our filesystems are going to look like databases. |
|
|
| (no subject) |
[Jul. 10th, 2009|03:50 am] |
|
Anyone know of a javascript tutorial which doesn't assume its my first programming language? |
|
|
| Looking for work |
[May. 12th, 2009|06:25 pm] |
The bad part about getting a PhD is you stop getting paid to be a "Grad Student Researcher"
I kinda (read "really") need some sort of temporary income between now and whenever I get my postdocs / real job.
Does anyone know where I can get temporary / contract work that I can do from Los Angeles County? |
|
|
| procrastination / graphics |
[Feb. 23rd, 2009|05:44 pm] |
Procrastinating from "writing papers" (and motivated by the fact that I might apply to graphics-related jobs using my very non-graphics-related grad school experience) I decided to fix most of the things that sucked about the graphics for my simulations.
Check out http://www.soe.ucsc.edu/~mds/cclsim |
|
|
| Perfect |
[Feb. 10th, 2009|04:59 am] |
http://www.processing.org/faq.html#java
The main rule when using Java code: You cannot use most of the AWT or Swing (which is built on the AWT), because it will interfere with the graphics model. If you want to add scroll bars and buttons to your projects, you should make them using Processing code, or embed your Processing applet inside another Swing or AWT application (see below). Even if they appear to work, such sketches will usually break when you try to run on other operating systems or other versions of Java.
Screw AWT and Swing
Also : Not so perfect
We currently only support Java 1.4 (and earlier) syntax. You cannot currently use 1.5 syntax in the Processing Development Environment. This means no generics, templates, enum, varargs, foreach, and the rest. If you want to use Java 1.5 (or later), take core.jar and develop your project with another Java IDE (again, see below). More about Java versions can be found on the platforms page. A couple of the syntax features in Java 1.5 are very useful (the enhanced for loop, some aspects of generics) so if you would like to use them in Processing, please give us a hand. You can start by visiting this bug which describes the obstacles to 1.5 support.
but workable... ...maybe...
Any advice? Anyone out there tried to tie a large simulation codebase in 1.5 java to a processing frontend (Processing.org front end is not written yet, but shouldn't be too hard...) |
|
|
| navigation |
| [ |
viewing |
| |
most recent entries |
] |
| [ |
go |
| |
earlier |
] |
| |
|
|