I have been developing for 20 years, handy w/ vi, eclipse, inteliJ, sublime...
But the new king is Atom. One reason is it easily plugs in the modern 'transpilers' / generators. Ex: jade. inteliJ is pita for jade.
i urge you to try the free atom.
But the new king is Atom. One reason is it easily plugs in the modern 'transpilers' / generators. Ex: jade. inteliJ is pita for jade.
i urge you to try the free atom.
I suggest an high end i7 for all developers, especially web dev/designers.
I suggest that too; unfortunately the company I work for gives us cheaper machines with AMDs to cut costs.
Since I am not going to follow the upcoming conversation, I sum it up in advance:
* [Insert here the usual "yes, but nowadays everyone has got X Go RAM, and a CPU scoring YYY WhateverMark." ]
* That's not true by any means, in real life most non-geek people do not have these or want to buy them (even if "every computer sold nowadays comes with it" was true, which it isn't either) just to do everything that they could already do 10 years ago, but in fuchsia now; and even people with an up-to-date machine may wish to run several different programs or several instances of the same application in these days without eating all their RAM, maxing their CPU or draining their battery.
Maybe pay developers more to the point where PC is cheaper.
This is simply not true. Explain to me why you need an i7 as a dev but the consumers using your product don't need an i7 to run the exact same thing.
> Explain to me why you need an i7 as a dev but the consumers using your product don't need an i7 to run the exact same thing.
Because dev tools take resources that the product doesn't take on the end user machine while running in delivered form.
Whether that's compile/build tools, whether that's running server and client simultaneously on a dev machine, whether that's running code in debug form under debugger rather than "naked" in delivered form, or whether that's just the power to run the code itself alongside an IDE, there's all kinds of reasons why a dev machine needs more than is required for an end user of the code being developed.
Similar, overlapping, but not exactly identical concerns apply to "designers" as opposed to "developers".
Web developers need to batch resize images to make them smaller.
Most developers are expensive and should not be paid to wait. But there are exceptions, some developers are not expensive.
You can add them for things like syntax highlighting, but they can do so much more, and in many cases can border on "IDE-level" features.
Things like autocomplete, code linting, smart refactor tools, find reference/definition, test runners, debuggers, git integration, and a ton more. (one that I use a lot adds a terminal in the browser so I can run some command line tools without having to tab away to something else)
They are pretty limitless. If it can be rendered via HTML/css/js, it can be a plugin.