notify
pico
Our great sponsors
notify | pico | |
---|---|---|
10 | 64 | |
2,467 | 11,969 | |
3.0% | 6.8% | |
8.1 | 9.3 | |
6 days ago | 15 days ago | |
Rust | CSS | |
GNU General Public License v3.0 or later | 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.
notify
-
FIM v0.4.6 - Realtime File monitoring tool
It is a great question. We have based the development on a library called notify, kudos to https://github.com/notify-rs/notify. This library adds a layer of abstraction to each system. It implements kernel-specific hooks as you mentioned. In some cases like Audit extended data, we have developed an integration that detects changes on the Audit log file and processes the given information including a lot of information into Linux systems. We have plans to include it in Windows as well.
-
Building a static site generator in 100 lines of Rust
In order to detect files changes, we use hotwatch, a simple wrapper over notify that will allow us to save a few lines.
- Let Rust detect changes in the Markdown file and generate HTML.
-
Track what process modify file
The notify crate uses the inotify API on Linux. However, it's probably not what you want, since one of its limitations is:
-
Hey Rustaceans! Got an easy question? Ask here (48/2021)!
If you want to build this yourself, you'll want to build on something like notify - there are libraries like linemux built on top of it that will do a lot of this for you too.
-
Effectively monitoring very large number of files
I'm most well versed in Python so I started with that and eventually ended up with a POC using watchdog, but the program took more than a day and a half to traverse everything and register all of the watches. I've been trying to learn Rust for a while, and decided to perhaps use this as an excuse to try something 'real' and not just a learning exercise. I found the notify crate (https://github.com/notify-rs/notify) and basically copied their example listed on their GitHub, but even this takes about 16-18 hours to place all the watches before it starts processing events. I did not see any obvious ways to enable asynchronous or async/await code in notify, so I don't know of a way to parallelize the disk I/O with this approach.
pico
-
Concrete.css
Modern CSS stylesheets include configurability via CSS variables on the root element so maybe that's where the "framework" comes from.
Also note: This project looks like an even more minimized version of PicoCSS [1]
-
Show HN: A template for Markdown-based sites (no static site generator required)
The templates grabs Markdown file data with XMLHttpRequest and converts it to HTML with https://showdownjs.com/ . Classless styles are done with https://picocss.com/ and code block syntax highlighting is done with https://highlightjs.org/ .
GitHub repo: https://github.com/dandalpiaz/markdown-pages
-
HTML Web Components: An Example
This is exactly why I love HTMX [1] in combination with PicoCSS[2]. HTMX is just the regular html elements with ajax extensions built into the tags (it is a js library currently but they plan on lobbying to have these as default functionalities with HTML in the future) and picoCSS also works without classes so you are "trained" to use the semantic tags for the page to be rendered beautifully
-
Crafting A Minimalist Portfolio Website with SvelteKit and Pico CSS
/*! * Minimal theme switcher * * Pico.css - https://picocss.com * Copyright 2019-2023 - Licensed under MIT */ /** * Minimal theme switcher * * @namespace * @typedef {Object} ThemeSwitcher * @property {string} _scheme - The current color scheme ("auto", "light", or "dark"). * @property {string} menuTarget - The selector for the menu element that contains theme switchers. * @property {string} buttonsTarget - The selector for theme switcher buttons. * @property {string} buttonAttribute - The attribute name used for theme switcher buttons. * @property {string} rootAttribute - The attribute name used for the root HTML element to store the selected theme. * @property {string} localStorageKey - The key used to store the preferred color scheme in local storage. */ export const ThemeSwitcher = { // Config _scheme: 'auto', menuTarget: "details[role='list']", buttonsTarget: 'a[data-theme-switcher]', buttonAttribute: 'data-theme-switcher', rootAttribute: 'data-theme', localStorageKey: 'picoPreferredColorScheme', /** * Initialize the theme switcher. * * @function * @memberof ThemeSwitcher */ init() { this.scheme = this.schemeFromLocalStorage || this.preferredColorScheme; this.initSwitchers(); }, /** * Get the color scheme from local storage or use the preferred color scheme. * * @function * @memberof ThemeSwitcher * @returns {string|null} The color scheme ("light", "dark", or null). */ get schemeFromLocalStorage() { if (typeof window.localStorage !== 'undefined') { if (window.localStorage.getItem(this.localStorageKey) !== null) { return window.localStorage.getItem(this.localStorageKey); } } return this._scheme; }, /** * Get the preferred color scheme based on user preferences. * * @function * @memberof ThemeSwitcher * @returns {string} The preferred color scheme ("light" or "dark"). */ get preferredColorScheme() { return window.matchMedia('(prefers-color-scheme: dark)').matches ? 'dark' : 'light'; }, /** * Initialize the theme switcher buttons and their click events. * * @function * @memberof ThemeSwitcher */ initSwitchers() { const buttons = document.querySelectorAll(this.buttonsTarget); buttons.forEach((button) => { button.addEventListener( 'click', (event) => { event.preventDefault(); // Set scheme this.scheme = button.getAttribute(this.buttonAttribute) || 'auto'; // Close dropdown document.querySelector(this.menuTarget)?.removeAttribute('open'); }, false ); }); }, /** * Set the selected color scheme and update the UI. * * @function * @memberof ThemeSwitcher * @param {string} scheme - The color scheme to set ("auto", "light", or "dark"). */ set scheme(scheme) { if (scheme == 'auto') { this.preferredColorScheme == 'dark' ? (this._scheme = 'dark') : (this._scheme = 'light'); } else if (scheme == 'dark' || scheme == 'light') { this._scheme = scheme; } this.applyScheme(); this.schemeToLocalStorage(); }, /** * Get the current color scheme. * * @function * @memberof ThemeSwitcher * @returns {string} The current color scheme ("auto", "light", or "dark"). */ get scheme() { return this._scheme; }, /** * Apply the selected color scheme to the HTML root element. * * @function * @memberof ThemeSwitcher */ applyScheme() { document.querySelector('html')?.setAttribute(this.rootAttribute, this.scheme); }, /** * Store the selected color scheme in local storage. * * @function * @memberof ThemeSwitcher */ schemeToLocalStorage() { if (typeof window.localStorage !== 'undefined') { window.localStorage.setItem(this.localStorageKey, this.scheme); } } };
-
Why everybody speaks only about Tailwind, what happened to Boo0strap?
I personally prefer Bootstrap to Tailwind, but my favorite is https://picocss.com/
Usually, I just want decent-looking default CSS styles. The benefits of a CSS framework have diminishing returns when using frameworks with styles scoped to components (like SvelteKit/Vue/React).
The fact Tailwind removes all styles so you can't even tell a button is a button unless you add classes is annoying. If you know the class names, sometimes it's a little more convenient to add Tailwind classes, but for the most part it just clutters the HTML. And it makes it difficult to update entire "classes" of elements: you have to update each element one at a time.
-
Modern CSS Framework or Library for Static Websites?
Do you want to customize it or get something that looks decent out of the box? Consider something like Pico.css which is just a stylesheet that can even be used classless. It just styles the native HTML elements in a nice way and nothing more.
-
Getting started with Pico CSS
According to its homepage, Pico is a minimal CSS framework for semantic HTML. Pico styles the built-in HTML elements so that when you’re building a small app, you don’t need to write a lot of custom CSS.
Here, Pico CSS comes into the picture. In some ways, it is the anti-Tailwind library. Pico CSS discourages using a large number of .classes in your application. Instead, it styles the semantic HTML elements in such a way that you don’t need to write a lot of code yourself.
-
how to choose a tech stack for a personal project
For styling you could try daisyUI on top of tailwind or you could use something like https://picocss.com
-
Ask HN: How do I make a website in 2023?
I still write basic HTML, styled using any of a number of simple classless CSS templates, like Pico.
What are some alternatives?
Tailwind CSS - A utility-first CSS framework for rapid UI development.
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
Grav - Modern, Crazy Fast, Ridiculously Easy and Amazingly Powerful Flat-File CMS powered by PHP, Markdown, Twig, and Symfony
unocss - The instant on-demand atomic CSS engine.
htmx - </> htmx - high power tools for HTML
astro - The web framework for content-driven websites. ⭐️ Star to support our work!
sakura - :cherry_blossom: a minimal css framework/theme.
Hugo - The world’s fastest framework for building websites.
eleventy 🕚⚡️ - A simpler site generator. Transforms a directory of templates (of varying types) into HTML.
BareCSS - A classless CSS framework
classless-css - A list of classless CSS themes/frameworks with screenshots
WonderCMS - Fast and small flat file CMS (5 files). Built with PHP, JSON database.