skysight-inc/HackerNews huggingface dataset:
A lot depends on how "systems software" is defined. Very few people have much use for a whole new kernel. Even little pieces of new kernel code are less useful than before, as various functions (e.g. storage) can be handled just as well in user space. So if "systems" == "kernel" then relevance really has been declining. On the other hand, if one considers "system" to include user-space storage and networking, distributed consensus and service discovery, package and system management, JIT and GC in language runtimes, etc. etc. etc. then we're actually in a bit of a renaissance.

The fact is that kernel/user hasn't been a very interesting boundary for a long time. There are hundreds of systems-programming problems that can be solved on either side of that boundary, except that if you try to solve them in the kernel debugging will be harder and you'll get embroiled in the constant turf wars that are the hallmark of a declining specialty. The idea that only kernel hackers do systems programming needs to die.
He seems to think progress would look like "a new wave of built-from-the-ground-up operating systems sweeping away all the old ones every decade or so". Say, if Plan 9 had become dominant in the 90s, would we by now be replacing it with something else? What would everyone moving to new operating systems every 10 years gain us?

There has been mind boggling progress since the 90s, just not in the direction he expected.
> No, how did you accidentally write to /etc/init.d?

Let me quote again, with a finer slicing:

> I went through all of the above because some real machines hit this for some reason. I don't have access to them
VclFiddle – experiment with Varnish Cache in a sandbox environment
GitHub is free, the repo owners are not the customer.
In this case my definition of a point is a single remote to github.com/<project> in all the OSS projects .git/config

A single issue tracker with hundreds of issues for all these projects. A single database of commiter permissions. Etc.
I suspect there's a few people out there with iPhones, they'll be ok.
This Is How You Can Raise Your IQ and Improve Your Memory
This is the actual link: http://www.lpi.usra.edu/resources/mapcatalog/usgs/
I have been using this and love this UI framework. +1
I see two sides in shells, you want high-perf high-density UI or you want design oriented low bandwidth ones. For the former emacs is not good (I'd say it's not even lispy to witness and crunch lots of data visually, write abstractions/queries and such and think higher).
When I was a Customer Support Engineer for SGI way back, I had to swap out a load of IBM drives on lots of SGI kit at various customer locations due to this, which was dubbed "The IBM Stiction Problem".

Power off --> remove drive --> Sharply tap the drive on desk --> replace drive + add new drive --> clone

The look on customer faces at the "Sharply tap the drive on desk" stage was as priceless as the data on the hard drive B)
I've got to build an SPA and I'm trying to choose between Angular and React, can you guide me a little,
the app will :

- create a big form based on an XML schemas, the form will be used to generate valid XML with the schemas

- some schemas can be really big with more than 3000 elements, the whole thing won't be shown in full to the user directly but probably folded

- because it is based on XML Schema, it must have interactivity to make some elements repeatable, and groups of nested elements repeatable, some elements with bounds, some maybe draggable to reorder them, everything an XSD can do...

- it will also some kind of polymorphism where you can choose the children element type and have the corresponding schema showed

- it will also show a leaflet map, with some interaction between the form and the map

- there is also a rich text editor where you can arrange xml objects between formated text

I fear that angular won't be fast enough for that, but his support for forms seems better, I've tested JsonSchema forms generator like https://github.com/Textalk/angular-schema-form and https://github.com/formly-js/angular-formly the first one is slow when editing 3000 items the second seems fast when editing, and slow when it generates the json. I've done some angular tutorials and their concepts don't stick in my head. I've tested React and their concept stick easily in my head but there is less native support for forms.

I had just decided to go with angular partly because of all the hype around it, but I see the article and others as a bad omen and I want to go with react now. Any advise ?
Exactly the same for me, it was such a fascinating character (and novel)
This seems to be the summary of every tech flame war ever, and applies rather well here:

A: I've used tech X in a lot of Y contexts, and I find it's not great. I will generalise slightly imply that tech X is not the panacea that it has been presented as.

B: Yeah? Well, I've used tech X in a lot of Z contexts, and I find it works fine! You're wrong! You're using it wrong! Maybe you're not wrong in context Y, but for most other contexts X is still the best tech!

C: I haven't used tech X at all, but here's my opinion on it anyway.
Earthcam
As a long time Oculus owner, I like that they put the screendoor effect on the video
Please note: 3d-printed prototype. I'd say, making a product out of this - instead of, say, an open model on thingiverse - is so 2012.
This is what's called gradual engagement. Google what patio11 has to say on the topic, but to summarize it it's not an obvious win and you should A/B test that (against just getting contact details + getting them into a free trial).

Now, I see you have just launched a beta version and have an aversion to copywriting (on the "try" page). In my opinion, you should focus on explaining the value proposition to users, getting a few of them onboard and working on the engagement. Avoid spending too much time on the product itself and listen to what the users have to say: is it solving a need? How are they using your product in their work? etc etc
It probably means ARM will create ASIC type encryption on their chips. May be helpful saving battery life.
I fail to see how an exception vs an error code makes any difference whatsoever.

The whole problem is that the library doesn't notice the error. If you don't notice an error you are not going to use an exception either.

Not to mention that an exception by default terminates the program, which is exactly what you don't want to do.
Jenny Holzer's piece is by far the most interesting and opinionated, and still relevant to current discussions on security, leaks et al. Love her take on this.

Sherpard and Davis' are trite in both concept and execution. IDEO's is prophetic, but they're a pretty good forecasting company. Truly disappointed with Sherpard and Davis' though, walkover commercial designers.
DSLReports
NetCraft
Actually it depends more on the time of development and project specs. For now I'll probably choose ReactJS.

If by the time Angular 2.0 is launched then I'll definitely give it a shot, it seems promising and is based on ECMA6 utilizing the new features provided by it will be a plus.

IMO AngularJS can be scaled _IF_ used with caution, though I won't recommend it unless one has a good experience with its core.
We didn't know how to get to the moon, but we knew we could get there if we tried. That's religion. We got to the moon, by doing the things we needed to do to get to the moon: thats Science. You can't have one without the other.
At first I was pretty sold on react too.

Now I'm trying to figure out if the bad parts in Angular are worst than the bad parts in React. I don't have an answer yet.

The only thing I'm sure is that the virtual-DOM thing is a good idea and most frameworks are likely to converge here.
This started happening before Fukushima.
I'm currently playing through Pokemon SoulSilver, which is a remake of Pokemon Silver. IMO it's the best Pokemon (though I've not played X&Y).
Just because securing http is not necessarily considered the "biggest challange" it's not useless or even harmful.

I don't see Let's Encrypt initiators communicate their project as the only action needed to fix all web security problems. (Not even to discuss the legal ones..)

Edit: Actually I think their "what we are" statement couldn't be more straight forward: https://letsencrypt.org/
Maybe attempt to work with their consumption. I they like watching kids TV shows online, show them how to download the videos and edit them. Maybe they can cut out parts they find boring at first, then move onto making a best of version from a season to eventually remixing the shows into something completely new. There's some fairly decent and easy video editing software nowadays - all drag and drop - that could be fun for them to explore, while still being able to consume.

The good thing is that this could be a gentle intro to critical thinking - ie analysing a show to say what they like and don't like and why - then move on to them creating a better version for themselves... The tech skills could come later when they bump into barriers to doing what they want - eg not enough RAM or harddrive space, so they then have to tinker to get the system to do what they want.

Just an idea..
Lavatory Laboratory: How sanitation is following the cell phone model
NetIndex
Sure. Sign me up. Also, ContikiOS.
There is The Architecture of Open Source Applications series of book http://aosabook.org/en/index.html were one of the author of the software explain the essence of the program.
A quick search on my local classifieds section shows a 2006 for $6,000, and a 2008 for $10,000, all the way to a 2011 (with rebuilt title) for $7,500 and everything in between. Used cars are almost always a better choice.
And a less advanced equivalent for VIM - http://vim.wikia.com/wiki/Automatically_refresh_display_of_h...

Just tested with Firefox Developer edition, MozRepl and VIM - works as expected.
When is a string not a string?
You're right of course, it can't rely on collimated light like the normal Schlieren system. But the background-oriented Schlieren technique, mentioned elsewhere in this thread, is more reasonable to look at for inspiration, and it provides pretty much the same end result.

I suppose it can be thought of as a differential filter: only minute changes are interpreted to create a representation of the flow of air.
That's true. What upstart could have done, though, is to watch for config changes in a separate process, so that it does not need to have an in-process dependency on something like this.

That would give upstart a way of handling the overflow and other (unknown) potential problems: rescan the config if the config watcher dies (after respawning the watcher).
Angular will force you to convert all your rendering logic into its declarative API: ng-if, ng-repeat, ng-include etc. With React, you can simply write your program logic in Javascript and compose, reuse and pass around parameterized components with ease.

Try building a simple nested tree in both Angular and React to see how both feels.

Khan Academy has open-sourced their QA builder that supports creating questions and answers with graphs, radiobuttons, multi-selects, images etc. It is built in React. Take a look here: https://github.com/Khan/perseus
Thats interesting, my first guess was something along the lines of a chunk is 16x16 so your "five hundred" is actually 512 at exactly 32 chunks and you're deploying chunk loaders along the road to keep the road loaded (and maybe also farm fields or trenches full of mobs or pipelines full of liquids or the worlds biggest applied energistics network or ...) Or something like each player can ask for a 128x128 "deed to the land" along the side of the road for megaprojects and there's exactly 4 along each side of every road segment.
Thank you very much. The client preview is indeed the "aha" moment, I will try to make it easier to view / reach.
The top 500 sites on the web
Veronika Hubeny's black hole research
His grave is in Mortlake just round the corner from me, it is ridiculous, a stone tent with a ladder at the backso you can see in through a glass panel. Picture here https://en.wikipedia.org/wiki/Richard_Francis_Burton#mediavi...
Maybe if Google actually open-sourced as much software as they consume, that would offer a way out. Some people would still want to run the centralized as-a-service tools because it's on a huge professionally-run infrastructure and because of network effects. Others might want to run the same services locally, to support privacy/decentralization goals like the OP's. Google's main revenue stream (ads) shouldn't be affected, and they'd even benefit from outside contributions.

So why don't they do this? Because of the difference between "shouldn't" and "wouldn't" at the end of the last paragraph. What if code to support ads - or other invasions of privacy - were embedded into every other thing they might open source? Then the sheer difficulty of refactoring to "sanitize" everything else would probably create a sufficient barrier to opening it up, and revealing how all of that ad infrastructure really works might hurt their business in other ways.

When Google continues to run as the new AOL (closed source, walled garden) I don't think it's part of a deliberate philosophy. Nor is it an accident. It's because their continued uber-prosperity, if not their actual survival, depends on it.
I think around 7 months into any project you start to realize the pitfalls of whatever technology you're using.

You've done the easy things after 7 months, and the hard things are always going to be hard.
Statcounter – GlobalStats
We built a pretty complex app with Angular (https://slimwiki.com) and have had nothing but great experiences. The main issues are no guidelines about the right/wrong way to do things, it needs to be more opinionated.
Mente Correta
Yes, nothing new here.

"This technology contains trade offs and is complex at times."

Oh, you don't say?
Thanks, the idea to use code instead of a limited set of declarations to create the view is convincing.
Insights from Startup Expo
I know you're being sarcastic but without a jot of sarcasm...

Fuck reality, we're going Virtual
No experience with Angularjs. Meteorjs is great, I just started a couple of mounths ago and I love how easy is to make complex real-time things. They should work on better documentation, there is only 1 valuable book right now to buy. Others are coming. The main problem is that meteorjs community is small compared to angularjs, and that is pretty strange to me. It's a well founded company - $11M - with a slow ramp of adoption. Why?
I will search what Patrick said about gradual engagement for sure. I was not aware it had a name or something, thanks.

I completely agree with you on focusing on user feedback, I simply wanted a different, more quicker first impression homepage.
Facebook Platform Status
Random thoughts on Artificial Intelligence at 1am
- Everything you need to know about Angular is explained in ng-book or the like. Trying to learn the framework by reading blog posts isn't going to work. There's just too much to know, and it's impossible to understand what's really going on unless it's presented in a logical and comprehensive way.

- Angular isn't designed to render large tables. Go with DataTables for jQuery instead, or if you don't need all the features there then maybe you can get away with ui-grid.

In general though if you're running into performance issues because you have too many bindings, then you're probably using it for things it wasn't designed for.

Also, don't forget 'track by' for improving ngRepeat performance:

http://www.codelord.net/2014/04/15/improving-ng-repeat-perfo...
I wouldn't be surprised if plan9 builds are an order of magnitude faster per LoC - Deeply nested includes and cyclic includes waste a huge amount of time.

Avoiding cyclic dependencies might also be a good thing in terms of overall software design.
I my experience, the talks at 30c3 were a bit more technical again than those at 29c3, at least some smaller ones. Personally, I like to discuss the implications of tech in society in bigger talks, because the most interesting technical discussions for me are happening at the assemblies.
>are worst than the bad parts in React

Which are...?
WonderPush Saas simplifies iOS and Android push notifications
Great, the site kept my CPU cores (and cooling fans) very busy, I accidentally clicked on the download link, which brought me 2.5 MB zip file. This thing ain't light. But gosh! 10k stars on github? are you people crazy?
How Alibaba’s Sales Hit $9.3B on 11.11
The library noticed the error and was (effectively) calling exit().

If the library was at liberty to throw, they would not have to change any internal callers and would get the same feature for them (not having to deal with errors anywhere) but they would still give the external caller a chance not to terminate.

Yes. By default, a caller would terminate, but it would get a chance not to in a way that doesn't involve changing the libraries public interface.
Πως να επιλέξετε ένα E-shop Theme σε Woocommerce – SEO – WEB DESIGN
Personally, I think if you want to kindle interest in people that aren't traditionally considered tech people, the usual course of action goes from user to power user to novice programmer. It goes from using the most appearent options to using less appearent options that do it better to creating your own options and tools.

Say someone watched a lot of different streams. Show them how they can do it in VLC from one place. Show them enough that the utility of using VLC outweights using whatever method they used previously. Then, give them some time till usage of that tool becomes a habit. Then show them how to use the VLC command line options to record and convert streams so they can download them onto say their phone. Gently suggest "There's a rabit hole here, and it's filled with fun". Then give them some time to tinker around, see what they can do. Once they outgrow these shoes, when they're running out of cool addons they can install or when there's something that's just not in there yet, you can start to teach them how to write their own additions.

Now this is just a single example, but i think it illustrates the point. You want to help them slowly build momentum and a need for better tools. Most people are cocconed in a comfortable level of software usage, and they belive that their tools are sufficient, and learning more isn't going to be worth the returns in regards to effort. If you manage to sucessfully change those beliefs, their entire modus operandi regarding computers will change.

Now what tool and which lesson will get that started differs from person to person. For some it's learning VBA scripting for work, for other people it might be using Autohotkey to create macros or even learning some keyboard shortcuts ("Wait, alt-tab switches windows? That is so neat!"). Luckily, about everything that is commonly used has some kind of handy add on that extends functionality, say Reddit and RES, or getting that Junior Junior Dev to move from notepad to notepad++ and then after a good while to vim or emacs.
Microsoft – Service Status
Chart.js – Simple, Clean and Engaging Charts
You mean like Gerrit? Or do you mean something else?
Right. My point was that the mention prompted to me to read TFM and find the fix.

I've just done the config file setting you mentioned.
I've been using Angular on-and-off in professional settings since 2012. Angular is a framework obsessed with testability that treats usability as an afterthought. That said I've found Angular to be more than flexible enough to meet the needs of your typical CRUD apps, and generally enjoy working with it.

One thing I agree with the author about is the importance of expertise for a successful Angular project. Some specialized knowledge is needed to get a decent fit and finish, and the results can be horrible without that.

Strongly discouraging globals goes a long way towards improving code written by inexperienced engineers, but Angular's provider system is still not clearly documented with practical examples, which makes those engineers more likely to shove everything into the unavoidable Angular constructs (controllers, directives, $scope).

The middling quality and small availability of third-party Angular libraries is a problem. I believe that greater awareness/better tooling for ngDoc would be a tremendous help there. Best practices are not well-presented anywhere in the Angular world, particularly for designing reusable Angular libraries.

The other big problem is the project source code which I find poorly organized and documented. If you want to get into the guts of Angular for debugging purposes, good luck!
A reflection on the gigantic difference between failing and failure
> For Windows, it's easier to start IDLE than it is to start python from a command line, and the editor is better. It's still terrible, but at least it's better.

I am pretty sure the Windows Python installer adds Python to your path. On my system, at any rate, starting Python on the command line consists of typing "python" and pressing enter. How can it get any easier?

That said, starting IDLE is easier, because hitting Winkey + py + enter opens IDLE whereas there's the extra step of opening the terminal if I want to use it on the command line.
Are the versions you're using up to date, however?
I'm currently enjoying angular after having spent a year and a bit working with it exclusively. I am keen to try out Flux and Mithril, but I've not had the time nor the opportunity. But as it stands, we're deploying several large projects into very demanding organisations that are stable, performant and easy to manage. We as a team owe lot to Angular in terms of our productivity. We're also a great team and that counts for a lot too.

The thing I would like to add to the debate is this: We've all learned that Angular is hard. It's a complex beast with it's own nuances and idiosyncrasies. It also offers plenty of ways to do things you probably shouldn't do (i'm looking at you expressions). But more than that, with Angular in the tool box, people push themselves to deliver products vastly more complex than would be feasible without it. And these two issues collide all the time. Learning a framework + the desire to deliver more; One should follow the other, but people tend to attempt both at the same time.

I personally don't think there's anything "wrong" with Angular, but people have to acknowledge that despite the marketing hyperbole, learning Angular means setting out on a long and difficult journey that will require the developer to rethink a lot of what they know about building web stuff. But that's web development in a nutshell. It's a different gig every year, and within an alarmingly short amount of time, Angular will probably be replaced with something better suited to the tasks that try to accomplish the thing we want to accomplish with mere HTML, CSS and Javascript.

There's also a lot to be said for how you organise your projects and what tools you use (eg Require or Browserify etc etc), but that's a very different kind of conversation.
After T amount of time with technology X, I've discovered it to be imperfect.

Furthermore, I've found that it either let me shoot myself in the foot, or would not let me shoot wherever I wanted.
Whenever I improve the title, it gets reverted back to the original. Whenever I point to a secondary source, it gets replace with the primary. When I use the primary source with the original title, it gets no votes.
The vulnerability is in less-the-complete-system. More doesn't even have the ability to pipe its input through random shell scripts that call exploitable programs, AFAIK.

The problem is parsing complex file formats in unsafe programming languages, and any system which does that will be vulnerable.