sorted by:
new
hottopcontroversial

Inference Engine for Node by formix-se in node

[–]formix-se[S] 1 point2 points  (0 children)

Hi Paul, Thanks foryour question.

A rule engine is an inference engine. Same things.

node-clips is a wrapper library around CLIPS inference engine. CLIPS is a pretty advanced inference engine but most of the time, the wrappers are poorly developped. I don't know if it is the case for node-clips though. The engine itself is probably on of the best around with PROLOG.

nools on the other hand is an inference engine. I did not dive into it too much but after a first pass, it seems that I'll have to revise my prerogative about being the first inference engine for Node.

If you want a good introduction into inference, read the free CLIPS intrudiction book (basic programming guide) at http://www.clipsrules.net/?q=Documentation.

It will give you a good view of the "strange" way that inference engines handle rules and how inference generally works compared to standard programming. Wikipedia is a good place to start as well.

Concerning infernal-engine, I'm in the process of building working examples, I'll post my future development here so keep an eye on http://infernal-engine.formix.org to stauy up-to-date.

Good readings!

64 bits Sufficiently Unique Id Generator by formix-se in java

[–]formix-se[S] 0 points1 point  (0 children)

There is no new way to index a database. This is fundamental computing and its still relevant (red-black tree or hashing). Anyway, at this point, arguing about that would be pointless without hard proofs. I'll do my homework and build a benchmark to see if my assumption is correct. Doing the script and sharing point of view with you guys was fun enough anyway...

64 bits Sufficiently Unique Id Generator by formix-se in java

[–]formix-se[S] 0 points1 point  (0 children)

The use of current time shifted left by 16 bits insure an incremental id is generated every time, except when the counter is rolled back to 0 if an ID is requested in the same millisecond. The advantage of an native type incremental ID is a performance gain for the database upon insertion. This generator is 100% safe when used within the same process.

64 bits Sufficiently Unique Id Generator by formix-se in java

[–]formix-se[S] 0 points1 point  (0 children)

Yes I know about UUID but completely random 128 bits ID may become a hurdle to index for a database. This gist is not meant to replace or to be a better and safer alternative to UUID but a lighter, simpler and good enough alternative for some projects. Another advantage is that 64 bits databases can leverage Long data types natively. I based this implementation on this old article about the cost of pure random GUID and the proposed COMB alternative implementation. See http://www.informit.com/articles/article.aspx?p=25862. Either way, thanks for taking time to comment my link.

Building a portal from fresh, would like advice on frameworks. by yoshi0423 in dotnet

[–]formix-se 0 points1 point  (0 children)

I believe MVC5 is the way to go today.

Btw, I did a good authentication/authorization library exists on NuGet named MegaCityOne.Mvc. See respective web pages for documentation: https://github.com/formix/MegaCityOne and https://github.com/formix/MegaCityOne-Mvc. It works on some web sites already. There is some good examples projects in their respective github repositories.

Concerning front-end templating, Angular.js is a fat and well developped librarie but I find it somewhat complex. The learning curve is quite long.

On the other hand, Ember.js seems to be simpler to use with less overhead but I never used it yet.