Another advantage of OpenSCAD (if you can call it that) is that LLMs seem to be able to work with it pretty well. A few days ago I asked chatgpt to make me a box for storing batteries, and it came out perfect on first try without any modification. It also made an okay-ish looking 3D pelican after some back-and-forth.
The problem with openSCAD is that you cannot modify it easily. I had made a complex geometry several years ago in openSCAD and I have been waiting for a model that can actually convert it into a python script that generates freecad parametric sketches that recreate it in an editable way. All frontier models fail at this, some more spectacularly than others (gemini never spent 40 minutes / $4 trying and failing, but opus 4.6 did).
OpenSCAD is ideal for making models that can be modified! You have to program your models with the mindset of parametric CAD though, if I was making a battery case I would start by defining variables for battery length, diameter and count and work from there.
Your ball looks well parametrized to me, what kind of editing are you missing from it? Unless you want to change the shape of the locking mechanism altogether, which I think would be a chore in any format.
there are a lot of "do what I mean" type papercuts in openscad. BOSL2 is a library that, for me at least, takes away enough of them to make a rewarding experience. still find myself brute forcing which axis to translate or rotate things the way i want.
concur otherwise that openscad is parameter friendly. the lightbulb moment for me was when i finally grasped its functional grammar and leaned into it, esp recursion instead of algebraic solutions. that should probably be the subject of a tutorial or several.
Yeah the lock is what needs iterating. It was always marginal and took several rounds of prototyping to even get to a printable state. I'd like to experiment with something like a keyed screw.
The issue with this scad file is that I built the geometry up with no functions. I tried and failed to get them working so I just pushed through, so now it is mind melting to try to refactor it. I'm hoping to one day melt a mechanical mind to get it done. Until then, it's a fun challenge prompt for these models.
It doesn't have to go away, it just needs to be better regulated. I could also increase my productivity by taking Adderall, if that was my end goal. But most people don't, since there are other factors to take into consideration, like becoming unable to function without it, or long-term cognitive decline...
The problem is, you won’t necessarily know which 20% it did wrong until it’s too late. They will happily solve advanced math problems and tell you to put glue on your pizza with the same level of confidence.
What counts as "large"? I'm pretty sure at some point in my life I'd opened the entirety of Moby Dick in Notepad. Unless you want to look for text in a binary file (which Notepad definitely isn't for) I doubt you'll run into that problem too often.
Also, I hope the irony of you citing Notepad++ [1] as what Notepad should aim to be isn't lost on you. My point being, these kinds of vulnerabilities shouldn't exist in a fucking text editor.
Remote into a machine that you're not allowed to copy data out of. You only have the utilities baked into Windows and whatever the validated CI/CD process put there. You need to open a log file that has ballooned to at least several hundred megabytes, maybe more.
Moby Dick is about 1MB of text. That's really not much compared to a lot of log files on pretty hot servers.
I do agree though, if we're going to be complaining about how a text editor could have security issues and pointing to Notepad++ as an example otherwise, its had its own share of notable vulnerabilities even before this update hijacking. CVE-2017-8803 had a code execution vulnerability on just opening a malicious file, this at least requires you to click the rendered link in a markdown file.
Oh right, generated files exist. Though logging systems usually have a rollover file size you can configure, should this happen to you in real life.
Honestly I'm okay with having to resort to power tools for these edge cases. Notepad is more for the average user who is less likely to run into 100 MB text files and more likely to run into a 2 kB text file someone shared on Discord.
> Notepad is more for the average user who is less likely to run into 100 MB text files and more likely to run into a 2 kB text file someone shared on Discord.
There's no reason it shouldn't handle both use cases.
> Though logging systems usually have a rollover file size you can configure, should this happen to you in real life
I get what you're saying. But if things were done right I probably wouldn't have to be remoting into this box to hunt for a log file that wasn't properly being shipped to some other centralized logging platform.
I know about the vulnerabilities in notepad++, however I was referring to the feature set.
Regarding large, I am referring to log files for example. I think the issue was lack of use of memory mapped files, which meant the entire file was loaded to RAM always, often giving the frozen window experience
There is a difference between a bug you laugh at and walk away and a bug a scammer laughs at as he walks away with your money.
When I open something in Notepad, I don't expect it to be a possible attack vector for installing ransomware on my machine. I expect it to be text. It being displayed incorrectly is supposed to be the worst thing that could happen. There should be no reason to make Notepad capable of recognizing links, let alone opening them. Save that crap for VS Code or some other app I already know not to trust.
Not knowing everything never "enables" you to do anything. Knowing how something works is always better than not knowing, assuming you want to use it or make changes to it.
Abstraction isn't ignorance, it's the very conscious choice not to depend on implementation details. Being ignorant to those details doesn't give you any superpowers, abstraction itself does. It doesn't work because you don't know everything, it works despite that. Not knowing everything is still a bad thing, we just find ways to make it less bad.
Set up a Github action to send out the secret if you don't commit to a repo every x days? You could even combine it with secret sharing to make sure your friends can't access it unless you're really in trouble.
reply