> This is going to hurt legitimate sideloading way more than actually necessary to reduce scams
Isn't that the objective? "Reducing scams" is the same kind of argument as "what about the children"; it's supposed to make you stop thinking about what it means, because the intentions are so good.
Building a shell is a great exercise, but honestly having to deal with string parsing is such a bother that it robs like 2/3 of the joy along the way. I once built a very simple one in Go [0] as a learning exercise and I stopped once I started getting frustrated with all the corner cases.
A common problem I noticed is that if you took certain courses in computer science, you may have a pre-conceived notion of how to parse programming languages, and the shell language doesn't quite fit that model
I have seen this misconception many times
In Oils, we have some pretty minor elaborations of the standard model, and it makes things a lot easier
To summarize that, I'd say that doing as much work as possible in the lexer, with regular languages and "lexer modes", drastically reduces the complexity of writing a shell parser
And it's not just one parser -- shell actually has 5 to 15 different parsers, depending on how you count
Author here, and yeah, I agree. I skipped writing a parser altogether and just split on whitespace and `|` so that I could get to the interesting bits.
For side-projects, I have to ask myself if I'm writing a parser, or if I'm building something else; e.g. for a toy programming language, it's way more fun to start with an AST and play around, and come back to the parser if you really fall in love with it.
Can say the same for control characters in terminals. I even think maybe it's just easier to ditch them all and use QT to build a "terminal" with clickable urls, something similar to what TempleOS does.
Yeah, I'm leaning towards that conclusion as well. While I don't publish my writings, I have a few friends who do. The stuff that comes from Lulu, even the cheapest "models", is honestly fine. The ones from Amazon, not so much.
Of course if you typeset and edit your book like a moron, that's going to impact the quality, but this has nothing to do with POD.
Fewer and fewer books get this treatment by experienced professionals and it is often left to the author to do this work. This is really a great resource!
Hey there, this is Lourenço! Right out of the bat, I just want to say: I'm not the typical application, as my background is in Economics, Philosophy and (organic) Farming. IT was always my hobby, and that's why I've recently decided to convert. I've already had entry-level positions in the industry, and I'm more than willing to continue to work at that level.
Location: Kraków, Poland
Remote: Yes, hybrid is also fine.
Willing to relocate: maybe (in the EU).
Technologies: GNU/Linux, Golang, Bash, Ansible, Terraform, Jenkins, AWS, Zabbix, Kubernetes (CKA certified), Docker, Postgresql, Elasticsearch, Git, and a few more
CV: drop me an e-mail!
E-mail: lgavales (małpa) gmail (kropka) com
Links: https://lourencovales.github.io/ + https://github.com/lourencovales
Hey there, this is Lourenço! Right out of the bat, I just want to say: I'm not the typical application, as my background is in Economics, Philosophy and Farming. IT was always my hobby, and that's why I've recently decided to convert. I've already had entry-level positions in the industry, and I'm more than willing to continue to work at that level.
Location: Kraków, Poland
Remote: Yes, hybrid is also fine.
Willing to relocate: maybe (in the EU).
Technologies: GNU/Linux, Golang, Bash, Ansible, Terraform, Jenkins, AWS, Zabbix, Kubernetes (CKA certified), Docker, Postgresql, Elasticsearch, Git, and a few more
CV: drop me an e-mail!
E-mail: lgavales (małpa) gmail (kropka) com
Links: https://lourencovales.github.io/ + https://github.com/lourencovales
Isn't that the objective? "Reducing scams" is the same kind of argument as "what about the children"; it's supposed to make you stop thinking about what it means, because the intentions are so good.
reply