setori88

If it's of any interest to anyone I recently did a podcast with Prof Robin Hanson too: https://www.youtube.com/watch?v=EIbOUjplFus [2hr 48min video]

My project http://www.fractalide.com is looking to build out a new hypercard type environmont

email sent

Any idea when custom allocator will become stable? That's the only thing holding us to nightly.

Steve you're a good chap doing some solid, respectable and valuable work. These things are just troglodytes looking to inflict pain. The interesting thing is, they could totally transform themselves by doing constructive work and presenting it to the community. It's then, quite possibly, they realize, it is your attention they seek.

Fractalide [1] just removed cargo from it's build system, and opted for nix to take up the role [2] of cargo.

[1] https://github.com/fractalide/fractalide

[2] https://github.com/fractalide/nixcrates

There is too much cognitive dissonance between nix and cargo. It might be better to get nix, a package manager, to do the job of cargo, a package manager.

a) yes it will, we'll have to do some design on the `fvm` to make it hotswap. It won't be ready for this stabilization release. The functionality is already there it just needs

b) I'm not really focusing on other market occupants. We need this system to solve some pretty hairy problems 100TB problems.

c) 'feature-credible, testable release' primarily this is dependent on `nixcrates`, documentation and maybe getting a few more services examples. I'd say a couple of weeks.

We have the early stages of a tutorial here: https://gitlab.com/dmichiels/dochttp/blob/master/http_todo.m... , it still has to be converted into a decent HOWTO. Hopefully this will give insight into designing applications using Fractalide.

An author here: we're working on the nixcrates project to remove cargo and allow for closer integration between nix and crates.io, so far you can check out the project at https://github.com/nixcloud/nixcrates (joachim and paul are super people, hit them up if you're interested in contracting them) the net/http stuff is currently incompatible with the most recent changeset, I'll get working on it tomorrow morning HKT to make it work, I have to refactor it to suit the new stabilized API. Anyway, this attention was a bit earlier than expected, still have a couple of weeks to go before stabilizing. I hope you guys can kick the tires, tell us what you don't understand and please comment on the API because we want something sensible. We're using the late Pieter Hintjens' C4 so please hop on board and collaborate!

Not sure if it's valid, but there's an implementation of a flow-based programming system over at https://github.com/fractalide/fractalide. Although it's not quite at the boxes and lines stage yet, the components are reusable and efficient.

How much different is this from https://github.com/fractalide/fractalide/tree/master/support...?

Fractalide is a Rust programming platform that makes it simple to reason about efficient microservices.

The Nix Expression language provides a language compatible with a Continuous Integration - Hydra (https://nixos.org/hydra) and Code Deployment - Nixops (https://nixos.org/nixops) and when combined with Flowscript, Fractalide's own actor oriented dataflow language, the two languages fuse beautifully to become a glue language that declaratively describes your microservice architecture, then lazily builds it, weaves it together and deploys it.

Soon we'll be stabilizing at 1.0, but it's suitable to take it for a spin now, especially with the new net_http module (github.com/dmichiels/frac_net_http)

We're using the C4 contribution contract, so you're welcome to contribute code!

Regarding microservices; it's my hopes https://github.com/fractalide/fractalide moves into this space.

"Currently, the focus of development is to improve SolveSpace's handling of complex assemblies with many similar parts by allowing to load a hierarchy of sketches instead of a single sketch and propagate the changes as they are made, and to derive many variants of geometry from a single sketch. For example, these changes would allow to use a single basic sketch to model framework made from varying lengths of 80/20 profile, whereas currently that would require a separate sketch for every size of cut."

  Location: Hong Kong
  Remote: True
  Willing to relocate: False
  Technologies: Rust, Nix, FBP, Capnproto
  Github: fractalide/fractalide
  Email: setori88 at gmail

Fractalide, a dataflow language (FBP) implemented in Rust is ready for corporate sponsorship and or contracting. We're keen to solve problems using Fractalide.

That getter is fascinating, it's a new concept to me. Recently we blew a picoammeter because we fired up a vacuum guage in UHV after disconnection from the roughing pump. The vacuum guage out gassed massively giving us shit vacuum, this then fried the picoammeter and left us scratching our heads for a few hours. Firing the vacuum guage while still connected to the roughing pump would have solved this problem. Thanks for sharing the getter information.

That induction heating step is critical. Ensure you heat metal whilst the vacuum system is still pumping otherwise if you heat the metal after the tube is sealed the metal will out gas giving you bad vacuum, completely destroying your Nixie tube. It's a pleasure to see such refined work, many many frustrating mistakes were made to reach this level of refinement.

Fractalide (http://githib.com/fractalide/fractalide) is an implementation of dataflow programming (specifically flow based programming). Component build hierarchies are coordinated via the Nix package manager. Capnproto contracts are weaved into each component just before build time. These contracts are the only way compenents talk to each other. Thanks Sandstorm.io for this great software.

Actually iElectric was one of the people who encouraged me to learn the Nix Expression language. Now we're doing stuff over at github.com/fractalide/factalide I could never have imagined. The promised gain iElectric hints at can only be earned by learning the Nix Expression language.

Take a look at Fractalide http://github.com/fractalide/fractalide It uses Nix Expressions to lazily coordinate the building and port linking of components.

We implemented a flow-based programming language in Mozart Oz at github.com/fractalide/fractalide if you're interested.

Chatty software able to synchronize state over the open internet using declarative concurrency is a distributed system. A high performance cluster running something like distributed message passing concurrency erlang is a distributed system. A single program written with the complexity of shared state concurrency executing over multiple cores is a distributed system. The concept of concurrency is vital for this, particularly what type of concurrency used. When this person talks about distribution what kind of concurrency is he referring to? I'd like to see this professor reimplement Dropbox for sequential execution on a single CPU to serve the world (you can only use shared state, or any other form of concurrency if you do it on the same CPU). This centralized system then should be fault tolerant. Which it absolutely will not be, as you need at least two machines for fault tolerance. This article was a waste of time.

Okay when I first started using NixOS as a desktop, I knew it would bite me. But I'm a firm believer of the way NixOS handles state, so I suffered through both my and NixOS' growing pains. Basically I had to change my graphics card for some strange reason (which worked on Arch Linux!), ALSA gave me problems with flash videos, this is when I found out how amazing the NixOS community is. They helped me solve this issue quickly, it was a one liner in my configuration.nix. I've had issues with harddrives not being seen on time and having to tell the boot process to wait a second (again a one liner). It's actually quite a fun ride, don't install it on a machine you intend to do real work on, once happy and you've tweaked the hell out of your configuration.nix then roll it out where you need it. So if you have any issues, determine if you can resolve it intelligently and then create a github issue, they are very supportive (thank you Domen Kožar for the quick qt4 fix!). Now my system is happily ticking along, with one nagging Tk issue.

Oh right, interesting. Now generally speaking I'd suspect things like concurrency, lazy and non-determinism should be made explicit in a language, these concepts should be language level not library/macro level. I'm quite curious to see how much this affects the expressiveness of the system. But I'm splitting hairs! This is LISP the old granddad of succinctness.

(Please correct me if I'm wrong) but the NixOS functional language is also lazy. Guix does not have this lazy feature. Though on the other hand, it does play well with the rest of GNU.

I've gotten over all the features of Nix, its become my environment of choice. What continuously impresses me now is the Nix community. An issue with your system can be resolved within minutes of a github issue submission. I'd like to see them use the ZeroMQ C4 development contract (http://rfc.zeromq.org/spec:16). No branches everywhere and it's just a rolling release. I highly recommend this distro, it has given me trouble in the growing stages but it's maturing nicely and things are starting to just work.

Agreed, though updating your system shouldn't break other packages. If those other packages are a security risk then they too should be updated. Once done, garbage collect that which is not used.

Quisquater was involved in the development AES. Are the NSA trying to find ways to crack it?