skysight-inc/HackerNews huggingface dataset:
I'm pretty sure that statement they quoted is vile and disgusting, but certainly not incitement to violence as the courts understand it.

Of course, Namecheap can probably choose their customers however they like according to their own TOS. But don't delete someone off the Internet who is saying things you don't like and spend the whole post patting yourself on the back for following principles of free speech.

I think it's pretty simple -- if you don't believe that Nazis should be able to voice their vile and disgusting opinions openly, you don't believe in free speech. If you don't believe that Nazis should get to organize a nonviolent protest, then you don't believe in freedom of assembly.

The Washington Post featured an article 'Who are the antifa' [1] by Mark Bray who is the author of "The Anti-Fascist Handbook" which explained, "Antifascists argue that after the horrors of chattel slavery and the Holocaust, physical violence against white supremacists is both ethically justifiable and strategically effective."

Of course we see how effective it is, because defending the bedrock principles of freedom of speech and assembly when the speakers are Nazis now apparently puts you at risk of being labeled a Nazi sympathizer / white supremacist / racist yourself.

I'm not sure exactly when it became impossible to have an adult conversation on the matter. When did it become impossible to understand that a protester can represent abhorrent viewpoints without it being OK to throw bags of urine and paint at them? That a protest can turn violent and even deadly without being able to then condemn every single protester that was present? And that we should not be celebrating, but in fact be very worried if not outraged, that private parties who have gained superuser access to parts of the internet through their course of business are now leveraging that power to police content they find personally offensive, or which they takedown for PR reasons to appeal to a populist mob.

[1] - https://www.washingtonpost.com/news/made-by-history/wp/2017/...
I'm glad the author thought about screen readers and other accessibility software. Yes, easy support for alternate input methods helps. But for screen readers in particular, the most important thing is a way to access a tree of objects representing the application's UI. Doing this efficiently over IPC is hard, at least with the existing infrastructure we have today.

Edit: I believe the state of the art in this area is the UI Automation API for Windows. In case the author is reading this thread, that would be a good place to continue your research.
Control of quality and auditing is another reason why apps stores exist and are useful: The (on average) high quality of the apps in the iOS store is the result of a rather strict auditing process, which in the end is also beneficial for the user. This is something that usually doesn't happen naturally with completely open systems. Even the Linux distributions (that are usually run mostly by volunteers and not profit-oriented) often have very strict criteria that your package needs to fulfill in order to be included in the official repository.
Lord, the downvoting of anyone who supports free speech is telling.
You conveniently left out the preceding sentence which is of the format "X, Y and Z can stop reading now" -- and whoever is left is assumed to already know Emacs or Symbolics.
Yeah this article felt like clickbait to me. Also Google's reaction to Damore kind of proves at least half of his assertions correct. That many topics are too sacred to discuss critically without being labeled a certain way.
I agree that sum types are nicer, but I don't see how they constitute error handling in a way other return mechanisms do not. The difference isn't categorical, it's ergonomic.
This request seems to come up occasionally whenever a topic on graph management comes up but I wonder how many people actually need a general purpose graph editor.

I am currently working on Solvent and one of its features is an object graph management system that can be used to construct any sort of hierarchical data structure, in particular I have started demoing in to DevOps people configuring things like Kubernetes, cloudformation..etc.

Product page:
http://codesolvent.com/config-mgr/
What's hard is making your backwards compatiblity story sane. You need to somehow make your new system provide some obvious advantages even to ported apps, while still plausibly allowing them to work with minimal porting effort.

But I think this "reinvent the world" concept has a deeper flaw - in all the discussion I didn't see any mention of how you make it performant despite that being an identified problem. If everything's message passing...how much memcpy'ing is going on in the background? What does it mean to pipe a 4gb video file to something if it's going to go onto a message bus as ... 4kB chunks? 1 mb?

Remember this is a proposal to rebuild the entire personal computing experience, so "good enough" isn't good enough - it needs to absolutely support a lot of use cases which is why we have so many other mechanisms. And it also (due to the porting requirement) should have a sensible way to degrade back to supporting old interfaces.

Microsoft owns the desktop partly because they absolutely were dedicated to backwards compatiblity. You want to make progress - you need to have a plan for the same.
On the other hand, it provides opportunities for new relationships that are even more toxic than those the attendees arrived with, since frequently this group has (or would have, if they were examined by a competent doctor) multiple diagnoses.
Online privacy is making a comeback
Bryan Cantrill – Oral tradition in software [video]
As someone who is facinated by what is happening I spend a decent amount of time spelunking in the dark web.

The Neo-Nazis are not that upset by this. They want to use the same tools to boycott the Zionist and Jews. It's actually one of the many things the Alt-Left and the Alt-Right agree on.

In addition we're making them into martyrs. Banning and suppression was counter productive on the original Nazis and it is counter productive here.

This should be we'll know by those who read civics. It is even codified in the book Rules For Radicals by Saul Alinsky. It makes me wonder what books Antifa are reading as they are doing all of the wrong things.

I get that it feels like we're (non nazis) are winning but we're not and this is isn't helping.
Oh yeah, here comes the zone, here comes the zone, it's taken an hour of intense study of all this code but now I can see all the pieces at once inside my head and I can feel exactly how to thread this code right through the middle of all of it and -

COLLEAGUE LEANS OVER FROM NEARBY DESK IN OPEN OFFICE:
"Hey buddy, what's the password for the - oh no, wait I remember."

Wait, what was I doing? What's all this code on my monitors? Why was I looking at any of this?
Chemistry teaches us that alcohol is a solution.
In the US, Indian is an ambiguous term due to Native Americans. Asian Indian disambiguates.

In the UK, Asian (or South Asian) often means Indian.
Interesting, as no technology is perfect, and people come up with clever hacking schemes for desktop computers till this day, I think the more valuable the network becomes, the more frequent this type of attack will be.

Do you think they will keep forking whenever major events like this happen? I worry that a couple of these attacks will be enough to drain all the trust from the network. Ethereum may have saved itself once by forking but a lot of people think this is not sustainable and think a couple more of these and people will leave.
As we age we succumb to our prejudices.
You're right, this is giving an inordinate amount of free publicity to daily stormer and is making people (like me) who support free speech uncomfortable. I'm now instinctively supporting their right to free speech against the horde of disingenuous virtue signallers.
There's also a reason no-one uses hard links: because you can't tell if you edit a file, where else you might be editing it.
Forced to transact but not forced to own. You can accumulate your wealth in gold, real estate, Dogecoin or S&P 500 stocks, and liquidate just enough to pursue a transaction.
There's a strong correlation between women entering a field and it having low prestige, and men entering a field and it having higher prestige.

Guess which field of ours was considered busywork for women to do until men realized it was going to transform society as we know it.
Why are registrars doing the policy decisions when its the registries has the mandate to control and policy the domain name system?

If IANA decide that .com address should not be used for sites like this, then at least it would be their decision to make. They also already thought about how to handle this type of questions, and drawn the lines where the consensus says they should be. If people want to change them, the process to do so is likely well documented.
I don't understand this whole thing.

Until recent years all developers I met were socially awkward men, me included.

These are not the kind of people I would attribute any power to "crowd out" anyone.

To me it seemed that they started doing computer stuff, because no one, including women, wanted to have anything to do with them.

The "cool", way more aggressive, kids wanted to do sales, law, finance, management and stuff.

Computers were new and complicated, a unsafe bet for people who were so good included into society.
I still don't understand what is it. An email client? What is this yellow "data" on top?

Seems rubbish to me.
The 1st amendment protects speech from being suppressed by the state. Private entities may ban whatever they see fit, basically; you know they do if you ever read a end-user license.
Sure, here it is: https://github.com/kaushalmodi/.emacs.d/blob/master/elisp/or...
The _very first sentence_ is a misrepresentation of Damore's memo.

"Why aren’t there more female software developers in Silicon Valley? James Damore, the Google engineer fired for criticizing the company's diversity program, believes that it’s all about “innate dispositional differences” that leave women trailing men."

"Innate dispositional differences" is a _quote_ from a paper he cites, Why Can’t a Man Be More Like a Woman? Sex Differences in Big Five
Personality Traits Across 55 Cultures, a 2008 paper from the Journal of Personality and Social Psychology. Damore introduces the quote with the phrase "research suggests."

The computing revolution is dominated by men because men have no problem at all spending thousands of hours tinkering with something just for its own sake. The real world confirms this.
Psychological flow (the zone) does require a slight challenge. A task that requires you to focus but which is within your capability.
Feynman Technique http://qz.com/849256/how-to-master-a-new-subject/
wow; that's a good example of why GLP v3 has value to end users of free software: the GPL2 allows them not to share improvements. The GPL3 requires the source code to be available, if those machines are used to serve results to users.
> In the screenshot below the user is lifting the edge of a window up to see what's underneath. That's super cool!

> https://joshondesign.com//images2/lift-window.png

Is this a sarcasm? Because it is complete garbage.
That sounds like the free version of OneNote that comes with Windows 10. The "full-fat" desktop version that comes with Office ("OneNote 2016") is much more flexible in this regard, and has a more powerful interface.

https://support.office.com/en-us/article/What-s-the-differen...

That said, the OneDrive integration is something I like about it; my notes aren't very useful to me unless they're cloud-synced.
Our evolutionary gift isn't intelligence, it's adaptability. We are by far the most adaptable species on the planet. The big brain is just one of the mechanisms we use to achieve it. That is never going to stop being useful.

I don't think two way implants are ever going to be a "thing" the way they're portrayed in fiction. Every brain is so different that it would have to be wired completely differently in each case. On the other hand, one way implants that allow a computer to "read" your mind are totally feasible and will definitely happen in our lifetimes. I doubt the resolution will get good enough that they'll be super useful for regular people, but they may help disabled people, and they'll create a much shorter feedback loop between man and machine that will be useful for specific tasks.
Isaac Newton?
>"It doesn’t take a Ph.D. in mathematics to understand that White men + pride + organization = Jews being stuffed into ovens."

To me, out of context, that reads as anti- White men, not anti-Semitic. Or at least ambiguous. Certainly not an outright endorsement as such.

I haven't read the material, and I'm sure it's as hateful as they say. But as their entire argument is predicated on how beyond the pale that statement is, and if "the site spends considerable effort demonizing Asians, Blacks, Mexicans, etc" - they could probably have found a better example to make their point.
He doesn't suggest to trow away the old layers just because they're old, but because he suggests a different approach. Anyway that's a really good quote, I like it very much.
Show HN: Marina.io, an open source Docker Hub with ARM support
So volume spoofing is you and me sending 100 BCH back and forth, but its undetectable because we're smart enough to use a different address each time...
Thanks, yes am now!
So, we’re back in Java 1.0, and using Object and just casting back again?

Seriously, this is why generics exist. I want to write it once, use it everywhere again, and want to have the compiler know if I made a mistake.
I think the author wants a bunch of really specific personal workflow ideas/concepts they have to be the standard, which is typically what these rants are. Such rant posts are always interesting to me as I do question my own workflow just to see if there are good ideas I'm missing out on, but a lot of the author's ideas just don't strike me as all that important in most cases, and in some of the complaints, I'm not sure what the complaint is.

Their complaint on the filesystem, for example, falls flat for me, but partially because I think I don't understand what they want or how BeOS did it. Maybe the author has a special meaning for "...sort by tags and metadata", but this looks to be baked right into Finder at the moment; I can add in a bunch of columns to sort by, tag my items with custom tags (and search said tags), add comments, and so on. Spotlight also has rendered a lot of organization moot as you just punch in a few bits of something about what you're looking for (tags, text within the document, document name, file type, date modified by, etc.) and you'll find it. I don't know exactly what is missing from modern OSes (Windows search isn't too bad either) that the author isn't contented with.

The idea of multiple forms of interaction with the computer are okay, but quite frankly it starts to get into an eerie situation for me where I'd rather have to take a lot of steps to set up such monitoring as opposed to it being baked into the OS. I realize that I'm squarely in luddite territory given the popularity of Home Assistants (Echo, Apple Homekit, Google Home), but to me these seem like very intentional choices on the part of a customer; you have to go out of your way to get the hardware for it and disabling it is as simple as pulling the plug. Look at the non-sense we're having to deal with in regards to Windows Telemetry - to me this is what happens when such items get baked into the OS instead of being an additional application; you end up with a function you no longer can control, and for no other reason than to satisfy the complaint of "I have to download something? No thank you!"

I could go on, but the author's rant just doesn't seem consistent and instead seems to just want some small features that they liked from older OSes to be returned to modern OSes. There is a huge issue with bloat and cruft and some real legacy stuff in Windows and macOS, and desktop OSes aren't getting the attention they should be, but these suggestions aren't what desktop OSes are missing or what they need.
> But the solution is NOT to throw out a bunch of those old layers and replace them with new layers!!!

Neither is keeping everything as it is and keep pretending it's fine!

> When you throw away code and start from scratch, you are throwing away all that knowledge.

I disagree with Joel on here. There's lots to be learned from throwing everything away and starting from scratch, and if anything those innovations could make their way into the current infrastructure, as it has happened with Midori and Windows.
As a current developer, former 10 year UX designer, and developer before that, this kind of article irks me to no end.

He contradicts his core assertion (OS models are too complex and layered) with his first "new" feature.

Nearly everything on this manifesto has been done before, done well, and many of his gripes are completely possible in most modern OS's. The article just ignores all of the corner cases and conflicts and trade-offs.

Truly understanding the technology is required to develop useful and usable interfaces.

I've witnessed hundreds of times as designers hand off beautiful patterns and workflows that can't ever be implemented as designed. The devil is in the details.

One of the reasons Windows succeeded for so long is that it enabled people to do a common set of activities with minimal training and maximizing reuse of as few common patterns as possible.

Having worked in and on Visual Studio, it's a great example of what happens when you build an interface that allows the user to do anything, and the developer to add anything. Immensely powerful, but 95% of the functionality is rarely if ever used, training is difficult because of the breadth and pace of change, and discovery is impossible.
Looking at [1] and the key value database described there, it would need some key coordination mechanism to make use of the system database. For instance, a way for an app to say that a document it stores is either directly of a given type or implements the interface (ex: an email or a music data), so that other apps can use this document. So the type field would refer to a standardized type like a uuid associated with some type of data or a URI (like in RDF). Also, it can have some mechanism for other types to implement the interface or extend existing types and for users to create new types just like we can register urls today.

Having a database with standardized interfaces for documents replace a filesystem is a really important feature mentioned in the article. It will allow the development of many useful apps like the itunes or email examples. Also, this is not specific to any OS can be standardized independently and implemented on current OSes we use by having some extension which stores metadata along with a file.
Different words for the same thing.
Ask HN: What is the HN for quantitative finance?
Any one knows any good sites / boards for good quantitative finance discussions?
Universal web components are a pipe dream.

Even within a community using the same framework or library, there is disagreement on how to solve certain problems. For example, the folks behind React Router removed parsing of querystrings, because people wanted the flexibilty of using alternative solutions [0].

It's hard to imagine something more trivial than parsing querystrings, yet no consensus exists among users of the same library (which itself is not officially-sanctioned by FB yet, and even React, while stronger than other libraries, is not loved and used by all client-side web devs) on how to do it best.

Yet people think someday in the near future, these differences will just disappear magically, and we will be able to author web components that snap--like Lego bricks--into whatever environment a developer wants?

[0] https://github.com/ReactTraining/react-router/issues/4410
> I suspect the root cause is simply that building a successful operating system is hard.

Well, it is hard, but this is not the main source of issues. The obstacle to having nice things on the desktop is this constant competition and wheel reinvention, the lack of cooperation.

The article shows out some very good points, but just think of this simple fact. It's 2017, and the ONLY filesystem that will seamlessly work with macOS, Windows and Linux at the same time is FAT, a files system which is almost 40 years old. And it is not because it is so hard to make such a filesystem. Not at all.
Now this is at the core of reasons why we can't have nice things :)
I hate to say this, but an ideal Desktop OS, at least for majority of consumers is mostly here, and it is iOS 11.

Having use the newest iPad Pro 10.5 ( along with iOS 11 beta ), the first few hours were pure Joy, after that were frustration and anger flooding in. Because what I realize, is this tiny little tablet, costing only half a Macbook Pro or even iMac, limited by Fanless design with lower TDP, 4GB of memory, no Dedicated GPU, likely much slower SSD, provides a MUCH better user experience then the Mac or Windows PC i have ever used, that is including the latest Macbook Pro.

Everything is fast and buttery smooth, even the Web Browsing experience is better. The only downside is you are limited touch screen and Keyboard. I have number of times wonder If I can attach a separate monitor to use it like Samsung Desktop Dock.

There are far too many backward compatibility to care for with both Windows and Mac. And this is similar to the discussion in the previous Software off Rails. People are less likely to spend time optimizing when it is working good enough out of the box.
A bit misleading. The maintainers have been working on large experimental features like a self-hosted "signaling server" which helps sync notes without storing any note data on it, and without relying on third-party hosting like Dropbox [1].

Also if you look at the dev branch [2], they have been making sweeping changes to the codebase; most recently it appears they have been removing "old" JavaScript libraries like Bower, presumably to move everything to an NPM setup.

[1]: https://github.com/Laverna/laverna/issues/778

[2]: https://github.com/Laverna/laverna/commits/dev
James Damore's arguments are only plausible in the weakest sense of the word. The only way someone would find his arguments convincing is if one's priors already favor his conclusion.

If one weighs the evidence for social factors against biological factors, the question is how should a critical person weigh one against the other? It turns out if one ignores all the evidence for social factors and squint really hard at the biological ones, one can, I guess, scam oneself into thinking there's a strong argument there.
I don't use D (I make my audio stuff using Rust) but it's always good to see new audio libraries/tools.

Slightly off-topic, I'd love to see an open project for audio plugin specs. VST and AU are managed by private companies and have a history of extremely poor documentation. For anyone who tried to code audio stuff at least once, it's a real pain. Audio is already hard in itself.

(Don't even get me started on the bugs around AUv3…)
When do you think programming began to have high prestige?

I didn't think programming in the 80s or 90s was a particularly prestigous or high status job, salaries back then kind of reflect that too
The only part I disagree with is "close the PR if nobody replies". Open PRs without a clear blocker are important indicators of project health. If a PR stays open for a long time, it might mean that the maintainers have trouble reviewing outside contributions, or aren't that interested in incorporating them. If I see that in a project repo, I think twice about doing the work to contribute when it might end up ignored.
It would be an authoritarian plutocracy. Power is held in the hands of a small group of super rich. Fascism isn't a form of government either, it was the name of Mussolini's party which has since been applied to any authoritarian or nationalist movement.