FabricPaul

7 ms·

1.
by FabricPaul 14y ago
As promised: Security was an important part of the design of Fabric. What security means depends on whether Fabric is running standalone from the command-line or as a browser plugin. When Fabric is run from the command line, we are in gene
2.
by FabricPaul 14y ago
we wrote this piece last year - it's focused more on why JS isn't enough, but there's some useful info about KL in there. http://fabricengine.com/2011/10/couldnt-you-just-use-javascr...
3.
by FabricPaul 14y ago
I've asked one of my colleagues to write a longer response to this (we may post it on the developer blog), but I'll give you a short answer in the meantime. We don't do sand-boxing - I think a look at the amount of money that's gone into Na
4.
by FabricPaul 14y ago
OpenCL/CUDA are GPGPU programming languages - that's something we're getting to soon :) We previously exposed OpenCL as an extension, but took it out because it's a nightmare to support. We're looking at it again at the moment - it's pretty
5.
by FabricPaul 14y ago
we did a lot of documentation work for launch - the overview is a good place to start: http://documentation.fabric-engine.com/latest/FabricEngine-O...
6.
by FabricPaul 14y ago
as per my other comment: "please correct me if I'm wrong, but I don't see anything about Cython handling multi-threading and I don't see anything about dynamic compilation on target. I just had a flick through their documentation, so if thi
7.
by FabricPaul 14y ago
it's awesome. Investors are going crazy
8.
by FabricPaul 14y ago
got it - thanks for the clarification :)
9.
by FabricPaul 14y ago
You're right - it should be publicly visible. We're working on it - it will be updated and public in the next week. We'll be offering subscription pricing - so initially it will be a monthly that allows you to run x number of instances.
10.
by FabricPaul 14y ago
p.s. Fabric Engine 2.0 has a flux capacitor
11.
by FabricPaul 14y ago
lol :) Read this older HN thread - http://news.ycombinator.com/item?id=3227905 - a few people took our code and tried to make it faster in C/C++ and Java. We made our benchmark code available: ( https://github.com/fabric-engine/Benchmarks
12.
by FabricPaul 14y ago
Using pointers adds a certain amount of complexity, and they also introduce the possibility of security problems. This was particularly important for the work we were doing on the browser plug-in. For the type of work that developers use KL
13.
by FabricPaul 14y ago
Replying to comment below (can't see a reply button) - please correct me if I'm wrong, but I don't see anything about Cython handling multi-threading and I don't see anything about dynamic compilation on target. I just had a flick through t
14.
by FabricPaul 14y ago
p.s. I meant to say - yes, it is misleading. We are most definitely not an automagical interpreter :)
15.
by FabricPaul 14y ago
The 'new' part relates to using LLVM to do the compilation on target - this actually makes a big difference in workflow, and is also much more familiar to people used to developing with dynamic languages. It also opens up some cool possibil
16.
by FabricPaul 14y ago
agreed - I was pulled up on this here last year when we published our benchmarks :) The other thing to remember is the low-level language we use sets a lower bar to entry than say C - the benefit of designing for a specific set of goals (ea
17.
by FabricPaul 14y ago
we offer commercial licensing that allows devs to bypass the AGPL requirements. I'll update the site info soon to show the subscription pricing options.
18.
by FabricPaul 14y ago
not really - Fabric is integrated with dynamic languages, we 're not interpreting JS or Python (we work with both languages). Fabric is basically a high-performance threading engine that you can call from your dynamic language - the key ele
19.
by FabricPaul 14y ago
for reference, we posted our beta benchmark stuff here and people had a good look at us: http://news.ycombinator.com/item?id=3227905
20.
by FabricPaul 14y ago
we dynamically compile on target (using LLVM), and the developer doesn't have to manage things like pointers.
21.
by FabricPaul 14y ago
Yes, this is correct - it's targeted at people who are comfortable using dynamic languages like JS/Python
22.
by FabricPaul 15y ago
Hi all - you might remember the Fabric benchmarks we did with node.js last year. We've now integrated Fabric with Python as well, so I thought I'd share the news. An important change since last time - Fabric will be released as OSS (probabl
23.
Python + Fabric Engine benchmarks - as fast as multi-threaded C++(fabric-engine.com)
2 points by FabricPaul 15y ago|1 comments
24.
Node.js + Fabric as fast as multi-threaded C++ (part 2)(fabric-engine.com)
5 points by FabricPaul 15y ago|0 comments
25.
A response to the 'Node is a cancer' problem (Fabric Engine)
4 points by FabricPaul 15y ago|0 comments
26.
by FabricPaul 15y ago
Hi again - we implemented asynchronous compute for Fabric and node.js, which means we can go after the much publicized Fibonacci criticism. We're looking for closed alpha participants, so if you're interested please submit the request using
27.
Fabric Engine + node.js Fibonacci benchmark (plus Alpha)(fabric-engine.com)
2 points by FabricPaul 15y ago|1 comments
28.
by FabricPaul 15y ago
Cool - can you contribute the code to the repository so we can test and merge it in? Thanks
29.
by FabricPaul 15y ago
I agree. I have made a separate post on this thread that calls this out. Thanks -Paul
30.
by FabricPaul 15y ago
I asked the engineer for a response: "For reference, I used -O6 because it's a historical convention (more of a joke, really) for "optimize the crap out of it". UNIX geeks have been using -O6 in this way for about 30 years."

More ›