Although the interface is well defined, the database itself is still an opaque binary blob. What happens if a library upgrade breaks a user's file in the wild? It's easier to hand-/auto-repair a plaintext file, whatever format that's in. Moving to binaries is a regression in my opinion.
On Wed, 26 Oct 2016 at 19:00 Kenneth Lerman <ler...@se-ltd.com> wrote: > SQLite is just another library. Yes, it is another dependency. But it > should be no more an issue than libc or libm or any other library. Unlike > mysql or postgresql, it does not require a separately running executable. > > Ken > > Kenneth Lerman > 55 Main Street > Newtown, CT 06470 > > > On Wed, Oct 26, 2016 at 11:07 AM, EBo <e...@sandien.com> wrote: > > > Then you are requiring SQLite in the dependency chain. Is that more > > maintainable than not? > > > > On Oct 26 2016 8:51 AM, Kenneth Lerman wrote: > > > I would go with SQLite. And a text (and/or JSON and/or YAML and/or > > > ...) > > > interface. > > > > > > But the change must provide all of the necessary tools: > > > 1 -- a tool table editor > > > 2 -- a flat file, text interface > > > 3 -- JSON or YAML interface > > > 4 -- a way to read the tool table at startup > > > 5 -- a way to access (the necessary parts of) the tool table at run > > > time. > > > > > > > > On Wed, Oct 26, 2016 at 7:00 AM, EBo <e...@sandien.com> wrote: > > > > > >> ... I was not aware of the 59 item limit. 256 (8-bit int) or > > >> 64K (16-bit int) seems more reasonable. For James example I would > > >> lean > > >> towards a 16-bit tool number. It is also possible that some of the > > >> bits > > >> could be used for status indication and we actually end up with > > >> something like 12-bits of tool numbers and 4 bits for status. > > >> > > > > > > This is NOT 1980. Memory (at this level) is free. There is no need to > > > pack > > > bits, save memory, or worry about stuff like this. > > > > True. I guess I am showing both my age and occupation -- last year I > > was handed a 2.4 Petabyte dataset to process. There, doubling the > > output by not packing the bits would increase the output by a full > > petabyte (which costs something like $100K to install and maintain for > > the project lifetime). For LinuxCNC you are correct -- it is not worth > > the time, headaches, or space. > > > > EBo -- > > > > ------------------------------------------------------------ > > ------------------ > > The Command Line: Reinvented for Modern Developers > > Did the resurgence of CLI tooling catch you by surprise? > > Reconnect with the command line and become more productive. > > Learn the new .NET and ASP.NET CLI. Get your free copy! > > http://sdm.link/telerik > > _______________________________________________ > > Emc-developers mailing list > > Emc-developers@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > > > ------------------------------------------------------------------------------ > The Command Line: Reinvented for Modern Developers > Did the resurgence of CLI tooling catch you by surprise? > Reconnect with the command line and become more productive. > Learn the new .NET and ASP.NET CLI. Get your free copy! > http://sdm.link/telerik > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
