skysight-inc/HackerNews huggingface dataset:
I don't know about the Chrome extension, but "anonymouth" is one such tool:

https://psal.cs.drexel.edu/index.php/JStylo-Anonymouth

https://github.com/psal/anonymouth
They have much larger budgets and tighter tolerances than all but a few domains. Nevertheless, their approach is more modular than you think. They do a lot of designing to interfaces, especially where the necessary tech doesn't currently exist.

EDIT: Forgot to mention how little engineering (relatively speaking) NASA does these days. They farm a lot of projects and sub-projects out to contractors, devoting most of their engineering expertise to the requirements phase. Now imagine if your clients spent that kind of time communicating upfront! Software would be a lot better across the board.
Lion of the Call Center – Must Have Qualities for Digital Era CC Manager
I used to work in banking security and I can understand the bank's concerns. If they allow a 3rd party access to customer data and that customer data is subsequently leaked and used for fraud, who's liable?

If a law could codify an acceptable answer to that problem, I think a lot of the security/regulatory problems could go away. Banks might still try to stop the process for competitive reasons, but they might not be able to lean on the crutch of "security" to do so.

In the UK this problem isn't new, there were aggregator services 15 years ago that screen-scraped banking data to provide customers with a consolidated view of their finances and they required customer's to provide their credentials for them to do that. Banks understandably weren't too pleased about the idea of 3rd parties having those credentials.
You're the one focussed on GNOME. I didn't read the article until you said it was about GNOME, which it isn't.

If would be nice if you'd tell me how Unity 7 is GNOME? Or apport? Or baloo? That's all GNOME? Gstreamer? GNOME? Really?

As mentioned various times: please read what I wrote, try to form an argument. Maybe even use your brain. Good luck!
Eugenie Bouchard Has a Blind Date with Stranger After Losing SuperBowl Tweet Bet
January 2017 links
Javascript is the app distribution platform that won, because the others were worse.

ActiveX? Too much lockin, no sandbox. Java applets? Too heavyweight. Flash? Nice tooling for the producer, terrible security record. ClickOnce/Silverlight? Never really got out of the gate and would have been MS/Win only.

The next generation of app distribution is "app stores" with arbitrary refusal policies which take a 30% cut of sales. A success for Apple.

Javascript mostly delivers "write once, run anywhere", albeit through a vast shifting layer of shims. Its sandbox is pretty reliable. It's not owned by anyone and they can't stop you shipping JS apps. Thus it survives.
A Selenium UI recording tool is a good starting point to help people learn. Quickly though it becomes pretty limiting and specialized testers need to switch over to using code.

The Selenium IDE I like using at this point is Oxygen. It's Atom with a Selenium recorder built in. It records and gives you code with details about the XPath and CSS Selectors provided in comments above each recorded action. It's the best tool I've found for quickly getting off of record-playback dependency and into working with code. The Oxygen IDE provides intellisense and real debugging. It strikes the right balance of allowing you to record when you need to, but then getting out of the way and providing you with a real IDE so you can work with the code.

http://oxygenhq.org

I did a blog post not too long ago about some of it's quirks on Windows...
https://scriptmonkey.wordpress.com/2016/06/03/oxygen-for-sel...
Readymade Script for your Business
Not only has Conkeror stalled, but scrapping XUL is a surefire way to murder it in cold blood. The only option going forward would be to rewrite it as an alternate browser that uses Gecko and/or Servo as the engine.

My hope is that the move to WebExtensions will actually help here. Currently, Conkeror is theoretically compatible with Firefox extension-wise, but it often meant writing a bunch of glue code to expose Firefox extension functionality without Firefox' actual UI. Now that extensions are forced to be UI agnostic, it seems reasonable that a browser that's Firefox-compatible could have a much easier time with that. Hopefully a post-XUL Firefox will continue to support something along the basic lines of XULRunner (i.e. present a Firefox window without the actual UI) to make that easier than having to fork Firefox itself.
And yet people praise SpaceX for doing much better and cheaper with their iterative refinement.

BDUF can work if you have a single organisation with a single stable set of requirements that's reasonably compact. The Kennedy "man on the moon" speech was such an example.

Where it falls down is trying to meet the needs to the 7 billion distinct human individuals, which are inevitably vague and shifting and change in response to publication of software.
Mercurial 4.1 has been released
This is quite misleading. Can you use the Volkswagen trademark like this?
Do you mean lighterweight as jQuery or VueJS/React?

I ask because I'm having a major FUD of using VueJS in a small (tiny) project - I don't seem to be able to think in those terms yet, and I don't really use npm (those starter projects generate 1000 files...).

I'm from the time when you would just list JS files in the HTML..
It's parody, so it should be fine.
I feel like that defeats the point of multiprocess; on Chrome at least, the one-process-per-tab model is intended to isolate tabs from one another without having to duplicate a bunch of work that the OS does already.
We made 5 or 6 major versions of a similar tool from 2011-now (https://spacedeck.com), in the end it failed to monetize in a significant way. We will probably open-source it soon to provide a continuity path for the (relatively small) core userbase.

Edit: You made some really good UX detail choices:
- Grid that snaps on releasing items
- Column object (smart!)
- Omitting zoom is also probably a good idea (complicates a lot of stuff in the browser: fighting with native zoom, text rendering bugs in firefox etc)
- In general being very resistant against feature creep is probably a good idea (in our case, users demanded tons and tons of stuff to be added)
Top Best Programming Languages of 2017
also in vue 2.0 you can use jsx e hyperscript
For the first option, you just consider your API endpoint as an RPC made in Golang and consume the content in NodeJS/Express.

For the second option, you're right.

For the third one, to make it simple, it's a V8 engine inside Golang. It's not another process or server.
Yes, erehwon is one of them: https://news.ycombinator.com/user?id=mirimir ;)

There's no geo, for me. And I'm not at all organized, so not much temporal, either.
Bravo, well done.
I have taken ReadCube into consideration, but quickly dismissed it because A) there is not Linux support [1]; and B) it is not open source.

The open-source side is important for me because the data accumulated in these software is really valuable. If one day the company has to close, you may be stuck without access to your data. With open-source software I'm at least sure to be able to continue running the latest software version on my own, and a community can start to take over and maintain it. Also the way data are stored in the computer can be deduced/found in the code, allowing to make exportation/importation to other software easier. I don't mind to pay for a good software – like I'll probably do with zotero for storage when I'll hit the memory limit – but it has to be open-source.

Except this the concept looks quite interesting and the UI seems nice. The only additional feature (in regard to my setup) that I can see on the homepage is the recommendation system, that can be quite interesting though.

[1] http://support.readcube.com/knowledgebase/articles/242873-ca...
Do yourself a favour; remove the distractions. The first few times, you'll probably give up pretty quickly, but as with everything, you'll get better at it.
My point is researching all this puts a huge burden on (serious) users that would not be there for a big standard library. Currently the Rust approach seems quite problematic, but I think this can be solved. For example by an explicit guarantee pledged by the Rust team (or a related umbrella / organization / consortium / ...) for a certain set of libraries (platform / ecosystem / 2nd tier standard library extension / stdx / nursery / ...).

I think it would be important to include in this pledge:

* Transitive closure rule. (No external dependencies not covered by the pledge. Possibly with certain exceptions e.g. for bindings to big known obvious third party dependencies like SQL databases or Operating Systems.)

* Uniform licensing rule. (Everything must use the exact same license, with a single group name as copyright holders and for any purposes of required notices etc.)

* Maintenance, backward compatibility and platform compatibility rule. (100% compatibility forever everywhere is not even necessary, but an _explicit_ rule of thumb of what reasonable time frames for deprecation windows and recommended transition plans can be expected would be nice.)

Or maybe this already exists and I'm just uninformed?
I'm reading 'Deep Learning' right now so this is going to be really useful. Thanks a lot!
Crimeans just asked for the same right against Ukraine as Ukrainians asked against Russia. And it was direction population liked most. The same asked east of Ukraine which is at war now. This is how "soft power" works in these countries with a little help from western friends.

Kiev is indeed awesome place to visit however you should be a desperate guy to move there not being slav.
There is very little difference between an API for you and an API for third parties. Unless the API just for you requires full credentials, and has no tiered access control, you could just give someone else the same API.

Eula's would be the greatest difference.

It is sad though, that no start-up would consider building a self-hosted version that'd keep all data local, instead wanting to offer it in SaaS form.
Nothing? Facebook is not a passport, you can be called whoever you want on it.
They'd be taken out behind the chemical sheds... and shot.

http://www.goodreads.com/quotes/341110-you-were-already-in-a...
Omg, why I have not seen it before! Very useful!
Vizio: Clash of the Titans, when capitalism is at odds with individual privacy
Somewhat fitting for it to be misleading, given it's namesake.
Show HN: Ecmascript2017 Atomics and SharedArrayBuffer based semaphore and mutex
The GP is referring to the person violating Facebook's terms of use I think
Show HN: Dive into the real world of web development
Screen-scraping is how it's still done, even internally, within banks. I'm told it's the easiest way to get data out of systems.
Short answer: You've been screwed over and are not going to get a dime.

Long answer: You're probably not going to get a dime. Learn from this experience and don't get suckered into this type of situation in the future.
While this is an extreme case of course, packages by themselves are quite cheap (apart from installing times), and usually if the author tries to keep the dependencies in check it doesn't really create a mess.
I wouldn't read a book from an author who reasons and writes like that.

The issue he is having with PCA can be solved by normalizing the data.
I'm not sure what your point is. Rails isn't any slower when deployed on-site, nor is it more likely to be a bottleneck.

If your local database is slow and the app code requires lots of DB resources, then sure...but that's the app, not rails.
It looks like a joke today, but it was quite helpful response back then. When shortages started to be massive, people from towns tried to find merchandise in cities, so they asked often «— Do you have a meat? — No, we don't. — You don't have a meat because you are selling something else or because of shortage? — We are selling fish. — Where I can find a meat shop? — Down the street, but they have no meat today too». (Sorry, if my English is incorrect).

Compare this dialogue to short but informative reply in the «joke» above.

Later, these responses are replaced with stickers like "No MEAT today" (it's meat shop, but we out of meat today, check us next morning) or "NO meat" (nobody saw a meat for at least two months, so don't ask us when it will be).

Maybe you understand this joke now:

Developed communism. «From each according to his ability, to each according to his needs.» Sticker at the shop: «NO need in the meat today, comrades».
Scaling Open Source Communities
I get the point you're making, but highlighting the original point, Facebook terms explicitly say you _can't_ do that.

"You will not provide any false personal information on Facebook, or create an account for anyone other than yourself without permission."
PICO-8 lighting, part 1: thin dark line
If you have a false facebook account, you broke facebooks ToS! That means you accessed facebooks servers without authentication!! That is a crime under e.g. the CFAA!!!

Criminals go to jail.

That is the argument at least.
None of my other personas post very much in public. At times, I've been active in other languages, with very different styles.
Funny, but VW were actually cheating the least of all car manufacturers: https://www.theguardian.com/environment/2015/sep/30/wide-ran...

See also: https://www.transportenvironment.org/sites/te/files/2016_09_...
> Eula's would be the greatest difference.

Or more generally contracts and regulations, yes. If you need to be registered with some regulatory authority with security audit requirements, say, in order to be able to gain access to the API, then you cannot use the API, whether you would technically be able or not.
I really want to assume this is a joke - and yet I'm left totally uncertain!
It's not a concern anymore, but when Android was created, the average application was less than 20kiB. Back then, resource restrictions were a lot more problematic.
As a citizen of Krakow, I feel safer already <3.
// Here we benchmark node-noop against various other things that are known
// to do nothing to see if we have the fastest way of doing nothing.
So if I understand you right, for syncing your bibliography you changed the "Data Directory Location" to a synced Box folder (a dropbox-like system)? I thought about doing so with owncloud, then I decided that paying when I reach the syncing limit would be a nice way to encourage the project.

Papership and LiquidText looks really nice, I would love to see such applications for Android. But I presume Apple is a more interesting platform as many researchers are on MacBooks. I suppose this is because researchers have really few spare free time and they don't want to use it fighting against the (linux) machines.
He was just joking around, he memed you.
Json-git – A pure JavaScript local Git to versionnize any JSON
What is advantage of Internet Leased Line over Broadband connection?
My recent findings is that it's better to not take any notes at all. Instead of adding some item to your todo list, do it immediately and don't send it off like some nasty surprise to your future self. The smaller my notes.txt the less complications I have to worry about and I can go on living a happy and fulfilled life.
You're probably overlooking the change in the quality of the good. Demand in London is highly elastic. If a lot of new sleeping units come on to the market, they will be filled easily because lots of people want to live there.

Now suppose we divide old units of accommodation priced £ in two (halve the slope of the supply curve). The price of a new unit will be close to £. But an old unit then costs nearly 2£. So you have a choice between slum housing and coughing up double the rent.
http://book.mixu.net/css/ is a free book you may be interested in.

Note that for the book you're looking for, modularity would require that it explicitly states the dependencies between sections. This is probably a good idea anyway.
In practice though, even the smallest toy project will pull out hundred tiny dependencies.

This is why funny stories like leftpadgate can happen.

Relying on an external dependency is a net win if and only if the time gain overcomes the loss of control.

Maybe regrouping all these tiny libraries under an umbrella project (lets call it node-utils or js-tinytools or whatever) will mitigate the problem?

This project will not have any external dependency though will be used by most of the projects and ergo might be watched with much more attention.
Generally speaking good healthcare (insurance) is going to cover the majority of the cost of the drugs for the person that has it.
Couldn't you equivalently just not connect the smart tv to the internet?
Another option would be to use Webpacker, in development now, https://github.com/rails/webpacker
The law is not strict enough. No single byte should be sent outside without user's consent. No matter whether it contains personal data or not.

And that would make proving company's guilt much easier.
Isn't this typical of what you get when you have a language that's easy for newcomers to pick up?

At one point it was PHP. Then it was Rails. Of late it's been Node. I'm sure Windows users might have some old VB war stories. (Admittedly, I'm not sure what to make of the Java StackOverflow tag, seeing that it's also is a sewers. Presumably school or Android related.)

Edit: good related reading:

http://yosefk.com/blog/redundancy-vs-dependencies-which-is-w...

> Redundancy sucks. Redundancy always means duplicated efforts, and sometimes interoperability problems. But dependencies are worse. The only reasonable thing to depend on is a full-fledged, real module, not an amorphous bunch of code. You can usually look at a problem and guess quite well if its solution has good chances to become a real module, with a real owner, with a stable interface making all its users happy enough. If these chances are low, pick redundancy. And estimate those chances conservatively, too. Redundancy is bad, but dependencies can actually paralyze you. I say – kill dependencies first.
Even contract formation is dubious, especially in cases of browsewraps.
I keep thinking we've reached peak npm, but node.js keeps surprising me. :)
> Hence you did not send me any feedback, and not hear from you, I decided to send you a feedback.

Most companies do not provide feedback for a rejected applicant because it's a legal minefield. At best it's neutral. At worst, it's fodder for a discrimination lawsuit.

> However the second round of interview, which I wasn’t expecting a technical one, was opposite. Interviewer was extremely disrespectful. In the first second I understood that he was prejudiced and going to ask amateur questions from his manners. A guy, without smiling and showing that he is not happy to meet a “different” eprson to interview, is not an uncommon type of interviewers I encounter.

Why would a technical second round be unfair?

> Asking questions on paper with a bic pen is extremely unprofessional, also improvisating questions on fly without preparing them is too.

Every interview I've done has been with a pen in my hand. I usually have a prepared list of printed questions and make notes over the course of the interview, sometimes to add notes about questions I'd like to follow up on at the tail end of the interview.

> Other than that, asking syntax order of a left or right join, instead of the purpose of that to a candidate that says she worked one year as front-end engineer is forcing her to fail.

If the interview shows that the candidate can't express the proper syntax of what I assume to be is a SQL JOIN then I think the interview was a success on the part of the company.

> Aslo is extremely rude to comment, “oh you wrote a book about it explaining but you don’t remember the syntax?” with a mocking face.

That does seem pretty rude.

> Actually I am not interested with your company or your offer anymore, hence a accepted a different offer from abroad, I hope my feedback is going to be useful for your company, not to frustrate future candidates with your unprofessional behaviour.

This whole post, especially the last sentence, just sounds like sour grapes.
> surely violating Terms of Use is essentially a breach of contract

Is it though? Not a lawyer and my layman's intuition makes it hard to see a connection between ToS and contract.

Like, if I type `something.com` in my browser by accident and their ToS is "you owe us $400 for each TCP packet, kindly do provide goverment issued ID". So I have couple of questions:

- How is that different from ToS on Facebook?

- How marking a checkbox creates a contract between a person and entity owning a site, same way as my signature or providing personal info, address and money to Amazon in exchange for goods?

- And who that person would even be in FB case (anyone can put my name into a website from a public library computer)?
Bots appear to be getting much better :)
> The only thing that matters in software is the experience of the user.

While ultimately true, it's a bit too simplistic, because it presents user-experience as a constant. Done deal. Delivered or not. In reality the user experience is something which will change over time, as the software is updated and evolves to accommodate the additional needs of the users.

If you can't keep your code clean over time, your code will start suck, needless complexity might sneak in, and so will the user-experience start to suffer as well.

A good user-experience, just like the code, needs to be maintained. And thus comes the need to organize the code. And for a developer to bother maintaining the code, and for him to be efficient at it, he should work with tools and within an environment which fits his needs (and accommodates his requirements for a good user-experience). And thus comes fiddling with editor-settings. Etc etc.

Basically this rant highlights a real problem: Software complexity is out of control. But the conclusion does not support the arguments given. Rather his conclusion drives all the things he rants about being wrong in the first place.

I think, in the end, to get clean code, to get rid of needless complexity, there's one simple thing which trumps everything else: You need someone empowered to make the required changes. And you need that person to care.

Without that, it's all just us waiting it out, until it starts heading into the abyss. We can already see that with lots of the bigger open-source projects which once fuelled the (small) Linux desktop revolution a decade ago.

So how do we cope?

> There will come a point where the accumulated complexity of our existing systems is greater than the complexity of creating a new one. When that happens all of this shit will be trashed. We can flush boost and glib and autoconf down the toilet and never think of them again.

Maybe we will. But I don't believe for one second that we're going to break the cycle this time around, because finding and keeping someone caring enough for decades to come is a pretty tall order.
Yes, it is a joke, check the tags at the github repo:

ironically-shitty
javascript
left-pad-level-dumb-module
noop
parody
satire