blubbi2

That's not 100 % accurate. Arguably symlinks are kinda weird under Windows, but that doesn't mean symlinking node_modules doesn't work (you just need admin privileges).

(Disclaimer: I'm the author of ied.)

We initially used a method similar to ied when we first started experimenting with internal usage at Facebook.

Would be really nice if you would e.g. add ied to "Prior art" on your README then. ;)

/ @alexanderGugel (the guy behind ied)

Probably easier to just use an assertion library here. E.g.

  assert.ok(element)

Yup. Thanks.

They are extremely different.

I made a quick comparison here: https://gist.github.com/alexanderGugel/a10ed5655d366875a280

Basically ied uses symlinks in order to resolve circular dependencies, while ied exploits the fact that require "falls back" in the directory structure.

Agreed. It's definitely on the roadmap. Should be done in a couple of weeks.

Awesome! Glad it worked that well! Please let me know if you run into any bugs: https://github.com/alexanderGugel/ied

Great to hear that! shrinkwraps + rollbacks are definitely coming!

Although using ied and npm at the same time for installing dependencies should work, you might run into some weird corner cases.

Therefore, npm and ied are compatible in the sense that you can use ied to install packages and npm for publishing them. At least that's the level of compatibility that is currently supported.

shrinkwrap is definitely coming :)

Its install process is very different from the one npm uses. E.g. just look into the node_modules directory produced by npm vs the one produced by ied.

Also the way it wires up dependencies (using symlinks) has been called "non humane design" by npm... so I thought it would be easier to just start a new project... it's not a lot of code/logic needed there actually... :)

Already taken by Atom's package manager: https://github.com/atom/apm

The initial set of dependencies is being installed via npm, the it installs its own dependencies via ied if told so: https://github.com/alexanderGugel/ied#installation

This is a "cool" feature during development, since it's a nice proof of concept.

Originally I checked in the node_modules directory, but then reddit was shitting on me as usual (yes, you shouldn't check in node_modules in an actual app, but this is PACKAGE MANAGER!). As far as I know, npm has also its own dependencies check in + a ton of packages as tarballs for tests, so I might do that later.

Mostly, yes, but there are some features that are still missing:

`ied publish` and `ied version` is coming next week. I'm also thinking of adding scoped modules, but I'm not sure about that yet.

You can also configure a private npm registry to be used: https://github.com/alexanderGugel/ied/blob/master/lib/config...

As I said earlier, it wasn't my intention to name it after a weapon.

That being said, it's a three letter name. It's very unlikely NOT to run into naming conflicts here.

edge - taken by Microsoft

jpm - JPMorgan

ppm - taken by Perl package manager: https://en.wikipedia.org/wiki/Perl_package_manager

fpm - taken by Effing package management: https://github.com/jordansissel/fpm

bpm - beats per minute

ayp - terrible to type, although taken by "Adequate Yearly Progress": https://en.wikipedia.org/wiki/Adequate_Yearly_Progress

nnm - What happens when it's no longer new?

Just in Germany for example there are a ton of companies called ISIS (just google "ISIS GmbH"). Being offended by a three letter shell command seems a bit over the top to me to be honest.

Edit: I won't respond to further comments on the naming issue. It wasn't my intention to name it after a weapon. As I said earlier, I will change the name as soon as anyone proposes a better one.

This looks very interesting!

Also related: https://github.com/dominictarr/npmd

Damn. Didn't think of that.

In fact I literally just renamed it: https://github.com/alexanderGugel/ied/commit/84628b3c871c85d...

Originally it was called mpm, but I figured that would have been pretty confusing, but it looks like the new name isn't necessarily better.

I'm pretty terrible at naming. Any suggestions are more than welcome!

Hey everyone!

I made this. I'm happy to answer any questions, but please bear in mind that this is a WIP. There is still a lot of work to be done, although feature parity with npm is not the goal.

Upcoming features are:

* Nix-like rollbacks * built in registry server * discovery + installation via BitTorrent DHT

Would love to get any feedback!

Favorite comment from the source code:

/* If your shitbox doesn't have getopt, step into the nineties already. */

Thanks (for submitting this).

Underweight

While I agree from a conceptual standpoint, the same argument could be made about online dating - and there are people successfully using it anyways. For some people getting to know a cofounder online might be the only way to find one (e.g. in more conservative parts of the world, where startups are a very rare phenomena).

I really like the carousel. Nevertheless, for those that are too lazy to click 36 times:

Given the choice of anyone in the world, whom would you want as a dinner guest?

Would you like to be famous? In what way?

Before making a telephone call, do you ever rehearse what you are going to say? Why?

What would constitute a "perfect" day for you?

When did you last sing to yourself? To someone else?

If you were able to live to the age of 90 and retain either the mind or body of a 30-year-old for the last 60 years of your life, which would you want?

Do you have a secret hunch about how you will die?

Name three things you and your partner appear to have in common.

For what in your life do you feel most grateful?

If you could change anything about the way you were raised, what would it be?

Take 4 minutes and tell your partner your life story in as much detail as possible.

If you could wake up tomorrow having gained any one quality or ability, what would it be?

If a crystal ball could tell you the truth about yourself, your life, the future, or anything else, what would you want to know?

Is there something that you've dreamed of doing for a long time? Why haven't you done it?

What is the greatest accomplishment of your life?

What do you value most in a friendship?

What is your most treasured memory?

What is your most terrible memory?

If you knew that in one year you would die suddenly, would you change anything about the way you are now living? Why?

What does friendship mean to you?

What roles do love and affection play in your life?

Alternate sharing something you consider a positive characteristic of your partner. Share a total of 5 items.

How close and warm is your family? Do you feel your childhood was happier than most other people's?

How do you feel about your relationship with your mother?

Make 3 true "we" statements each. For instance "We are both in this room feeling ... "

Complete this sentence: "I wish I had someone with whom I could share ... "

If you were going to become a close friend with your partner, please share what would be important for him or her to know.

Tell your partner what you like about them; be very honest this time saying things that you might not say to someone you've just met.

Share with your partner an embarrassing moment in your life.

When did you last cry in front of another person? By yourself?

Tell your partner something that you like about them already.

What, if anything, is too serious to be joked about?

If you were to die this evening with no opportunity to communicate with anyone, what would you most regret not having told someone? Why haven't you told them yet?

Your house, containing everything you own, catches fire. After saving your loved ones and pets, you have time to safely make a final dash to save any one item. What would it be? Why?

Of all the people in your family, whose death would you find most disturbing? Why?

Share a personal problem and ask your partner's advice on how he or she might handle it. Also, ask your partner to reflect back to you how you seem to be feeling about the problem you have chosen.

Almost done. Now silently look into your partners eyes for 4 Minutes.

Congrats! You're in love! :)

Native apps might always be superior in performance. Nevertheless, I doubt that the performance benefit of native over web will be big enough to justify a significantly longer development time as we're approaching (near) native performance. Things changed quite a lot last year: WebGL enabled by default on iOS, Ionic had massive adoption, Firefox OS makes the web a first-class citizen again. IMHO it's only a question of time.

A couple of things:

1) webtorrent [1] will be used to build the next generation of The Pirate Bay. Media companies will have to realize that suing teens for infringing copyright is not an option, since participating in file sharing is no longer a deliberate act when WebRTC is enabled by default.

2) io.js [2] will heavily influence the future of Node.

3) Angular 2.0 will probably be released at the end of the year [reference?]. People might start establishing an Angular fork (similar to what happened in the Node world).

4) Full stack Google: Angular, Dart and Go.

5) We'll find out if there is a tech bubble [3].

6) One of the following will happen: 1) Developers might tend to use bigger and bigger frameworks, or 2) substack-like extreme modularization (current situation in the npm-world).

7) People will move away from native app development. [4]

8) More frameworks will evolve to "reinvent" the DOM. DOM updates will still be expensive as hell. React was just the beginning.

9) Everything will be a SPA. Now that Google executes JavaScript [5], there is no more reason to render websites on the server. (Unless you're using HN, where 50% of the users are using Lynx).

[1] https://github.com/feross/webtorrent [2] https://github.com/iojs/io.js [3] http://www.theguardian.com/technology/2014/aug/17/technology... [4] Disclaimer: I work for famo.us. These are my own thoughts and might not express the thoughts of the company I'm working for. [5] http://googlewebmastercentral.blogspot.nl/2014/05/understand...

Although I think that PHP is certainly not the best language in the world and it's pretty easy to write unsafe code in it, I don't think that's true.

I agree that PHP tends to trick you into writing unsafe code, but I generally don't agree that their documentation is full of unsafe examples (not anymore at least).

Can you name an example that proofs your point?

Another interesting article about Julia by Evan Miller (was on HN a while ago): http://www.evanmiller.org/why-im-betting-on-julia.html

HN thread about it: https://news.ycombinator.com/item?id=7109982

Sorry to be that guy, but are there any apps in production based on FRP/ Elm?

According to the Elm website, under "big projects" it lists the Elm website itself and a couple of rather PoC games. - http://elm-lang.org/Examples.elm

(I'm not saying that FRP is bad, I think it's an interesting concept, but I'm wondering on how efficient it is in production.)

(commenting on one of the articles)

Wow. Just stumbled upon the following quote and read the corresponding article.

Programming language comparisons usually focus on the brevity and expressiveness of the language. If the solution to a programming problem has fewer lines and is “easier to understand” or “clearer” in one language than another, that is an argument for using the former over the latter. This comparison is useful if one supposes that the art of programming is primarily concerned with writing programs. It isn’t, of course. It is mostly concerned with debugging programs.

- https://codewords.hackerschool.com/issues/one/why-are-object...

In summary, then, every concept that object-orientation brings to the table makes debugging harder. If you believe (as I do) that the majority of effort a programmer expends is devoted to finding and fixing bugs, then an imperative programming approach will be more efficient (in programmer time) than an object-oriented approach.

Depends on your blog.

I would ask myself the following questions:

- Does the audience you are addressing already have a "home"?

Your primary goal shouldn't be to run a forum for the sake of running a forum. Your primary motivation should be to give your community a home.

- Can you reach initial traction?

How many readers do you have? How many of them do you think will contribute to the forum? Your blog seems to be pretty popular. Why don't start with one category and see how it develops?

Looking at your blog, I don't think that this will be a problem. Nevertheless, you need to be prepared to spend quite some time answering questions in your forum yourself.

When in doubt, fake it 'til you make it. That's how reddit got started: By creating massive amounts of fake accounts and posting everything they found online.

Here are a few "golden rules" on running a forum:

- Don't start with n different categories.

Start with one instead. See what people are talking about. If a category becomes to cluttered, add a new one.

Don't try to structure your forum before you have content!

- Ask users what they want.

- Define the scope of your forum.

What should be the primary topic people are supposed to talk about. An off-topic board is ok, but it'g good to have a general idea on what your community is supposed to look like.

- Sign up beta users first.

It's probably a good idea to start with a small core group before launching and inviting everyone. People won't post in an empty forum, because they think it's dead. By starting with a small core audience, you have two advantages:

1. They feel special because they are first. 2. They KNOW the forum is empty, but NOT DEAD.

However you decide, good luck! Running a community is tough, but a lot of fun.

Sorry to be "that guy", but what is System.Linq.Parallel? Can anyone provide a brief description/ list of links where to read more about it? Why is open sourcing it such a big deal?