raytracing
vale
raytracing | vale | |
---|---|---|
8 | 46 | |
- | 4,197 | |
- | 1.5% | |
- | 9.3 | |
- | 5 days ago | |
Go | ||
- | 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.
raytracing
- Ray Tracing in One Weekend Book Series
-
What are the best textbooks/resources for learning graphics programming practically in 2023?
I’m getting started too in graphics programming (web developer here) and I’ve started with the Raytracing in One Week-end, I find it to be great (I use ChatGPT along the tutorial to exchange and ask questions when I struggle). Other than that I also bought the OpenGL bible book and the book Computer Graphics from Scratch that you can both find on Amazon, they’re really great.
-
C++ Project Ideas?
Nope, because they are easy to find. Here they are on GitHub: RayTracing/raytracing.github.io: Main Web Site (Online Books)
- Ray Tracing in One Weekend
-
Changelog best practices
At https://github.com/RayTracing/raytracing.github.io, we have a master branch that serves as our primary release branch, and then three coordinated development branches: dev-patch, dev-minor, and dev-major (according to the SemVer https://www.semver.org/ change level). You could develop on all three level simultaneously, merging according to your next planned release (whether it's a patch, minor, or major release). In practice, we tend to figure out what the next release level will be, and then just develop on that branch. For example, we're working on a major release right now (v4.0.0), so all development work is going into our dev-major branch. Accordingly, we try to keep the CHANGLOG up to date as we go (see https://github.com/RayTracing/raytracing.github.io/blob/dev-major/CHANGELOG.md).
-
help, where did i go wrong in raytracing in one weekend?
I have now had a brief look at the repository for the book and see that there is work on a version 4 that may address some of the issues. Since you appear to be contributing I believe this issue covers the incorrect images for those sections.
-
How I Wrote My Book
Very cool. I co-edit Peter Shirley's _Ray Tracing in One Weekend_ (https://raytracing.github.io/) and have taken a similar approach, though with a different toolset. At some point if I find the time, I'll write up a similar article on our approach and what we've learned. Our books are open-sourced on GitHub (https://github.com/raytracing/raytracing.github.io), and we also use GitHub to host our books.
Basically, we use Markdeep (https://casual-effects.com/markdeep/), a _very_ powerful Markdown implementation with a bunch of built-in features. The killer feature is that with a handful of boilerplate lines (UTF-8 declaration at the top, and JavaScript loader at the bottom), you get content that automatically self-transforms in the browser into a full HTML document. This eliminates any build step, and means you can treat it as you would any other HTML file, with optional CSS and other features. It also bundles in a LaTeX engine, ASCII diagram rendering, and a whole host of other features. If you look at the three ray tracing books, you can see how simple the source is, and how pleasing the final rendering.
Check out the books and the GitHub repo — it's a _great_ way to quickly and easily pound out a web book.
-
Raytracing In One Weekand (and in Rust)
If you want, you can add it to the list! https://github.com/RayTracing/raytracing.github.io/wiki/Implementations
vale
- Software Technical Writing: A Guidebook [pdf]
- Grammarly editor writing service are malfunctioning
- Vale.sh – A Linter for Prose
- Ask HN: Best tool to proof-read technical documentation?
- Val, a high-level systems programming language
-
Common Bugs in Writing
Vale is an OSS tool that you can use as a "prose linter" with many of these rules. You can also write your own rules. Together with a spellchecker its a good replacement for proprietary tools like grammarly.
- https://github.com/errata-ai/vale
-
Just Simply – Stop saying how simple things are in our docs
> Write in US English with US grammar. (Tested in British.yml.)
heh, that was funny but it turns out the file is a list of British words checked using Vale, which I just learned existed: https://github.com/errata-ai/vale#readme (MIT)
Also, another TIL is that the "e" version of gray is British https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/.vale... I had previously erroneously assumed they were just one of those quirks of English (which, I guess is still true but it is less random than I thought)
-
Tools that enforce/promote corporate standards?
Off the top of my head, Vale and Acrolinx.
-
Over 60% of Writers Already Use AI in Their Writing Workflow
I have recently thought of feeding the suggestions from Vale (https://vale.sh/) into an LLM along with your writing. Currently I just simply ask an LLM to take what I wrote and put it into a more "active voice". I then manually edit my writing to make it more "active" if I choose -- I do not just publish LLM generated content unaltered.
Note: I did not ask an LLM for this comment.
-
What terminal apps are you using?
vale to spell check and enforce writing style on my articles
What are some alternatives?
LearnOpenGL - Code repository of all OpenGL chapters from the book and its accompanying website https://learnopengl.com
proselint - A linter for prose.
computer-graphics-from-scratch - Text, diagrams, and source code for the book Computer Graphics from scratch.
lsp-grammarly - lsp-mode ❤️ grammarly
tinyraytracer - A brief computer graphics / rendering course
nvim-lspconfig - Quickstart configs for Nvim LSP
rust_rayweek - implementation of ray tracing in one weekend in rust.
write-good - Naive linter for English prose
build - Source code and build system used to generate the book Hands-on Scala Programming
markdownlint - Repository for the markdownlint-mdl-action Github Action
vulkan-guide - Introductory guide to vulkan.
remark-lint - plugins to check (lint) markdown code style