On Feb 22, 2018, at 2:16 PM, Devon H. O'Dell <devon.od...@gmail.com> wrote:
> (Re-adding list in here with Bakul's okay.)
> 2018-02-22 12:27 GMT-08:00 Bakul Shah <ba...@bitblocks.com>:
>> On Thu, 22 Feb 2018 12:02:35 -0800 "Devon H. O'Dell" <devon.od...@gmail.com>
>>> Hi all,
>>> It's been some time since I really contributed much of anything to the
>>> project (sorry!), but after 8 years, I'm finally writing Go outside of
>>> the project itself (and outside of porting efforts). I was lamenting
>>> to some coworkers about the lack of a comparable feature to C's
>>> "malloc idiom" and they suggested I write an experience report on it.
>>> I wrote the bulk of the article a month ago, but finally put in some
>>> finishing touches and published.
>> I still run FreeBSD at home and test any go programs I write
>> on it as well as MacOS (and sometime on plan9)! But FreeBSD
>> support seems to be falling further and further behind.
> I'm aware of some strange crash, but I don't have any FreeBSD systems
> anymore to investigate. Are there other areas that FreeBSD is lagging
> in? (Maybe tangent should go to separate thread :))
Go compiles and runs fine but packages don't always. For
instance I was trying to use shiny but indirectly it depends
on shmat(2) & friends. This means adding syscall support in
golang.org/x/sys/unix for FreeBSD. Overall (not just for X
windows or shiny) there is support for various flavors of BSDs
but it is quite haphazard. This is probably due to the small
number of people developing Go code for the BSDs. It is quite
easy to write portable code in Go (compared to most languages)
but a systematic effort is needed to find and fix all the
porting problems - most of them are typically quite minor.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.