Atom 1.11

The machine was in sleep mode in day 1, but I forgot to put it to sleep mode before closing the screen (I hate this the most at OSX 10.10) in day 2. You can see that there is a little bit different between 2 charts.

This machine is MacBook Air 13" 2013. The battery goes down to 86% design capacity (7150 mAh) according to coconutBattery.app

VS Code's intellisense (which uses typescript for both js and ts files) however requires definition files for any dependencies to be installed separately (which may or may not exist/be up to date), requires you to explicitly exclude stuff like your node_modules folder otherwise it will simply stop working with no error message. This gets worse if you have multiple nested node/npm projects as is common with, for example, electron projects where you have to make sure you explicitly exclude the paths to any node_modules directories under the jsconfig.json root and you'll need separate jsconfig.json files for every project (which might be what you want, but isn't strictly required with tern like it is here). Another issue is that since vscode is clearly geared towards typescript, a variable's type is determined when it's declared and only then so something like "let app;" sets the app variable's type to "any" which it stays for the entire file no matter what object is assigned to it later.

There are some things I like, such as the ability to define JSON schemas and a number of the issues above don't apply when using typescript but when writing regular old javascript it's pretty lacking.

Outside of that, i havent had this happen. However, if it is simply annoying in your editor you can put them in .gitignore and either tell vscode to not list anything in the .gitignored list, or explicitly ignore files and folders by default.

Although it could probably be argued now that Atom has a better plugin ecosystem in regards to your comments about customization.

It's better because much of the features many people hope to have is built by the professional team and built-in. You don't have to waste a weekend to check 3 alternatives for every feature you want that may not be as good in the end as they are created by developers whose skill vary greatly.

I got tired of tuning the editor when things work out of the box and even better than properly equipped atom/sublime so I can actually get stuff done.

I hope these discussions include more of other non free apps than free vs free.

Thanks for mentioning this, I wouldn't have noticed otherwise :).

I've seen things like vim have problems with files like that, I think mostly from trying to syntax highlight the visible region.

The kind of files that choke Atom are large data files that there are usually better/different tools for, that have very different requirements from code editing. And that has little to do with the relative huge-ness of your projects.

For example, just a random snip out of a random file:

  let tree = root.render({state: store.getState(), push: store.push})
    let rootNode = createElement(tree)
    let oldRootNode = document.getElementById('root')
    oldRootNode.parentElement.replaceChild(rootNode, oldRootNode)
    store.subscribe(() => {
      let newTree = root.render({state: store.getState(), push: store.push})
        let patches = diff(tree, newTree)
        rootNode = patch(rootNode, patches)
        tree = newTree
    })
    

AltGr worked fine in DOS editors like the Borland Turbo C 1.0 "IDE" from 1987.

That's comical and sad at the same time.