Augh, I hate type casts. Hate hate hate hate hate.
I thought the IDE was supposed to help you manage that dumb bullshit. My. Ass.
| 1. |
complete my distributed computing class
2 entries |
1 person |
| 2. |
complete my senior thesis project
1 entry |
1 person |
| 3. |
complete my business issues class
|
1 person |
| 4. |
complete my GUI building class
1 entry |
1 person |
| 5. |
complete my UML class
|
1 person |
| 6. |
finish the APO scrapbook
1 cheer |
1 person |
| 7. |
lose 10 pounds
|
5,947 people |
| 8. |
get a job for the summer
|
14 people |
| 9. |
find a place to live in the fall
|
2 people |
| 10. |
finish building my Rails app
2 entries . 1 cheer |
1 person |
| 11. |
learn Lisp
1 entry |
266 people |
| 12. |
Take more pictures
2 entries . 1 cheer |
14,326 people |
| 13. |
master Ruby
1 entry . 2 cheers |
179 people |
| 14. |
learn how to cook
1 entry |
1,487 people |
| 15. |
learn how to do personal financing
|
1 person |
| 16. |
fall in love
|
24,514 people |
| 17. |
develop a folksonomy that uses personally defined ontologies instead of *just tags*
5 cheers |
2 people |
| 18. |
make a better squarified treemap application
|
1 person |
Augh, I hate type casts. Hate hate hate hate hate.
I thought the IDE was supposed to help you manage that dumb bullshit. My. Ass.
I talked with Professor Varela for about 45 minutes about the syntactic constructs and some implementation details that would go into building an Actor Library/DSL in Ruby and generally things look positive.
He liked my idea of using futures to pass the results of actor message invocations around (even though it means a fair bit more implementation work) and I think the syntax for the rest of the job should be pretty easy.
Score one for Ruby’s flexibility. I just hope that there’s some practical use for this sort of thing.
Not quite sure when I’m going to get to sit down and take a read, but I’ve got it now (well, not now, I’ve gotta pick it up from the mail center).