One of the big changes in my opinion is the addition of a "Smart Dimension" tool where the system interprets and previews the constraint that you want to apply instead of requiring you to pick the specific constraint ahead of time(almost identical to SOLIDWORKS), and the ability to add constraints such as length while drawing out shapes (like Autodesk Inventor, probably also Fusion but I haven't used that). It makes the sketcher workflow more like other CAD programs and requires a little less manual work with constraints.

Hmm, that actually sounds like a bug. I haven't seen that on my end (once I set the locations of options in my toolbars they stay there, even after restarts). You may want to report that on their issue tracker. Sorry that you're having a rough experience!

Last I tried it, there was no fix. Their latest update on the website says:

The work on the toponaming problem is an ongoing project, and we are very grateful to the FreeCAD community for contributing a lot to that effort. But it’s not complete yet, there will be much more to say when it’s largely done. So let’s focus on the other three.

So I take it they haven't implemented a fix. They previously said they were going to work with the FreeCAD team on mainlining a toponaming fix, using realthunder's work as a proof of concept, but said fix has not landed in mainline FreeCAD yet. I believe that's the major feature they're looking to implement for FreeCAD 1.0.

Definitely excited for Ondsel though! Hopefully that fix can be integrated quickly.

IMO the bigger problem with FreeCAD is the topological naming problem. It's very easy to get frustrated because your model broke due to a change you made in an earlier feature.

The UI isn't amazing though, and that unfortunately happens quite a bit with open source software. Hopefully it'll go the way of Blender and KiCAD with an eventual major release that overhauls the UI.

Ondel has a nicer user interface, but I personally use and recommend realthunder's LinkStable branch of FreeCAD. Mainline FreeCAD (and by extension, Ondsel) suffer from the topological naming problem, which can be especially jarring to users coming from proprietary CAD software. realthunder put a lot of work into a solution that handles the problem pretty well, so I'm using his fork until toponaming gets mainlined.

Yep, and for good reason honestly. I work in CV and while I don't work on autonomous vehicles, many of the folks I know have previously worked at companies or research institutes on these kinds of problems and all of them agree that in a scenario like this, you should treat the state of the vehicle as compromised and go into an error/shutdown mode.

Nobody wants to give their vehicle an override that can potentially harm the safety of those inside it or around it, and practically speaking there aren't many options that guarantee safety other than this.

Yeah I think Lemmy would actually work pretty reasonably. It reminds me of how lots of software and projects have Reddit communities. I agree that being able to share 1 account over many services, and especially not having to pay for infrastructure is something that drives discord use over forum-based platforms.

Personally, I'd prefer that projects use forums for community discussions rather than realtime chat platforms like Discord or Matrix. I think the bigger problem of projects using Discord is not that it's closed source, but rather that it makes it difficult to search (since no indexing by search engines) and the format deprioritizes having discussion on a topic over a long period of time. Since Matrix is also intended for chat, it has these same issues (though at least you can preview a room without making an account).

Afaik the StarFive SOCs used in SBCs are a lot slower than current ARM offerings. Part of that might be because software support is worse, so maybe compilers and related tooling aren't yet optimized for them?

Hopefully development on these continues to improve though. The biggest nail in the coffin for Pi alternatives has been software support.

As of right now VLC also doesn't properly support Wayland, but MPV does. It's a great piece of software!

Agree on the sentiment about VLC though, having an open source project demonstrate what is possible and stand the test of time definitely paves the way for future work and improvements.

Right, as someone in the field I do try to remind people of this. AI isn't defined as this sentient general intelligence (frankly its definition is super vague), even if that's what people colloquially think of when they hear the term. The popular definition of AI is much closer to AGI, as you mentioned.

I haven't used all of the assembly workbenches but I've found Assembly3 to be pretty robust to design changes if you use realthunder's Link Stable fork of FreeCAD. I wouldn't be surprised if all of the assembly workbenches would benefit from toponaming fixes, though I don't know how they all work.

The topological naming problem is handled quite well by realthunder's FreeCAD Link Branch fork, and his Assembly3 workbench is an acceptable, albeit imperfect method of making assemblies when combined with his fork. Assembly3 can run on upstream FreeCAD but I found it to work way less consistently due to issues like the topological naming problem breaking links in the assemblies.

Nonetheless the added features by Ondsel look interesting. I'd consider switching once upstream FreeCAD implements a solution to the topological naming problem, but like you mentioned, toponaming is such a huge leap in usefulness that I'm hesitant to switch to another FreeCAD version that doesn't handle it well.

Not sure what's going on but if the printer was flashed with Klipper, it won't show anything on the screen until it is connected to a computer running klipper's host software.

That sounds about right. You can technically achieve full torque at 0 RPM, but the current required for that might be very high (and may not be practical for the small size, power limits, and cost of a 3D printer). I know this is a problem in Asian import mini-lathes - if you run the spindle too slow you won't get much torque out because the driver can't supply enough current.

I think it would be a better idea to use linear encoders if you were going to add encoders to the shaft, as that way you could directly readout the position of the tool along an axis without issues like backlash that would mess up your calculated position. This is what I've seen on (both manual and CNC) mills and lathes.

BLDC and AC servos maintain full torque at stop too, and have about 2-3× the torque of a stepper of similar size.

Huh, this is true about BLDCs as well? I remember seeing in a video that BLDCs tend to have very poor torque output when stopped and especially when at low speeds (due to very low efficiency requiring too high currents for drivers to supply), whereas AC motors have a pretty much flat torque curve until they get fairly fast. I'd be interested to know if this is true.

I'm a researcher in ML and that's not the definition that I've heard. Normally the way I've seen AI defined is any computational method with the ability to complete tasks that are thought to require intelligence.

This definition admittedly sucks. It's very vague, and it comes with the problem that the bar for requiring intelligence shifts every time the field solves something new. We sort of go "well, given these relatively simple methods could solve it, I guess it couldn't have really required intelligence."

The definition you listed is generally more in line with AGI, which is what people likely think of when they hear the term AI.

I believe this is the referenced article:

https://arxiv.org/abs/2311.03348

I've been using FreeTube since Piped was very inconsistent for me, but I guess that's just the nature of these services. I'll have to check out Invidious again, last time I tried it was several years ago and I stopped using it after the main instance shut down. Is it still under active development? I remember its development status being unclear, partially because the language it uses is not super mainstream, but it's probably changed since then.