ion-docs
go
ion-docs | go | |
---|---|---|
4 | 2,100 | |
21 | 120,631 | |
- | 0.9% | |
4.1 | 10.0 | |
9 days ago | 4 days ago | |
Java | Go | |
Apache License 2.0 | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ion-docs
-
Rob Pike: Gobs of data (2011)
Have you tried the superset of json from AWS?
https://amazon-ion.github.io/ion-docs/
-
Introducing JXC: An extensible, expressive data language. It's a drop-in replacement for JSON and supports type annotations, numeric suffixes, base64 strings, and more!
How it compares to Amazon Ion?
-
Amazon Ion – a richly-typed, self-describing, hierarchical serialization format
Disclosure: I manage the Ion and PartiQL teams at Amazon.
If you want to create an issue for it (the best repo is probably the ion-docs one: https://github.com/amzn/ion-docs/issues) that will help to show us there is demand for it. Providing information on your use case helps us prioritize.
go
-
Function fitting in Go
must.Do proposal https://github.com/golang/go/issues/54297
-
Criando um modulo xk6 para k6
Go instalado
- Orbail proposal for go error handling
-
Swift Static Linux SDK
This melding of the sync and the async is actually kinda interesting to me. I know that at least in lots of environments, the sync and async paths are effectively separate for things like I/O[1]. I wondered (and still do for some cases) how Go handles this.
For those curious I looked at Windows and Linux, but not much else.
Linux: no io_uring support. There's debate on even whether to use it as people are discussing security implications[2]. It looks like (from perusing this issue, but could be wrong) AIO wasn't used.
Windows: it looks like they're using IOCP everywhere. Seems sensible enough.
General case: there seems to be an open issue regarding this[3].
[1]: For example, Windows has IOCPs, Linux has io_uring, FreeBSD has kqueue, POSIX has... POSIX AIO, etc.
[2]: https://github.com/golang/go/issues/31908
[3]: https://github.com/golang/go/issues/6817
-
Component Generation with Figma API: Bridging the Gap Between Development and Design
In today's fast-paced software development landscape, efficient workflows and clear responsibilities between development and design teams are crucial. One effective way to streamline these workflows is by automating component generation from design tools like Figma to code using powerful programming languages like Golang. This article will explore the process of converting Figma components to code, focusing on the clear differentiation of responsibilities between development and design teams.
- The Functional Programming Hiring Problem
-
A single ChatGPT mistake cost us $10k
> The Go database/sql package actually executes ROLLBACK in the SQL engine.
No: https://github.com/golang/go/blob/beaf7f3282c2548267d3c89441...
-
Go: Sentinel errors and errors.Is() slow your code down by 3000%
Nice write-up.
It's a shame that errors.Is is slow for general use, and at least some of that seems attributable to the Comparable change requiring reflection. Multi-errors seems to have bloated the switch. And of course the lack of a happy-path that was fixed in [1].
Since Go already has two ways of handling exceptional state: return or panic, it does feel like a stretch to also introduce a "not found" path too. All bets are off in tight inner loops, but I think as a general coding practice, it'll make the language (de facto) more complicated/ambiguous.
But my take away is that the question has been kicked off: can wrapped errors be made more efficient?
1. https://github.com/golang/go/commit/af43932c20d5b59cdffca454...
-
Fast Shadow Stacks for Go
I know that at least two engineers from the runtime team have seen the post in the #darkarts channel of gopher slack. One of them left a fire emoji :).
I'll probably bring it up in the by-weekly Go runtime diagnostics sync [1] next Thursday, but my guess is that they'll have the same conclusion as me: Neat trick, but not a good idea for the runtime until hardware shadow stacks become widely available and accessible.
[1] https://github.com/golang/go/issues/57175
-
Runtime code generation and execution in Go
I guess the meta programming that most often gets used with //go:generate ends up being text/template.
The Go sort algorithm (pdqsort) is implemented in this way so the same algorithm can be used to implement the various existing sort APIs.
https://github.com/golang/go/blob/master/src/sort/gen_sort_v...
What are some alternatives?
Protobuf - Protocol Buffers - Google's data interchange format
v - Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. Supports automatic C => V translation. https://vlang.io
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
DeDRM_tools - DeDRM tools for ebooks
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
zish - A data serialization format
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
cue - The home of the CUE language! Validate and define text-based and dynamic configuration
Angular - Deliver web apps with confidence 🚀
binlog - A high performance C++ log library, producing structured binary logs
golang-developer-roadmap - Roadmap to becoming a Go developer in 2020