skysight-inc/HackerNews huggingface dataset:
We are a small shop that has 4 repositories and 36 users (over half the company). About 10 of those users actually contribute code, the others are monitoring issues, pulling code just to run tests or create distributions, or bots.

If we accidentally hit the upgrade button (we won't), our cost would go from 300/year to 3,648/year. Since only a small number of projects are on github - we use TFS for our main project and github for tools - its just a non-starter.

Heck, 5 "bot accounts" is $540/year to support CI builds and slack notifications. Yikes! More than we pay now.

It seems like the only shop that would save money would be the little in-house development departments with 5 people and tons of projects. However, even there they would probably forego using issues tracking in github because of the extra user cost.

I would be very interested to see real stats on how many orgs actually "upgrade" to this new more expensive pricing model vs how many stay with the more sane model. The real losers are orgs that can't sign up under the old model. The real winners will be the github alternatives (gitlab, bitbucket, etc) that can use this as an opportunity to grow user base.
Great tool! I sometimes do the same locally to check out language behaviour, but most of the time it's just one compiler. This tool lets me see compiler differences and the evolution between compiler versions. Nice.
Certainly not web dev. I do see it in jobs ads from bank after bank, broker after broker, information dealer after information dealer.

I don't really know what "popular" means in this context. There's certainly no shortage of jobs requiring C++ in London.
I'm responding to the article that the author linked to, which does mention static typing. This comment is an attempt at a hypothesis for why some developers dismiss the importance of such features/tools.
Great idea - definitely will check it out in the future.
Imagine the financial impact on the manufacturers of performance-enhancing drugs and forged birth certificates (to make athletes seem older than they really are)!

Edit: If the IOC is half as corrupt and greedy as the FIFA, canceling the olympics should be a financial plus for Brazil.
You've never seen a Perl or PHP codebase age poorly?

That's unbelievable.
Computing explains the technological world around us. The same reason it's very beneficial for society to have a solid understanding of basic science (and that doesn't mean being scientists), today society should expand its horizons and have a basic understanding of computing (without being software engineers).

I don't need to be a mechanic in order to fix my car was used a few decades ago. Today, cars may very well be black boxes, but if society had a basic understanding of computing, perhaps they'd advocate for more open car technology. It's beneficial for everybody.
The Panic Sign
I put "enterprise grade" in quotes on purpose. React stack (not React alone) being used successfully by a 9-5 Java or C# shop is not something I'd be willing to bet on.

Sure it's simple as far as hello world apps go, but once you start adding state management, routing, etc. you start seeing that it diverges from conventional architecture approaches. Not saying that's necessarily bad but it does not mesh well with enterprise development - I hope you understand what I mean by this.

And tools that help ensure consistency/quality in that kind of environment like TypeScript are very unsatisfying with React and various libraries, for eg. look how tedious Immutable.js typed records are, and check out typings for Redux related libs - bunch of any typed parameters and return values. Flux basically has no support outside of React and it wouldn't even run on Windows last time I checked.

So like I said - it depends on the context - if we're talking a bunch of JS frontend devs I'd say go for React if it fits what you're trying to do. If you're a .NET/Java shop Angular 2 is probably going to be a better fit, patterns like DI, OOP, etc. are all at the core and it's a full stack framework you just pick up and follow it's conventions/best practices/design decisions - way less decisions than React and way better docs (for the stuff not included in React I mean, React documentation is decent).
He may have used the stolen funds to get a smaller mortgage, thinking it would speed things up (as was mentioned in the video).
None the less it's all too fishy.
Why wait a year hoping to get the funds and not sue right a way for embezzlement, sell the house pay the bank and the rest of the cash will be returned to the company.
He did return 110k from somewhere so at least more than that would be returned to the company......
To quote Tertullian, what does data structures have to do with setting up a home wifi network? The latter most certainly doesn't need knowledge of the former.
To offer a different perspective, we also had the cold war during this period. This was an era where the US was successfully outspending USSR militarily. I would argue, as others have, that if we hadn't dedicated significant resources to our military then those resources could have been applied to society and possibly avoided the crisis of democracy.

Or to put it simply the hawks in power manufactured our own crisis to stop us from focusing on domestic and social improvements.
This is also probably why there are so many just-plain-awful coders out there who don't belong in the same room as people who do things well.
The world is what it is regardless of anyone's views. And there's a difference between values and beliefs about the state of the world that are open to empirical investigation. If someone thinks the sun orbits around the earth, this is not a "value". It is a hypothesis that can be investigated and refuted.

The question is: how do you react when the data contradicts your hypotheses? How do you react when it is shown that the arguments you base your views on are fallacious? The SJW position is to dismiss empiricism and rationality instead of changing their views.
The 50% heuristic comes from a story I read once about a company claiming they were able to build a ~200 kloc app in a dynamic-typed language.

The secret was their ~200 kloc unit test suite. :)

It has nothing to do with argument types per se, just that one must have very high coverage in order to be able to be reasonably sure that their app won't crash after minor code changes.

In my current project we can get away with having integration tests cover a lot of ground and only unit test what makes sense thanks to static typing. High coverage is good to have, but should be balanced with test development and maintenance effort.
It should be considered, dont know if it makes sense but the pros and cons should be weighed and respected international health organizations should weigh in.

Overall though, think given the fact the facilities have not been fully constructed, the Brazilian government is on the verge of collapse, and the risks of being a major disease vector is plausible...

Should definitely consider delay or moving
From the article: "And while we're currently not enforcing a timeline to move..."

I too was sad to see many of the new developments at Github, but if they were money grubbing like you say, wouldn't they make everyone switch faster than this?
Is Java really that unusual of tool? Java 8 + Spring boot + Jooq is a simple and powerful tool to build backend services. There is already great tooling, libraries, and a wealth of information around solved problems. Dare I say, it is almost boring to build backend services with the above stack because it is so straight forward. Maybe that is why it is not used, I mean talked about :)
In the original article, he indicates Swift, Rust, and Go are tomorrow's languages. The issue really is that the level of support in the various frameworks, the eons of bug-crushing and feature additions, and the libraries available, are going to be behind for some time. This is why I'd still gladly pick Django today.

What is "the future" isn't really so interesting as what is productive.

Yes, performance matters a bit, but development time is usually much more expensive than adding a few nodes to an autoscaling group, and not worth the cost of using less fleshed out libraries.
No doubt; it still doesn't follow that she holds a grudge based on it. Lots of people have plenty of karma; patio11 isn't even the #1 on HN.

It's fine that you think "that's probably it". Posting that as if you knew it for sure is unjustified and rude.
How we approach product design at Unsplash
Please don't learn to train AIs
It would probably more beneficial for everyone to learn the logic used in coding rather than the less important syntax of coding. The logic is what is applicable to other fields.
Will Saudi Arabia Be Able to Break Its Oil Addiction?
You're very welcome to switch to GitLab.com, we are free forever https://about.gitlab.com/gitlab-com/#why-gitlab-com-will-be-... and it can import directly from GitHub.
She even said as much in her blog.

She had to leave HN for 18 months because she couldn't even form a civil response to any comment by patio11.

This post really has no place linked on HN - it skirts the letter rules of the site by being an offsite link but violates them in spirit.
see, the whole repo is accessible to the members of the team that are allowed to see the secret - basically the two folks that have root on the machine anyways. There's very limited use in encrypting the repo. There are no SSL keys or any secrets that would require tight security. It's basically our newrelic and some other api keys for reporting services. Even if that repo would be breached you could only start sending fake data to those services.

I'm more concerned about someone hacking the machine than someone hacking github to access the repo and retrieve the newrelic key from there.
Being able to fix your own sink is actually a useful skill.
At the same time, disparities in practitioner quality are going to exist in every field, not just software development.
> a failed initial pricing model by GitHub

It's been 8 years since they revealed their pricing model, which has remained mostly unchanged on the lower end and only adjusted on the high end to account for GitHub Enterprise and suggest people move to that instead of the gargantuan $3k/mo plans. I don't know many SaaS companies that don't tweak their pricing much more infrequently than that. Thoughtbot's Giant Robots Smashing into Other Giant Robots podcast for the past few episodes has been consistently talking about A/B testing pricing models, prices changes and signup, conversion and churn, as a weekly adjustment on some of their services (FormKeep, Upcase, etc)

https://github.com/blog/22-the-pricing-plans
Yes! Take risks, try new stuff, follow your muse. Later on, possibly with responsibilities like partner, kids & mortgage you won't have so much freedom.
I searched 'hostels in the world' and got "sugary drinks can kill" and "Fanya's rare metal bubble: Indium prices since 2011".
> it's a desire to teach powerful problem solving techniques and tools to everyone

And like any teaching, that job should be properly paid. What I find irritating is that it almost seems to be a given in the tech industry that people would do this job for free. And the fact that it will create more software engineers on an average leads me to think that all the "Learn to Code" movements are not as altruistic as they may seem.

I agree that everyone should learn to code, but similarly why shouldn't everyone learn basic science, economics, or civics? I know a lot of people the US anyway seem to be really behind the curve on these matters, but because it doesn't really benefit large corporate entities, they aren't lining up to teach kids these skills.
I hope that any team using github to share passwords is driven to move away from that method because of this price change. That's a bad bad idea.
The boot ROM's recovery mode lets you load arbitrary code into RAM and then boot it. The conventional way to use this is load a flasher program that you then use to flash a new OS image, but you can use it to run any Linux kernel and and software of your choice purely from RAM, which can then do what it likes to the existing OS install. See http://linux-sunxi.org/FEL/USBBoot
I see it more as offering the opportunity to people to have an interest in it. I learned to code in my own time, by digging around and finding tutorials and snippets.

Part of my secondary school (high school) education was mandatory science classes where we covered biology, chemistry and physics. The majority of that stuff I haven't used since. With computers being more and more a part of our daily lives, why shouldn't coding be part of what we teach our kids? If they don't take an interest in it then that's fine, but there'll be a good chunk that will then use it later on in life.

Not to mention that it's actually great for teaching problem solving. Showing that breaking down a problem and solving it in a number of steps really helps grasp how to solve a problem.
I read an article not long ago that Github had to spin up three physical machines, just to handle one customer. Although it was an extreme example. Compared to slack, who could probably have a million users one a single machine, making it almost zero marginal cost per new user. While a user for Github means buying more hardware and a notable marginal cost.

If you for example are a reseller of commodity goods, you can't have a lower price then the price you buy it for. So you can't have a model of say unlimited goods for a monthly fee. And the price will most likely be based on per good.
whether implicit trusts such as for example Google Play Licensing[1] or explicit trusts such as for example the set of Certification Authorities Android devices ship with, you are trusting Google in many ways.

[1] https://support.google.com/googleplay/android-developer/answ...
I think the old icon is very 'iconic' and to ditch that may be a mistake.
Looks like with our company the price goes from $25 a month to $133 if we move (or are forced to move) over to the cost-per-user model.

GitLab was already looking good, if we're forced to change well likely move to GitLab. Github's pricing was already overly expensive for what you get, in my opinion.
Think about how much time people spend in front of 24" screens with a keyboard. "Desktop", or whatever that evolves into, is overwhelmingly where real work still gets done. For as critical as that environment is in the modern workplace it's historically been drastically underserved by this community.

Yes, there are a lot of tools like Swing, Qt, Cocoa, GTK, WPF/WinRT, but their development communities are much smaller than the javascript/web ecosystem. They also create enormous portability problems, particularly in an environment (especially in the business world) so heavily dominated by Windows machines.

This community is acutely aware of what happens when the barrier to entry is lowered and the development tooling improved. The tooling that Electron provides via Chromium is also something that should not be understated. Chromium's dev tools are remarkable and improving every day. Few other ecosystems, especially old desktop ones, have debugging environments as rich. The painting performance / profiling tools alone go to great lengths to keeping everything running at 60fps. Furthermore modern CSS layout engines like FlexBox give you an enormous head start on a notoriously difficult problem and is a joy to work with when you don't have to worry about browser compatibility.

I will admit, the getting-started cost of Electron is high. Shipping all of Chromium and Node is no small feat and frankly probably not suited for a minor utility. However once an app crosses even a modest level of sophistication the benefits of this environment are definitely worth it. There are also several specialized tasks that Node probably isn't suited for. Luckily, since you have full process control and the ability to compile native modules any additional specialized task can be run on the side.

The past 18 months working with Electron at Nylas have been some of the most enjoyable development experiences of my life. Much of the crap that frustrates people out of web development (compatibility issues) go away. Being able to build an app at the core of people's day-long experiences is deeply satisfying and something I'm indebted to the Electron team for.

If you're in the Bay Area and still have questions or are just curious, come join us at the Electron Meetup on Wed May 25: http://www.meetup.com/Bay-Area-Electron-User-Group/events/23...
Okay, I would like to remove Hello and Pocket from Firefox. Do you think Mozilla will merge my pull request that I am empowered to initiate?
Indeed.
They could have hold off receiving the money until a proper company can be formed.
Although David was the CFO so he could have easily embezzled the money even in a corporate account.
Define quality journalism and you will come up pretty short I think :)

What most people mean with quality journalism really is stuff like investigative journalism or opinion pieces by people like Thomas Friedman. And there is plenty of that online.

The idea of quality journalism beyond that really doesn't exist in anything but the journalists heads.
> Sounds like the only customers being lost were those using github for no-commit users. Is that really a huge segment? If so they just need a special account status to fix this.

I would think this is a large segment, or at least Github would like it to be. Any software company that sells its software directly, and so has a sales team, a support team, marketing and so on will need to make all of those people users in Github if they're going to raise GH issues, see the code, prototype something for a client, help with branding, or anything else. If you're using Github the way they want you to (issue tracking, wiki, all of the things Github adds over vanilla Git that are "sticky"/hard to transfer to a competing service) you don't want to restrict access to just your developers. You want your whole company to be using it.

In any software company I've worked for, those non-developer users number 3-4x the actual number of developers. And I've never worked for a company that would consider restricting which users could raise issues with the product.

I agree that having a non-commit account status that didn't count toward the per-user pricing would fix this, for that particular (I think common?) case.
Every time I see these types of articles I think about forming my own consultancy and farming myself out. If they're paying you $600 a day then I assume they're making $900 a day.
I agree completely, I'm just saying it's a factor that should be considered, like many others, when making a comparisons with other shells.
Life and death also hang on other factors that swing the argument in the other direction, like can you scale quickly if you are the next big thing, are you stable, is your uptime acceptable, are there huge security holes that can tear your company to the ground over night...

Speaking in generalities isn't very useful.

Each project has to weigh the pros and cons of each decision. It's basic engineering.
Hi, I'm writing a book comparing them both at the moment:

https://www.manning.com/books/cross-platform-desktop-applica...

Having built apps in both, my view is that if you want the tool that fits best with Node.js' conventions, Electron is closer to that philosophy. I say this because of the way that the Node.js contexts of the main (backend) process and the renderer (front-end) process are kept separate. This is different to the way that NW.js has managed to blend the Javascript contexts of both into one, which can lead to odd behaviour when it comes to apps that run with multiple windows.

In terms of momentum, Electron is definitely capturing the most attention and it looks like it will eventually become the goto framework for cross-platform desktop applications over NW.js, which is a shame because NW.js has been around for a while now and was the pioneer of being able to build desktop applications with Node.js.
You have hit the nail right on the head. Everybody + opportunity + non-mandatory. This concept of equal opportunity seems to have disappeared in the last 5 years and I'm heartened to see people still talk about equal opportunity (vs the fallacy of equality), even if the media doesn't discuss opportunity anymore.

I was a kid who was writing assembly at about 10 years old because I loved it. I saved up to buy my own computer by delivering newspapers for 2 years. I learned to program by trial and error. I introduced my kids to programming but never pushed it. They have not embraced programming like my wife and I did when we were kids. I would not want programming mandated for my kids, despite my own passion for programming.

A comfort using computers to do research, word processing, calculation and create basic posters/articles/projects/videos would be very beneficial and may be better a better mandate than programming.
lower rates tend to be hourly, higher ones tend to be daily.

though that's not a hard and fast rule.
I think the article title and body are a bit disconnected. The author doesn't _really_ want no one to learn to code. They do, however, want to make sure people understand it's not going to be their golden ticket to the Wonka factory.
"Everyone needs computer programming. It will be the way we speak to the servants." -John McCarthy in 1966 (Developed Lisp, coined the term A.I.)

(Later he said: "Alas, it didn't come to pass.")
I've found upgrade hell can apply to C#/dotnet stuff too. I work on a project that has attempted to upgrade Entity framework versions multiple times and keeps pushing it off because we get buried in compile time errors. It's a case where Microsoft supported several different paths to architect an app and then quietly deprecated half of them - database first vs. code first, POCOs vs. ObjectContext, etc. and we happened to be on the losing side of history. Compile-time errors are definitely easier to find, but the path to fixing them can be just as bad. What I really long for is good documentation and a clear path forward for each breaking change.
Making your JavaScript resources load 30% faster
GitLab has a hosted solution, take a look at that. We love them, and they making moving over from GitHub easy.
> What other lucrative professional industry is this easy to break into?

It's only easy if you're an autodidact and have high-level English proficiency. In reality it's easy for the people it's easy for, but 95% of the population is still excluded.

Programming as a skill will be completely commoditized in the next ten years. But some developers will still make good salaries, because as the world gets more interconnected the value of being a winner in a winner-take-all market is only increasing.
Please don't learn to think critically.
It is useful for people to understand what goes into developing software in the same way that it is useful for people to learn geometry in high school. Code is the most tangible form of algorithmic thinking that is accessible to most people. If a few hours of coding help people understand what it means to think that way, then it's a good thing for them to do. I took a drawing class, as an adult, to help me understand artistic perception. I'll never make a trade of it, however.
Thanks! We are looking for feedback as well, so let us know if you think of anything.
A huge upgrade on code with no tests and a bunch of magical dependencies?

The problem wasn't Rails there.
Peachy Printer Creator Admits Fraud in Latest Update
Don't worry, the virus will not be racist.
I know the bar is pretty high in terms of what is passable as a programmer that works actual gigs. It's higher than a lot of other professions, where credentials mean more than actual performance and you can fudge/bs your way out of many situations. So it's fine if someone wants to try more power to them. Anyone can potentially do it, but to do it at a commercial level you can't just pass yourself off you have to be relatively good at what you do... otherwise you won't get hired or get fired rather quickly.