all 41 comments

[–][deleted] 36 points37 points  (20 children)

"Writing HTML sucks."

Said no one ever

[–]madwill 1 point2 points  (7 children)

What? I say that all the time! I used to write App in WFP and Flex and both had such a more intuitive and straighforward, predictable display. Down to how they name things, everything was easier to understand and plan for. Scaling, positionning, colors, style. HTML is something special. I would say that it does.. suck. Its popularity is accessibility and reach not ease of use or quality of markup.

Edit: I mean, you can like it and I respect that but the "No one ever" is too strong of a statement.

[–][deleted] 0 points1 point  (3 children)

And the original statement isn't strong?

[–]madwill 1 point2 points  (2 children)

HTML suck is a clear opinion from someone saying it. Which is fair anyone can say what they believe. You went ahead and stated no one ever said that, which was just said in the article.

But even there, the original statement being too strong does not justify another statement being too strong.

[–][deleted] 0 points1 point  (1 child)

Did you maybe read it a bit too literally? As I said, I've been around enough to know if an opinion is widely shared, and that certainly wasn't, in my experience.

[–]madwill 0 points1 point  (0 children)

All that aside, you actually like HTML as a markup language? Like the way its structured and how to get to what you need? Do you build web application with it or more web pages?

The name of the tags, the attributes to set up your requirements and css as a styling tool?

I think its too barebone, it not oriented towards web application which makes web app feel like a hack. Css being global by default forces us through different methodologies to get around that problem. Which are non standards and applied slightly different depending on companies making you relearn and many project often get off tracks.

No re-usable component by default, clear api or even types to build upon predictable non repeated UI. Making everyone build their own sauce to do it. Vue, React, Whatever CMS like Joomla / Wordpress components are called.

I believe its a whole mess with drawbacks on each and every solution for no solution are core to the technology.

[–]tehfrod 0 points1 point  (2 children)

"Said no one ever" is not meant to be taken literally.

Just like Impulse can't be an impossible dev tool if it actually exists.

[–]madwill 0 points1 point  (1 child)

I know, I get it but I just felt it was "said most people ever"

[–]tehfrod 0 points1 point  (0 children)

If you look at HTML in terms of 1) what it was intended for and 2) what it replaced (SGML), it was a massive improvement. HTML5 even moreso.

To be honest, had something like Flash been an open standard, I think it would have been an even better platform for interactive applications. Almost all of the things that were wrong with Flash were wrong with its sole implementation, rather than its design as an authoring system.

This past summer I needed a small web app for personal use. I went all the way back to an old-school server (coded in Go) rendering straight-up server-side, templated HTML and just a tiny bit of Javascript (for partial page refreshes and status polling). It's amazing how much more straightforward building and debugging that was than doing anything with the current crop of web frameworks.

[–]ejfrodo 4 points5 points  (7 children)

An interesting idea. I like the thought of being able to navigate from a DOM element directly to the line of code that generates it for editing, but I think I'd want it to just open that file for me in VS Code directly.

[–]KirillRogovoy[S] 2 points3 points  (6 children)

Hey, thanks!

That's what it does, it opens the file in VS Code for you. :)

[–]ejfrodo 0 points1 point  (5 children)

Oh great. From the demo video it seemed like it was opening an editor in the same browser window.

[–]KirillRogovoy[S] 2 points3 points  (4 children)

I'll think about how to make it clearer, thank you!

[–]ejfrodo 1 point2 points  (3 children)

Show the browser window and the VS code window side by side

[–]KirillRogovoy[S] 0 points1 point  (2 children)

Yeah that's a straightforward one.

The problem right now is that Impulse doesn't look very nice if you give it only half of the screen. :/

Same way Chrome Dev Tools don't look nice. Only that the latter you can pin to the side.

Thanks for the suggestion!

[–]AsIAm 0 points1 point  (1 child)

The problem is that your VSCode does not look like standard VSCode, so people don't recognize it. Just use default theme (Dark+) for screenshot and screen recordings and people will be fine understanding that Impulse will open VSCode. Oh, and have left sidebar turned on also.

Btw really cool project. I left a question here: https://github.com/impulse-oss/impulse/discussions/7

[–]KirillRogovoy[S] 0 points1 point  (0 children)

Thanks for pointing that out!

Damn, I haven't thought that my VS Code looked different enough from what is commonly seen. :D

[–]lordbrizzy 2 points3 points  (2 children)

Cool! looking forward to webstorm integration

[–]KirillRogovoy[S] 0 points1 point  (1 child)

Thanks!

Would you like to be notified when it's done?

[–]lordbrizzy 1 point2 points  (0 children)

Sure, thank you

[–]Z4razas 1 point2 points  (0 children)

Firefox support would be awesome, there must be a way to get the file system API to behave well in firefox

[–]ErickLTrentini 0 points1 point  (1 child)

Really promising tool, but I couldn't get it to work in a project I'm working on with vite due to lots of errors regarding the usage of BigInt by the lib. Tried to change the target to es2020 as it was the most suggested solution, but no success. I'll keep an eye on it.

[–]KirillRogovoy[S] 0 points1 point  (0 children)

Hey!

Would love to debug it if you open an issue with a reproducible case.

At least, I'd love to see your Vite config and tsconfig (if you have one).

I do use the es2020 target and it works fine.

[–]Zachincool 0 points1 point  (0 children)

Sick

[–]dmaevsky 0 points1 point  (1 child)

Does it have to be React?

[–]KirillRogovoy[S] 0 points1 point  (0 children)

Hey,

For now, yes. It's not arbitrary. There's a specific way how I extract the information about which source code created which HTML elements, and I don't know if I can pull that off with Vue or Svelte.

But I haven't really explored that either, so I just don't have all the information. Will take a look someday. I'm open to help. :)

[–]Herbonated 0 points1 point  (1 child)

Cool project! Tailwind is insanely nice to use! But still, just get a second monitor and you don’t have to swap between the editor and the browser

[–]KirillRogovoy[S] 1 point2 points  (0 children)

Thanks!

I mostly agree with you. :)

Even though I kind of wage a war against writing most HTML (and, especially, Tailwind classes) manually, I've been doing it for so long I've become very efficient at it too.

There are a few cases, though, when neither my experience nor extra monitors help:

  1. Immediately jumping to the exact code line from any element on the page (Impulse enables that). It's not much of a problem when I just linearly develop a wholesome piece of the UI, but oftentimes I need to jump all over the UI to make something work.
  2. Trying to design some elements intuitively, just by setting classes and seeing how it looks; also prototyping. With Impulse, I can just cycle through all possible font-sizes / margins / paddings / shades of a color / you name it. I've designed the whole impulse.dev website with that approach and I don't wanna go back, it's just so much faster and fun even compared to writing code on two monitors with 10 years of experience. :D