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.
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.
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.
I'm right there with you. Our condo building is just over 100 years old and has 2 parking spots for 6 units (we're not one of the lucky ones). We'd love to own an EV, but it's just not practical.
This gets to my big complaint with companies like Tesla. They designed an impressive, game changing EV, but their solution ecosystem works best if you have a home with a garage in the suburbs. I don't have a garage to install a Tesla Powerwall that's charged by a Tesla Solar Roof for me to park a Model S.
If Tesla wanted to truly address climate change and get more electric transportation to more people, they'd solve city charging and start designing commuter transit.
It’s little things like this that keep me from using Firefox. Context menus, various micro-interactions, visual design decisions—they all feel so non-native.
NPCs in Half-Life 2 mentioned a number of times that Gordon doesn’t say much and is a “man of few words.” I’m sure this is a nod to his silence in the first game as much as it’s a storytelling device.
I’ve always liked that his character never said anything—feels like Gordon can be anyone. Same goes for the lack of cutscenes that take control of the player’s camera. You always feel like you’re looking from your own POV vs. being pulled out of the immersion.
The other commenters here are right about the importance of text contrast, but there is a consensus in typography that pure white on pure black contributes to eye strain and decreased stamina when reading. This is especially true for people with astigmatism who experience a glowing effect around the letters known as halation.
While there is room here for both personal preference and accessibility needs for a true 21:1 contrast ratio, a better default would be to use a white on a dark gray background. Supporting a dark mode design is a lot harder than just inverting the colors, which this site appears to fall short on.
I just bought from Newegg for the first time in probably a decade and was surprised to see third-party sellers. I went there specifically because I remembered them being reputable, but came away with a different feeling entirely.
I have an AeroPress and like it a lot, but I also love making a pour over every morning precisely for the process (and taste). Bringing the water to the right temperature, weighing and grinding the beans, blooming, managing the flow rate… the ritual is very calming.
Design version control has actually been a big win for our design team and the handoff to engineering. We use Sketch + Abstract to do this. WIP projects live in separate branches that we can share out to get feedback.
Once the design is locked in for that milestone, we push to Master and hand that off to engineering where they can inspect the mocks right in Abstract.
We don’t mind using multiple tools if they’re all really good at what they do. Our core toolkit includes Sketch, Abstract, and Marvel. Sketch Cloud has supported prototyping and commenting for a while now, but Marvel is a bit more robust.
Obviously each team has their own needs, but this has worked for us.