5 ms·
I’m genuinely curious: Why are you not okay with the compilation step? I work primarily as a developer using compiled languages so I may be missing something.
by finaliteration 8y ago
I’m genuinely curious: Why are you not okay with the compilation step? I work primarily as a developer using compiled languages so I may be missing something.
- TekMol 8y agoThere are many aspects to it. From setting up a new project to 'edit a line and reload in the browser'. Everything feels so much faster, lighter, fresher.
- deleted 8y ago[deleted]
- stefanfisk 8y agoI'm one of many who don't seem to understand your point of view. how would editing and reloading be faster than hot reloading? I usually edit my styling live in Sublime while viewing the changes in Chrome.
- deleted 8y ago[deleted]
- TekMol 8y agoStyling?
- stefanfisk 8y agoyep, as in style sheets. personally I prefer Sass before native CSS, so I usually use the broader term to avoid assumptions about the technology stack used.
- szatkus 8y agoI usually write down styles to some kind of Notepad and then rewrite it to sass. At the beginning it was annoying, because I was forgetting that my css will be reloaded, but I got used to it.
- spankalee 8y agotsc --watch is incredibly fast. And you don't need a bundler and hot-reloading. Just stick to JS modules, output JS modules and let the browser take care of it.
- peterkelly 8y agoBut when you use a tool like webpack it's even simpler - you just save your file and it recompiles & reloads. You can also run 'tsc -w' (watch mode) and it will automatically recompile as soon as files change. And since doing so maintains a local cache of the compiler's state in memory it's extremely fast. The tiny amount of time I spend waiting for compiles is several orders of magnitude less than when I had to deal with the lack of static typing, particularly when refactoring code.
- ww520 8y agoFast REPL cycle.