Reminds me of jasonette (https://jasonette.com/) ...

Whether it is JSON or XML, what I particularly like about both approaches is that both are fundamentally HATEOAS (https://en.wikipedia.org/wiki/HATEOAS)

Wow Adam! I owe you a drink! I have been looking for something like intercooler + sse / mercure. What a great example of NoJS!

I thought I was stuck with just amp (https://amp.dev) as an option. Please ignore the nitpickers saying it is technically not zero lines of js.

If the app can be developed without writing js, it can be considered nojs. The list here (http://markapp.io) is based on that principle.

Please please keep on chronicling your adventures. So many questions but I will take the weekend to explore properly.

I totally agree, the benefit of NoJS comes from not needing to write custom code in order to implement a feature. Thanks for the link to that list of other NoJS libraries. If you have any questions about Intercooler, please leave a comment on the post.

Only windows? Seriously?

You should post on r/selfhosted (https://www.reddit.com/r/selfhosted/)

Been waiting for something like this for a long time ...

Only thing I would change is use sqlite rather than mysql. That way your data is in a single file that is easily portable.

It's using Doctrine so the configuration should be easy to change in the .env file. Update the "DATABASE_URL" line to...

`DATABASE_URL="sqlite:///%kernel.project_dir%/var/app.db"`

And point it to the correct directory where your file is located.

I can't edit, but I was hoping the backticks would create a code block, so please ignore those backticks. Also, more details can be found on their documentation [0].

[0] https://symfony.com/doc/current/doctrine.html#configuring-th...

  DATABASE_URL="sqlite:///%kernel.project_dir%/var/app.db"

Use two or more spaces at the start of the line: https://news.ycombinator.com/formatdoc

That's helpful, thank you.

I mean, you get a similarly portable file with

mysqldump -u username -p database_name > data-dump.sql

and you can load that dump back in with

mysql -u username -p new_database < data-dump.sql

I love sqlite3 for the ease of setting up, and the ability to use in any device or environment immediately, but I'll go to a more featured database like postgres or mysql for larger projects, or for speed. This projects seems to benefit with using mysql to be able to secure the database with a password, as well as the ability to have a timestamp type (but the project saves timestamps with a string rather than a datatime except for user login timestamps so ¯\_(ツ)_/¯)

Hey thanks for that info - I will check that subreddit. I will stick to mysql. I agree that it would be more portable but I dont really intend to take it with me anywhere.

Brave doesn't block first party cookies by default IIRC, so that's not hard to imagine.

Has anyone used web workers at the edge ... like with cloudflare workers?

Despite the similar naming, "Web Workers" is a specific browser API that has nothing to do with "the edge" or any server-side thing.

Point is well taken. I have not tried cloudflare workers yet. It seemed like at least the architecture was the same. But I guess you would not have access to the full browser API. It seems like you can still play around with request / response side of things though.

Cloudflare Workers is so-named because it uses the same API as Service Workers, which are one kind of Web Worker. That said, Cloudflare Workers currently implements only a subset of the APIs that are normally available in the browser, though missing APIs are being added all the time.

So, your understanding is basically correct.

(I'm the tech lead for Cloudflare Workers.)

Yes @dassurma. But web workers are not everything. Your own blog post does not score 100 : https://developers.google.com/speed/pagespeed/insights/?url=... And those issues are not necessarily addressed with web workers. Good basic static design matters too.

I never claimed that Web Workers are the silver bullet that will absolve us from all our problems. On the contrary, I don’t think such a silver bullet will ever exist.

I am saying that we should be using web workers to keep the main thread free. That is completely orthogonal to good static design, proper bundling, right caching headers, code splitting, asset hashing etc etc.

I agree with you on keeping the main thread free. What are your thoughts on WASM via workers?

We are using loads of Wasm in Workers in https://squoosh.app

Since Wasm is synchronous, I’d say it should almost always be run in workers except if the module needs access to some main-thread-only API.

They scored a 96. There is exactly one issue, and it’s esoteric in my opinion.

Even G Suite might be pushing it... if there is not even email!

A lot of people expected search engine. I did too. But I also expected something about privacy. I presume that would be the main impetus for a lot of people to switch. Make sure you get the privacy / encryption done right (as in even Bloom would not be able to access your documents in the clear). Better privacy is what made search engine alternatives grow in popularity (duckduckgo, startpage, or qwant in france). It would not be any different for G Suite.