Had a recent Show HN at <a href="https://news.ycombinator.com/item?id=36194473">https://news.ycombinator.com/item?id=36194473</a>
Saving a few clicks for readers:<p>Project page: <a href="https://sql.ophir.dev/" rel="nofollow">https://sql.ophir.dev/</a><p>GitHub project: <a href="https://github.com/lovasoa/SQLpage">https://github.com/lovasoa/SQLpage</a><p>It is built in Rust, and the project website is built in SQLPage: <a href="https://github.com/lovasoa/SQLpage/tree/main/examples/official-site">https://github.com/lovasoa/SQLpage/tree/main/examples/offici...</a><p>As a data analyst and witnessing the enthusiasm of the presenter makes me want to test this!
It’s interesting to me how far you have pushed the SQL language in this framework, such that it truly is “SQL only”.<p>The challenge as I see it with enabling analysts to build websites is that you need to build abstractions to get from familiar (SQL, yaml) - the language of analytics, to new (HTML, CSS, JS) - the language of the web browser<p>As one of the maintainers of Evidence (<a href="https://evidence.dev">https://evidence.dev</a>), one of the things I’ve often considered is how accessible our syntax is to analysts. Our syntax combines SQL and Markdown, with MDX style components e.g. <Component/><p>The </> are inherently webdev-ey, and I do think they put off potential users.<p>On the flip-side, by adhering to web standards, you get extensibility out of the box, and working out what to do is just a Google search away.<p>Anyway, thanks for the thought provoking piece.
Well, I've watched most of the video.
IMHO it's a step back.
You know separation of concerns, clean templates, don't mix presentation and data.
Well, this is the extreme in the opposite direction.<p>Instead of using proper <component>s you're using
"select 'Label' as text".<p>No. Even if the guy is sympathetic, keep presentation separate.
If it had markup mixed with SQL queries, ok, sure.<p>But this is going too much in the other extreme direction.<p>I not just would like but need to have control over my presentation.
And with doing pseudo SQL queries this is too complicated vs regular markup or something like vue etc.<p>Only upside of this is performance and/because it's SSR