On Wednesday 2 October 2024 at 18:11:10 UTC+1 opennota wrote:
Cold-start builds are slow af on my machine (think tens of minutes), and
have been like that since around Go 1.20.
Have you ruled out that it's not anything to do with the automatic fetching
of toolchains, introduced in 1.21 I think
On Wed, Oct 2, 2024 at 11:53 AM opennota wrote:
>
> I'm seeing lots of GOCACHE accesses, but there's a considerable delay after
> `go build -x -toolexec time` prints `WORK=/tmp/go-build329465119` and before
> it starts to print all the other commands/package names/times.
Hmmm, OK, then maybe yo
I'm seeing lots of GOCACHE accesses, but there's a considerable delay after
`go build -x -toolexec time` prints `WORK=/tmp/go-build329465119` and
before it starts to print all the other commands/package names/times.
On Thursday 3 October 2024 at 00:21:30 UTC+7 Ian Lance Taylor wrote:
> On Wed,
On Wed, Oct 2, 2024 at 10:11 AM opennota wrote:
>
> Cold-start builds are slow af on my machine (think tens of minutes), and have
> been like that since around Go 1.20. (See also maybe related
> https://github.com/golang/go/issues/38939). Is there a way to profile `go
> build` to determine why
Cold-start builds are slow af on my machine (think tens of minutes), and
have been like that since around Go 1.20. (See also maybe related
https://github.com/golang/go/issues/38939). Is there a way to profile `go
build` to determine why it takes it so long to build even a simple
hello-world pro
Hi,
Tip of the hat to Brad for the mention :)
But Brad is being far too modest. vugu was shown at GopherCon 2020. You can
find his talk here:
https://www.youtube.com/watch?v=JIsUb1t6un0
There is also a #vugu channel on slack if you want to ask questions.
The code repo is at https://github.com/
https://www.vugu.org/ is a project I created a while ago (and had quite a
bit of help and contributions from others in the community on) to build web
UIs a in Vue-like fashion. I agree that a component library would be
really handy, I just personally haven't had the time to work on.
More recen
Worked! Thanks
On Wednesday, October 2, 2024 at 9:18:41 AM UTC-4 Jan Mercl wrote:
> On Wed, Oct 2, 2024 at 3:07 PM Mandolyte wrote:
>
> > What did I do wrong?
>
> Copying the go.mod file effectively declares the code in hello.go to be in
> package modernc.org/tk9.0.
> That's the package hello.g
On Wed, Oct 2, 2024 at 3:07 PM Mandolyte wrote:
> What did I do wrong?
Copying the go.mod file effectively declares the code in hello.go to be in
package modernc.org/tk9.0.
That's the package hello.go imports, hence the import cycle. This works
here:
jnml@t3610:~/tmp$ mkdir tk
jnml@t3610:~/tmp$
It has been a long time since I have done any Go work, so probably my
ignorance... but I did the following:
- in an empty folder
- copied the hello.go from the examples folder
- copied the go.mod file from repo root folder
- ran `CGO_ENABLED=0 go run hello.go`
- with this result:
```
$ CGO_ENABLED
Go is already a fast backend language.
Why are the creators of *Web Frameworks* for Go, still missing the point?
I mean, things like *React*, *Vue*, and *Svelte* make it possible to create
*reusable
Web Components*.
Their additional strong point is *State Management-- *where an
application's
11 matches
Mail list logo
