By empty, I mean it didn't actually contain any actual data, just zeros.
That's why it's being compressed that much.
I embedded the file into the Go code using the standard embed directive.
```
package main
import _ "embed"
//go:embed .empty
var data []byte
```
On Friday, 16 December 2
Please clarify what you mean by "embedded an empty 100MB file". What
does "empty" mean and how did you "embed" it? Can you show us an example of
what you're trying to do (obviously replacing the 100MB of "empty" with a
placeholder).
On Thu, Dec 15, 2022 at 10:58 AM Aurora wrote:
> I've embedded
I've embedded an empty 100MB file in my Go code, for some testing purposes.
When I run 'go build', the binary output would be something around 20MB.
I want the output binary to be more than 100MB, its real size.
How's this compression being applied to the binary?
How to disable all such optimisat
Hi,
I think App Engine is not getting as much development efforts as Cloud Run
does.
I foresee it the same fate as Legacy Networks versus VPC.
That said, it looks like they were unconfortable with this situation as
they released Go 1.18 and 1.19 (NB: not 1.17) a few days ago:
https://cloud.goog
Assuming that it is a basic Hello World program, I don't have such problems
on my Windows 11 laptop and like many Windows machines, it has antivirus,
etc. running. I think it could be something specific to your machine or
environment.
On Thursday, December 15, 2022 at 2:11:48 PM UTC+7 marc...@g
