Reaction score: 10,739
This is highly subjective. What works best for me may not work at all for you. And an IDE for what language? What do you expect of an IDE?what is the best IDE for freebsd?
Then you should use Windows and install it there.i would like something like microsoft visual studio
In what language? And you don't need an IDE to program, in any language. All you need is an editor and an appropriate compiler. There's plenty to pick from. But maybe you should learn the basics first, an IDE isn't going to help you with that. Get a good book for the language you're interested in and start learning.but to create programs for freebsd on freebsd, and of course with a graphical interface
Then I guess you probably have some experience with Visual Studio in Windows, and also I'm completely aware that Visual Studio Code is not Visual Studio, but I think editors/vscode AKA Visual Studio Code, is a good alternative. It's all up to you, but it would be great to invest some time to learn developing in FreeBSD with native/traditional FreeBSD/UNIX tools. Read the following article: Unix as IDEi would like something like microsoft visual studio
Reaction score: 211
maybe I am wrong but you dont know any programing language "graphical" like GTK or QT dont?what is the best IDE for freebsd? i would like something like microsoft visual studio, but to create programs for freebsd on freebsd, and of course with a graphical interface
Reaction score: 819
To begin with, coding and debugging is not at all 100% of the work of a software engineer. A very significant fraction of the work (I would say typically 1/3 to 2/3) is gathering requirements, designing, holding reviews, communicating with stake holders (be it customer support, engineering management, finance, ...). From a "improve productivity" point of view, much more important questions are: what tool do you use for e-mail and remote meetings? Is your company culture conducive to working together? Are coding rules sensible, and enforced reasonably? Is the requirements/design/code review process smooth, efficient yet accurate? Are source control, issue tracking, and project management tools integrated well enough to know what's important? These are big questions. Compared to them, details (like how to arrange windows on the screen) are actually minor.Only masochists use vi or any other console text editors for projects with 10ths of thousands of lines of source code in hundreds of files.
Fair enough. I'm using both nvi/vim and vscode. It would depend on the situation. Function autocomplete is one of those. Another one was MPLAB, which is not available on FreeBSD.I don't have to remember how every API I might ever want to use in every language is spelled.
That IDE does look really interesting. They look to have a thoughtful approach to what they support and the scope rather than just chucking in absolutely everything.
This is an interesting view point. I’d be nice if FreeBSD had it’s own widget toolkit/Graphics Library to supplement native GUI development. Sort of like a barebones base system for applications, but the environment is still left up to the user.
It is possible. Case in point sound(4). (*) Although that's different story. It's in the base. Regarding the GUI, it's up to talented developers to develop a FreeBSD specific GUI system and maintain it in the ports tree. But it's a gigantic task. It takes a lot of time and investment. Frankly I don't think it ever happens. Of course for legitimate reasons. Let's imagine I'm a FreeBSD developer. Personally I prefer invest my time on embedded projects and dealing with CLI, rather than developing a GUI system from the ground up.I’d be nice if FreeBSD had it’s own widget toolkit/Graphics Library to supplement native GUI development
I was thinking from the perspective of FreeBSD being a ”toolkit” for developing anything GUI related. Whether it’s a desktop GUI, a kiosk, phone/tablet OS, a console/media player, etc. It’d give FreeBSD complete independence from any external entity. We‘re going to be shipping DRM in base soon; It’d be nice to have other native libraries in base to facilitate GUI development. One could throw i3 on FreeBSD, and quickly get started, for example, using that “Unix as an IDE” concept.It is possible. Case in point sound(4). (*) Although that's different story. It's in the base. Regarding the GUI, it's up to talented developers to develop a FreeBSD specific GUI system and maintain it in the ports tree. But it's a gigantic task. It takes a lot of time and investment. Frankly I don't think it ever happens. Of course for legitimate reasons. Let's imagine I'm a FreeBSD developer. Personally I prefer invest my time on embedded projects and dealing with CLI, rather than developing a GUI system from the ground up.
Footer (*): FreeBSD Sound
Is X.org not a candidate?FreeBSD provides (n)curses in base. Since there does not exist a standard display system in open-source, I don't see how a meaningful widget set could ever be provided by a UNIX-like OS.
Chasing Linux upstream with shims and re-writing dependencies isn’t exactly productive either. That’s probably most of our ”desktop” ecosystem in FreeBSD anyway.That's the problem. Division of labour is essential. Total self-sufficiency leads to poverty!