4 ms·
So, these days this style of thing is not uncommon. For example, much of the Rails community uses Sass, a language which compiles to CSS. In development mode,
by patio11 15y ago
So, these days this style of thing is not uncommon. For example, much of the Rails community uses Sass, a language which compiles to CSS. In development mode, it gets compiled anew on every page load. This doesn't happen in production: there are a few ways to make it happen, but basically, in production it looks like auto generated CSS sitting on the hard drive waiting to be served up quickly.
Doing the same thing with WebPutty would take maybe a dozen lines of code. I'm assuming anyone with multiple environments can make it happen in their language/framework of choice.
- AndrewHampton 15y agoI'm curious if you used this already since you've been working w/ Fog Creek or if this is the first you're seeing it too.
- patio11 15y agoI haven't used it. I will never answer questions about what knowledge I have/had regarding clients' upcoming product releases. You don't have to be Steve Jobs to get touchy about that one, and it's specifically enumerated in most NDAs I sign.
- AndrewHampton 15y agoOK, thanks
- dolinsky 15y agoI can definitely appreciate the usefulness of realtime here, 'n having led teams in the past I'm all for using tools like Sass/less/blueprint/etc that expedite development time and empower the team. I guess it's the 'Publish' part of this tool that is really irking me, as any environment I've either designed or been a part of has always had a process for sending files to live, and it never included editing and saving files already in a live environment without some intermediary testing platform first.
- iamwil 15y agoInstead of publish, I'd rather have a button that says 'commit'.
- ehutch79 15y agoThe problem is you can't use webputty locally, it needs to access the page in order to use it. so anything you're working on needs to be live on the internet