spec
buf
spec | buf | |
---|---|---|
11 | 40 | |
585 | 8,281 | |
1.2% | 1.6% | |
9.7 | 9.5 | |
7 days ago | 7 days ago | |
Ruby | Go | |
MIT License | Apache License 2.0 |
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.
spec
-
What is the best way to make simple games with Ruby?
You may define that Ruby is "CRuby" (MRI), the full-fledged implementation of the Ruby programming language specification (https://github.com/ruby/spec/).
-
Ending the predominance of the Array in Ruby
Testing: Interestingly, most of the work was figuring out how to test the library reliably. Grizzly-rb is proudly tested against the ruby/spec repository using Mspec and Rubocop. Special thank you to the person recommending Rubocop in a previous post. The tests cover Enumerable, Array, Enumerator and Enumerator::Lazy classes.
-
Personal efforts to improve the quality of Ruby interpreter
Ruby interpreter is a complex program, so it naturally has bugs, and Ruby interpreter developers are taking various countermeasures against them. For example, we write tests and check them in CI environment (This is the result of daily maintenance of the test environment, such as RubyCI, chkbuild, ruby/spec: The Ruby Spec Suite aka ruby/spec and machines).
- Finally: A Language Specification for Protocol Buffers
-
Where is Ruby language specification or full reference?
I can't find the link to the official announcement, but many years ago they published an official ISO for Ruby, however at the time the ISO was based off of 1.8.7 syntax/semantics. Other than that, you have the RubySpec project which is a series of tests that validate how Ruby should work.
-
Rewriting Libimagequant in Rust for Portability
Java could have been a good example, but Sun had a rather strict validation process for calling something Java.
Furthermore, there are big difference in philosophy with C:
1. IB and UB are not considered normal parts of specifications, meaning there's way less opportunity for originality in the interpretation of the specifications
2. there tends to be an ur-implementation, and notable divergences from that tends to be interpreted as either a bug in the other implementation(s) or a lack of specification to be resolved between all implementations
Rust only has UB in unsafe (AFAIK), which greatly limits implementation flexibility in terms of observable behaviour; and the reference implementation would very much be considered the reference implementation, so I expect e.g. rust-gcc will be sticking close to the reference implementation and behavioural divergence will either be fixed to match, or will lead to more precise specification and both implementations converging.
Probably eventually with, if not a Sun-style validation suite, a Ruby-style Spec Suite (https://github.com/ruby/spec).
-
Announcing TypeScript 4.5
Ruby: https://github.com/ruby/spec Yes, it is not a word document, but it is a spec nonetheless. It is an authoritative source. TypeScript has nothing like this; no, unit tests aren't the same.
- A History of the Rubinius Ruby JIT
-
Opal 1.3 released
Opal is simply a Ruby to JavaScript compiler. While it may be someday possible to run Rails on it, as you can run Rails on JRuby, the primary focus of this project is to allow you to write frontend code in Ruby and possibly share some code between your frontend and backend. It's possible to compile entire Ruby libraries to JavaScript (with little changes needed due to some caveats). Opal supports a Ruby 3.0 level of features (regardless of your backend Ruby version), often surpassing MRuby in terms of compatibility. It is being actively tested for regressions against Ruby Spec and is self-hosting, ie. can compile itself (see: TryRuby).
- Ruby Class Inheritance Flowchart
buf
- Building a gRPC Server with NestJS and Buf: A Comprehensive Showcase
-
5 Open Source tools written in Golang that you should know about
The Buf CLI is a versatile tool designed for handling Protocol Buffers (Protobuf), a method of serializing structured data. It offers several key features, including managing Protobuf assets through the Buf Schema Registry (BSR), providing a linter to enforce optimal API design and structure, and a breaking change detector to maintain compatibility either in source code or at the wire level. Additionally, the Buf CLI includes a generator that activates plugins based on user-defined templates and a formatter to standardize the formatting of Protobuf files according to industry norms. It also integrates seamlessly with the Buf Schema Registry, supporting comprehensive dependency management.
-
Create Production-Ready SDKs With gRPC Gateway
We'll use the Buf CLI as an alternative to protoc so that we can save our generation configuration as YAML. Buf is compatible with protoc plugins.
-
gut: convert golang structs to typescript interfaces
Not so much anymore! Take a look at buf.build, it makes the whole thing notoriously easy :)
-
Flutter + gRPC for Desktop and Mobile App Development - Good choice?
In my opinion it's a good idea, it's the architecture we use at work, and it works well for us. The main limitation to be aware of is that many PaaS don't support gRPC traffic (because of the proxies used). For example, DigitalOcean App Platform or Heroku if I remember correctly. If the way you want to host your backend is OK with HTTP/2 and gRPC traffic, then it's not a limitation. One way around this limitation is to use the gRPC-Web protocol, or the Connect protocol (https://connect.build/). Unfortunately, Dart's gRPC client does not support the gRPC-Web protocol outside the web platform. So for a mobile application, it's not usable at the moment. (If this PR were accepted, it would solve the issue: https://github.com/grpc/grpc-dart/pull/557.) As for Connect, no client is currently offered by Buf for Dart. Don't hesitate if you want to know more. That said, I'd advise you to use the Connect implementation for Go to implement your backend. Connect will enable your server to speak all three protocols (gRPC, gRPC-Web and Connect), which is very useful in the long term. What's more, the code is cleaner, and you benefit from official support for observability with OpenTelemetry. If you don't know Buf (the creators of Connect),I suggest you visit their website: https://buf.build/. :-) Good luck!
-
Building a modern gRPC-powered microservice using Node.js, Typescript, and Connect
As mentioned in the intro, we are going to use Buf and Connect as our tools. We’ll start by installing the dependencies.
-
Building High-Performance Web Services with Golang gRPC
gRPC itself is quite nice, especially with buf which makes generating Go code much easier. The rest of the code was in a bad state. Unmaintained router packages, repository pattern without any actual benefit or a repository pattern.
-
gRPC vs REST: Comparing API Styles in Practice
The second big difference is that we now have auto-generated client and server stubs. For this task, I chose to use buf and the protobuf-ts plugin in order to generate idiomatic Typescript classes and objects. Not only do these classes describe the types we'll use in the server and client, but also includes the actual gRPC implementations used to serialize and send messages back and forth across the wire.
-
Show HN: ProtoCURL, a Curl for Protobuf
Our team has been using Buf (https://buf.build) recently, and they have a nice solution for schema dependency management.
-
Resources for getting into cloud computing?
I've found that https://buf.build/ is easier to use than protoc directly.
What are some alternatives?
Opal - Ruby ♥︎ JavaScript
protoc-gen-validate - Protocol Buffer Validation - Being replaced by github.com/bufbuild/protovalidate
grizzly-rb - The Ruby library you will love to hate
prototool - Your Swiss Army Knife for Protocol Buffers
opal-rails - Bringing Ruby to Rails · Rails bindings for Opal
grpc-web - gRPC for Web Clients
dssim - Image similarity comparison simulating human perception (multiscale SSIM in Rust)
goprotobuf - Go support for Google's protocol buffers
custom-gtksourceview-languages - Custom modifications to the Gtk.SourceView Languages to support Markdown and syntax highlighting of code blocks in Markdown.
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
opal-devtools - A Browser extension providing tools for developing with Opal Ruby in the browser.
oapi-codegen - Generate Go client and server boilerplate from OpenAPI 3 specifications