sjm-yc-acct

I first read the book nearly 40 years ago when I was 12. I recently found this radio adaptation narrated by the author himself.

Battery failures can also be caused by manufacturing/design defects in the cells (as in the Boeing batteries) or malfunctioning components of the active cooling system in the Model 3 like fans/pumps/coolant (like the Tesla club owner).

Having a coolant temperature gauge in front of you could show you a trending problem, before the car announces to you that it is shutting down as you attempt to merge into 75 MPH traffic.

Wait, the car doesn't tell you if the battery is overheating? That doesn't happen with Li-ion batteries? I heard it does in cars and airplanes and laptops...

https://en.wikipedia.org/wiki/Boeing_787_Dreamliner_battery_...

https://teslamotorsclub.com/tmc/threads/overheating.109238/

I have spent a little time flying in the left seat and right seat of real single engine aircraft (although I have never been in any Tesla.) I would say it's comparable, but a matter of degree. It is true that there is a much higher workload on the a/c pilot, especially on taxiing, takeoff, and landing. Pilots rely completely on their instruments during IFR.

I have the feeling safety would be an issue if I was fumbling around for the defroster menu item in the mountains rather than having it at hand when my windshield was rapidly fogging up--in any vehicle. (Ask me about my trip to Laramie, WY last week.) Driving off a cliff would be a bad day, too. What about the battery overheating indicator? I would rather that be in front of me too in an electric car. A chime could help in this situation, but what if people where honking at you while seeing smoke coming from your vehicle?

BTW, did you notice the redundant mechanical instrument cluster in the Cessna Mustang (located above the display with the map)--another design element that increases safety if you have a primary display failure...

Thanks, this is an interesting insight. Still, looking at aircraft with flat screen "glass cockpits" without HUD, they tend to follow the Model S pattern:

https://en.wikipedia.org/wiki/Cessna_Citation_Mustang#/media...

Critical displays and controls in front of the pilot, other controls readily accessible by feel/muscle memory. Aircraft designers tend to be very conservative due to safety, but cars involve safety considerations too--which is why I think car designers do tend to stick to standard configurations.

I would work on it for money. My company's website is listed on my HN profile--there is contact info on the website.

I tried Portable Hemlock from Quicklisp, and IIRC it would not install from the repos.

On Clozure, the IDE with Hemlock only runs on OS X--I use Linux.

The one in CMUCL might work, but I haven't tried it because they only have 32 bit support for x86.

I wasn't trying to be dismissive--I would really like to run Emacs on CL!

There have been some efforts like this (etc.) for Emacs on CL:

https://common-lisp.net/project/phemlock/

I have never been able to get one to work, though.

MIT Scheme also has an Emacs 18 compatible editor called edwin written in Scheme.

In all seriousness, and hopefully more constructively--there really is a lot to like about the Tesla Model 3. We have been looking for a new car for a while, and we did consider the Model 3. I just wish they had retained some more of the instrumentation/controls like the speedometer in front of the driver.

I've been thinking about this more tonight and in a way, the clean minimalistic interior design of the Model 3 is more like the Protege and the "old" Camry than other modern cars. Obviously, the Tesla also has the advantage over these cars of not having a tail-pipe.

Here's a related business idea:

OEM and aftermarket activated charcoal cabin filters (not the paper kind) to remove diesel and other exhaust fumes.

I think some luxury cars have them (Porsche?) but I think the rest of us should as well. They might sell like hotcakes too.

That's their modern one, Mazda 3 (oddly enough).

I was kind of joking with my original comment, because this was an economy car--but it actually is a nice design:

http://gtcarlot.com/data/Mazda/Protege/1999/12552040/Dashboa...

I would probably like this one better:

https://www.stoddard.com/media/catalog/category/IMG_1365.jpg

Early 911 interior.

Have they driven a Protege? :)

I wish they would hire the interior controls engineer that worked on the 8th gen. Mazda Protege. Simple, elegant, and ergonomic.

That giant iPhone in the middle of the Tesla 3 puts a crick in my neck just from looking at the pictures.

SGI's 3D APIs, OpenGL and Open Inventor, were sublimely innovative. Some of us are even trying to keep Open Inventor alive:

https://bitbucket.org/Coin3D/coin/wiki/Home

https://common-lisp.net/project/clive

I wish more tech businesses were about the greatest common factor, and not the least common denominator. If I could find a place like SGI to work, I would camp on their doorstep until they let me in.

You're right--communicating about the intent of a patch is a good idea, especially if that intent is outside of normal expectations.

In a similar vein, I recently learned about prefixing a pull request on Github/Gitlab with "[WIP]", or a "work in progress", to suggest that the proposed changes are for informational purposes or not yet complete.

FreeCAD uses Open CASCADE, which is is a free software (LGPL) CAD kernel. Open CASCADE has a comprehensive modeling API which uses B-rep. For scripting, FreeCAD has a Python interface. CadQuery is another Python tool (DSL) which is a plug-in for FreeCAD. FreeCAD itself already has some constraint functionality.

Libfive is layered and can be used without Studio to generate models with its extensible Guile Scheme binding. It uses F-rep modeling.

Correct me if I'm wrong, but it should be possible today to add a programmatic (non-GUI) constraint solver to either FreeCAD or Libfive.

Matt Keeter's Libfive is a very promising project. Our company has written a Common Lisp binding:

https://common-lisp.net/project/tovero/

and it would be useful to have a constraint solver. We are looking at ways of applying Libfive to mechanical design.

I have also developed a prototype of a Libfive viewer--written in Guile Scheme for use with a REPL/Emacs:

https://github.com/sjm-tl-gh/inspekt3d

Coding 3D models in Lisp has been an amazing experience (even without a constraint solver).

Libfive also has a FFI-friendly C API, so other language bindings (e.g. Python) are very feasible.

One feature Libfive is currently missing is a general sweep of a shape along a curve--which seems to not be so straight forward with F-rep modeling.