Conversation

Notices

1. Embed this notice
   Pete Keen (zrail@hachyderm.io)'s status on Sunday, 19-Nov-2023 11:34:22 JST Pete Keen

   • Thomas 🔭🕹️

   @thomasfuchs "Houston, we, uh, we have a problem. The displays are all showing [Object object] again."

   • Embed this notice
     Jason Sando (jasonsando@hachyderm.io)'s status on Sunday, 19-Nov-2023 11:35:53 JST Jason Sando

     • Thomas 🔭🕹️

     @thomasfuchs YIKES

     I've built embedded apps that run 24/7 on Chromium and would say it works great 95% of the time. And the 5% it doesn't you will have no chance to figure out where in the 35 MILLION LINES OF EXTRA CODE YOU DIDN"T NEED is the problem.

   • Embed this notice
     ROTOPE~1 :yell: (rotopenguin@mastodon.social)'s status on Sunday, 19-Nov-2023 11:45:04 JST ROTOPE~1 :yell:

     • Thomas 🔭🕹️

     @thomasfuchs that is oversimplifying the situation

     It also has node

   • Embed this notice
     Robbie Coleman :verified: (erraggy@hachyderm.io)'s status on Sunday, 19-Nov-2023 12:12:54 JST Robbie Coleman :verified:

     • Thomas 🔭🕹️

     @thomasfuchs
     Nothing like having Just In Time in between a human and their life support 👍🏻

   • Embed this notice
     Jim Jones (greatbigtable@mastodon.social)'s status on Sunday, 19-Nov-2023 13:00:28 JST Jim Jones

     • Thomas 🔭🕹️

     @thomasfuchs source, please! I would love to read more on this. It's giving off Titan submarine vibes.

   • Embed this notice
     number137 (number137@mastodon.social)'s status on Sunday, 19-Nov-2023 13:24:17 JST number137

     • Thomas 🔭🕹️

     @thomasfuchs slightly off topic, but what are Tesla's main applications based on? Since the risk being fragged by Musk's N1 is probably smaller for me compared to all his killer cars let loose.

   • Embed this notice
     spacer (spacer@hachyderm.io)'s status on Sunday, 19-Nov-2023 14:21:50 JST spacer

     • Thomas 🔭🕹️

     @thomasfuchs I work with that kind of stack, and this terrified me

   • Embed this notice
     Phil Picton ? (philpicton@hachyderm.io)'s status on Sunday, 19-Nov-2023 19:20:14 JST Phil Picton ?

     • Thomas 🔭🕹️

     @thomasfuchs oh shit …. I mean I love JS but people like me shouldn’t be writing mission critical systems that lives depend on 😂😂

   • Embed this notice
     mxk (mxk@hachyderm.io)'s status on Sunday, 19-Nov-2023 20:58:36 JST mxk

     • Thomas 🔭🕹️

     @thomasfuchs are there other gui-toolkits left, than chrome?

   • Embed this notice
     Linh Pham (qlp@linh.social)'s status on Monday, 20-Nov-2023 01:22:48 JST Linh Pham

     • Thomas 🔭🕹️
     • Camilo

     @cam @thomasfuchs LCARS = Lightweight Chromium Automated Rendering Servlet

   • Embed this notice
     Shannon Quinn 🐍 🐘 (magsol@quinnwitz.house)'s status on Monday, 20-Nov-2023 01:30:53 JST Shannon Quinn 🐍 🐘

     • Thomas 🔭🕹️

     @thomasfuchs So if I’m reading this right:

     Between submersibles that dive to bone-crushing depths using Xbox controllers connected to the metal tube using Bluetooth, and now rockets that carry humans into orbit using home compiled Chromium with a JavaScript UI, the message I’m getting is that we trust our most extreme human exploration missions to technology that can best be described as “finicky”.

   • Embed this notice
     Trammell Hudson (th@social.v.st)'s status on Monday, 20-Nov-2023 02:20:50 JST Trammell Hudson

     • leyrer
     • Thomas 🔭🕹️

     @thomasfuchs @leyrer JWST also runs JavaScripts https://jwst.nasa.gov/resources/ISIMmanuscript.pdf

   • Embed this notice
     Jake Hamilton (jakehamilton@hachyderm.io)'s status on Monday, 20-Nov-2023 03:12:23 JST Jake Hamilton

     • Thomas 🔭🕹️

     @thomasfuchs I love JavaScript, I write it for a living. But good lord these important systems should be several orders of magnitude simpler. Absolutely no reason for it to be running chromium with a web app...

   • Embed this notice
     Shahor - 🎸🎙️💻🎮📖 (shahor@hachyderm.io)'s status on Monday, 20-Nov-2023 17:41:15 JST Shahor - 🎸🎙️💻🎮📖

     • Thomas 🔭🕹️

     @thomasfuchs pardon my ignorance maybe, but how is that a problem in itself apart from the shit-on-js banter? What issues could arise that would be specifically tied to this stack that would never exist by default in another?