5 Well, my new job has been going well working at IOpipe. I love it. It does
6 take a bunch of my time since it is full-time. Also recently I removed a
7 distraction from me and honestly it seems really peaceful now like I can think
8 and such. Maybe I was addicted. But anyway, going to continue work on
9 SquirrelJME. I got a new logo designed and Lex is being redesigned by
10 [CYMKat](https://twitter.com/CMYKhia).
14 Need to figure out the best way to initialize classes. But honestly I think
15 something that just works will be good enough. Because I hit this problem
16 before where I tried to solve it without understanding it. SpringCoat is
17 supposed to be dirty and not the best way to implement. I mean once
18 everything is working much better I can recycle and reiterate to SummerCoat
19 and slowly develop everything.
23 Would be easiest to invoke a static main entry point, will not need to deal
24 with initializing objects and such.
28 I think having services would be a bit too complex, something more direct
29 might work out better in the end. But I will avoid thinking about this until I
30 actually write SpringCoat. Hopefully I can write SpringCoat.
34 Actually an idea, it is inefficient but it could work. Basically when I load
35 and initialize a class I load all of its information such as fields, methods,
36 and other things. Then I maintain everything that is actually available for
37 the class. So there will be duplicated information but it will remove the
38 need to do recursive handling of classes and such. I can load everything as it
39 needs to be for a class and just use back references and such. But I need the
40 basic class hierarchy to exist first before I can process fields and methods.
41 But basically say I load class `A`, that will load `Object`. No class can
42 recursively depend on each other, so there is no issue there.