go-server-core
crubit
go-server-core | crubit | |
---|---|---|
7 | 13 | |
0 | 556 | |
- | 4.9% | |
0.0 | 9.8 | |
about 2 years ago | 7 days ago | |
Go | C++ | |
The Unlicense | GNU General Public License v3.0 or later |
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.
go-server-core
-
Carbon Language: An experimental successor to C++
What language would you use to build a server? I've been using go for a while and have enjoyed using the different emerging frameworks and even just the standard packages.
-
Is there an issue with hosting multiple applications on 1 port through a gateway application?
That's true - there are totally unrelated projects all running under this 1 system. I suppose I could launch a series of these servers that only include pieces they need. That's easy enough here.
-
Go shoutout in the Rust Programming Book.
Oh cool, that is the case, yes. There are a lot of other issues with what I'm doing, but at least that isn't one of them. You can look at it here if you're curious but honestly I don't know how much longer I'm going to build it up before that joke from ~2018 is put down and I adopt whatever go server framework is popular now.
-
Web gateway utilizing golang plugins
Here is the main server, here is the router I made with some project specifics in mind, and here is a monster repository that is holding several sub projects that are all reachable from the gateway. Files contains various files served by the sub applications, src contains the go code that gets compiled into plugins.
-
Our policy at work - are we wrong, though?
Y-yea, me too... it's totally obvious that tomato is a restful router, right?
-
Big yikes
Well, we are on reddit. I'll take validation where I can get it. Want to criticize my shitty golang router?
crubit
-
Making C++ Safe Without Borrow Checking, Reference Counting, or Tracing GC
See also:
Thomas Neumann's current proposal for memory safe C++ using dependency tracking:
- https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2023/p27...
Google's proposal for memory safety using Rust-like lifetime analysis:
- https://discourse.llvm.org/t/rfc-lifetime-annotations-for-c/...
- https://github.com/google/crubit/tree/main/lifetime_analysis
- Will Carbon Replace C++?
-
Supporting the Use of Rust in the Chromium Project
For the people who are curious: crubit is an attempt to develop the way to seamlessly integrate C++ and Rust.
-
Crubit: C++/Rust Bidirectional Interop Tool
Please see the experimentation and proposals at https://github.com/google/crubit/blob/main/docs/lifetime_annotations_cpp.md and https://github.com/google/crubit/blob/main/docs/lifetimes_static_analysis.md
-
The Unicode Consortium announces ICU4X 1.0, its new high-performance internationalization library. It's written in Rust, with official C++ and JavaScript wrappers available.
autocxx is good, though crubit is aiming for direct bidirectional interop
-
Programming languages endorsed for server-side use at Meta
The areas you mentioned (CLI, web services, low level systems programming) are not mutually exclusive. Doing a good job on one doesn't mean something else is affected.
The folks who worked on the most popular command line argument parser (https://docs.rs/clap/latest/clap/#example) made a positive contribution that didn't detract from any other use case.
Similarly, the folks working on improving Rust for web services will also make it better for systems programming. In a blog post published today (https://blog.rust-lang.org/inside-rust/2022/07/27/keyword-ge...), they discuss keyword generics, a feature that will be equally helpful for `async` code and `const` functions evaluated at compile time.
There is already some interoperability with C++ (http://cxx.rs) and ongoing research into automating this interoperability (https://github.com/google/autocxx, https://github.com/google/crubit). Feels like there's enough effort
-
Carbon Language: An experimental successor to C++
This language was started by folks at Google. (Although it's interesting that they're publishing it under a separate github org, which suggests ambitions beyond Google's needs.) Google has a huge, performance-sensitive C++ codebase. At Google, major product teams' backends are typically written in C++, as well as common infrastructure like D (disk server), Colossus (distributed filesystem), Spanner (distributed SQL database), and Borg (cluster management). More than a few people would love for it all to be be written in Rust instead, but migration would be challenging, to say the least. I'm told people are looking into it—see Crubit for example. But AFAIK, no one's decided yet whether Google will stay with C++ for all these things, migrate some to Rust, migrate some to Carbon, and/or do something else entirely.
It's currently unclear if Rust can interop with C++ with high fidelity. For example https://docs.rs/moveit/latest/moveit/ and https://github.com/google/crubit/blob/main/rs_bindings_from_... provide functionality to use non-trivially relocatable C++ types from Rust.
What are some alternatives?
hylo - The Hylo programming language
carbon-lang - Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
go-sumtype - A simple utility for running exhaustiveness checks on Go "sum types."
DIPs - D Improvement Proposals
HVM - A massively parallel, optimal functional runtime in Rust
verdigris - Qt without moc: set of macros to use Qt without needing moc
val - A small library to bring NaNboxing to C
hack-game - it reminds me of .hack
autocxx - Tool for safe ergonomic Rust/C++ interop driven from existing C++ headers
Vale - Compiler for the Vale programming language - http://vale.dev/
cxx - Safe interop between Rust and C++