> > Interesting. Does this work on all browsers on all platforms?
Untested here. I've seen it work on macOS with Safari, Chrome, and Firefox. The || is to support how different browsers indicate a back button press / back cache load. Matt On Saturday, January 27, 2018 at 3:49:19 PM UTC-6, Pat Farrell wrote: > > > > On Saturday, January 27, 2018 at 4:34:39 PM UTC-5, Lars Seipel wrote: >> >> We're talking about a beginning Go programmer that has yet to learn how >> some of the more advanced parts of the language fit together properly. > > > Sorry, no. Folks coming from other languages want to know how to do the > usual stuff with go > Seems like a reasonable requirement for me. > > I will gladly grant that most of the frameworks for other languages are > huge, bloated messes that are not consistent, clean and worst, not > orthogonal, all of which are beauties of go's design. But a beautiful > design is not a good thing if you can't write a simple application (web > app in this case) that actually works properly on browsers that real users > have in the real world. > > The "back button" issue has been around since folks first started web > writing applications in the mid-90s. Sadly, for a trivial problem > statement, its still a far more difficult issue than it should be. > > Simple stuff should be simple. Its the design goal of every modern tool. > For 99% of what I think I want, go meets it. But in the real world, users > expect GUIs and that means browsers. So the back and forward and refresh > buttons have to do the right thing. > > IMHO, YMMV, etc > -- 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.
