pocl
bestmotherfucking.website
pocl | bestmotherfucking.website | |
---|---|---|
3 | 24 | |
60 | 816 | |
- | - | |
0.0 | 3.3 | |
over 8 years ago | 9 months ago | |
HTML | ||
- | Creative Commons Zero v1.0 Universal |
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.
pocl
- Tree-shaking, the horticulturally misguided algorithm
-
Web bloat impacts users with slow devices
https://github.com/avodonosov/pocl
The unused javascript code can be removed (and loaded on demand). Although I am not sure how valuable that would be for the world. It only saves network traffic, parsing time and some browser memory for compiled code. But js traffic in the Internet is neglidgible comparing to, say, video and images. Will the user experience be signifiqanty better if browser is the saved from the unnesessary js parsing? I don't know of a good way to measure that.
-
Red and blue functions are a good thing
> for such a small piece of work
Don't take the example too literally, some functions calls can be here.
Running computations in parallel is often valuable. Or run computations in parallel with waiting for external resource - why does not the code in the article compute something while waiting for a, b and c?
Anyways, if async functions are so good, why not have all functions async?
The article says this a kind of "documentation" that tells you what functions can wait for some external data and what functions are "pure computation". If it was so, it would be OK. Such a documentation could be computed automatically based on the called function implementations and developer is hinted: "these two functions you call are both async, consider waiting for both in parallel". In reality, the async / await implementations prevent the non-async functions from becoming async without code change and rebuild. This restriction is just a limitation of how async / await is implemented, not something useful.
As other commenter says, the article "embraces a defect introduced for BC reasons as if it's sound engineering. It really isn't."
When my code is called by a 3rd party library, I can not change my code to async. That's the most unpleasant property of today's async / await. What yesterday was quick computation tomorrow can become a network call. For example, I may want to bodies of rarely used functions to only load when called first time (https://github.com/avodonosov/pocl).
The article suggest we have to decide upfront, at the top-level of the application / call stack, which parts can be implemented with as waiting blocks and which should never wait for anything external. This is not practical.
> It's almost always faster to do them in parallel if possible.
bestmotherfucking.website
- Web bloat impacts users with slow devices
-
Memory usage of egui
That's because the web is a pig, not because using 54 MB to do nothing is fine. Chrome uses 18 MB just walking through the parking lot.
- Many motherf-ing websites
-
No CSS Club – because no JavaScript was not hardcore enough
https://bestmotherfucking.website/ is my favorite (https://thebestmotherfucking.website/ is an abomination).
- The necessity of webpage animations?
- Looks great on my machine
- This is how an important Linux kernel patch cover letter SHOULD be written, please read
-
CS Professor Websites Be Like
An alternative one
- Dont you miss old sites?
-
All you may need is HTML
I was happy to see someone finally referred to the motherfucking websites.
On the other hand, I was disappointed to see the unique one of those I think it is worth to follow the advice [1] was not cited.
For curiosity reasons, I found out about [1] on a well-known website [2] that definitely puts content in front of presentation, even though I like their website's design.
[1]: https://bestmotherfucking.website/
[2]: https://suckless.org/sucks/web/
What are some alternatives?
unison - A friendly programming language from the future
perfectmotherfuckingwebsite - 🖕 And it’s really more fucking perfect than the last guy’s.
lawvere - A categorical programming language with effects
govuk-design-system - One place for service teams to find styles, components and patterns for designing government services.
annotate - Annotate text and publish it on the web
digital-gardeners - Resources, links, projects, and ideas for gardeners tending their digital notes on the public interwebs
caniuse - Raw browser/feature support data from caniuse.com
consumerfinance.gov - Django project protecting American consumers
vike - 🔨 Like Next.js / Nuxt but as do-one-thing-do-it-well Vite plugin.
govuk-components - Lightweight Ruby on Rails components for developing with the GOV.UK Design System.
browserslist - 🦔 Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-preset-env
astro - The web framework for content-driven websites. ⭐️ Star to support our work!