freenode/#lisp - IRC Chatlog
Search
4:46:49
no-defun-allowed
Are there any good examples of using ABCL's FFI? I think I'm doing it wrong and reinventing Java inheritance in the process.
5:20:52
no-defun-allowed
Perhaps I do have to reinvent Java inheritance, since I have to swizzle all my method names according to that goddamn obsfucator.
7:20:03
fiddlerwoaroof
no-defun-allowed: ABCL ships JFLI in a contrib, which makes dealing with Java a lot nicer
7:24:49
no-defun-allowed
Most of the complexity is coming from the stupid obsfucation Minecraft has, so I had to write some methods which look up a table to translate the human friendly names (like posX) to crap (like field_12345)
8:13:14
no-defun-allowed
ACTION uploaded a video: aimbot.exe.mp4 (5666KB) < https://matrix.org/_matrix/media/v1/download/matrix.org/QHnNwKOxBHLEZoFkPsUouPJz >
8:13:24
no-defun-allowed
drmeister: I made a terrible, terrible aimbot to test out the deswizzler (and I only had to provide one obsfucated name, thanks to god damn method overloading.)
8:15:45
no-defun-allowed
I guess I have to key my method table using all the Java classes...somehow.
8:40:54
seok
I'm stressing out whether I should swap to SQL as the lack of community of common-lisp - mongodb users make it difficult to ask for help in odd cases
8:42:11
seok
I would love to use lisp image as a db, but I have doubts whether it would keep up with the performance standard of SQL or NoSQL DBs
8:42:58
jackdaniel
when you use external database you need to: a) speak some protocol (transmission), b) serialize/deserialize data (computing)
8:43:45
jackdaniel
however I could imagine a database in beach-envisioned system where your process simply gains access to the database memory
8:43:53
seok
What about data integrity? How can I be sure that data won't be lost in case of unexpected shutdowns
8:45:00
jdz
Integrity does not safeguard from data loos, it just guarantees integrity of written data.
8:45:57
jonatack
seok: did a one year project for the paris airports where we were required to use mongo... never again
8:45:59
jackdaniel
seok: but yes, using "real" database will give you some guarantees which are not available in stock lisp image :)
8:47:52
seok
If I could be convinced that a lisp database can be just as scalable and data-secure as full DB's, I would go for that right away
8:48:52
jonatack
mongo was fun at first but if any risk of evolving toward needing a RDBMS instead... heh
8:49:51
jackdaniel
seok: that was primarily meant as a joke, lisp image is not a way to go for managing data in any non-personal project. if it is a small project with single client use sqlite, otherwise use postgresql
8:50:56
jonatack
mongo is the wrong choice for relational mapping without going down rabbit holes to accomodate/cascading updates and let's not get started about maintaining db integrity in that case
8:53:49
jonatack
basically an SQL backend with maybe a mongo one for the document part would have been fine, but some manager sold the project as cheaper by speccing only having to deploy and admin mongo for everything
8:55:02
jonatack
the takeaway: if the value of the data is in the relationships between the data, then go for an RDBMS.
8:56:32
jonatack
it was unfortunately not CL but a ruby/rails/react app but the database aspect should apply broadly
8:59:36
jonatack
part of it was a web app, the rest an internal management/AI tool to dump data from employees' heads as they were nearing retirement, centralise the data, and apply learning to it
9:00:47
jonatack
to automate tasks and probably hire fewer people, hopefully doing more interesting work without the dumb automated parts
11:39:25
beach
Yes, unit testing is good most of the time. Sometimes it is very hard to accomplish, though.
11:39:54
beach
And many times it is tedious if the technique used is to enumerate every possible case.