xmorse

I am thinking about creating a proof-of-writing signature. Basically an editor with an "anti-cheat", you can't paste text into it. It signs your text with a public key.

Xiaomi is an amazing company

Write a function that given a long text splits it into multiple chunks of max N characters, with the splits on punctuations points or spaces when not possible

Both use AWS under the hood

Imagine being a Postgres developer and getting 1% of that while being the core technology powering all these startups

It would be cool if Zig added a .. syntax, the same way . gets a child field, .. gets the parent field

Then the code would become

```

const user: *User = n..

```

Now it's easier to understand that .. is simply getting the parent struct.

There is Mojo and Vale (which was created by a now Mojo core contributor)

Even better than RAII would be linear types, but it would require a borrow checker to track the lifetimes of objects. Then you would get a compiler error if you forget to call a .destroy() method

There is also ai-fallback [0] to automatically switch to a fallback provider in case of downtime

[0]: https://github.com/remorses/ai-fallback

My app didn't go down yesterday, this was a downtime related to internal API and some specific regions.

It's free until it isn't anymore

And then later add a script that downloads the binary from Github releases. Doesn't improve the situation with curl script haters

Dive doesn't have a JSON output, I had to use the internal API to do it.

It's a treemap graph, frontend people use it all the time to analyze a website javascript bundle size, I created this so Docker people can make smaller images more easily

Finally switched to Nvidia and already adding great value

Another pain point for me: no syntax highlighted code blocks

I see a lot of people using GitHub gists to embed code blocks for this reason, this means that writing any article code related is a pain

Edit: i think it's available now but definitely too late

I do E2E tests for the core features against a staging database and url.

This way i don't waste time with unit tests that quickly get old and no one wants to maintain and run

If you want to start a blog quickly check out Notaku [0], it can create a blog website using Notion to manage content

[0] https://notaku.so/product/blog

The hard part of building a CDN is scaling it. The best approach imo is to use fly.io to host an anycast IP (with horizontal scaling) and store cache files on disk

Fly.io also has a Grafana dashboard built in for your machines

I think SendGrid uses MailChannels to send newsletter emails and probably most other email marketing tools too

This is awesome! i was searching for a writing tool integrated into Notion just yesterday

Together with Notaku [0] i can now create blog posts and help articles much faster, choosing Notion for my websites CMS was the right idea

[0] https://notaku.so

Query memoization with optimistic updates

If you want to do the same without having to write any code there is Notaku [0].

It's a tool to easily use Notion as CMS for your docs, blog and changelog websites.

[0] https://notaku.so

Compile time speed (this is gonna come later with a full hosted compiler, without LLVM)

I would like to have basically everything in the Go `net`, `io` and `ioutil` modules (especially functions to work with streams like io.Copy)

The most annoying problem is CI, i cannot even use a private git submodule in Github Actions without creating a personal token, passing it to secret and use some git command

ZLS currently does not run any comptime code as far as i know

It would be cool to have an official Zig language server that can do it

It looks to me that the main problem of zig's async implementation is that it cannot understand if a runtime function pointer is async or not

Maybe Zig could add something to these pointer to mark them async?

Thank you for that, the submissions got restored

It would be cool to have this, but i think that adding so many features at once to the language isn't going to happen, and adding one piece at a time doesn't make sense.

Also, the parser performance will probably take a hit.