Back on my rotary broaching nonsense this evening, made a new broach. Mild nose dish (about 4°), through hole for pressure relief when broaching an undersize hole.
Man now I want a Rack Robotics EDM! Drilling 30mm with a 1/16" drill bit without breaking a bit and without wandering was a long task and tested my patience.
I haven't bought a toaster oven just for the shop for tempering, so my long-suffering family is putting up with a 2.5 hour 200°C tempering cycle in the kitchen toaster oven. ❤️
@mcdanlj That bites. I hadn't realized they did that. I've had good luck with the two I've had, but I'm definitely not loyal to them, should anything like that happen to me.
Big #FreeCAD news! Feature freeze for FreeCAD 1.0 is now on. If you have held back from trying development builds, please consider running weekly development builds starting this week and filing clear bug reports. The may give you ideas what to expect and look for, but also lots of testing has been focused on explicitly new behavior, so just using the new version for general use (of course saving early and often!) is likely to uncover a few stray problems here and there that would be great to fix before the big 1.0. 😁
I'm not one of the FreeCAD developers (my sole code contribution so far has been fixing a tooltip typo, and I've contributed to a couple Workbench extensions), but if you, like me, were previously scared off by the "no bug reports not first discussed in the forum" rule, that rule is gone. FreeCAD now take normal GitHub bug reports and even have someone dedicated to triage. Bug reporting for FreeCAD is now a good experience!
500 Internal Server Error from https://apnews-prod.appspot.com/ trying to load an article about this afternoon's guilty verdict. Interesting that they are using appspot URLs in prod.
It's not just the weird contrived queries getting worse-than-useless artificial "intelligence" summaries. One of my kids just did a google search for something they actually wanted to find, and got AI nonsense. This "oh it's only contrived queries" line from Google doesn't convince me. There's a lot of ambiguity in normal speech, and fine judgment of ambiguity is not the strong suit of an LLM.
@xarvos@kaia Well, the first paragraph is from immediately before "[do]lorem ipsum" in Cicero's De finibus dolorum et malorum from which lorem ipsum was borrowed, and the second is a later sentence from which some of the garbage text of lorem ipsum was borrowed. So you could say it's not exactly lorem ipsum. 😀 But despite the brilliant loose translation here provided, I do suspect that in practice it was intended as placeholder text.
Another similar article. The chlorine gas one is new to me, as is the suggestion of jumping off the golden gate bridge in response to someone saying they are depressed.
An exciting milestone for upstream #FreeCAD integration of the TNP mitigations designed by Realthunder and debuted in his LinkStage3 fork: New bug reports against upstream reproduce current LinkStage3 topological naming behavior.
@Flux Most of what I've done lately has been trying to make useful bug reports. Though I did end up contributing to the Lattice2 workbench recently, which was kind of ironic because I've used it exactly once and so really don't know how to exercise it. I'm still at the "carefully following a tutorial" stage; I haven't graduated to "understand it well enough to use it fluently" at this point.
But the FreeCAD contribution process was easy enough. I put up a PR with the typo fix, and a few days later it was merged, after tests passed. Also, in before the 1.0 string freeze for translation... Well, string slush? 😀 Anyway, can't really think of anything that would have made the process any easier.
I'm at a crossroads with 4.0 and future development. For a long while, I've been considering a complete re-write. The only way I think I would consider that is if other devs signed on. Otherwise, there are various paths forward with refactoring. And/or splitting out CAM from the rest of the package to provide more freedom of UI expression.
...
there are so many things I would do differently looking back. JS has evolved, browsers have evolved, tool chains have evolved. I would like the final product to be able to be served statically without a server and retaining the options for cloud connected features (as long as they're not necessary for normal functions). I would focus on making a CLI / library for everything first instead of building the UI in lock step. nodejs was not a thing when this project started. I'd like to offload more code into WASM from the start, etc.
What's the intersection of the #javascript#cad and #maker communities here? Anyone interested in both high-performance JavaScript and CAD/CAM want to join in?
In order to help someone build an "open source" project that was built with windows-only proprietary tools, I need to install Windows on a computer at least for a while. I think I spent at least an hour trying to create bootable media on someone else's windows computer before finding a comment buried somewhere that the windows media tool just silently fails to work with sandisk thumbdrives, with no information shown.
Compare that to Linux iso images that can just be written to a USB drive and still work (thanks to H. Peter Anvin's work many years ago) and work just fine on those same sandisk drives.
Well, "windows-only" wasn't true, I guess there is a mac version too. This was f360 for a custom keyboard build published only as f3z files. F360 kept failing its license check as I tried all sorts of things.
Turns out that the windows install didn't respect DHCP and Windows time was way off. Once I fixed the clock, I was able to start f360 and get the STEP, sch, ipc, gerbers, and drill files created. Progress unlocked. Not without f360 complaining about me having intel graphics, though. I couldn't find a way to export a PDF of a schematic, either. I'm sure it's buried somewhere, but the alternative was to just capture a screenshot...