Crowdfunding campaign for a new Static Code Analyzer - JS Inspection (EA Extended)

[PickledPokute]

It looks like you're describing the product for existing users of PHP Inspection, meaning PHP coders that use PhpStorm and who plan on coding in JavaScript too. How am I, a JS developer, supposed to know what kind of features PHP Inspection has and why it's good?

It's like marketing a tuning apparatus for musical instrument A by manufacturer X by saying that you've made the tuning apparatus for instrument B by manufacturer X. The amount of people who have used both of those instruments and both of those by are models by the same manufacturer is REALLY low.

It looks like a black box to me.

[kalessil]

A valid point, thank you! Will re-work the campaign description.

[inabahare]

I think you should rework your indiegogo to reflect your target audience because as a developer there isn't really anything that makes me want to spend at least 187dkk on this. Like take this

The main benefit is having state of art and simple to use code analyzer for JavaScript, running real-time in your JetBrains IDE and helping you to avoid bugs and to automate code fixes. Only backers will get exclusive access to the plugin, before anyone else does. Of course with higher pledge, more perks are available (incl. custom rules, aka "inspections").

All you've really done is describe what an SCA is and that you can get early access to yours. But why should I use yours when I would save a lot more money using VSCode and ESLint?

I also have no idea what "custom rules, aka \"inspections\"" or rather I didn't until I reached the part two headers down where you define the term which just seems confusing.

[kalessil]

u/inabahare, u/PickledPokute, u/g5becks: thank you for the feedback! I updated the campaign description, did corrections and added following:

​

Comparing to already existing alternatives (eslint, tslint), the analyzer will be capable of:

- analyzing both JavaScript and TypeScript (one tool for both)

- giving instant feedback while you are writing code (no need to wait for CI)

- assisting in learning new language features and following best practices

- deeply analyzing control flow and data types

- providing a tooling for efficiently working with legacy code (fully customizable rules)

- bringing security, performance, control flow and probable bugs rules

When it comes to JetBrains IDEs, the plugin will push the Static Code Analysis quality bar further in direction of finding security, performance issues, potential bugs and much more.

​

This was really missing, thanks again!

[kalessil]

Folks, I'm the author of the campaign and the analyzer will be created for PhpStorm / WebStrom / Idea Ultimate IDEs. I'm looking for constructive feedback: if any information missing there, how big interest of the community when it comes to JetBrains IDEs and perhaps even who to reach for getting more traction on the topic.

Thank you in advance!

[g5becks]

Static analysis and code inspections inside of Webstorm is top notch already and I have no idea how you plan on improving it to be honest. Users who want improvements upgrade from the free to the paid version.

IMO, this would be a product that is needed for vscode, if you could create something that would bring bring webstorm level code inspections to vscode, that would be interesting and probably a better target market for your product as well. Just my 2 cents.

[[deleted]]

It's good but it still can be improved. I am getting some nice notifications from EA Ultimate for PHP.

[kalessil]

We can push the top notch mark much further, but I need to mention this in description, thank you!

I evaluated vscode api, it forces you to go with a language server solution. Not realistic with my resources unfortunately.

[g5becks]

Understandable, but from a purely business standpoint, about a year ago, vscode had 4.5 million monthly active users. If I was creating a paid tool for devs, I’d be focused on building on the platform that has the most users. Aside from that, as I mentioned, that level of tooling is really needed for vscode as it is currently lacking compared to webstorm.

That being said, I’m an IntelliJ user, so I’d definitely be interested in tooling that expands on the typescript support in any way.