Viewing profile — G4Vi
G4Vi
HN member- Joined
- Mon, Feb 18, 2019, 2:59 PM UTC
- HN karma
- 21
- Public activity
- 22 items
- HN profile
- View on Hacker News ↗
About G4Vi
No profile information was provided.
Recent public activity
-
comment
Comment #48748820
Location: New Hampshire Remote: Preferred, 3+ years experience fully remote Willing to relocate: Yes Technologies: C, C++, Rust, Perl, TS/JS, Go, Python, WASM, Linux, Windows, Embe…
-
comment
Comment #45561047
Location: New Hampshire Remote: Only (occasional travel okay), 2+ years experience fully remote Willing to relocate: Yes Technologies: C, C++, Rust, Perl, TS or JS ES6+, Go, Python…
- story
-
comment
Comment #45104203
Location: New Hampshire Remote: Only (occasional travel okay), 2+ years experience fully remote Willing to relocate: Yes Technologies: C, C++, Perl, TS or JS ES6+, Rust, Go, Python…
-
comment
Comment #44759214
Location: New Hampshire Remote: Only (happy to come-in or travel occasionally). Worked remote for the last 2+ years. Willing to relocate: Maybe Technologies: C, C++, Perl, TS or JS…
- story
-
comment
Comment #39145437
On the devx, there's definitely some rough edges around building and using Wasm. My company has been working on a framework to ease integrating Wasm into existing applications. One…
-
comment
Comment #38033353
It would be cool to package Wasm for every platform easily. You could make a hermit runner for android that loads the module and wasi configuration from the hermit, but uses its ow…
- story
-
comment
Comment #35425134
Location: Not quite Boston (Southern NH, US) Remote: Only (happy to come-in or travel occasionally) Willing to relocate: No Technologies: C, C++, Perl, WASM, Linux, Windows, Embedd…
-
comment
Comment #34984202
Location: Not quite Boston (Southern NH, US) Remote: Only (happy to come-in or travel occasionally) Willing to relocate: No Technologies: C, C++, Perl, WASM, Linux, Windows, Embedd…
-
comment
Comment #34699019
Location: Not quite Boston (Southern NH, US) Remote: Only (happy to come-in or travel occasionally) Willing to relocate: No Technologies: C, C++, Perl, WASM, Linux, Windows, Embedd…
-
comment
Comment #34009309
It's mostly likely a false positive, but you're welcome to build from source with apperlm. The polygot binary format including the compressed ZIP archive probably sets off the scan…
-
comment
Comment #34006344
> HTTP::Daemon, HTTP::Tiny and HTTP::Server::Simple I haven't tested any. Pure Perl servers should be the easiest to get working. The Cosmopolitan Libc doesn't support fcntl F_SETF…
-
comment
Comment #34006063
Update on the APE Linux kernel support (for fork/ --assimilate)less APE execution. jart informed me: "It's in the process of being emailed out to the kernel developers. I anticipat…
-
comment
Comment #34003996
I would first create a script that runs a web server that performs as expected (serving files, and handling dynamic functionality in the script or in a perl module, or by paths to …
-
comment
Comment #34003390
APPerl creator here. I appreciate all the feedback and hope it comes in handy. It's linked from the page, but thought I'd point out if you're curious what went into making APPerl, …
-
comment
Comment #34003279
I forgot to mention APPerl and StaticPerl have many overlapping use cases, but APPerl is more tailored to application packaging. APPerl is built with a patch to Perl adding argv[0]…
-
comment
Comment #34002858
Author here. Nice comparison. By default (and the released) APPerl binaries do not self-modify (they use the non-self modifying ape loader) however on unix-like they install the AP…
- story
-
comment
Comment #32651070
It would be nice if you didn't need to start out with tons of ccflags and ldflags, but I'll point out you don't actually need to use the amalgamation header, alternatively using -i…
-
comment
Comment #19191069
I needed to calculate the potential output file size tar would produce, so what better way than using tar itself to calculate it. It just required hooking read, write, and close. h…