flipflipper

Im not a LLM / vibe code hater (in fact a big user) but I wonder are these people just not looking for an existing solution or do they want their own bespoke version for access to some internals and to (kind of?) learn the high level of what goes into these projects.

If its the former, people are wasting their own time, money and energy when spending a similar amount of time searching vs prompting might yield better results for their use case. If its the latter, unless there is a killer feature, which I dont see in the github repo, why not point people to use the actively maintained project instead of the one the vibe coder is going to let die on the vine once they get bored. Its fracturing the space, for what gain? (no pun intended)

Also how much of this code is the LLM lifting from Stellarium either indirectly in the training data or actively searching for it to reference the code in its context?

https://github.com/Stellarium/stellarium

https://stellarium-web.org/

I brainfarted a bit and mixed up my attempts with making LTSPICE asc schematics (which are the text representations of the GUI sch, with wires) with the normal node based SPICE syntax. I just tried this specifically asking for spice to run with ngspice to run in a CLI. Seemed to run great! Going to play around with this for a bit now…

Try having it output the circuit in SPICE. It actually works surprisingly well and does a good job picking out components values for parts and can describe the connectivity well. It falls apart when it writes the SPICE (professionally, there isn’t really one well accepted version)and making the wires to connect your components, like you say missing the minds eye. But I can imagine adding a ton spice schematics with detailed descriptions with maybe an LLM optimized SPICE syntax… it’ll be designing and simulating circuits in no time.

Ollama + open web-ui in a container

https://ollama.com/

https://github.com/open-webui/open-webui

Another reason to not use a DSLR is that many (all?) have timeouts (<30min) in their video mode due to some import tax reason, even when hooked up to a computer. Atleast this is what I found when I tried a canon DSLR with canons webcam software.

Timing is inconsistent and the contacts will stick and weld together after a bit of regular use. Solid state is better if its designed well. Checkout the kWeld. https://www.keenlab.de/index.php/product/kweld-complete-kit/

There were couple demo sats launched a few months ago. One with the tether, one without. https://www.dragracersat.com/

NYC did legalize e-bikes at the start of all this, a step in the right direction.

>Low-orbit satellites spend half their day in darkness too. To hit a receiver on the night side of earth a satellite would have to be at a very high orbit, reducing beam efficiency and increasing launch costs.

Pedantic, but for LEO there are dawn-dusk SSO orbits that ride the terminator [1] so they get continuous sunlight, you could power some peoples evenings depending on how far the grid spans into the dark side. Not a solution for getting power at 2am though.

Might be able to compete if the cost if a rectenna is cheaper/kwh than solar panels (and free as sunlight). Then you can use your same battery solution for night time.

[1]: https://en.wikipedia.org/wiki/Sun-synchronous_orbit

I heard, anecdotally, that non-approved masks have the possibility of aerosolizing a cough/sneeze more

The exact number wasn't really the point + elon has a history of releasing high performance spec's before the actual technology is ready. Maybe they have special tires in the works, but the rubber that's on the market today can't do that

Yep, and why every supercar's 0-60 time is limited to about ~2.6s these days. Also why tesla is claiming to be able to achieve <2.6s only with the cold gas thruster "SpaceX" package, they're no longer solely relying on the tire traction.

>However, the power supply uses a more complicated design to provide electrical isolation between the spacecraft and the clock. I'm not sure, though, why isolation was necessary.

I believe this is to maintain a single point ground, usually the chassis on a spacecraft. The chassis of the clock is probably connected to the isolated side's ground, which avoids ground loops when the clock is integrated into the S/C.

More detail on grounding and isolation in S/C is covered here: https://standards.nasa.gov/standard/nasa/nasa-hdbk-4001

I believe that most BEVs are limited by the power the battery can output safely, not by the motor's individual power rating.

I could imagine an EV with a 400hp battery + a 400hp motor at each wheel allowing for 100% of the power to be used at one wheel, where in 4x4 mode each motor would be seeing 25% at max power. I'm not sure exactly how much of a premium you would pay for that but motors are cheap compared to batteries.