newbie needs guidance

BTW, now that OP has explained the project a bit more, I can see that Phishfry is right, versions of Goland and GStreamer really don't matter here.

Yeah, it's important to grab the most recent available stuff, but it's not a great idea to go totally bleeding-edge and reinvent the wheel by going upstream. I think it's far more important to be comfortable with the development stack and the workflow of the OS that you choose.

FreeBSD's development stack does have all the tools you'll need, and it's actually comparable to Linux in that regard. The real difference is in how it represents the hardware and installs the software. Once you get past that, and install/configure all the tools, it actually stops mattering if you're on FreeBSD or Linux. You'll still have access to tools like Golang, git, GStreamer, SSH, and more.

Basically, just get Golang and GStreamer from ports, and don't worry about upstream.
 
astyle said:
versions of Goland and GStreamer really don't matter here.
Click to expand...
I won't disagree with you, but my reason for wanting GStreamer 1.26 is that they say this freezes the API. So if I write a lot of code and get something working and later need to upgrade, there could be a lot of changes to deal with. However, I'm extremely slow, so it probably won't be a problem.

Please could you, or someone else, give precise instructions on how to install the available Go version and GStreamer (both gst-launch-1.0 and development, including all plugins good, bad and ugly - free and not free).
 
Michael Nayor said:
Please could you, or someone else, give precise instructions on how to install the available Go version and GStreamer (both gst-launch-1.0 and development, including all plugins good, bad and ugly - free and not free).
Click to expand...
I'd suggest that you become familiar with installing software on FreeBSD by reading the relevant FreeBSD User Handbook chapter. Everything you need is in ports. BTW, the latest snapshot of ports does include GStreamer 1.26 (since March 21), so you're in luck.
 
Can I very gently suggest that learning vi / vim won't really take "months" of effort and furthermore will repay you with many years of enjoyment and use value, since it is ubiquitously available on practically every linux and *bsd box in the world?

There was an excellent vi tutorial written by Walter Zintz many years ago; I found this project recently where someone has very helpfully updated the Zintz tutorial for the current versions of vim. They have packaged the Zintz originals in too for reference.

The actual learning time for vim to get to first base is probably only a couple of days, if that. Above all just start using it, you don't have to learn everything up front, learn it incrementally and you will soon find that you rapidly become accustomed to it. A little bit of work will repay you with years of programming and editing pleasure. :)

github.com

GitHub - dahu/vim_waz_ere: Vimmified version of the venerable Walter A. Zintz Vi/Ex Tutorial Series

Vimmified version of the venerable Walter A. Zintz Vi/Ex Tutorial Series - dahu/vim_waz_ere
github.com github.com

 
Thank you to all who have helped. I'll get on with it now and read more of the Handbook and learn. I do have this tendency to be lazy, so don't be surprised if I pop up in another thread.

By the way, I mentioned the Zed IDE earlier. If there are any Rust developers here, this may be of interest - their reply to the feature request I submitted...

"We don't currently provide freeBSD builds, but some work has gone into making it compile in theory. If you build the remote_client on a freeBSD machine with cargo build -p remote_server, you should be able to copy it to ~/.zed_server/zed-remote-server-0.179.7 (or whatever version your client zed is running) and they will connect over SSH."
 
You must log in or register to reply here.
Back
Top