rust-cssparser
hound
rust-cssparser | hound | |
---|---|---|
5 | 10 | |
682 | 5,573 | |
1.2% | 0.6% | |
7.2 | 4.9 | |
8 days ago | 5 months ago | |
Rust | JavaScript | |
Mozilla Public License 2.0 | MIT 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.
rust-cssparser
-
Looking for this. html + css rendering through wgpu.
If you were to implement this yourself, i'd look into either swash or cosmic-text for the text rendering stack (this is one of the things you really don't want to write from the ground up). For accessibility, AccessKit has quickly become the standard for communicating with crossplatform accessibility APIs in rust GUI. lightningcss (or its lower level counterpart cssparser) are both decent options for CSS parsing. Taffy handles some of what browsers offer for a layout engine, but is still being worked on.
-
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.
- Parcel CSS: A new CSS parser, compiler, and minifier
- Can't handle cssparser's ParseError
hound
-
Code Search at Google: The Story of Han-Wen and Zoekt
The same algorithm is also used in Hound (https://github.com/hound-search/hound) though I have to say the best implementation of code search by far that I've seen is https://grep.app
You really should check it out if you haven't already. It's incredibly useful; I used it all the time. Not open source though.
- Hound: Fast code searching made easy
-
Sourcegraph is no longer Open Source
There is also Hound [8].
[8]: https://github.com/hound-search/hound
-
DockerHub replacement stratagy and options
Agreed, I already have Hound setup to search across all the different repos I pull from (bitbucket, gh, gitlab, gitea etc) but now I need to find a docker equivalent.
-
Gitlab to lay off 7% of staff
i know you're looking for first-party tools that is part of the whole package, but hound does this fantastically and is extremely easy to setup, and is ridiculously fast.
-
Ask HN: How do you search large code-base before adding a feature or fixing bug?
Especially if this is long term, this is a great tool:
https://github.com/hound-search/hound#hound
It would be great if someone integrated this with tree-sitter plus something to make the search semantics a bit smarter about usages of X:
https://www.etsy.com/codeascraft/announcing-hound-a-lightnin...
Screenshots:
https://jaxenter.com/hound-go-react-code-search-engine-15008...
Another trick I use for Java: javap all the Enums out of the compiled artifacts; these indicate weird things like "modes" that you can use to start asking questions relevant to the domain. Like "why are there four ways to reprice an invoice" or finding the "types" of fees or w/e in a billing system. (assuming enum classes are used)
-
Parcel CSS: A new CSS parser, compiler, and minifier
Nice too that it's a compiled language, so you get the end tool in a nice static binary. As a non-Node dev, I hate the experience of hacking on some project and having to install a giant pool of NPM stuff just run some minifier or linter. Hound is an example of this— the guts of the project are golang, but it has a frontend that uses webpack, jest, etc: https://github.com/hound-search/hound
Which is fine, I guess; definitely use the right tool for the job. And maybe Node developers hate finding my Python projects and needing to set up a virtualenv to run them in. But all the same, I approve a direction where more of this kind of tooling is available without a build-time Node dependency.
- Grep.app: search across a half million Git repos
-
Ask HN: What are you using to introspect your code base
[2] https://about.sourcegraph.com/
[3] https://oracle.github.io/opengrok/
[4] https://github.com/hound-search/hound
What are some alternatives?
lightningcss - An extremely fast CSS parser, transformer, bundler, and minifier written in Rust.
opengrok - OpenGrok is a fast and usable source code search and cross reference engine, written in Java
swc - Rust-based platform for the Web
codesearch - Fast, indexed regexp search over large file trees
cosmic-text - Pure Rust multi-line text handling
Gitlab CI - GitLab CE Mirror | Please open new issues in our issue tracker on GitLab.com
css-modules - Documentation about css-modules
septum - Context-based code search tool
icss - Interoperable CSS — a standard for loadable, linkable CSS
dropcss - An exceptionally fast, thorough and tiny unused-CSS cleaner
libjs-test262 - ✅ Tools for running the test262 ECMAScript test suite with SerenityOS's JavaScript engine (LibJS)
the_silver_searcher - A code-searching tool similar to ack, but faster.