libjs-test262
bstr
libjs-test262 | bstr | |
---|---|---|
4 | 10 | |
28 | 743 | |
- | - | |
1.9 | 6.7 | |
10 months ago | 2 months ago | |
Python | Rust | |
MIT License | 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.
libjs-test262
-
We're building a browser when it's supposed to be impossible
Linus Groh of LibJS is an Invited Expert in TC39: https://linus.dev/posts/road-to-working-on-serenityos-and-la...
ECMAScript conformance test results looking good, 87-88% passing at the moment: https://libjs.dev/test262/
-
Ladybird Web Browser – SerenityOS LibWeb Engine with a Qt GUI
this is a qt frontend (definitely works on linux) for the serenityos browser engine, libweb.
this is a new, from-scratch implementation of both a modern html/css layout engine and a javascript runtime.
see https://libjs.dev/test262/ for ecmascript conformance tests.
the browser engine is far from finished but is able to display moderately complex pages like github.
it's always exciting to see a completely new web engine running in conventional environments like linux!
-
Show HN: We launched a new web browser
> Our JavaScript engine is decently mature, test262 score tracked here: https://libjs.dev/test262/
In a few years when they have achieved feature parity with Chromium or at least Safari we can discuss this again, but for now it's not ready for real life use.
-
LibJS JavaScript Engine
See https://github.com/linusg/libjs-test262 for an example, specifically the CMake files and `src/main.cpp`.
The separate website is just to have a nice & short link to the test262 graph and whatever else we'll put there eventually; and also because it's built/deployed in a slightly different way than the main serenityos.org website.
bstr
-
We're building a browser when it's supposed to be impossible
Libraries for a lot of this stuff exist (albeit in many cases not very mature yet):
- https://github.com/pop-os/cosmic-text does text layout (which Taffy explicitly considers out of scope)
- https://github.com/AccessKit/accesskit does accessibility
- https://github.com/servo/rust-cssparser does value-agnostic CSS parsing (it will parse the general syntax but leaves value parsing up to the user, meaning you can easily add support for whatever properties you what). Libraries like https://github.com/parcel-bundler/lightningcss implement parsing for the standard css properties.
- There are crates like https://github.com/BurntSushi/bstr and https://docs.rs/wtf8/latest/wtf8/ for working with non-unicode text
We are planning to add a C API to Taffy, but tbh I feel like C is not very good for this kind of modularised approach. You really want to be able to expose complex APIs with enforced type safety and this isn't possible with C.
-
Chunking strings in Elixir: how difficult can it be?
As the author of bstr and also the regex implementation that bstr uses to implement word breaking, it is linear time.
NSFL: https://github.com/BurntSushi/bstr/blob/86947727666d7b21c97e...
-
A byte string library for Rust
OsStr uses WTF-8 on Windows, and just represents the raw underlying bytes on Unix.
Byte strings can be WTF-8. They can be anything. The problem is that there is no real way to (easily) get the underlying WTF-8 bytes of an OsStr on Windows. So there's no free conversion to and from byte strings.
I wrote more about this in the bstr docs (and don't miss the link to os_str_bytes): https://docs.rs/bstr/latest/bstr/#file-paths-and-os-strings
I'd be happy to answer more questions if you have them. :-) https://github.com/BurntSushi/bstr/discussions
-
Where is the `str` struct/primitive defined ? I am learning Rust, so don't shoot please :).
Check out bstr, which does this exact thing for its BString and BStr types.
-
Tips when porting C++ programs to Rust
Currently slated for next Monday: https://github.com/BurntSushi/bstr/issues/40
- bstr 1.0 request for comments
-
Let's Stop Ascribing Meaning to Code Points (2017)
This is just an FYI. I don't mean to say much to your overall point, although, as someone else who has spent a lot of time doing Unicode-y things, I do tend to agree with you. I had a very similar discussion a bit ago.[1]
Putting that aside, at least with respect to grapheme segmentation, it might be a little simpler than you think. But maybe only a little. The unicode-segmentation crate also does word segmentation, which is quite a bit more complicated than grapheme segmentation. For example, you can write a regex to parse graphemes without too much fuss[2]. (Compare that with the word segmentation regex, much to my chagrin.[3]) Once you build the regex, actually using it is basically as simple as running the regex.[4]
Sadly, not all regex engines will be able to parse that regex due to its use of somewhat obscure Unicode properties. But the Rust regex crate can. :-)
And of course, this somewhat shifts code size to heap size. So there's that too. But bottom line is, if you have a nice regex engine available to you, you can whip up a grapheme segmenter pretty quickly. And some regex engines even have grapheme segmentation built in via \X.
[1]: https://github.com/BurntSushi/aho-corasick/issues/72
[2]: https://github.com/BurntSushi/bstr/blob/e38e7a7ca986f9499b30...
[3]: https://github.com/BurntSushi/bstr/blob/e38e7a7ca986f9499b30...
[4]: https://github.com/BurntSushi/bstr/blob/e38e7a7ca986f9499b30...
-
os_str_bytes now has string types!
This is a great idea. I realize the find implementation is not ideal and have considered bringing in an optional dependency to improve performance. I remembered bstr using two-way search, so I was wondering if depending on the full crate for searching would be worthwhile, but I see that changed. Thanks for the tip!
-
What you don't like about Rust?
Fun little nit-pick that does not detract from your overall point: you can actually count graphemes with a regex and that's exactly what bstr does. :-)
What are some alternatives?
rust-cssparser - Rust implementation of CSS Syntax Level 3
miniserve - 🌟 For when you really just want to serve some files over HTTP right now!
vimium - The hacker's browser.
tonic - A native gRPC client & server implementation with async/await support.
beacon - Beacon browser for desktop
rust-memchr - Optimized string search routines for Rust.
tersenet - A new type of JavaScript-free light-weight fast browser built on rst and web assembly. Does not actually exist.
cargo-geiger - Detects usage of unsafe Rust in a Rust crate and its dependencies.
serenity - The Serenity Operating System 🐞
rust - Empowering everyone to build reliable and efficient software.
wpt - Test suites for Web platform specs — including WHATWG, W3C, and others
rust-semverver - Automatic checking for semantic versioning in library crates