RAM is the kind of thing you’re better off having too much than not enough. Worst case the OS ends up with a very healthy and large file cache, which frees up your storage and makes things a bit faster/lets it spend the CPU on other things. If anything, your machine is future proofed against the ever increasing RAM hungriness of web apps. But if you run out of it, you get apps killed, hangs or major slowdowns as it hits the swap.
The thing with RAM is that it’s easy for 99% of your workload to fit comfortably, and then there’s one thing you temporarily need a bit more and you’re screwed. My machine usually uses 8-12/32GB of RAM but yet I still ended up needing to add swap to my machine. Just opening up the Lemmy source code and spinning up the Rust LSP can use a solid 8+GB alone. I’ve compiled some AUR packages that needed more than 16GB of RAM. I have 16 cores so compiling anything with -j32 can very quickly bring down a machine to its knees even if each compile thread is only using like 256-512MB each.
Another example: my netbook has 8GB. 99% of the time it’s fine, because it’s a web browsing machine, and I probably average on 4GB usage on a heavy day with lots of tabs open. But if I open up VSCode and use any LSP be it TypeScript or Rust, the machine immediately starts swapping aggressively. I had to log out of my graphical session to compile Lemmy, barely.
RAM is cheap enough these days it’s nice to have more than you need to not ever have to worry about it.
I have 64GB as future proofing (ITX board, two slots, can’t address any more). Normally I probably use 8 to 10 of those doing things like gaming and hoarding internet tabs like they’re a nonrenewable resource. I actually managed to crash my machine with an out of memory condition compiling something a while back. I don’t remember what and I’m sure it doesn’t count as regular use but I installed ZRAM to prevent it from happening again.
Just pick one and roll with it. Eventually as you use it you might want to switch so do that if you wanna. Distro just comes down to preference so find one you like. At the end of the day they’re all Linux
I use FreeCAD and Assembly3 for everything and have for many years now. I sometimes use realthunder’s fork of FreeCAD but right now it’s quite a bit behind upstream and there are some cool new features in sketcher so I use upstream for those.
Some people get confused about workflow in FreeCAD because there are so many options and every youtube video has different opinions or tries to feature a particular workbench like curves or something. My opinion… Pretty much your workflow starting out should be to ignore everything else and use part design and sketches, it’s the simplest way:
enable autosave with a short interval, like 2min
Switch to part design workbench
create body
create sketches as the base of the features of your part attached to the xy, xz, yz planes, offset them to create a “wire frame” that resembles your project
a. Your sketches should be fully constrained
b. Your sketches should have as little geometry in them as possible, if you need more complex stuff make more sketches
c. Your sketches should have closed wires, you can’t pad something that doesn’t create a face.
use pad, pocket, revolution, loft, and hole operations on those sketches to form a 3d solid
if you need to create additional sketches which import geometry from the previous operations (using the external geometry tool), import SKETCH geometry from the previous ops, not edges of solids, whenever possible. Hide your solid, unhide your sketch, select that with the external geometry tool.
a. Use sketch on face sparingly.
Do fillets and chamfers last, if you need to change something, delete them and recreate them once you’ve made your changes.
To make multiple parts make multiple bodies with the same workflow as above.
Once you get pretty good at making static parts with constrained geometry, holes, threads (with the hole function), etc, which you can do with only the stuff above, then you can branch out into other workbenches like assemblies or curves, but all of those things build on the concepts above, so it’s easy to get overwhelmed if you try to do it all right from the start. Learning how to recover from a mistake is just part of CAD in general, though I admit that it’s a bit more effort to find what’s wrong in FC vs commercial platforms, but we aren’t here, on lemmy, in a linux community, to use commercial platforms.
AFAIK that’s pretty much the same workflow as F360 uses for single-solid parts though things have different names. pad=extrude for example.
It’s obviously far from perfect but in my opinion it’s the best solution that runs natively on Linux and is actually open source. Also assembly3 uses solvespace as it’s backend solver so if you make assemblies using that you are kindof using solvespace too.
Also, I hear/read a lot of complaining about instability but I’ve honestly never had a crash that wasn’t on an experimental branch like RT or the edge release of upstream. However step 0 above should help if you’re worried about that.
I think yes. In general if you have good setup instructions (preferably automated) then it will be easier to start from scratch. This is because when starting from scratch you need to worry about the new setup. But when upgrading you need to worry about the new setup as well as any cruft that has been carried over from the previous setup. Basically starting clean has some advantages.
However it is important to make sure that you can go back to the old working state if required. Either via backups or leaving the old machine around working until the new one has been proven to be operational.
I also really like NixOS for this reason. It means that you can upgrade your system with very little cruft carrying over. Basically it behaves like a clean install every update. But it is easier to roll back if you need to.
Its weird that its not consistently needed though, for the workspace and modifying existing gaps in real time, it looks like the postfix ‘px’ isn’t needed.
Your i3 is too old. Perhaps your distro’s repository has a package called “i3-gaps” which was the former fork that implemented this feature. i3-gaps was merged back into i3 in the meantime.
I’ve been using SALOME to create parametric 3D geometry. My use case is to parameterize my geometry features and export to STL files that I use with OpenFOAM. SALOME is integrated with a couple of grid generators, and I really like it’s 2D/triangulation/STL integration with netgen. You can specify faces for refinement to a desired mesh size, so for example around complex features you can create a fine STL mesh and on simple shapes you can have a really coarse mesh.
I’ve found the 3D modeling to be pretty straightforward, and SALOME usually does a pretty good job if you have to go back and modify previous features (something I’ve struggled with in FreeCAD).
I’ve also used FreeCAD for mesh generation, and it works ok but I’ve found the triangulation leaves a lot to be desired for splitting up the mesh as needed for OpenFOAM boundaries.
If you’re making STL files for 3D printing and you want a parametric CAD modeler for engineering parts, give it a try. If you want complex faces with artistic style, I would suggest Blender.
LSPs, linters, AI auto complete, multiple ranked auto complete sources, contextual syntax highlighting abused to feed things like symbol tree views, type analysis, scoped file trees depending on what you’re working on, infinite undo since last commit, and all available in real-time.
I feel like I use up 8GB the moment I type “neovim” on a sufficiently large node project, lol.
If you’ve designed everything correctly, then yes, it should be much easier to deploy a new instance on a new machine than to upgrade an existing machine.
Lol it was “fun” two days ago when all the outlets originally wrote about it. Now it just feels like the headline might as well be, “heh, remember how we all laughed at that thing two days ago?”
Doesn’t seem necessary to bring it up again for 6.6.7 any more than it will for 6.7.6 or 7.6.6. I’m not really familiar with the outlet though, maybe they make a headline for every minor patch release.
I’m with you. Not even necessarily with your original comment, but I have also had the experience of making a mild complaint and being dogpiled by people who are somehow super butthurt about it. It’s weird. They could have read your comment and moved on like they are demanding you do.
Most excellent. I’m glad to see things are working out, and that you’ve found something that works well. I hope your experience is as beautiful as mine was - mine pushed me to pursue computer science and programming.
I recommend at this point learning Flatpak and exploring Flathub for your favorite apps. Flatpak is treated as a first-class citizen on Fedora, so its my go-to recommendation. Should be super easy. Here are the instructions: flathub.org/setup/Fedora
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.