I Don't Want to Teach My Garbage DSL, Either
1–10 of 54 posts
Re: I Don't Want to Teach My Garbage DSL, Either
#2Unrelated to the article, just found it interesting how he’s using github to literally auto generate his blog via their md-to-html thingy, and issues for comments.
Re: I Don't Want to Teach My Garbage DSL, Either
#3Unrelated to the article, just found it interesting how he’s using github to literally auto generate his blog via their md-to-html thingy, and issues for comments.
It's not a bad idea, aside from putting your blog entirely on a third party like github. Utterances is the alternative to disqus that uses github issues.[0]
Personally I think the best solution is using a static site generator like Hugo or Zola to control how you generate your content, and then host that using Caddy + Docker. A database is overkill.
You can also use caddy's git plugin to kick off automatic builds build from any git repo, not just a github one. It just needs to support webhooks, I believe.[1]
[0]: https://utteranc.es/
Re: I Don't Want to Teach My Garbage DSL, Either
#4If you’re developing a DSL which is just a query language, you are reinventing the wheel, and you should ask yourself if any benefit of your language over SQL is worth the effort of all your users to learn your new query language. It may be worth it of your data can not be usefully be modeled by tables; e.g. document query languages like XQuery and even simple XPath are useful and can not be easily replaced with SQL.
Re: I Don't Want to Teach My Garbage DSL, Either
#5Then again, REST/RPC are query languages in their own right.
How would one go about securing this thing anyways?
(I agree with the basic sentiment, but find it somewhat unrealistic)
Re: I Don't Want to Teach My Garbage DSL, Either
#6Then again, REST/RPC are query languages in their own right. How would one go about securing this thing anyways? (I agree with the basic sentiment, but find it somewhat unrealistic)
Do anyone here expose real sql querying capabilities to your users?
Re: I Don't Want to Teach My Garbage DSL, Either
#7Then again, REST/RPC are query languages in their own right. How would one go about securing this thing anyways? (I agree with the basic sentiment, but find it somewhat unrealistic)
Do anyone here expose real sql querying capabilities to your users?
In a dark past my company did: because these users were paying CMS users, they would not try to hack things, but rather because of the power of SQL and their lack of knowledge, they broke a lot which required backups to restore. We are talking mid 90s and Perl CGI scripts.
Re: I Don't Want to Teach My Garbage DSL, Either
#8Earlier quoted context omitted.
Do anyone here expose real sql querying capabilities to your users?
In a dark past my company did: because these users were paying CMS users, they would not try to hack things, but rather because of the power of SQL and their lack of knowledge, they broke a lot which required backups to restore. We are talking mid 90s and Perl CGI scripts.
That sounds kind of terrifying.
Re: I Don't Want to Teach My Garbage DSL, Either
#9Unrelated to the article, just found it interesting how he’s using github to literally auto generate his blog via their md-to-html thingy, and issues for comments.
It's not a bad idea, aside from putting your blog entirely on a third party like github. Utterances is the alternative to disqus that uses github issues.[0] Personally I think the best solution is using a static site generator like Hugo or Zola to control how you generate your content, and then host that using Caddy + Docker. A database is overkill. You can also use caddy's git plugin to kick off automatic builds bui…
raganwald.com uses github’s md-to-html thingy, which is jekyl.
But there is nearly zero walled garden downside. I own the domain, I don’t use github.io, so I don’t fear link rot if I move.
Because it’s git, I always have a copy of everything locally, I don’t depend on github for storage.
Because it’s jekyll, I can generate my blog on my own system and upload it somewhere else whenever I want.
I don’t support comments at all, but that’s a personal choice. I’m not in the community business, I outsource comments to Hacker News. Which is also how most of my readers want to discuss my writing.
Re: I Don't Want to Teach My Garbage DSL, Either
#10I agree to an extent. But, I disagree that learning ORMs are a waste of time. For example, I'm on Phoenix, using Ecto. I find
`Repo.all` much more convenient that "SELECT * FROM .." etc.
I don't know if it's better or worse - the original blog post asking governments to regulate data formats/code!