Gregory's ServerBetween the aggresive type-checker, formatter, structured editor reassembler, I've built the perfect self-asphyxiation programming framework to never ever get anything done ever again. Don't mind me while I proof the hello world printing routines for a month.
 8 comments
@csepp It's not so much that it takes resources, that it takes me too much brain juices to figure out why the type checker complains sometimes. I have to find the sweet spot where it's dumb enough to let me experiment without getting in the way, otherwise I've noticed that I've developed the habit as marking everything as unsafe and getting on with it, which defies the purpose why I did this in the first place.  @neauoire Law of conservation of static checks Languages that don't start out with static checks will tend to add them or be replaced by other languages that do. I haven't done this yet, but I know what you are talking about (except the email thing). PS You guys are cool |
@neauoire Yeah, that's the trick of type systems, you gotta choose something powerful enough to easily express useful programs, but not too flexible, otherwise the type checking algorithm gets way too hairy and use too many resources.