malerba118

Many developers know that they should use it but don't really understand why.

Moreover many developers simply don't use it because they don't understand what it does for them and trying to adjust size/layout on the <Image /> component is kinda finicky compared to sizing a standard <img /> element with css.

Of course, this quirky layout api is to prevent layout shift but again, many developers don't know this.

Another thing i think many developers don't know is that every next app has a whole hidden image service spun up along side it at an endpoint "/_next/image" that takes the images passed to the <Image /> component and optimizes them by adjusting size, quality, and format.

The <Image /> component even tries to load different sized images based on the size of the device viewing the page and nextjs does this by filling in the srcset attribute for you on the underlying <img /> element.

But all of this is too magical imo. The developer experience when trying to use the <Image /> component is bizarre and the abstractions are leaky. To utilize it well you need to understand the underlying concepts/impl anyway.

<img /> concepts including srcset, sizes, and webp are important to understand as a web developer, especially if you find yourself outside of the context of nextjs.

Binsta does all this stuff for you but more transparently so that you're in control and get to learn about web fundamentals. Binsta also can handle videos which is cool and works outside of the context of nextjs.

You can literally edit and simulate the project while anonymous without any limitations.

And then when you decide to sign up/sign in it will restore the changes you made while you were signed out and you can pick up where you left off.

Is that still not enough?

Also, it's completely free and we have no plans to do anything with your data.

For real, i have no clue how to make it any easier/more enticing for you...

This has been 3 months of painstaking work and you can't even be bothered to try it for free?

Pretty insulting honestly and pretty hard to be an app developer these days as this mentality is becoming quite pervasive.

Indeed it's hard to drag things around in 3d which is why we restrict movement of parts to the XZ plane effectively making it a 2d editor in a 3d viewer.

Hard to use? what do you mean, you drag parts around and then you click a simulate button, that's it. You think configuring a transient analysis with 8 parameters is easier? I'm sure it's easy for people who are already familiar with it. But face it, no high schooler is going to be itching to start an electrical engineering career because they got their hands on a spice simulator.

We envision it going more like this:

"here's an interactive simulation to illustrate my point <embed src="diode-url" />"

instead of:

"to see my point please download these files, download this version of ltspice, and then give it a run"

Aesthetics aside, we're interweaving a wasm port of ngspice with a microcontroller simulator and running realtime simulations all in the browser which i would say is innovative in several ways

Thanks, appreciate the kind words!

It's been challenging to say the least, but that's half the fun.