MSEdgeExplainers
hound
MSEdgeExplainers | hound | |
---|---|---|
18 | 10 | |
1,255 | 5,573 | |
1.1% | 0.6% | |
8.1 | 4.9 | |
4 days ago | 6 months ago | |
HTML | JavaScript | |
Creative Commons Attribution 4.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.
MSEdgeExplainers
- Microsoft Edge Side Panel API
-
Tether elements to each other with CSS anchor positioning
The spec is a W3C CSS working group draft: https://drafts.csswg.org/css-anchor-position-1/
It looks like less of a Chrome thing and more of an Edge thing? The Intent to Prototype [1] links to an Edge explainer [2] with Microsoft authors. It doesn't look like anyone has asked Mozilla for a position yet [3] but I expect if they get positive signals from web developers (us!) that will be soon.
[1] https://groups.google.com/a/chromium.org/g/blink-dev/c/vsPdd...
[2] https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/...
[3] https://github.com/mozilla/standards-positions/issues?q=anch...
- Make your design compatible with foldable device
-
HTML document subtitles?
Read the explainer here
- More than “Just a web app”
-
What's New In Microsoft Edge Devtools?
You can learn more about Focus Mode in this Edge explainer document.
-
Parcel CSS: A new CSS parser, compiler, and minifier
For a spec about a browser feature, "getting it" can mean a few different things.
1. Understanding the purpose of the feature ("why/when would I use this?")
2. Understanding how to implement the feature
3. Understanding how to use the feature
4. Understanding the feature's "corner cases" (surprising implications, cases where it doesn't do what you'd expect, etc.)
5. Understanding why the feature works the way it does (instead of some other way)
Most of the web specs really only explain how to implement a feature, and even then, they're not great at that, because they do such a poor job at explaining the purpose of the feature.
Assuming that you, like most of us, aren't working on implementing a browser, that means that web specs are mostly unhelpful to you. It's almost completely beyond the purpose of a spec to teach you how to use a feature, what its corner cases would be (which are often unknown at the time a spec was written), and why the specification says what it says.
This is an area where the web spec community has made some improvements in recent years. Nowadays, it's understood that new proposed specifications shouldn't just provide a specification, but also a separate "explainer" document, whose purpose is to communicate #1 (the purpose of the feature), and also persuade the other browser vendors to implement the feature. ("This will be really cool, and here's why…")
At a minimum, specs nowadays often include a non-normative "Motivation" section, as the CSS Nesting spec does. https://www.w3.org/TR/css-nesting-1/ I you'll find that you can "get" that spec much better than you can the CSS OM spec https://www.w3.org/TR/cssom-1/ which is old enough to buy alcohol and doesn't include a "Motivation" section.
You can often find explainer docs linked off of https://chromestatus.com/ e.g. https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/... I think you'll find that explainers are 10000% better for learning features than specs are. (They typically even discuss #3, #4, and #5, as they typically discuss alternative rejected approaches.)
-
Introducing transparent ads in Microsoft Edge Preview
Transparent ads are enabled through ad providers joining the Transparent Ads Provider program. More info on the program and the requirements for providers here - https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/TransparentAds/Program-Overview.md
-
The strangely difficult problem of drawing a box around text
Not necessarily for a Swift project, but your experience makes me wonder about the current web API for highlighting spans of text.
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/...
Complicated...
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?
dropcss - An exceptionally fast, thorough and tiny unused-CSS cleaner
opengrok - OpenGrok is a fast and usable source code search and cross reference engine, written in Java
ngx-foldable - Angular library to help your build dual-screen experiences for foldable or dual-screen devices
codesearch - Fast, indexed regexp search over large file trees
react-foldable - A set of components to help you work with foldable screens
Gitlab CI - GitLab CE Mirror | Please open new issues in our issue tracker on GitLab.com
Tailwind CSS - A utility-first CSS framework for rapid UI development.
septum - Context-based code search tool
surface-duo-photo-gallery - This repo is an Angular re-implementation of the Surface Duo Photo Gallery sample
lightningcss - An extremely fast CSS parser, transformer, bundler, and minifier written in Rust.
rust-cssparser - Rust implementation of CSS Syntax Level 3