I disagree with a few of those, but the simplest example is image. There still needs to be an image.Image interface for methods common to all image types. Then sub packages for raster and vector (others?) There are too many different image types so you end up a multitude of packages and since package names need to be short you lose a lot of information. An easy example is fractal. There are fractal images do you would have fractal.Image but most people seeing a package called fractal would assume it handle fractals....
Personally I would like to look at the documentation for the image package to quickly see all of the supported types. Thus is why having a “rule” is tough to do in practice. > On Dec 1, 2018, at 8:22 AM, Michael Jones <michael.jo...@gmail.com> wrote: > > I'll also add that personally I saw a lot of "change this" commentary with > rather little "thank you." That was not in the best spirit of what (at at > least I think) it should be. It's always good to act on ideas, build > solutions, and share results. It would be great if everyone always started > with that. You deserve it as does your code. > > Thank you! > Michael > >> On Sat, Dec 1, 2018 at 6:17 AM Michael Jones <michael.jo...@gmail.com> wrote: >> I can see why you're feeling that. My sense is that what causes flare-ups is >> when people (universally rather than just here) get the feeling that the >> discussion is becoming personal rather than technical. Go is lots of >> people's work / tool / job / fun / etc., so passions may be strong, but I've >> never seen any tendency to be angry and protective about people raising >> issues with poor choices. What does come up is the desire for examples, >> use-cases, and other kinds of supporting information so that the >> conversation moves from "i feel that" ==> "in these situations" ==> "a >> workable resolution" ==> ... ==> "X seems the best way forward after much >> analysis." That made go great so far, and the conversations generally >> collegial. >> >>> On Sat, Dec 1, 2018 at 6:00 AM Robert Engels <reng...@ix.netcom.com> wrote: >>> This is a problem with it seems more than a few in this community. Someone >>> makes a criticism of an idea, backs it up, and is treated in a childish >>> manner because it doesn’t go along with dominate opinions of the >>> controllers of the group think. Not good IMO. >>> >>>> On Dec 1, 2018, at 7:48 AM, Jan Mercl <0xj...@gmail.com> wrote: >>>> >>>> On Sat, Dec 1, 2018 at 9:47 AM Dan Kortschak <d...@kortschak.io> wrote: >>>> >>>> > Very nice. >>>> >>>> Indeed. >>>> >>>> -- >>>> -j >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "golang-nuts" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to golang-nuts+unsubscr...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "golang-nuts" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to golang-nuts+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> Michael T. Jones >> michael.jo...@gmail.com > > > -- > Michael T. Jones > michael.jo...@gmail.com -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
