Howdy folks, made this project to see if you can really use the stdlib to
write a web app server without using a framework and also give me a base
for future web apps that I feel like building with a set of generic docs.
It almost to the state where I can take it and actually start using it
So I'm going thru some of the Github issues, I'm wondering what will become
of these packages that are frozen in the stdlib:
- log/syslog (Implements logging facilities for *nix operating systems)
- net/smtp (Implements RFC 5321)
- net/rpc (Implements remote procedure calls for Go-Only
On Wednesday, May 2, 2018 at 3:12:58 PM UTC-5, Manlio Perillo wrote:
> Yes, but many developers may need a "debug" mode or more options available
> to where to store the assets.
> Why should a "standard" tool or API be restricted to where to store assets?
>
I can kinda see where your going
thing like...
*go build -ldflags="-X main.Asset1=./SomeFileA main.Asset2=./SomeFileB"*Think
this would take a little more effort to integrate in but it's a interesting
concept thou.
On Monday, April 30, 2018 at 2:57:12 PM UTC-5, Ian Lance Taylor wrote:
>
> On Mon, Apr 30, 201
UTC-5, Ian Lance Taylor wrote:
>
> On Mon, Apr 30, 2018 at 7:03 AM, John Unland <unlan...@gmail.com
> > wrote:
> >
> > Hey everyone I've been mulling over this for a couple of days, thought I
> > would get some feed back on the possibility of shooting a proposal
Hey everyone I've been mulling over this for a couple of days, thought I
would get some feed back on the possibility of shooting a proposal to have
embedding static assets into the stdlib. From the looks of it this wouldn't
break Go 1 compatibility thou I'm wondering if it would be better to
