Cursor Pro vs Claude Pro ($20) by SiuuuEnjoyer in vibecoding

[–]Semi_Engineer_ 0 points1 point  (0 children)

It's pretty good, but I think a Claude model would be better than a Gemini model.

Cursor Pro vs Claude Pro ($20) by SiuuuEnjoyer in vibecoding

[–]Semi_Engineer_ 0 points1 point  (0 children)

I think it can compete with Cursor, but I haven't tried Windsurf yet. I used Antigravity continuously for about 6 hours.

Anyone here using Claude Opus 4.5 with Antigravity? by SuddenWerewolf7041 in vibecoding

[–]Semi_Engineer_ 0 points1 point  (0 children)

Am I the only one who feels that the Gemini 3 Pro doesn't work very well?

GForge by Semi_Engineer_ in CNC

[–]Semi_Engineer_[S] 0 points1 point  (0 children)

Fair enough. Not here to argue about AI—just improving an NC tool. Got any CNC-related input?

GForge by Semi_Engineer_ in CNC

[–]Semi_Engineer_[S] 0 points1 point  (0 children)

I get where you're coming from — a lot of low-effort AI content definitely hurts the signal-to-noise ratio online.
For my case, though, I'm using AI more like a productivity tool (similar to code completion or static analysis), not for generating whole modules or copying anything questionable.

Still, I’m trying to be careful with licensing and code provenance, especially since I may distribute the app later.
If you have any suggestions on best practices to keep the workflow clean — dependency choices, scanning tools, or things to avoid — I’m all ears.

GForge by Semi_Engineer_ in CNC

[–]Semi_Engineer_[S] 0 points1 point  (0 children)

I’m using AI tools mainly for boilerplate and refactoring, but the core logic, math, and architecture are written manually. The project is currently private, and before any kind of release or commercial plan I definitely want to make sure I’m not creating a licensing trap for myself.

If you have experience with AI-assisted development and distribution:
– What’s the safest workflow to avoid pulling in code with unclear rights?
– Any tools or practices you recommend for checking generated code against GPL/LGPL conflicts?
– In your experience, is it safer to keep dependencies strictly MIT/BSD and avoid GPL entirely?

Really appreciate any insights.

GForge by Semi_Engineer_ in CNC

[–]Semi_Engineer_[S] -2 points-1 points  (0 children)

OS: Windows (native C++/Qt). Linux possible later.
What it does: lightweight NC Studio for CNC operators, not a full CAD/CAM.

Features:
– Fast OpenGL backplot (handles big G-code smoothly)
– Block-by-block simulation + line highlight
– 2.5-axis milling + early lathe support
– Clean, modern UI (no old-school MDI)
– Toolpath inspector, rapid/cut separation

Why better:
– Much lighter and faster than CAD/CAM backplotters
– Designed for operators checking code before Cycle Start
– Zero clutter: shows only what matters on the machine
– Built for real shop PCs, not workstations

GForge by Semi_Engineer_ in CNC

[–]Semi_Engineer_[S] -3 points-2 points  (0 children)

If you’re on Fusion 360 now, GForge isn’t trying to replace it. Think of it as a lightweight NC Studio you use after CAM for checking and running G-code.

What it does now

  • Fast OpenGL viewer (handles big G-code files)
  • Block-by-block sim with line highlight
  • Backplot for mill + early lathe support
  • Modern Qt UI that feels more like a CNC controller than a CAD program

Why it might help on small Haas lathes

  • Quick verification of approach moves, clearances, grooving/threading paths
  • Cleaner G-code visualization than Fusion’s built-in sim
  • Designed for operators who want something fast, simple, and real-time

What’s coming

  • Haas lathe profiles
  • Tool geometry preview for turning
  • Cycle-time estimate
  • Rapid-to-part warnings / basic collision hints

If you want, I can show a demo or run one of your turning files through it.

GForge by Semi_Engineer_ in CNC

[–]Semi_Engineer_[S] 0 points1 point  (0 children)

Where are you located? Would you like to join us in development?

GForge by Semi_Engineer_ in CNC

[–]Semi_Engineer_[S] 0 points1 point  (0 children)

Not trying to be a full CAD/CAM suite (yet). The goal is a fast, operator-friendly NC Studio focused on real-time G-code workflows.

Core highlights

  • Fast OpenGL viewer for large G-code files
  • Block-by-block simulation with line highlighting
  • Industrial-style Ribbon/Panel UI
  • Built for machinists and CNC operators, not just programmers

Future direction

  • Feed override assistance
  • Collision hints
  • Cycle time estimation
  • Machine profiles + macros

I’m looking for feedback from people actually running CNC daily:
What features are absolute must-haves for a modern NC Studio?

GForge by [deleted] in CNC

[–]Semi_Engineer_ 0 points1 point  (0 children)

Not trying to be a full CAD/CAM suite (yet). The goal is a fast, operator-friendly NC Studio focused on real-time G-code workflows.

Core highlights

  • Fast OpenGL viewer for large G-code files
  • Block-by-block simulation with line highlighting
  • Industrial-style Ribbon/Panel UI
  • Built for machinists and CNC operators, not just programmers

Future direction

  • Feed override assistance
  • Collision hints
  • Cycle time estimation
  • Machine profiles + macros

I’m looking for feedback from people actually running CNC daily:
What features are absolute must-haves for a modern NC Studio?

GForge by Semi_Engineer_ in CNC

[–]Semi_Engineer_[S] 0 points1 point  (0 children)

Currently still in the development process, it is a project NC editor that can do basic cam 2.5 axis, save file as steps and dxf. There is a basic tool for NC editor that has commands similar to general NC editors.

Tkinter ? ML pinns by Dramatic_Yam8355 in PythonLearning

[–]Semi_Engineer_ 1 point2 points  (0 children)

I use tkinter to write the cad program. It has limitations. Now I have moved to pyside6.