mariusasdf

I'm a designer, and consider HTML/CSS/JS to be as good a design tool as any, perhaps even better than any CAD app. I use Sketch, Illustrator and Photoshop as needed for icons, illustrations and photos.

Also, code is a really handy tool for design (generation/automation).

I believe in using the right tool for whatever "material" I'm working with. For (responsive) web apps, that tool is HTML/CSS/JS.

Most designer's have their own preferences. I don't believe any current or future wysiwyg app can meet all needs.

It's possible using nested elements and transform: translate(0, -100%) on the inner element. It's elegant enough for CSS, I suppose. (I'd make an example if I wasn't on my mobile atm.)

Read the question.

eslint is great. Through plugins it supports ES6, jsx, etc. Also, automatic code fixing.

Ok, got you. If you use the "Create New" button in the top right corner, you get the option to create a "JS" project.

The project template comes with jQuery pre-installed. However, it can easily be removed.

I guess the people behind Runnable assumes that it's more convenient to have to remove jQuery than having to add it for each new JS project, and personally I agree with that assumption.

Hope this helps!

This reasoning seems fundamentally confused, so I feel like clarifying some concepts:

On Runnable you can create basic client-side JavaScript files to be run in the browser (without jQuery) and do window and DOM manipulations.

Node.js isn't a framework for the browser (like jQuery), but a server application platform (with a bunch of objects and functions).

"Pure js" doesn't exist as an environment. It runs within a parent environment (e.g. a browser or a server) and manipulates the global objects in that environment.

JavaScript is just a language specification, and can be implemented in any environment. (For instance, it's implemented in Adobe Illustrator.)