News for hackers. Stuff that matters.
Re:BCHS stack – BSD, C, httpd, SQLite by setq on Sunday June 18, 2017 @11:30AM (#14581056)
Back in 1999 I managed a similar thing written in C with flat file storage. The whole tool chain chucked out a static binary and a directory full of templates and you just cp'ed it to the target and restarted the process.

When I look back I've got to be honest and say that it was actually a thing of beauty. The heavy lifting required for some core functions was quite bad but the whole thing pales in comparison to some of the enterprise and microservice based c# behemoths I have looked after since which require literally hours of head scratching to deliver a simple change.

I'd rather spend that time writing C than scratching my head. I'd have a lot more hair now.

Re:BCHS stack – BSD, C, httpd, SQLite by liveoneggs on Sunday June 18, 2017 @11:53AM (#14581173)
you can duplicate that experience with go web dev today! :)
Re:BCHS stack – BSD, C, httpd, SQLite by setq on Sunday June 18, 2017 @12:36PM (#14581441)
I have actually tried that and you're right. The whole experience made me consider going back to electrical engineering when I realised that the status quo hadn't improved in 20 years :)
Re:BCHS stack – BSD, C, httpd, SQLite by walterbell on Sunday June 18, 2017 @02:35PM (#14582097)
Have you looked at Lua+C and LuaJIT+nginx (CloudFlare, OpenResty)? Work is underway to compile a subset of Perl6 to LuaJIT+nginx.
Re:BCHS stack – BSD, C, httpd, SQLite by setq on Sunday June 18, 2017 @04:16PM (#14582662)
I can't get over the 1 based indexes in Lua, unless that has changed in recent years.
Re:BCHS stack – BSD, C, httpd, SQLite by walterbell on Sunday June 18, 2017 @04:39PM (#14582797)
Still there :) The trade-off is rapid development (interpreted, GC), fast execution (JIT faster than Javascript) and easy interfacing to C libraries.
Re:BCHS stack – BSD, C, httpd, SQLite by setq on Sunday June 18, 2017 @05:28PM (#14583054)
I shall have a try next week and see if I can cope with it :)