3 ms·
My hope is that you take this (rather good-looking) code, and port it to a closed-source, for profit tool based on node-webkit. Let me buy it for $100, and run
by javajosh 13y ago
My hope is that you take this (rather good-looking) code, and port it to a closed-source, for profit tool based on node-webkit. Let me buy it for $100, and run it on my local machine, and not suffer the downsides and dependency inherent in the SASS model.
It looks like a nice product, but honestly, unless I control the bits (or at least have a nice illusion of controlling the bits, e.g. what I get when I use Chrome or Firefox) then I'm not interested. I'm especially not interested in a SASS that essentially holds my tooling and my code hostage, that if I don't pay the fee then my tools go away. That's just a stupid decision to get into that kind of a dependent relationship with a tool vendor. If the last few years have taught us anything its that SASS is convenient and wonderful in many ways, but has some severe, even debilitating downsides: no privacy, no control, no freedom.
There are some SASS tools that I use, but it's with increasing reluctance, and I have "plan B" ready at hand. (Although honestly I haven't looked into what it would take to export all of my Evernote data). There is no chance in hell I'd ever use a SASS IDE. It's just too important.
There's another reason why a SASS IDE will never fly, at least with me, and that's the fact that once you commit to it, you can never, ever code offline. For many people this is not a deal-breaker, but for those who place a premium on uninterrupted, undistracted coding going offline for a while is invaluable. Of course, any SASS app will not be available unless you are actively connected to the internet, so this use case is out.
- taude 13y agoI think this is going to be a necessity in a few years when web-based IDEs are functionality complete enough that enterprises can use them.