examancer

Give it time. Moving to a native python DSL will make extending the dependency system more straightforward. Also, if they continue copying the best of Ruby's bundler they will have a way to specify python version/platform specific dependencies.

The main reason this is better is explained in the third paragraph in the README: Deterministic builds. You can specify target versions in your Pipfile, while your Pipfile.lock will contain the actual exact versions pip installed (even the exact git commit) so if your app is built on another machine you know the libraries are exactly the same, preventing slight version differences from causing you problems without requiring you to be ultra-specific in your dependencies.

Another benefit is named groups, which allow you to more succinctly specify dependencies for various environments (dev/test/production/etc.) Along with this you get the benefits of the lock file so you can be assured the subset of libraries you use in production will be the exact tested libraries you use in your larger dev/test environment.

This is almost identical to how bundler in Ruby works, right down to the language native dependency DSL, named groups, file name conventions (Pipfile = Gemfile, Pipfile.lock = Gemfile.lock), and deterministic builds.

It's identical because bundler mostly got it right and dependency management in Ruby, while still not great/perfet, is better than just about everywhere else.

Kudos to python for moving forward.

Kind of an odd post to see on hacker news. As somewhat of a car buff my take away is that this article gives an adequate high level explanation but leaves out a lot of useful details, especially to anyone evaluating 4WD/AWD vehicles, like the tremendous differences between modern AWD systems.

Come to Omaha! Lots of talk about how you can't find jobs or culture in small places, and talk of how the big cities are expensive for a reason. That may be true if you're trying to be an actor, but Omaha has a thriving tech scene, extremely low unemployment, and one of the lowest costs of living of any major metro area. It's safe, LGBT friendly, family friendly, great schools, and the people are nice and laid back.

There is a sweet spot between too big and expensive and too small and isolated. I have lived in NYC and there is nothing I'm missing in Omaha. Although the scale is obviously much different everything I want is within reach, and usually takes a lot less time to get to. Public transportation sucks, but it really is a great city otherwise and has some things NYC doesn't (better beers, and steaks that are better and actually affordable).

There are others within this sweet spot. Minneapolis, the less expensive bits of Denver, Kansas City, and others I am less familiar with. Omaha is pretty much the cheapest of the cities I consider acceptable, but I encourage all of you to find your sweet spot city if you want to live well or cheap.

After reading this I wondered what accountability measures are in place for board members of the Mozilla Foundation.

Many non-profits have elections for board positions where members of the organization or its community can help determine board membership and vote out bad directors. Mozilla Foundation's by-laws (http://static.mozilla.com/foundation/documents/mf-bylaws.pdf) states "This Foundation shall have no members" (Article II).

Existing directors are the only ones who can vote in board elections. They are only accountable to themselves.

Mozilla Corporation is a wholly owned subsidiary of the Foundation, meaning all voting shares are controlled by the Foundation's board.

I find this to generally be a dangerous structure for a non-profit to have. Think twice about donating to any charity where the directors are well compensated and accountable to no one.

If the board is stubborn there is nothing anyone can do to force them out. Hopefully with pressure the community can achieve some reforms. One I would push for immediately is adopting new by-laws that allow community involvement in board elections.

Currently developing a Chrome extension I was dreading porting to Firefox. I am glad this is coming. Microsoft is also promising a mostly-Chrome-compatible API for Edge browser extensions.

This will mean my extensions for all three browsers can mostly share the same code. Since they use pretty standard HTML/CSS/JavaScript much of the code will also be shared with my app's traditional web services. This sounds like a huge win for bringing rich, native-like experiences to all browsers.

Would be great to see all browsers support a common extensions API. I hope WebExtensions is that API.

The article asserts Artemis will need to become a MVNO. This would be a large hurdle and one I don't think is remotely necessary. Unlimited data will make Artemis very attractive for fixed home internet service.

Also, some small cellular networks don't offer roaming and only work in very limited geographic areas. Many have successfully found niches among people who don't travel much or have alternatives when they are traveling.

Fantastic demo and the source code is concise and clean. Thanks.

After writing my comment I went looking for a summary/analysis and discovered how recent the news is. There was really nothing out there.

Speed of dissemination definitely trumps ease of reading, so, yeah, I was wrong. The OP clearly should have linked to the source here.

I appreciate the HN desire to link to the source, but as I reader I'd really appreciate submitters link to a good summary/analysis for dense subject matter such as court documents or scientific papers. Ideally they'd chose a summary that itself links to the source.

I disagree with the premise. Twitter Bootstrap is a skill in much the same way as Wordpress is a skill, even if its a less significant one than wordpress.

Familiarity with bootstrap's internals, its less mixins, their sass equivalents, its inventory of javascript plugins, and how to integrate with it is a skill worth having in many situations.

The article's closing statement "make something happen from scratch" is almost the antithesis of what it means to be a good developer. Not re-inventing the wheel, learning to integrate with existing solutions, is a skill you will find among the best developers.

On its own, Twitter Bootstrap is not enough of a skill to get any job. It is worth something, though.

Wonder if things like this might cause an issue: http://tommorris.org/posts/2550

Mozilla has always stood for freedom of knowledge, and by extension human rights (so people can access that knowledge). I don't know what Brendan's political beliefs currently are, but I hope he doesn't still wish to restrict the human rights of certain people based on their sexual orientation. Not trying to make any assumption and wish him the best, but its at least possible this could be indicative of a world view that sees discrimination as acceptable in certain situations. I sure hope that's not the case. It would not be good for Mozilla, or the Internet at large.

I read the article and recognize your closing arguments are much more nuanced than the thesis of the article suggests. I apologize for not making that clear in my post.

I still feel the overall point attacking the statistics of income inequality is much more likely to be used as a gavel to silence those working to improve the status quo. Articles like this are often cited when people try to take action to correct income inequality, regardless of what the article ultimately advocates.

That said, I do think its important to get the statistics correct. I don't think you said anything wrong (except maybe with your definition of gini, as others have noted). Your headline is a bit salacious, but ultimately my concern is how this article might be used by others.

Calling progressive tax systems institutionalized theft is incredibly clever, and incredibly false.

No one who has wealth created it by themselves. You don't print your own money, you don't extract wealth from a vaccum. Wealth is built by extracting that wealth from a shared economy. Asking those who were able to extract the most wealth to help the most in paying to protect this shared system, and help those who were exploited by it, is not theft.

You are being intellectually dishonest. I would not be surprised if deliberately so.

This is a side show. Whether or not the statistics show rising or falling income inequality is irrelevant.

There is massive income inequality. Its trajectory isn't nearly as large of an issue as the status quo, which is pretty dismal.

Until that gini coefficient is much better, and we have no one living below the poverty line, we still have a ton of work to do.

This article seems to be making a shallow point only to encourage inaction on the core problem. The trajectory of income inequality is a red herring trying to distract us from the harsh reality of our present wealth, opportunity, and income inequality.

The right thing to do is to keep working to solve the core problem. Restore the US to a progressive tax system instead of regressive. Pass living wage laws. Improve the social safety net. Maybe even consider doing what Switzerland is considering, and give everyone (rich and poor) a reasonable guaranteed income as an alternative to expensive and sometimes ineffective welfare programs.

At the small scale, volunteer locally, especially anything having to do children and improving their education.

Unfortunately, along the way we will be fed a constant stream of garbage articles like this, held up with straight faces by a chorus of onlookers telling us there is no problem to fix. Look outside. There are poor and hard working people out there who aren't being rewarded for their hard work and are severely struggling. No amount of fancy statistics bending will justify inaction.

Not a lot of meat to this article. "Ra ra, python" with no real comparison to anything else. You could rewrite the article for Ruby or javascript and you'd really just be changing the names of the tools/libraries, the points could remain the same.

Generators? Hello Enumerators in Ruby and using simple callbacks in node.

Speed? Hello V8 for JS. Hello vast speed improvements in MRI, C extensions, or leaning on the speed of the JVM for Ruby/JRuby.

Broad? Javascript is probably the most widely deployed language on the planet, and by many measures the most used. Ruby trails JS, and maybe Python too, but its still plenty popular. Not to mention the depth of libraries for both is pretty stunning.

Javascript is not javascript, ruby is not ruby. There are a number of vastly different and wildly popular JS implementations, and embedding JS in other applications is plenty common. Ruby has MRI (CRuby), Rubinius, JRuby (which is much more active than Jython), mruby (embedded ruby), and opal for compiling ruby into JS, not to mention the heavy ruby influences on CoffeeScript and Sugar.js.

The articles points are all valid, but none of them really demonstrate that Python is the answer to the article's thesis question: "You are looking for a job, which language should you learn?"

That said, Python is great. I like Python. Just not a big fan of poorly argued fan boy articles.

I wonder how the trello approach of building more complete DOM elements in backbone prior to insertion, to avoid layout thrashing, would compare to using requestAnimationFrame batching? It seems like RAF might allow the browser to see all those DOM "thrashes" as a single render and not try to render them separately, thus speeding them up.

I'm just getting started with using RAF for some JS animations I want to be very high performance, but haven't seen what impact it would have on something as large as a huge trello board.

RAF performance may also be more variable between browsers than simply reducing layout thrashing. At this point though I'm speculating. Would be good if someone more knowledgable would do a comparison.

I agree. They compared the GPU to Intel Iris GPU, but only on certain benchmarks. Seems like the meat of the review was thrown together and they attempt to distract from that with excruciating levels of technical detail.

2 of your 3 red flags can be almost immediately dismissed.

A quick search into the mentors will reveal that many of them are indeed highly respected members of their community and skilled developers. Some of the skilled developers have also worked in or built startups and have experience with doing much more than development.

Also, its pretty clear this will be the program's inaugural class, so providing outcomes from program grads is obviously not possible. The fact that this is the inaugural class might give some cause for concern, but they are very up front about that.

Your criticisms about the application seem valid, though minor.

I am in no way affiliated with the school, though I have met a few of the mentors before.

Wow. I have some trouble with faces, but that sounds awful. I'm terrible with names and not very good with faces, so those two issues compound sometimes and make me feel like an ass. Once someone adds in some details of a conversation we previous had it usually comes flooding back, but by then they probably feel a bit slighted as I've let on I don't remember their name from their face, and even with their name I'm obviously still drawing a blank.

Non-creepy networking step 1:

Don't make plans for a "weekend at a weird naked hippie spa together" during your first conversation.

Seriously, this article starts out a bit creepy and then follows it mostly with stuff that should be common sense, even for an introvert like me. I did find some of the excuses for non-awkwardly ending a conversation to be decent. Might add a few of those to my list.

I was able to scan two "unscannable" codes: (5) "Even more reduced contrast", and (30) "Spray painted code" on my Moto X. Woot! What do I win?!

I like the concept, but wish this announcement would have come with at least one or two concrete steps taken towards the stated goal. Maybe your experience getting a basic shell working or something similar. At this point I have no reason to believe anything will come of this. Was maybe a bit too early for an "announcement".

I don't know why, but this was posted before (https://news.ycombinator.com/item?id=6389664) and removed. Great article though that provides interesting commentary though satire on the state of women in software development. Worthy of more than an hour on Hacker News.

Looks cool, but was immediately turned off by the request for access to read/write private gists when logging in through github.

I don't feel `.is_a?(Class)` is ever idiomatic ruby. You should always be coding to an interface, not an implementation. This prevents things like mocks and duck typing, making testing more difficult and adding complexity when you want to add AnotherEnemy that doesn't share the same inheritance tree.

I try to avoid using `.is_a?(Class)` in all of my ruby code when possible. `.respond_to?` is much more responsible way of probing whether an object has the interface you are looking for.

I too have been in a similar situation, and it was made less stressful by the #1 thing @incision mentions.

Realize that as bad as your company is at building software, it is probably equally bad at other things, like: Recognizing that someone has checked out, or Firing someone.

When I was in your situation I went into cruise control. I did the absolute minimum to avoid disciplinary action and began seeking out greener pastures.

This was my first development job, so I wasn't sure everywhere else wouldn't be the same. I also didn't have a very strong resume yet. I also wanted to switch from Java to Ruby. It ended up taking me almost a year, partly because I wanted to be certain the next place would be an improvement.

The next company I went to work for was awesome :-)

OP, you appear to have plenty of experience and can probably be chose-y about your next move and still not have to wait very long. There are a lot of great places hiring.

> You don't know which category your project will end up in when you start it.

So true. I don't know how many times I've started building a native audio streaming app and all-of-a-sudden I realize I've really built a web-based real time strategy game.

Your points are valid... just thought that one statement was a bit absurd and quite humorous.

Are you really trying to assert that by not going after doz for having a vaguely close name in the same industry you would no longer be able to protect yourself from egregious misuse of your mark?

By not canceling doz's trademark you would be prevented from going after a hypothetical Mozz, who attempts to pass themselves off as moz by using similar branding and product offerings?

You and I, and your lawyer, all know that is complete fantasy. Yes, not going after doz may prevent you from going after similar companies who aren't really infringing your mark anyways... but you would still be fully able to litigate against companies trying to confuse your customers.