Makes me think of the Star Trek episode “A Taste of Armageddon” where a computer simulates the outcome of a war and its causalities, and then those civilizations actually go to murder that number of people in real life.
As it’s been noted, these bots don’t comprehend what they’re saying. But I thought ChatGPT saying ”How can I assist you today?” and “I'd be happy to help with any questions or information you may need.” in the beginning of the conversation really reinforced this. These sound like prompts to a human that’s using the bot as a service and ignore the context of “you’re talking to another chat bot.” You wouldn’t say that if you’re meeting/learning about someone.
Indeed. That's how my brain reacts to it - it keeps nagging me that thing is not properly balanced and will tear everything apart when rotating, like a washing machine does when you throw a brick inside it.
Yeah, I didn't like that either, so I just quit it and didn't try it again for a couple of weeks.
It has some nice UI/UX features. For power users of Firefox or Chrome, many of the features can be replicated by various plugins, etc. What's nice about Arc is that it's all integrated and built-in.
For example, I had different user profiles in Firefox (work, personal, etc.) so the cookies and search history were separate and also tabs on the side instead of the top.
Lots of these features appear in different browsers; but arguably, Arc is one of the first to include all of them be default in an accessible UI. I think Vivaldi has many of the same features but it has so many features that it can be a little overwhelming. Arc's features are a lot more accessible.
I think a good parallel of this is Webflow, which I find to be an incredibly powerful tool and gives design teams a lot of freedom to build and deploy their designs, however it’s incredibly cumbersome if you’re using it to mock up options and explore iterations. That work still happens in Sketch for our team, and when it’s approved that same team brings it into Webflow and “does it for real.”
I expect exporting from Sketch/Figma into React components would be cumbersome in this same way.
If I may pose another example from my days of industrial design, Rhino is a great tool for rapidly iterating designs and building CAD for renderings, however when your design is approved you really need to rebuild it in Solidworks for it to be made.
The real solution here is for companies to adopt a Design Ops/Design Systems Manager that can design and code in the front end. This would remove burden from the engineering team so they don’t have to worry about doing tiny design tweaks, etc.
Judging by partlysean’s response, “our industrial design team would use Rhino and then hand it off to the mechanical engineers to rebuild it in Solidworks.” I would think Rhino lacks the entire Computer Aided Engineering (CAE) capabilities that Solidworks has.
The Wikipedia page for Rhino says it’s a CAD tool, but Solidworks says CAD and CAE. So Rhino has a subset of Solidworks’ capabilities.
Engineers use CAE to help with determining how the materials, dimensions, and other engineering choices will be have under loads. So these have some similarities in that Solidworks can also do 3D modeling, which is used as an input to performing CAE.
It’s not necessarily a feature comparison, but I’ve found it much easier to just “try” things in Rhino. Solidworks is best when you already have a clear idea of what you’re building. In that way, our industrial design team would use Rhino and then hand it off to the mechanical engineers to rebuild it in Solidworks.