skysight-inc/HackerNews huggingface dataset:
I think the central issue here is: javascript has only recently turned the corner of utility in most environments. It used to be the toy scripting language that you used in order to tie form fields together. I used javascript back in the day to send events to a java applet that handled rendering molecule pdb files (jmol).

Nowadays, and quite suddenly, javascript is at the center of everything. Java applets? Flash? Everything's imploded. On top of that, we're revolutionizing the language (block-lexical scoping, classical OO syntactical sugar, standardizing import/export, promises, generators, async/await, optional type annotations) in a way that improves productivity and the reach of the language.

There's a lot of churn in tooling and tools, because things are new. I've been doing software since before the STL and generics in c++, and I can say that I've seen this kind of churn before. It happens with lots of languages when they turn the corner in real exponential growth. I'd say it used to be the case that there were far fewer programmers in general, and they were a far more homogeneous lot than they are now (we still have a long way to go on that front, of course), so standardizing around autoconf and make was easier than standardizing around (say) ant vs maven or grunt vs gulp.

To the original issue - I've been doing a lot of flexbox work lately, and one of the more annoying issues is dealing specifically with grids. If you just use flex-grow like a good flexboxer, stuff doesn't align well in columnar format on your page. Flexbox is great for some things, but handy macros for making a grid out of flex boxes are pretty useful. Useful enough that I ended up writing pretty much the same thing myself anyway, and useful enough that it makes sense to hoist some of that code out into a standalone library. That way, you can encapsulate fixes for browser quirks (shakes fist safariiiiiii!), and have the option to pull the whole thing into new projects or leave it out if you don't need it.

People can complain about making a spiffy project page for a small library, but hey. People complain about a lot of things. Those kids, for example, on my lawn. I installed a motion-controlled sprinkler to keep them off, but those wacky kids are still on my lawn.
I live in Canada.

I haven't actually had actual cash in my wallet since before Christmas. Every store takes credit or debit. I can email money to people I owe money to. Cash is darn inconvenient.

Giving money to homeless people is just about the only thing in your list I can't do.

We also have contact-less payments with both credit or debit so it's even faster for low cost purchase. Need a coffee from starbucks? Just tap your credit card and go. But the time you put the wallet back in your pocket it's authorized.
Not the most elegant solution, but quick & easy: you could paste the list into a Google Spreadsheet, then add a formula to create a hyperlink to Netflix. E.g. for iTunes (I'm not on Netflix) this would be

"http://ax.itunes.apple.com/WebObjects/MZSearch.woa/wa/search?term="&A1

, with A1 being the field for the movie title.
So take a look at the Netflix search results url and see if you can do the same there.
Perl is not dead: It was early web novices that gave it a bad name
Cloud identity management for developers: Getting started guide
Every time I think of Javascript language concept, I think about Lisp, and every time I think of "javascript fatigue" I think of Lisp Curse.

I think that the core feature of JS and Lisp is the fact that there's no concept of "compile time". Declaring classes, methods, even entire language concepts like promises happens entirely in runtime, and the language is soft to touch that every programmer with a healthy dose of curiosity and love for his craft is trying to build his own OOP system on it at some time.

This softness allows for incredible freedom for a programmer, and incredible speed of development of the language. But freedom is dangerous, both when you work with code written by others (often idiots, either only in the eyes of maintainer or completely objectively) and when you just support your own codebase that you wrote several years prior. Would anyone expect anything else from language with such capabilities?
> Like the only thing between terrorists and the subway platforms is that they can't afford ticket, so they have to go through the staff gate.

Obviously, terrorists must always break all laws in the process of committing terrorism. They have to illegally park their cars, jaywalk to the location, commit some acts of public indecency on the way, litter at random, and pop their heads into a crowded theatre just to yell "fire!"
On UK to France you are checked because you are crossing the Schengen border.
They are not stupid. They are just driven by wrong set on incentives. One which emphasizes short-term local success - i.e., being able to see the phone of the terrorist and maybe find something there and get a good press release and promotion, and maybe find some other terrorist (that rarely happens but has to be at least part of the law enforcement motivation) or drug seller (that happens much more often and is really what it all is about). Long-term problems do not figure much in that calculation - if the system gets corrupt and ruins security, it's not their fault, they didn't do it, they just did their job. And note that with drug war going on, which law enforcement is losing miserably, and terrorist threat to which they don't really have a good answer (not their fault here, nobody does, at least not in the enforcement realm) they may not exactly feel they have the luxury of long-term planning. Now add mass-media to that which provides extremely sensationalistic short-term reporting with almost no long-term focus - and you get perfect collection of incentives driving this behavior.
> they only care about the encryption their adversaries actually use which - given that 99.9% of the FBI's adversaries are not crypto experts - turns out to be whatever ordinary people are using automatically thanks to tech companies switching it on.

Of course, this is also the technology that 99.9% of U.S. federal staff use too. Probably more like 100% counting personal use of technology.

Across the board, enterprise security today is dependent on the security of consumer technology. Unfortunately, a lot of people in the federal government don't get this; they still think there is a difference between "secure federal technology," and what every else uses.

There's not even a Cabinet official charged with enterprise security for the federal government, so there is no one to even speak up. The FBI and intelligence chiefs are all very high-profile, and they are primarily concerned with access, so the federal conversation seems skewed. Which it is--it matches the skew of the federal mindset in general. The best technologists go to the breaking and entering teams. Meanwhile OPM loses 22 million accounts.
I didn't argue any of those things. I think you missed the subtlety of my comment.
At work: Mostly support inbox type stuff, and building reports.

Outside of work: I'm working on a project that involves Elixir for the backend and Vue.js/Vuex for the frontend. It's like/is a dispatching web application. So far I have login/logout working properly, user roles are up and running. Next: Event CRUD, Call CRUD, then Socket.io for communication with Mobile and SMS for others.

https://alpha.highwayapp.co - Couldn't find a good name for it so I called it Highway.

Also I'm trying to figure out the best way to go about multi-tenanting the application.
On Troubles of Team Communication
Server and client remote code execution through buffer overflow in Git
> The problem is that we now know that the government has the goal of unlawful surveillance without oversight from courts, the legislature, or the public … There has been a profound breach of trust (revealed by Snowden) and we must insist upon the rule of law …

Nothing Snowden alleges is illegal or unconstitutional, despite his and his supporters' repeated assertions. 'I don't like it' does not imply 'it is illegal and unconstitutional.' Neither the law nor the constitution forbids all bad things (nor does either mandate all good things, but that's another issue).

You are correct, of course, that one major issue is that States cannot be trusted to respect their citizens' liberties. Another is that States cannot be trusted to take care of their own data: an escrowed key will shortly become a leaked key.

> Incidentally, if Apple seems likely to lose the battle over a back door, it ought to offer an Ethereum smart contract that will unlock one phone every day, require a key provided by each member of congress (with 100% consent required to unlock a device), and publish all unlock key requests on the Ethereum blockchain after a 30 day delay in case an investigation is in progress.

That doesn't make sense, since the Congress is the legislative branch and it is the executive which actually does things. What could make sense is a smart contract which is unlocked by the judiciary.

But we're a long, long way from enforced smart contracts which do things like handle succession of new members &c. I can't wait until we're there, someday, but it'll take a good long while.
Note that this use is the original meaning of "alien." The contemporary meaning of "extraterrestrial" is a recent mutation of it.
Related blog post: https://medium.com/@outduoapp/introducing-outduo-69fec10820b...
Structured interviews work better than unstructured but they are still a poor indicator of an employee's future value.

You should try psychometric testing and other measurable things instead of chatting.

http://www.theguardian.com/lifeandstyle/2015/nov/22/why-job-...
If only there was a standardized system for installing frontend and backend javascript libraries so that the devops people don't need to learn about the specifics of each library. We could call it something like the "package manager for libraries in node" or something.
Which is exactly why the gun community is unwilling to enact ANY type of new gun restrictions no matter how "common sense" they are. People on the left constantly boast about how they want to take all of the guns away and will use a baby-step approach to do so. While Obama uses crocodile tears after a tragedy and tries to convince the people that "nobody wants to take your guns away"
If only good guys used guns, nobody would need them.

It actually is "we know bad guys already have guns, so better if good guys have them too".

Same with crypto, btw.
I fear the easier it is to submit links the more low value ones will be submitted.
I don't even use TypeScript but I don't buy your arguments at all.

> when it can be compiled into WebAssembly then count me in I'll certainly give it another shot. But until then I just don't want to deal with an, albiet probably rare but possible, transpiling bug

You really think a TS->WebAssembly compiler is less likely to have bugs than a TS->JS transpiler (which essentially just strips out the type annotations)? Yeah, no.

> It lets me dogfood more effectively and write better, real world unit tests.

I have no idea how these things are relevant. Why would adding type annotations to your code affect your ability to write unit tests. What does dogfooding have to do with anything?
I don't think "honorable software" is a great idea. Laws and social mores change all the time, but software could be forever.

What if, in the 70s, the first creators of Unix tried to make it "honorable" by baking in DRM restrictions? DRM restrictions "enforce the notion of intellectual property for all users", but I and many others consider it terminally abhorrent to the concept of user freedom and general computing. Imagine a world where you could only grep a file on your system if the file's intellectual "owners" allowed your system to do so. Such a world would have never seen the open source computing revolution we're living in now.

Gay marriage was illegal until just recently. Would "honorable" wedding planning software compiled in the year 2001 explicitly reject gay couples, not because of the developer's personal preferences, but because their union was against the law at the time? By my reading of your definition, then yes, that's what "honorable" software would have done--enforce the day's law on the user on the justice system's behalf.

I'd go even so far as to say that "code as law" is an extremely dangerous concept that conflates the uncaring lockstep precision of a mathematical system with the messy, changing, and imprecise reality of human law and justice. Humans must enforce their own laws, not machines, and thank God we have judges and juries, not algorithms.

No, "honorable" software is not a useful target. Better to make general-purpose software, agnostic of today's laws and mores, in the spirit of empowering users to use that software as a tool in whatever way they deem useful--not in whatever way you thought was "honorable" at the specific time of compilation. The software I use is my tool, not my overlord.
because they replicated a function of humans that they wanted intact, like speaking, that requires breath, nice demo, as always story is king, it gripped me :)
I do think people would object to it, doing so on the view that he would have already considered silent films and didn't think any of them should make the list, and that now he was just bowing to external pressure.
How will they come back if there isn't a tech scene waiting for them?
It's not an easy win compared to just adding more length. Yes adding those characters to the set would increase the search space by 34%, but going from 2 characters to 3 (with the original set) would increase it by 6100%.
I think this is a bit of a hasty claim with a bit of truth to it, sort of like if someone said "All JavaScript libraries should be authored in CoffeeScript" in 2010. A cambrian explosion occurred, then the community eventually coalesced. Coffeescript itself isn't (and wasn't) perfect, but it pioneered an approach that led to a whole lot of progress in JS.

A better framing of this is: "Type systems are good. The JS community should sort this out in the next couple of years and will probably a standard approach, but it's worth diving into the assorted tools that exist -- TypeScript, Flow, and any others -- to understand the ecosystem and find pain points."
Exchanges are devouring each other because no one buys individual stocks anymore
> I bought my midrange desktop including monitor and peripherals for less than $900 three years ago and yet from a performance perspective it's still 30% faster than the PS4.

In raw computing power perhaps but consoles have an advantage over the PC due to the fact that developers will optimize their games heavily and specifically for a console.

> Somehow that PS4 lasts 10 years but the PC has to be upgraded every year

Not sure where you're getting this from. I said that the PS4 would be upgraded 3 times over 10 years (i.e. the console lasts 3 years) and that the PC's GPU would be upgraded every 2-3 years, with other upgrades like CPU, RAM etc. coming around every 4 years. I think that's fair given that a mid range GPU from 2013 can barely meet the minimum requirements of some of the latest games.

> You are also forgetting the fact that you can literally get the best consumer PC hardware on the planet for a mere $1700

$1700 is not a trivial amount of money. Sure you could get a beast of a PC for that price. You could also buy a PS4 and 23 new release games (or say 3 new release games for $60 and 30 older games for $40). I think selling the PC is pretty hard with those kinds of numbers.
Very interesting I didn't realize the difference.

How about this? https://github.com/shashi/ComputeFramework.jl

But I suspect it has the same problem.

Edit: There is also this https://github.com/JuliaDB/DataStreams.jl
JavaScript, IMO, forces the developer to do a lot more defensive coding. All API's have contracts. An add() method that computers two numbers shouldn't expect a JSON object. For that matter, your method's contract shouldn't return an "any" for the same reason that you shouldn't expect "any" as its input.

What TypeScript does is remove the ambiguity of API development for front-end work. Considering I've worked in some big enterprise wide JS projects, TypeScript answers the question "Wtf is this returning?" which lessens my debugging time because I know exactly the type of the object being returned.

Your arguments are actually kind of moot. When you write in Java, you're really just boiling it down to an intermediary language. Should you write it in IL? Why not C/C++? Why not assembly? Shoot, just handout punch cards again and let's get to working. Abstraction isn't the enemy here, it's the value of the abstraction that gives value to it. TypeScript isn't so much an abstraction as a superset but it's static typing alone is worth 1000x over.
I have a hard time putting it to words, but I do feel that while computers are pretty good at statistically parsing language, humans have an extra sanity check that parses "meaning" (what ever that may satisfactionally be defined as).

Maybe it means we need to hook up our NLP pipeline to deep-visual networks and knowledge-graphs in order to ask "Did the message of that sentence make sense, and if not, should check a similarly sounding sentence or a different parsing of the sentence in order to make it more cohesive"
> And everyone with legitimate access to the warehouse will be 100% trustworthy no matter what for the entire span of time they are granted access

Of course. These are upstanding FBI agents we're talking about. There's no way one would ever cheat or steal or blackmail anyone.

http://www.cnn.com/2015/03/30/politics/federal-agents-charge...
JUCE seems interesting. What kind of difference in executable size are we talking about, approximately?
> I (as strictly ops person)

Aha!

Vagrant, Docker, Chef, Ansible, Fabric, Puppet, Jenkins, Octopus, TeamCity, Sentry, SVN, Git, AWS, Azure...

We all have monkeys on our backs. We all search for the best tools to use to make our lives easier and our products better and more reliable. When something new or improved comes out, we evaluate it, we weigh its use against everything from performance to code quality to backwards compatibility to having everyone learn yet another tool/library. If the benefits outweigh the drawbacks, then we make the switch. If not, then we leave our tool chain as it is.

Are there people who blindly switch to the Next Big Thing (tm) every 3 months? Yes. But I've found that in general they are few and far between. Perhaps you happen to work with one or more, but know that the entire web-dev community discourages that behavior.
It doesn't have to look "exotic" at all: Sam just sends Joe a file in base 64. But that is how all the multimedia content is sent in e-mail now. Until dig into what Sam sent, it looks like just another JPG file sent in e-mail. But translate it from base 64 and give it to an image program and will discover that the file is not a JPG file. Or a PNG, BMP, MP3, WAV, EXE etc. file either. But about have to translate from base 64 to conclude this.
I do have a unique genuine piece of North Korean propaganda for sale if anyone is interested. It's a hand-painted poster for a state opera called 'Sea of Blood'. Contact me if interested: http://imgur.com/LKiYMWD $10,000
Vancouver has various restrictions just like any town, but in general it would be incorrect to state that they restrict construction or don't build high density buildings. Comparing a photo of 1990s downtown Vancouver to now it is shocking how many glassy residential towers there are now. Vancouver and its satellite cities are constantly building new condo buildings.

I suppose you can always argue that a city can build more, but I've seen more construction cranes in Vancouver than just about any city I've ever visited.

I think more dominant issues that have influenced the price of Vancouver housing is low interest rates, lax lending rules, government policies that promote home ownership and speculation, and the influx of foreign capital.
> QuickFlux is promising start for the Flux pattern in Qt. I was thinking more on the lines of React Native [1] like support in Qt.

I know :) , and I searched for that too when I joined a QML project after working on a React one. So far there's nothing like that, thus the "around" in my comment.

Now, about why no one tried that yet, I'd propose that newcomers (including me) want it but don't know the platform well enough to build it, and experienced C++/Qt-ers could try it, but they don't care about new frontend stuff like React the slightest bit, as they are used to their own thing (which works well too!).

It's just two different technical worlds with different working solutions, and little interest to pick ideas from the other side of the fence. That being said, I'd love to be proven wrong.
Gaming Veterans Start $50M Virtual Reality Fund
This seems to be a direct result of capital flight from China. Wealthy chinese who are able to get their money out (through corruption, money laundering, or otherwise) are looking for somewhere safe to park their money for the inevitable decline in value of the yuan. China can only artificially peg their money to the dollar for so long, until they run out of dollars, and they are drawing down their reserves at a record pace due to the appreciation of the dollar.

Wealthy chinese know this, and use real estate in markets such as Vancouver, SF, and NYC, because it's fairly low risk and likely to appreciate. See http://www.npr.org/sections/thetwo-way/2016/01/13/462994857/... and http://www.nytimes.com/2016/01/14/us/us-will-track-secret-bu...
Nope, in fact you should not use JSDoc, and you should not follow Google's JavaScript standard, despite the fact they authored V8.
Instead, you should follow a self-proclaimed "standard", that adopts unsafe practices such as not using semicolons, something that Google itself factually demonstrated as being unsafe. But even that doesn't matter.

Let's let humans do the job that computers can do faster and more reliably, like validating the types of variables and function signatures. Let's do everything by hand. Let's give control of our programming future to people that don't care at all about programming.
seems this has not been fixed even up to git v 2.7.3

https://marc.ttias.be/oss-security/2016-03/msg00195.php
If you're planning to run your own server, give this a shot
https://github.com/mail-in-a-box/mailinabox
It's fascinating, in Saskatoon we've got a pretty neat little tech community. Some people leave, but there's a few companies that identified that people were leaving or contracting remotely and increased their salaries to be sufficiently enticing to keep people here.

There's still some people who leave (apparently there was a thing for a while at Apple where people would hang their Saskatchewan license plates on their cubes), but as a whole there's a lot of people staying and making good money here. In the last 10 years or so since I've graduated, entry-level salaries are up probably 50-70% and intermediate-experience salaries around $90-100k/yr aren't unheard of.
Crawling a page that loads content dynamically with Selenium in Python
Just yesterday I got the question "Why can't we just use Windows XP" and we're just moving users from Windows Server 2003 to 2008 (Windows Terminal Server). The changes are minimal, yet it's enough to disturb people.

True, given time and education they might like newer versions of Windows better, but let's face it, most companies won't do retraining for Windows and Office.
Pigeons have proven themselves over the centuries, but I'll take a look at Seedboxes!