This is what everyone's first experience of programming in Scala should be like.pic.twitter.com/hfAMXAplFf
-
-
-
Replying to @tmnd1991
It wouldn't seem so much like magic if you weren't so familiar with the current model, which I believe is unnecessarily complicated!
2 replies 0 retweets 3 likes -
Replying to @propensive
I’m curious how import —> add dependency workflow works... are there some pre-defined lookup tables or is a search on ipfs ?
1 reply 0 retweets 0 likes -
Replying to @tmnd1991
When you start a new project you get a default base layer. That's a curated set of projects composed of other layers (recursively). Modules declare their packages, and the namespaces cannot conflict (for security). When an import isn't found, Fury looks it up in the layer.
1 reply 0 retweets 3 likes -
Replying to @propensive @tmnd1991
Anyone can create and distribute a layer. Teams may decide to do this just with the projects they want to use. It's the curator's job to maintain the consistency of a layer (project and package names must be resolved) but that job can be delegated up the layer tree.
1 reply 0 retweets 1 like
Or any user can just do it themselves if they want to combine two or more layers that contain conflicting projects.
-
-
Replying to @propensive
That looks very very neat... can’t wait to try it out!
0 replies 0 retweets 3 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
