skysight-inc/HackerNews huggingface dataset:
I think it missed the broader point that there's many reasons you'd want to endlave others apart from economic reasons or "power for its own sake". Altruism, for instance.

Who among us doesn't want to make the works a better place? Who among us doesn't have our own personal view of what a better place would look like, which might not be exactly in line with someone else's view? Congratulations, there's your dictatorial urge right there.

Most of the worst people in history, from Hitler to Marx to Pot to ISIS were all motivated by the desire to make the world a better place. Ascribing bad outcomes to bad intentions is a classic mistake.
The question was:

> So, how do I connect what that .NET Framework 4.0 VBC.EXE does with the discussion in the OP?
Your personal anecdotes and opinions do not trump national safety data. Statistics say bikes are safer than cars. Further, common sense says bike crashes involve far smaller amounts of kinetic energy.

Lastly, you make several assumptions that education, enforcement, culture, and bike infrastructure would not change with a persistent focus on increasing active transportation.
Some people expect many self-driving cars to be owned and operated as a service by a big company, rather than being owned by the users. Like riding a bus or train, they won't let you take a wrench to it.
Yep, it's incredibly disappointing. The CLR model is rich enough that MS Office can be compiled entirely to MSIL and run fine. The F# folks had to drag Microsoft kicking and screaming into shipping generics - else the CLR and C# would have probably only gotten the lame Java-esque erasure model.

Yet despite being shown up, utterly, entirely, they just sorta stumble forward. They realise there's no serious competitor in the language space - Java's remained terrible. There's no threat to C#, and it's a lot easier to maintain a compiler than a platform. The runtime hasn't seen any change since .NET 2 introduced generics (with driving work from MSR). Since then, they've tweaked perf a bit, but haven't extended the model at all.

Until there's a real threat, they continue down this easier path. Swift shows up and demonstrates tuples and matching won't kill average devs, ok C# will probably add those. And honestly they can probably get fairly far just reacting here and there.

It is sad though to see the grand idea of the CLR fall this far.
That'd be nice, as it gets around the limits of both products.

Truth be told, I'm now hooked on OneNote. I have ample free storage without bandwidth limits, and the client apps are really nice.
It seems a long time since - if ever - I read anything touching on accessibility on the web with anything genuinely positive to say.

I know it's a hard, complex set of problems, but it really does seem that everyone essentially concludes "well, we're not there yet", and that's a real shame.
Can't believe such an uninformative post is trending#2 here. Literally didn't taught me anything new.
Uncloaking the Origins of Collegiate Secret Societies
Some related terrible bad luck (well, for the Third Reich) in organization: the scientists' saving throw to get serious resources devoted to the project was ruined when a secretary preparing the invitations for a seminar accidentally substituted the agenda for a highly technical one happening around the same time, and the major figures who would have otherwise shown up declined.
They are also expensive as all shit.
Holy hell. Today I learned that "appstore optimization" is a real thing...
You mean, having an one-in-10-million chance of having a small impact on a billion people.
As a Type I diabetic for — what is it now — 21 years, stories like this make my heart race.

I simultaneously admire the author's fortitude and am hit by powerful worry and frustration that facing the non-stop challenges of T1D for so many years can result in such outcomes — and often as a result of one's own imperfections facing those challenges.

The guilt the author describes when realizing she'd go blind had to be unbearable. Man I hope to work hard enough and be lucky enough to not face that.
Sorry, I meant that that particular nib file (an AppKit UI asset) was not licensed for reuse; the rest of the code is, or will be. The nib is not included in the repo; I mention it in the description to explain why the project is missing a file, and also to ensure that people don't clone my app outright and sell it. (Not that anybody would want to do this with a small project like this, but I hope to follow this pattern with my later, bigger commercial projects.) I'm going to add a real LICENSE file in the next commit, probably new BSD, and I've edited the description to clarify this. That would still be under the purview of "open source", right?
Both, plus the fact that significant new tech infrastructure projects like the Windows Runtime are (mostly) restricted to Store apps.

I'm not anti- app stores or declarative UI in general, and I think things like standardized sandboxing would be great for many desktop apps too. But a platform that places you at the whim of a single distribution path, and cripples portability to boot, isn't worth it.
It's fine to think of JavaScript as something that you depend on for major features but I still think you have to follow progressive enhancement. A small, but potentially growing, number of users have JavaScript disabled completely but a much larger number of people effectively have it disabled for a non-trivial period of time while things download or even, due to errors, until they reload the page.

If you don't degrade well under those circumstances you're at a competitive disadvantage to sites which do something like quickly return a core HTML page which can display immediately while the full app loads.
The video of the kid who had been drinking and driving, got in a wreck, and had to have a hole drilled in his skull to relieve the buildup of blood was pretty effective for me.
Unmanaged native code definitely has an edge, even in I/O-heavy applications like databases.

http://www.scylladb.com/technology/cassandra-vs-scylla-bench...

Not to mention low-memory environments like mobile.
As a Linux user I have never used Evernote, but Google Keep has cross-device persistent notes and I've never had even the tiniest glitch with synchronization.
It doesn't at the moment. .NET Native only applies to Windows Store (metro) apps.

But in theory, it would work like a super-powered ngen.exe does (look up ngen if you don't know). But instead of still requiring a runtime installed, .NET Native will also link in the required bits of the runtime statically (the GC for instance).

This model is old and has been discussed quite a bit. Mono has supported it for a long time. MS has been ideologically opposed to it for over a decade and only just recently reversed their opinion, probably due to limited resources on low-end devices that MS has now realised are important.
Tinnitus in relation to neck/head muscle tension
Mostly because they aren't user-inputtable. Yes you can't realistically hand-edit a 3gb .csv either, but csvs don't usually start out that large.
Especially when you consider that it may not be certain who the "other people" are. It may have a probabilistic model that says there's a 45% chancce it's hurtling towards a mother pushing a stroller and that it has a 100% that it has a driver sitting in the seat. If it's two actions endanger either the driver or the mother, what kind of calculus should it do?
From the article: "last year, TechCrunch pegged the company's revenue at around $36 million, and while revenue has increased, we've heard the numbers are still short of internal expectations"

So Evernote is valued at more than 27x revenue??
I think we invited eatonphil to repost a couple of stories.

Reposts aren't necessarily a problem if the story hasn't had attention yet. On HN we want to optimize for curiosity, which means getting the best candidate stories in front of the community. Since /newest by itself does a poor job of that, we've been experimenting with other approaches.
The VB compiler compiles your code, not into native machine code, but into an intermediate representation targeting the virtual machine defined by the Common Language Runtime. This intermediate representation is known as CIL (Common Intermediate Language), and it is the bytecode that the .Net CLR then JITs at runtime.

This article is about compiling .Net code direct to machine code and skipping the whole CIL/CLR/JIT chain.
Unsurprisingly, I usually bike to work and take a keen interest on bike safety improvements. I hate the "protected bike lane" phenomenon with a passion. My most common incidents with cars start with not being seen by the driver. A "protected" bike lane destroys whatever little visibility I have to begin with and worse, the increased turning radius means that what was once a mild sideswipe will become a T-bone.

As a protected bike lane is usually also a wider than normal bike lane, ~8' vs ~4', I posit that you see a huge perceived and actual safety increase by just taking the existing normal bike lane and widening it.
IIRC the .NET Native literature says the main benefits are reducing RAM by a fair amount. Which makes sense - no runtime to load type info and no JIT to run. AFAIK, they aren't claiming the compiled code is _that_ much better than what the JIT does.

Of course it's probable that reducing RAM footprint significantly might improve runtimes if it makes better use of cache.
QP low level state machine generation
This isn't the future. This is the present.

We built Userify[1] (ssh key management for EC2 & elsewhere) entirely using this model (REST API) because it gives us a clean way to inspect incoming data and respond with pure JSON.

Since it's just JSON over HTTPS, clients are all easily implementable in any language (i.e., Javascript and HTML5 for the web app, beta client SDK's currently in Python and JS, more on their way), or just a curl shell script. (The agent[2] is just a single Python script with no dependencies.)

And, now, with great tools like Phonegap/Adobe Build/etc, you can convert your responsive mobile web app into an Android or iPhone app in seconds (performance is no longer an issue, either).

Best of all, you maintain a clean separation of concerns and isolation between your API resources and the front end.

Compared to the server-driven ways from the last century, this is so much better; we can provide a full desktop app experience, make it feel more like a web page, or anywhere in between.

AJAX changed everything. This is simply better.

1. https://userify.com

2. https://github.com/userify/shim
I have, indeed, no eyes although I'm less sure about the laughs.
It's not a moral thing exactly; Uber's competitive advantage is that they don't bear the cost of compliance.
I was a longtime user of evernote but recently gave up. The webclipping tool was phenomenal but the notetaking interface was so and so (their desktop app was also poorly built which made things worse). After awhile, onenote took care of my notetaking needs and pocket of my linksaving needs.

I think this was a great part of why evernote faltered. They just became a repo/dump of user crap. People didn't care to engage with the platform and therefore did not care to find out what extra value it could give them, thus preventing them from converting to paid users.
T1D here too, echoing your sentiments. It's a terrifying reality to face. Perhaps foolish to say but I think I'd rather lose all of my limbs (another fun possibility for diabetics) before I lose my vision. Huge respect to the author.
Whether you get a USRP or not, the Ettus Research bootable image has GNU Radio already installed and configured, as well as a bunch of other useful radio tools:
http://files.ettus.com/liveusb/latest/

They've also got some good tutorials on using GNU Radio Companion.

I'd recommend an RTLSDR, USRP, or HackRF. All good, all different price range, and all have a good community and support around them. If you're interested in a particular band, you may want to get an antenna for that band as well. Ettus Research sells some antennas, or you can buy one from an amateur radio store, or build one for very cheap from the dozens of plans out there by ham radio operators.
What if not all columns are quoted? A lot of the time only the columns that need quoting are quoted and the others are bare.
Have a look at his resume: https://github.com/eatonphil/resume

Now decide if you want to listen to his opinion of all his 'experience' of these projects.
Wasn't this the exact reason Apple was so strict about the one-button mouse for Mac OS and the menu bar? In fact, obfuscation is the exact reason Google ditched the menu button on Android?

3D touch does resolve the iOS issue of not having a back button(without adding any of the ambiguity I hope). I sincerely doubt regular users would use it. It would be like multitasking or the does cool 4-finger gestures on the iPad, something only power-users use extensively.
I think too much has been made out of this thought experiment. Practically, I don't think driverless cars would have any strategy other than "full stop". There are too many variables to consider for any other strategy. Of course there will always be Bayesian priors that these cars will use to avoid such situations to ever happen in the first place.
I was staying on raw numbers without factoring the "some people may deserve saving/protection more than others", because that's yet another can of worms ...
> I have no interest in following [the] guidelines

Ok, we've banned this account.
Pedestrian overpasses are going away. A mall near my house just removed one built back in the 60s, replacing it with a new street-level intersection. That was the cheaper option than making the overpass wheelchair safe. We also have a huge number of older people who will always opt for level crossings, what real estate people here now call "all one-level living".
It seems like there's a pretty simple solution to this, based on the definition of "ownership" that so many products are trending towards lately: you don't own the car. Even if you've technically purchased it outright, all you really have is a perpetual and transferable license to use a car that's really owned by google. The car has a responsibility toward its true owner - google - to do the least damage to their reputation and their company, so if it has to choose between killing its occupant or killing four other potential google customers, it's going to choose the occupant.
The paper actually illustrates many advances in OS abstractions and techniques before and after UNIX that was superior to them. There's others outside this paper as well. Many, even on limited systems, smashed it in terms of IPC performance, fault-isolation (esp drivers), concurrency safety + throughput, shared memory support, management, and so on.

It was discovered far back that there were limits to how reliable or secure the UNIX API could get when improvements were attempted. Look up UCLA Secure UNIX, LOCK/ix, Trusted Xenix, Mach ports, L4Linux ports, and so on. Outside of isolating a whole OS (i.e. virtualization), they had to change the behavior of and/or eliminate many calls because they had too many negative effects on system state in fault or malicious conditions. This was not true of many alternative architectures that naturally decomposed systems, isolated faults, protected at interfaces, and/or implemented language-based protections. It's just a UNIX + C thing.

Let's re-illustrate this economically. MINIX 3 took a few people a few years to get it to a stage where it was quite reliable ("self-healing") as a console OS and easily modified due to architectural choices. How long did it take UNIX/Linux kernels to do that? No, really, because Sun's and Linux's kernels were still crashing on me in the late 1990's plus corrupting my filesystems on occasion. I'm wondering if it took two decades with hundreds of contributors or three decades? Either way, I think the effort vs results says something about their architecture and implementation strategy.

Similarly, Oberon was thrown together in a short time with few people while achieving more reliability, consistency, language-oriented protection, and concurrency performance (with AOS vs forking etc).

Many examples of systems doing it better with better results across the board. That also directly contradict UNIX model. It never won for superiority: just simple enough to run on the "cheap" hardware back then, open-source, and lots of users already.
402: Payment Required
Chaotic classifications are character traits in Dungeons and Dragons.
For fans of Jorge Luis Borges, he has a short story that covers similar thematic ground: https://en.wikipedia.org/wiki/Tl%C3%B6n,_Uqbar,_Orbis_Tertiu....
Oh, I'm well aware, having worked on a NASA program for the prime contractor for 2 years (and being a life-long space nerd). I love the idea of NASA, but the reality that I encountered was quite jarringly different. The culture was toxic to any new thought, or any outside opinion. I fled (at great personal expense and stress) before the toxicity of the environment broke up my marriage and eroded my soul. My wife is a veteran of NASA HQ and ultimately left for similar reasons -- the agency just wasn't interested in actually doing anything that wouldn't further its own political interests.

Disclaimer, of course, is that my experiences only apply to the specific NASA site I was at (that's why my profile says "reformed sounding rocket engineer"). I think I've posted extensively about that job before.

My point was simply this: NASA is now a large hierarchical organization whose primary goal (as must be the goal of every hierarchy) is to perpetuate itself. The parent made it sound like all that's needed to solve some of these complex problems is to open the fiscal floodgates to NASA. It's going to take more than money. It's going to take a culture change.
Ditto your props to author.
>> No enjoy-cooking-people I know want to write software.

I enjoy cooking, I enjoy eating what I cook and I write software because I want to.

When I think about it, I'm actually a bit sad I can't taste my own code :7
Agreed – I have spent so much time in traffic consistently going at the average speed, not tailgating, etc. and repeating the cycle of passing and being passed by aggressive drivers who are too busy making crazy lane changes to notice that they've spent an hour not getting any further ahead.
Thanks for the profound insight, captain obvious.
Google don't need to do trains because other companies have been progressing this since the 1960s — the Victoria Line on the London Underground opened with the first automatic train operation in 1968. There are now many similar systems.

Buses are more complicated than cars (city driving, people at stops etc), so doing cars first makes sense.
This suggests a strategy for improving the healthiness of soda: the government should work to make the ice-cream float come back into fashion. "Don't drink your soda plain: add a scoop for your health!"
The compiler has no concept of what a thread is anywhere, even in the standard library. The safety is imposed by careful bounds on exactly the right functions: those that interact/create new threads, e.g. std::thread::spawn has signature:

pub fn spawn<F, T>(f: F) -> JoinHandle<T>
where F: Send + 'static + FnOnce() -> T, T: Send + 'static

Other than implementations of `Send`/`Sync` themselves, this is essentially the only function in std that needs to bound by them.

The same approach can be used in a kernel context, e.g. place bounds on the functions that create (or, at least, initialise interaction between) concurrently executing pieces of code.
If you do this again, we're going to ban your account. You've broken the HN guidelines so many times, and we've warned you and cajoled you and asked you to stop so many times, that enough is enough.

Edit: you edited out the worst of it, but the comment is still a personal attack.
"Chaos",James Gleick

Maybe not the best book for understanding chaos theory, but I have not stopped seeing stochastic patterns and applying concepts of fractal geometry to things I come across in life as I attempt to wrap my mind around some of the deeply complex phenomena in the universe. Whether being enraptured by the flitting and fluttering of a curtain in a breeze, or in observing the fundamental structure of a trees growth and branching.
The whole concept of the poincare section completely blew my mind open, even though the math was well over my head. The book stunned my feeble mind. Even though it has been about 15 years, no scientifically centered book has resonated as strongly since.

As an aside: GEB has come up so often it has reminded me that it was on my short list of books to read once upon a time, alas, before the internet stole my time.
I saw "I Dream of Wires" on netflix. I enjoyed it, and grew up in those days so have a fondness for the sounds.

But there was one thing I didn't quite get, which it didn't explain, just glossed over, is why people got so obsessed with synths. It assumed you already know why. I've always tinkered with things, but don't get it. Perhaps because I never had access to one. Commodore 64, yes, soldering iron, yes, modular synth, no.
Some of those ore samples are quite beautiful.
I'm reluctant to call this "wisdom", though...I've learned not to be surprised when friends and colleagues who are otherwise near-paragons in wisdom in work and life can suddenly turn into road-ragers. For some people, getting angry in the car is not a typical characteristic but may result after a series of stresses that day.

So the machine isn't being "wise" when it avoids road rage, it's just being a machine.
Tracking aircraft with a passive radio receiver? You just sold me on SDR.