completions VS ideas2

I am building _exactly_ the same thing for Playwright over at https://ray.run/. I think this is the future of writing tests no doubt. Planning to launch next week.

Note: Use page.goto('/') and have "baseURL": "http://ray.run" set in the playwright.config.ts file for concise code.

Your website https://ray.run/ does have that nostalgic early 2000s vibe, which is cool! Regarding the search functionality, you might want to explore open-source alternatives to Algolia.

Projects like Elasticsearch, Solr, or even using Google Custom Search can provide search capabilities without the cost. They might require a bit more setup and maintenance, but they can be budget-friendly options for a free community.

In case you need help or assistance with your project, feel free to contact us! https://www.ratherlabs.com

* Most of the pages I use are rendered at the request time, rather than build time

For context, this is the website https://ray.run/

Ensuring in-article hover definitions for terms on the https://ray.run/ blog.

I have added a zone to Cloud DNS (GCP) for https://ray.run/

I updated completions library to allow statically typed responses:

import { type Browser, chromium, test as base } from '@playwright/test'; import getPort from 'get-port'; import { playAudit } from 'playwright-lighthouse'; export const test = base.extend<{}, { browser: Browser; port: number }>({ browser: [ async ({ port }, use) => { const browser = await chromium.launch({ args: [`--remote-debugging-port=${port}`], }); await use(browser); await browser.close(); }, { scope: 'worker' }, ], port: [ // eslint-disable-next-line no-empty-pattern async ({}, use) => { // Assign a unique port for each playwright worker to support parallel tests const port = await getPort(); await use(port); }, { scope: 'worker' }, ], }); test.describe('Accessibility Testing with Lighthouse', () => { test('should pass the Lighthouse accessibility audit', async ({ page, port, }) => { await page.goto('https://ray.run/'); await playAudit({ page, port, thresholds: { accessibility: 100, }, }); }); });

import { test } from '@playwright/test' test.beforeEach(async ({ page }) => { await page.goto('https://ray.run/login') await page.fill('#username', 'admin') await page.fill('#password', 'password123') await page.click('#login-button') expect(await page.url()).toContain('/dashboard') }) test('should display user profile', async ({ page }) => { await page.click('#profile-button') expect(await page.textContent('body')).toContain('Admin User') }) // Other tests...

My blogging/journalling setup is simple.

I just use GitHub. I just rely on the default repository view on GitHub.com

I create a README.md and add markdown headings to the bottom or to the top (bottom if its a journal, top if it's a blog) and then when I get to 100-800 I create a new repository and repeat.

https://github.com/samsquire/ideas (2013)

https://github.com/samsquire/ideas4

https://github.com/samsquire/ideas3

https://github.com/samsquire/ideas2

Thanks for posting this Ask HN question.

I journal ideas and thoughts about computers and software. I am interested in software architecture, parallelism, async, coroutines, database internals, programming language implementation, software design and the web.

https://github.com/samsquire/ideas (2013)

https://github.com/samsquire/ideas2

https://github.com/samsquire/ideas3

https://github.com/samsquire/ideas4 <-- this is recent but needs editing

https://github.com/samsquire/ideas5 <-- this is what I'm working on now

https://github.com/samsquire/startups

https://github.com/samsquire/blog <-- thoughts I want to write about, but incomplete

I use README.md on GitHub and create a heading at the bottom for each entry. I use Typora on Windows or the GitHub web interface to edit.

[3]: https://github.com/samsquire/ideas2#5-open-demand-mapping-an...

Thanks for this.

I love the idea of breaking up a flow into separately scheduled but still linear message flow.

I wrote about a similar idea in ideas2

https://github.com/samsquire/ideas2#84-communication-code-sl...

The idea is that I enrich my code with comments and a transpiler schedules different parts of the code to different machines and inserts communication between blocks.

I read about how Zookeeper algorithm for transactionality and robustness to messages being dropped, which is interesting reading.

https://zookeeper.apache.org/doc/r3.4.13/zookeeperInternals....

How does Mats compare?

LMAX disruptor has a pattern where you split up each side of an IO request into two events, to avoid blocking in an handler. So you would always insert a new event to handle an IO response.

I am more likely to journal and blog if the friction to creating a post is as simple as opening a document and writing. The important part of journalling or note software is that you actually create notes. I did use Hetzner to run a Wordpress blog but it had an overhead of server expenses and keeping Wordpress up-to-date.

I don't want my data trapped in a proprietary system where it is difficult to export, so I use plaintext. I looked into Publii [1] but I prefer my current plaintext setup. Today I journal software ideas, computer ideas, startup ideas and community ideas on GitHub in the open, as README.md files. My journal is all public on GitHub at the following links. There are over 550+ journal entries, I am sure you shall enjoy them.

https://github.com/samsquire/ideas

https://github.com/samsquire/ideas2

https://github.com/samsquire/ideas3

https://github.com/samsquire/ideas4

https://github.com/samsquire/startups

https://getpublii.com/