3 ms·

>You don't get to decide how I allocate my time Please point to the location where I say I'm deciding how you allocate your time. >I think we're done discussi

>You don't get to decide how I allocate my time Please point to the location where I say I'm deciding how you allocate your time. >I think we're done discussing this. Thank you for your contribution. That language was probably more harsh than it needed to be. Still I've been hacking on my blog for the day and (granted it is much smaller than yours) I couldn't fathom how changing one line could ever be described as "a huge amount of work" when it currently looks like this to me: <change line in editor. save the file> $ fab deploy That's all it takes. If what can be reduced to the above really takes half an hour for you then I think it would be a good time investment to try and speeden that deployment process up. Sorry for the language above - really I just like your post and am saying how I find it could be improved.

jacquesm 14y ago
> If what can be reduced to the above really takes half an hour for you then I think it would be a good time investment to try and speeden that deployment process up. You are still telling me how to allocate my time. For historical reasons my blog is a mix of badly interacting scripts called 'octopress'. I already spent a day and a bit just getting it to work properly and to migrate the content from Drupal. Whenever I so much as touch it something breaks. This can be for random reasons, a misplaced character here or there does wonders. Drupal sucks (for different reasons) but at least it worked. Octopress is nicer in theory but it simply does not scale beyond the trivial, there is a lot of content in those pages and clearly octopress has a problem with that. Just correcting a typo takes several minutes (if it works at all). So let's make a deal here: you allocate your time and you run your blog and I won't tell you what to do or change, and I will do the same with mine. And if and when that rainy Sunday with nothing to do rolls by (I wish...) then I'll spend the time required to re-write the software underpinning the blog to improve the turn-around time. Likely that will be several Sundays. Until then I thank the guys that wrote Octopress for doing the job they did. Figuring how to make the template to change for just one file is beyond my current level of knowledge and I do not have the time right now to improve on that. It most definitely is not as easy as you make it out to be, this is a generated blog, not one built up from separate pages of pre-rendered content. So any change I make to the end product is automatically reverted on the next generation. The pages themselves are flat text (markdown), and do not have the ability to output javascript.

jacquesm 14y ago

> If what can be reduced to the above really takes half an hour for you then I think it would be a good time investment to try and speeden that deployment process up. You are still telling me how to allocate my time. For historical reasons my blog is a mix of badly interacting scripts called 'octopress'. I already spent a day and a bit just getting it to work properly and to migrate the content from Drupal. Whenever I so much as touch it something breaks. This can be for random reasons, a misplaced character here or there does wonders. Drupal sucks (for different reasons) but at least it worked. Octopress is nicer in theory but it simply does not scale beyond the trivial, there is a lot of content in those pages and clearly octopress has a problem with that. Just correcting a typo takes several minutes (if it works at all). So let's make a deal here: you allocate your time and you run your blog and I won't tell you what to do or change, and I will do the same with mine. And if and when that rainy Sunday with nothing to do rolls by (I wish...) then I'll spend the time required to re-write the software underpinning the blog to improve the turn-around time. Likely that will be several Sundays. Until then I thank the guys that wrote Octopress for doing the job they did. Figuring how to make the template to change for just one file is beyond my current level of knowledge and I do not have the time right now to improve on that. It most definitely is not as easy as you make it out to be, this is a generated blog, not one built up from separate pages of pre-rendered content. So any change I make to the end product is automatically reverted on the next generation. The pages themselves are flat text (markdown), and do not have the ability to output javascript.