apps-script-samples VS gvisor

One of the things that stifles openness is noise. Sifting through our public repos, some are very obviously redundant and just distracting. So we started by archiving a whole bunch of them - over half, in fact. We wrote some Google Apps Script in a spreadsheet to import and analyze the state of all our public repos:

I am not a JS developer, but in some tech areas there are niches with relatively fewer developers competing for the same position.

I don't know if this is actually a niche, but since I don't see it mentioned frequently on HN, perhaps you could have a look at Google Apps Script [0], which is basically JS for automating and extending Google Docs (Docs, Sheets, Forms, Slides), and integrating them into GCP. Tons of companies have whole departments living inside Google Docs, so I imagine they would pay for software making their lives easier. I would but I currently don't have the budget for it, so I am writing short scripts myself. Curiously, Bard and ChatGPT produce really bad Apps Scripts code, which would be to your advantage.

When I occasionally hire people, I do look at their repos to see how good they are in a specific language. Specifically, how easy to follow and idiomatic their code is, what the quality of their comments and documentation is, are there any tests, even if very rudimentary. I particularly enjoy original projects like home automation, custom keyboard firmware, an alternative Netflix UI, a ggplot extension, a basic Python wrapper for some overly-complicated API vs. your typical to-do app or yet another analysis of the Bike Sharing dataset. I don't expect all people to have public repos or FLOSS contributions because not everyone has the time for that. However, if you wanted to demonstrate skills in a technology you haven't used professionally, I think it is a good idea.

0. https://developers.google.com/apps-script

I have a function in Apps Script that returns the Document Position, and I currently have it set to be called every second. However, I'm concerned about potential limitations or quotas that I might reach by making such frequent function calls. I got the idea from their own samples.

Here is the documentation link to help you: https://developers.google.com/apps-script/

Before we get started with ChatGPT, you'll need to set up Google Apps Script. If you're not already familiar with Google Apps Script, you can get started with the documentation here.

Since a few years I had a Google Apps Script that prefixed some events in my calendar with an emoji. This helps me spot certain events or categories of events. This blogpost explains very well why I like to add emoji's to my calendar events.

From my current employer I discovered that you can get surprisingly high mileage with spreadsheets and a little bit of scripting.

My employer uses Google Sheets with app scripts [1].

It automatically reads emails, updates a bunch of spreadsheets, makes other API calls, creates entire report documents etc.

The initial setup might take a while though.

[1] https://developers.google.com/apps-script

I have completed https://grasshopper.app entirely with no prior knowledge of coding. It is very hands on easy to follow. There is more doing coding than reading and each question has a walkthrough available. It is by Google and directs you too Google's own coding platform when you finish. It covers the basics of coding, automation, HTML/CSS/JavaScript and Google's AppScript that work with apps like Google Drive and Sheets. Each course has a PDF certificate of completion. (Last I checked the app was bricked and suggested using the webpage until they figured out the bug with the new operating system.)

Isn't gVisor kind of this as well?

"gVisor is an application kernel for containers. It limits the host kernel surface accessible to the application while still giving the application access to all the features it expects. Unlike most kernels, gVisor does not assume or require a fixed set of physical resources; instead, it leverages existing host kernel functionality and runs as a normal process. In other words, gVisor implements Linux by way of Linux."

https://github.com/google/gvisor

This sort of feels like seeing someone riding a bike and saying: why don’t they just get a car? The simple fact is that containers and VMs are quite different. Whether something uses VMX and friends or not is also a red herring, as gVisor also “rolls it own VMM” [1].

[1] https://github.com/google/gvisor/tree/master/pkg/sentry/plat...

There's two major production-ready Go-based operating system(-ish) projects:

- Google's gVisor[1] (a re-implementation of a significant subset of the Linux syscall ABI for isolation, also mentioned in the article)

- USBArmory's Tamago[2] (a single-threaded bare-metal Go runtime for SOCs)

Both of these are security-focused with a clear trade off: sacrifice some performance for memory safe and excellent readability (and auditability). I feel like that's the sweet spot for low-level Go - projects that need memory safety but would rather trade some performance for simplicity.

[1]: https://github.com/google/gvisor

[2]: https://github.com/usbarmory/tamago

It uses gVisor to create a TCP/IP stack in userspace, and starts a wireguard interface on it, which the HTTP server from http.Serve listens on. The library will print a URL after startup, where you can access your server. You can create multiple listeners in one binary.

The playground compiles the program with GOOS=linux, GOARCH=amd64 and runs the program with gVisor. Detailed documentation is available at the gVisor site.

You could use a container sandbox like gVisor, light virtual machines as containers (Kata containers, firecracker + containerd) or full virtual machines (virtlet as a CRI).