121–130 of 167 posts
This is so funny Like... It's a hot dog. Like code version of lips and asses I'm trying to think of what's still running in objective-c since the 90s outside of legacy iphone apps and it's SOGo [1] [1] https://www.sogo.nu/
Earlier quoted context omitted.
This is nice. But less space-efficient than CSV when its strictly tabular, since CSV has columns legend on first row allowing 'pure' rows, whereas JSON will have to key every field, on every row.
I don't understand why people keep using CSV today while SQLite is MIT-licenced and can be used everywhere, has a very portable and lightweight implementation, has a stable file format with long-term commitment, and a good compromise on the type system that gives enough flexibility to be on par with CSV if some entries happen to have a different type...
I remember using a program called HotDog Professional a long time ago. Brings back memories.
HotDog was sweet. Back when nobody cared what the code looked like. All you needed was a WYSIWYG editor to be a powerful webmaster, and "deployment" was just FTP
Sounds like my PHP stuff in 2022. Sorry, not sorry, just works. :-D
Earlier quoted context omitted.
This is nice. But less space-efficient than CSV when its strictly tabular, since CSV has columns legend on first row allowing 'pure' rows, whereas JSON will have to key every field, on every row.
I don't understand why people keep using CSV today while SQLite is MIT-licenced and can be used everywhere, has a very portable and lightweight implementation, has a stable file format with long-term commitment, and a good compromise on the type system that gives enough flexibility to be on par with CSV if some entries happen to have a different type...
It's terrible, I love it. I also love that all the setup scripts are badly-written Perl scripts, and even some custom C code just to change the mixer rather than use alsactl. This is 1000% something I would have made years ago. edit Holy moly, the configs are CSV files.... that encode JSON?! And hey, Slack 15 is out! If they do a new release they won't need to release again for another 6 years!
> CSV files.... that encode JSON?! We need a new schema language with the ability to specify such cross-format …formats.
https://www.ibm.com/docs/en/datapower-gateway/10.0.1?topic=2...
Earlier quoted context omitted.
Since the smaller scripts run in separate processes, there is in fact a safety benefit to the break-up, which compensates in some way for the lack of strict. Processes are isolated; you know that a function call in one script will not misuse a function in another. Or that a global variable defined in one script can't be modified or accessed in the other. The scripts can only communicate via external mechanisms: comma…
Simple is beautiful, less is more.
Earlier quoted context omitted.
This is nice. But less space-efficient than CSV when its strictly tabular, since CSV has columns legend on first row allowing 'pure' rows, whereas JSON will have to key every field, on every row.
I don't understand why people keep using CSV today while SQLite is MIT-licenced and can be used everywhere, has a very portable and lightweight implementation, has a stable file format with long-term commitment, and a good compromise on the type system that gives enough flexibility to be on par with CSV if some entries happen to have a different type...
Earlier quoted context omitted.
I don't understand why people keep using CSV today while SQLite is MIT-licenced and can be used everywhere, has a very portable and lightweight implementation, has a stable file format with long-term commitment, and a good compromise on the type system that gives enough flexibility to be on par with CSV if some entries happen to have a different type...
Because if I want to do a graph from some data, it's much much easier to open the csv in Excel (or LO Calc) and create a graph from a sum of the subset of three columns VS a fourth column than it use to write an SQL query.