edweis

Koa is a backend API library and is independent of your SPA front end tech.

It is still maintained (last commit 2 months ago) and yields are deprecated in favor of promises now.

They am even removing generators in v3

I did start several small projects and always used koa without reconsidering it.

We are using Koa in production, and the library is still being maintained.

IMH, the upside is that it's a light abstraction of the node's HTTP request. All extensions are provided in different packages (unlike express).

The downside is that you need to set up the basics (like routers[0]) that are out-of-the-box.

[0] https://www.npmjs.com/package/koa-router

Here it is, 1907: https://fr.wikisource.org/wiki/Essais/%C3%A9dition_Michaud,_...

EDIT: my bad, this is not modern French

Great interface. I love the fact we can use Google Sheet to do the math.

I am not sure how feasible it is, but can't SQLite be partially rewritten step by step on the main branch instead of being forked?

As the article mentioned, a complete rewrite will not be as stable as the original.

TLDR:

   How Do We Fix the Rulebook? My first answer is: I don't know!

- Having the card background the same colour as the website background is quite deceptive. It takes more effort to distinguish the content from the container.

- As the comment says, rounded buttons make the website too playful and reduce the clickable space.

- I am glad they have the dark theme; however, when navigating services that are using the old theme, we get a surprising flash of bright light.

The website is so legible I want to read it.

Zed is great. But as long as they don’t support eslint properly, it’s a turn down for me and my organization.

It's the first time I've seen an advertisement for Ubuntu. Are they getting ready to get new users dissatisfied by Apple's AI?

When returning an error, you can fill the input values in your HTML response.

Indeed the most pleasant UX is to set an additional validation logic on the client side and I don’t think this should the go-to solution.

The best native HTML validation is server-side validation.

The only downside: the user has to wait 300ms.

> A password with 327 bits of entropy is nearly impossible to crack even if you burn the whole observable universe trying to do so.

This is exactly the question I was asking me when starting the article, and it is answered perfectly.

We would love a write up about your findings.

Seclist actually has a similar password "correct-horse-battery-staple" in one of their dictionary.

    curl https://raw.githubusercontent.com/danielmiessler/SecLists/refs/heads/master/Discovery/DNS/dns-Jhaddix.txt | grep "horse-battery-staple"

For what reason should we move from SNS/SQS to RabbitMQ? Our SaaS processes ~20 events/second.

> I'm always a fan of 'bring your own key' (BYOK) approaches.

"Bring your own key" has the same amount of syllables as "BYOK"

Looking at the source code, I have never seen so many files for such a simple HTML page.

Any has experience moving from React to LitJs + Haunted?

I would say it is a convenient way to explain their technical limitation

It is ok to let some fire burn.

Say no more often, and focus on the core of your business.

Using the same device,Fastmail never asks for a password except when doing sensitive actions (like adding an email account).

There are a lot of words here, this is an SEO bait, rather than a product update.

Wait, so if I open my MacBook it is still under warranty ?

I came to the comment section to say that.

What is n8n ?

Similar and also very neat: https://luna-park.app/

Marvelous. I spent an hour to understand the code and play with it. Here is a live implementation: https://particules.kapochamo.com/index.html

There are some articles marked as "Artifact destroyed", does it mean that the original document is lost forever? I see there are missing on another website [0]

[0] https://avalon.law.yale.edu/ancient/hamframe.asp