recentpopularlog in

kme : rust   35

Why would a python programmer learn rust when there are no jobs in it - YouTube
That is the coolest shirt I've ever seen. Please someone tell me where I can buy that, and port it to a vim color theme
rust  devel  programming  conference  talk 
october 2019 by kme
GitHub - alex/csv-sql: Query your CSV files with SQL
Query your CSV files with SQL. Contribute to alex/csv-sql development by creating an account on GitHub.
csv  sql  datamining  commandline  rust  textprocessing 
june 2019 by kme
BurntSushi/tabwriter: Elastic tabstops for Rust. - https://github.com/
Elastic tabstops for Rust. Contribute to BurntSushi/tabwriter development by creating an account on GitHub.
rust  cli  tui  library  tabstops  tabs 
april 2019 by kme
BurntSushi/xsv: A fast CSV command line toolkit written in Rust. - https://github.com/
A fast CSV command line toolkit written in Rust. Contribute to BurntSushi/xsv development by creating an account on GitHub.
rust  csv  textprocessing  commandline 
april 2019 by kme
sourcefrog/conserve: [alpha] robust portable file backup tool in Rust | https://github.com/
[alpha] robust portable file backup tool in Rust. Contribute to sourcefrog/conserve development by creating an account on GitHub.
sysadmin  backup  backupandrecovery  commandline  rust  alternativeto  duplicity 
february 2019 by kme
Why does Cargo use toml? - The Rust Programming Language Forum
The TOML readme has a small section comparing itself to JSON, YAML and INI:

In some ways TOML is very similar to JSON: simple, well-specified, and maps easily to ubiquitous data types. JSON is great for serializing data that will mostly be read and written by computer programs. Where TOML differs from JSON is its emphasis on being easy for humans to read and write. Comments are a good example: they serve no purpose when data is being sent from one program to another, but are very helpful in a configuration file that may be edited by hand.

The YAML format is oriented towards configuration files just like TOML. For many purposes, however, YAML is an overly complex solution. TOML aims for simplicity, a goal which is not apparent in the YAML specification: http://www.yaml.org/spec/1.2/spec.html25

The INI format is also frequently used for configuration files. The format is not standardized, however, and usually does not handle more than one or two levels of nesting.

From: https://github.com/toml-lang/toml#comparison-with-other-formats65

While I can not speak for the Rust authors, having used the different formats in my own projects (as well as JSON variants such as HCL) I believe they made the right choice.

I don't think they are. Especially security issues aren't emphasized enough. The biggest issue is that YAML attempts to be many things to many people. It's JSON, it's a serialization format, it's human readable, etc. I've been reading the mailing list for YAML for quite some time now.

To me YAML has become F-35 of the ML formats. That is to say overly complex, does many things and isn't really good at any particular thing. I mean, can YAML parser beat JSON parser at parsing JSON (I don't think it is possible, simply because YAML has more states)?
butwhy  rust  cargo  json  configfile  inifile 
april 2017 by kme

Copy this bookmark:





to read