skysight-inc/HackerNews huggingface dataset:
Ars Technica did a retrospective on the BeOS filesystem[1] which may help explain things. The tl;dr of it is that the filesystem is the canonical database that all applications can use and query without any special domain specific knowledge. I'm not up to date with how MacOS works so it's possible they've added a layer on top of the filesystem which works similarly. However, I do know that Windows is nowhere near that level, mainly because it's encouraged for metadata to be stored in file specific ways.

[1] https://arstechnica.com/information-technology/2010/06/the-b...
I would argue that boys and girls today still have this attitude, and now Radio Shack has died (and in that context, isn't Raspberry Pi such a blessing?). It's hard to persuade boys and girls that math and science are cool. It's also unfortunate because a lot of parents think that throwing an iPad in front of their kid will make them more technical, when the characters coming over YouTube / Minecraft are just cancer.
Complecting a GUI into an OS doesn't sound very ideal to me.
Quote from https://blog.namecheap.com/we-say-no-to-sopa/

"Why are we against the proposed SOPA legislation? It’s very simple; at Namecheap, we believe in internet freedom.

When you register a domain name, you can do anything you wish with it within the confines of the law."

You find how much you believe in your principles, when they lead to outcomes you don't like. Given their actions now, namecheap's SOPA opposition now sounds like just a cheap publicity trick they did to distinguish themselves from GoDaddy.
> Truly understanding the technology is required to develop useful and usable interfaces.

+100. This is something I have advised to any designer that would listen. You must have at least a basic understanding of the technology in order to understand the set of affordances with which you use to design your flows.
I think pairing can be different for different people. I've often heard people saying that "the zone" comes more easily when pairing. Personally, any zone I'm feeling pairing has a different character from one achieved alone. It's easier to focus on the task at hand (because there's peer pressure).
diaspora is flawed by design. it will only ever be used by techies b/c either you take care of your own server or you have to trust somebody with your data.

what is needed is a facebook e.V. with a strict data safety policy.

https://en.m.wikipedia.org/wiki/Registered_association_(Germ...

it would cost transparently what is needed to sustain the service.
Just once, I would like to read in one of these articles about an actual non-anonymous woman who could plausibly demonstrate that a.) she had a strong desire to be a software developer, b.) she had developed sufficient skills in a marketable language to be employed as one, and c.) she had made a prolonged effort to find employment as one, and d.) she was unable land a job as a software developer.

Instead, it's always about something that a magazine ad said in 1969, or a teacher who told them that woman couldn't be programmers, or the boys in their school computer club ignored, them, etc. etc.

And the prescriptions, as usual, are that in order to get more woman into software development, that changes must be imposed on men, not woman.

This crap got old a long time ago.
>My understanding is abstinence programs are for those that have tried to moderate and cannot.

I hope I did not suggest that abstinence is not the correct answer for some. It just isn't the answer for all, which is what is generally taught in AA. And the quotes from Chapter 3 are not serious, in the sense that if a newcomer to AA says something like, "Maybe I can drink moderately," the answer is pretty much always, "How did you end up here then!?" (Frequently, the answer is, "The judge told me I had to come in order to avoid jail.")

>It also seems strange to suggest naltrexone as an alternative to aa.

Living Sober was written before naltrexone was invented. I have known a number of folks who were prescribed Valium and similar drugs in the '60s and '70s and '80s who became addicted to both Valium and alcohol.

Further, the Living Sober quote suggests medication may be appropriate, but "alcoholism" (or whatever the DSM-5 calls it now) is often the main diagnosis, with any other diagnoses placed as subordinate to that main diagnosis. The implication is, "Stop drinking and the rest will go away," which is frankly bullshit. The Orange Papers (for all its many flaws) has a good section on this.

>I'm having a hard time finding where it's suggested in their literature that salvation comes from sobriety?

This is not from the literature, but rather from my observation over many years. Many times I have heard it suggested that AA is "basically christian" or "based on christian principles" but the reality is that it is based on what is properly called "Buchmanism" (for Frank Buchman, the founder of the Oxford Group). There is a tinge of christianity to it, but it is based on works (staying sober) rather than on grace.

This is why many moral failings in AA are glossed over with, "Nobody's perfect! Just stay sober and you'll be OK!" That is an appropriate response to dealing with a medical issue -- for example, a heart patient may also be a greedy, corrupt thief. The moral failing does not generally have any bearing on the treatment of the cardiovascular issues. So why are alcoholics taking moral inventories and making amends and confessing their shortcomings to others?

In other words, is it a disease, or is it a moral condition? If it's a moral condition, then let's not call AA's solution "christian," because it is not. If it is a disease, then let's treat it like one rather than using the twelve steps.
Wow, what an amazing quote to pick since that is exactly the kind of thing a far-leftist would say.

If the site is as bad as they say they should have picked a better quote than that obviously ironic one...
"insisting the current state is somehow the "natural state""

This is a strawman, nobody assumes this is natural in any way.

The point is, yes we want more women in the field, but the awkward male nerds that are there right now aren't the main problem.

Better look at the hiring managers and what society "shows" women every day.
It's a dilemma isn't it, without funding it probably won't happen, with funding it's corrupted in some way.
I appreciate the article for its coverage of many OS (including BeOS, wow, I should try that). What about package management though? Package management really defines the way you live under your flavor of linux, and there is a lot of room for improvement in current package managers (like decentralizing them, for example).

Also:

> I know I said we would get rid of the commandline before, but I take that back. I really like the commandline as an interface sometimes, it's the pure text nature that bothers me. Instead of chaining CLI apps together with text streams we need something richer [...]

I can't agree with that, it is the plain text nature of the command line that makes it so useful and simple once you know a basic set of commands (ls,cd,find,sed,grep + whatever your specific task needs). Plain text is easy to understand and manipulate to perform whatever task you need to do. The moment you learn to chain commands and save them to a script for future use, the sky is the limit. I do agree with using voice to chain commands, but I would not complain about the plain text nature and try to bring buttons or other forms of unneeded complexity to command-line.
Recover My Files v6.1.2.2375 Crack and Serial Key Free Download {HERE}
The same way they approach the notion that P probably doesn't equal NP.
Firefox on Fedora 26 here, silky smooth for me.
> "When you throw away code and start from scratch, you are throwing away all that knowledge. All those collected bug fixes. Years of programming work."

But, sometimes, that's exactly what you should do. It brings to mind OpenSSL after Heartbleed. I remember reading that the LibreSSL people were ripping out all kinds of stuff (like kludges and workarounds to support OpenVMS), and rightly so. You might call it "knowledge [and] collected bug fixes," but sometimes the crap is just crap.
I wonder if acamprosate would work for internet addiction?
Not OP, but I'm chiming in. The crux of his original argument was that inventing more languages begets more semantics to keep track of, more syntax to know, overall more conplexity. A scheme codebase of sufficient maturity could express orders of magnitude line-by-line compared to the equivalent c code. Nim has macros, no? Either way, scheme is decades more mature, and lots of PL efforts have already been ventured into the ()-verse.

I'd be curious to hear what nim would have over scheme, if anything like that came to mind.
Agile is not about improving performance - its about removing the burden of efficiency proof from management. Pre-agile every manager had to be constantly on the prowl to get "numbers" and dates from teams, to gain a metric, to show progress, to demonstrate them actually having a place and job in the whole cooperate process.

Now they can point at realized features and make a funny progress bar from ice-box to Tested.
That this progress bar might hide tech-debt, that some realized modules might have to be silently rewritten to accommodate follow up stories- and thus that one last feature might be as expensive as all that have gone before.
Well that is treacherous developers, slacking off.
That's more like claiming transport is OK with just tanks when we've got electric vehicles. Tanks are not that efficient and neither are they that fast, and probably will not be allowed in the city - but they can go literally anywhere. And to be fair the guy has a point (a had a point for years beforehand).

Unless you're that networking guy that just massively tries to organise a thousand meetings a day on the go - I believe that a laptop is a better way to use your organiser.

I've had a lecturer at the university who still used a console-based e-mail client. He knew all of the shortcuts by heart - and I am pretty sure it would probably take me a few years to casually learn how to use Outlook/Gmail/etc.. as efficiently (and even then - most of the UI-based applications tend to somehow forget that a keyboard exists at all).

You'll ask me: "but what about mobile?". Well - the guy _never_ replied to your e-mails outside his office hours; but when he did - he gave you a proper, short and an informal answer. And to be fair, he seemed to have a great personal life.
I don't think any of the comments so far have addressed what EY is trying to get across with this story. He's saying we aren't very good at extracting information from data (doing science), but that we do have tools that can help us do better. I'm not sure it's worthwhile to target this argument at the highest levels of science and say "You physicists really should be more efficient about discovering a theory of quantum gravity." But I do think it's a valuable lesson to the rest of us. We may be relatively blind meatbags by default, but we can improve our own reasoning systems by leaps and bounds and probably be better for it
It is the windows 10 of treatments. It is cheap. It is often forced upon those in need. It only "works" if one buys into a theology. It suggests that there are no alternatives and actively seeks to weeken those that appear. Many of its lauded features are of little utility to most users. And it is american.
These are mostly solved problems (minus omniscience or scale) with just handfuls of books that represent most parts of the solution.

Workaday environments suffer impediments to SE application not solvable by tooling. Many large organizations run de jure or de facto Need-to-Know (NtK) departments. I have witnessed Functional or Class Decomposition and Module Hiding repurposed for NtK atomized development teams not knowing shared OUTCOME semantics. Organizations and people turn SE abstraction boundaries into NtK semantic ASYMMETRIES, i.e., SECRECIES.

That does not work well, efficiently, or predictably. Anyone can rightfully detect motivations for both FSF/OSS and Skunkworks structured "startup" teams where all wood is behind the same arrow.

Other problems are lack of SE training. There are big tugs in finite training days between reading/writing skills, problem domain maths, tool churn, machine models, scheduling techniques and so on. Many HN Skunkworks styles teams are in VERY good shape compared to 20 years ago or contemporary organizations trying to turn SE into contract management.
Yeah, but there's more to Java than the language.

Compare to one of their primary competitors, Visual Studio. VS is still struggling with the transition to 64 bits because they can't take the plugins with them. It essentially can't be made cross platform with the result that they gave up and started a rewrite (VS Code). Despite Microsoft having vastly more resources than JetBrains, IntelliJ seems to have more features.

I credit a lot of that to the underlying platform being higher level and more productive.
No, no, the LtU discussion is a million times more interesting.
I used to go through the trouble of etching boards at home working with fairly nasty chemicals long ago. However the ease, speed and low cost of ordering PCBs nowadays means I can no longer justify to myself the time, trouble and danger especially with a kid in the house. Much better to get a prototyping shop to do it and send you.
I agree with a lot of the critics in the comments, but I will say that the author has brought to my attention a number of features that I'm now kind of upset that I don't have.

I always thought LED keyboards were stupid because they are useless, but if they could map to hotkeys in video players and such, that could be very useful, assuming you can turn off the LEDs.

His idea for centralized application configs and keybindings isn't bad if we could standardize using something like TOML . The Options Framework for Wordpress plugins is an example of this kind of thing, and it does help. It won't be possible to get all the semantics agreed upon, of course, but maybe 80% is enough.

Resurrecting WinFS isn't so important, and I feel like there'd be no way to get everyone to agree on a single database unless every app were developed by one team. I actually prefer heterogeneity in the software ecosystem, to promote competition. We mainly need proper journalling filesystems with all the modern features. I liked the vision of Lennart Poettering in his blog post about stateless systems.

The structured command line linked to a unified message bus, allowing for simple task automation sounds really neat, but has a similar problem as WinFS. But I don't object to either, if you can pull it off.

Having a homogenous base system with generic apps that all work in this way, with custom apps built by other teams is probably the compromise solution and the way things have trended anyways. As long as the base system doesn't force the semantics on the developers, it is fine.
LinuxAcademy is good, surprisingly it really shines for AWS stuff. A Cloud Guru is also good. Also want to add LinuxJourney.org, although it's free.

Absolutely consider Udemy, they have some real gems in their catalog. Good for everything from React to IT Security to mastering VBA/Excel.
>But now is a time where most of the basic jobs can be done automatically.

I wouldn't be surprised if that has been said 100 years ago before.
There have been a ton of times I've been typing something in but needed to see what's behind it. Reaching over for the mouse is slow.

I use Windows, where there is this utility which lets you adjust the transparency of windows from the keyboard: http://www.vanmiddlesworth.org/vitrite/

Thus you can see the contents of both the upper and lower windows at once, and not just briefly. Very useful on a laptop with limited screen space. I know adjustable window transparency is definitely possible on Linux too.

On the other hand, this looks like it's just effects for the sake of effects.
Hi,

The Product owner link is not working.
It's easy to say React is simple if you are looking at, say, a barebones create-react-app. But most production React apps I have worked on (I work at an consultancy) seem to accrete complexity faster than functionality.

I used to chalk this up to me not "getting it". Now I think it has more to do with the desire to incorporate newness into React apps. Stuff like ripping out routers to replace with another router but then the old router was rewritten so lets replace it with that one again. That kind of stuff happens, and even it is preferable to someone deciding to incorporate something like [shudder] styled-components half way through a project. This kind of stuff almost always incorporates new abstractions that will increase surface complexity. In the interest of avoiding a rant, I won't start with people monkeying with context or not understanding the effects of setState.

React should be judged by the quality of it's ecosystem and extant production code, and I would argue that if you survey these things often you will find plenty of unnecessary complexity.
I certainly did not imagine doing this on my own, nor have I tested the limits first-hand. The self-sufficiency permit isn't that difficult to obtain for a committed nomad, as I see it.

But the chatter in the Greek expat forums specifically describe the purely financial nature of the Schengen zone penalty: pay-to-play. The punishment comes in the form of the fine amount, which in a range is left to the discretion of the customs agent. Evidence of "flagrant disregard" or an otherwise spoiled attitude might get the maximum fine, whereas an honest mistake (or an engaging attitude) might cost only a few hundred euros.
A lot of people could start by learning the difference between a story and a reenactment. If your "story" takes the form:

And then she said x
So I responded with y
And then she was all like, "I can't believe you responded with y"
And I was like, "blah blah blah"

...then it's not a story; it's a reenactment. I love stories. I hate hearing reenactments.
Great mindmap.

One thing I want to add though is that for some reason "mindmaps" are all the rage now, but they really are just one type of "concept map". If you get a chance, look into concept mapping. It will give you a greater overview / understanding.
How I Learned Python and Landed My Dream Job as a Data Scientist
Yep: "The reason God could finish the earth in six days is that He didn't have to worry about backward compatibility."
DOOMDAY MAY BE SEPT First UK SET FOR DEVASTATION,
I would avoid the business guy trap. Find another tech guy or go solo and make a startup.

Ideas are cheap, tech is the hard part. Why waste 66% if your equity on two guys with an idea? If their idea is good they can hire developers or raise VC to makd their MVP.

Have been on both sides of this. In most cases i dont think the random business guy is worth hooking up with.
ARDOP[0] is the planned replacement data protocol for Winlink, and is slowly shaping out to be a faster, OS-agnostic open source system.

Unfortunately, there's still a FCC limit[1] on HAM radio "symbol rate", which hamstrings these systems by forcing low bandwidth operation, though there has been some official traction in updating the rules.

[0]: https://www.winlink.org/content/ardop_overview

[1]: http://www.arrl.org/news/arrl-files-symbol-rate-petition-wit...
A lot of hate in this thread seems against even discussing this, but I think it's worth exploring.

I usually refer to some of these groups of ideas as "composability of workspaces". People question why you would want to dock or undock a tab from different apps, but we already work like this a lot when we use modern IDEs and web browsers. I'd argue that Emacs and Linux CLI still has a lot of appeal for this reason of workspace composability.

Are we better thinking and debating about how we want computational environments to exist, or simply hope that the next version of iOS or Windows 'does not suck'? Will we be able to seamlessly compute across multiple devices; will OSes become specialized? What would be optimal?

There are social, economic (scarcity of programmer time), and institutional limitations to undertaking huge projects. But that doesn't rule out any type of progress toward a long-term goal, or prevent people from booking small wins.
Ebay sounds like a real world project to me.
There are a lot of ways that things can go, but starting out with the disposition that either the bug report is wrong or the other machine is somehow made of worse silicon than our own, is rarely helpful.
Zuck et al probably realised very early on that casual stalking was a major use case. Not in a dangerous way, but maybe you wanted to find out a little more about that guy or girl before you asked them out, that sort of thing. They were all in college at the time after all. So he was careful not to include any feature that would inhibit this.
TreeSheets (native cross-platform app based on wxWidgets) is great and in need of new contributors.

For non-linear organizing on iOS, the indie app MindScope (https://www.macstories.net/reviews/mindscope-review/) is uniquely fast for brainstorming and re-factoring visual layout, before exporting an outline to another tool. A single node can be linked from more than one location in the hierarchy.
It's hilarious that they criticize the stereotype of nerdy outcast male. If you're a girl, 9/10 you will never get flak for being nerdy (yes, exceptions exist, i know, but in my experience), on the other hand, emasculating the male nerd is practically a national pastime.

To add to the irony, a surprisingly large proportion of the anti - Damore tweets were criticizing his appearance and/or calling him a virgin.
Granted. I'll throw out the cloud platform, but keep the others.

1) There is no substitute for the relational model. Clearly it is a paradigm for building mathematical objects.

2) I didn't strongly advocate my choice of F#. Strongly-typed, functional first, ML syntax language is the sweet spot today. In theory this predicts faster development and fewer bugs. All software assemblies are mathematical objects, those built with strongly-typed, functional languages tend to be more humanly comprehendible.

3) No estimates allows practitioners to make useful projections of the course of a project. (Of the 4, this one has the weakest claim to belong to theory, yet I will argue useful projections are a kind of prediction.)

4) TLA+, or something like it, separates spec from implementation detail and makes "predictions" (at arbitrary level of granularity) of what a completed software component will do.
Who said anything about paying men more?

The claim in the memo is that men are pushed towards jobs that are high paying. If a man tries to go to low paying jobs they are generally punished by society, often by being called things like lazy, weak, unfocused, and so on. Those that do seek and get high income get rewarded with high social status and strong correlation with dating success. It has nothing to do with getting paid equally.
Google warns webmasters Chrome will mark http pages with forms as 'not secure'
Thanks for the down-vote.

More on this, computer were expensive toys, and traditionally boys get more expensive toys than girls. It's quite understandable the marketing decision there.

https://www.theguardian.com/world/2005/dec/06/gender.christm...
No.
1000 times no.
For the pizza base you use flour, water, salt and yeast.
For fresh pasta most of the time you use flour and eggs.
The process moreover is completely different.
You NEVER use tomato for making the fresh pasta or the pizza base.
You may use tomato as a condiment for pasta and pizza.
This comparison is even more wrong than comparing apples and oranges.
But I expect that unlike me you never cooked pizza and fresh pasta if you can't see the obvious difference.