Hacker News new | past | comments | ask | show | jobs | submit | more samdroid's comments login

Sometimes when someone asks me for advice for how to learn to program the conversation goes like this:

Them: I want to learn to code Me: What do you want to code? A game? A robot? Them: I don't know, I just want to program.

I think this is a bit like the issue this article talked about, but coming from the learner not the teacher. In a way people who want to learn need to have an opinion too!


I was surprised to see this today as I want to use slides!

I am actually a fan of the simple, anti-powerpoint editor - that is why I use slides.

I hope you keep the old edited as an option so there is still the easy way to make WOW slides!


The old editor will be around for a long time since old presentations can't be opened in the new editor. To create new decks with the old editor, append ?version=1 to the URL: /username/new?version=1


Well (I think) part of the whole point of a package manager is to reduce space by sharing dependencies. Npm seems to actually store a copy of the dependency individually for each package that requires it. I really think that is inefficient and a step backwards.


A good package manager should allow to: -share dependencies -provide a way to install multiple versions of the same package

These requirements are not mutually exclusive. With a proper file system hierarchy both of them could be accomplished.

Most of the popular distribution's package managers (apt, pacman, etc) support the sharing dependencies but almost none of them support installing multiple versions of the package.

Given that storage space is very cheap nowadays I think a package manager like NPM which stores copies of the dependencies is not that bad actually.


This is where most Linux package managers do a really good job.

However, the system should be designed in a manner where I have a choice.

This here: https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

Makes no sense in a world of dynamically linked libraries and 6 month release cycles.


Yes, npm uses more space than what is necessary, but luckily disk space is cheap. That said, npm does optimize the disk space usage a bit. If I have package A which depends on packages B and C, both of which need D, then (if the versions match), D will be installed only once.


I really think this is exaggerated a lot. Maybe we don't use a lot of complex features, but at sugarlabs we have written a whole desktop environment and app ecosystem based of gtk3. We use the python gtk3 wrapper and I think there was only 1 instance this year where gtk3 broke our ui (icon_size got removed or something like that). We also use a lot of other gnome things (eg: gsettings) and those don't seem to be an issue.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: