skysight-inc/HackerNews huggingface dataset:
SEL4 is provably free of segfaults, without any runtime overhead at all. Unlike Rust. Though it took considerable development time overhead to achieve that.

(Moreover, rust itself may have bugs, or there could be bugs in unsafe code in the standard library. The amount of trusted infrastructure is much smaller for SEL4, I suppose if you compile it with compcert, I imagine it's quite small)

The worst case latency is also part of the proof for SEL4-- which is a kind of correctness you cannot achieve via rust (even ignoring overhead).

There are many elements of program correctness beyond memory safety. The developers of rust generally eschewed concerns about other kinds of correctness. For example, your integer types may overflow and your algorithms could fail to work as a result. SEL4's proofs show the operation of the software match its specifications completely (given some assumptions), it's really far far beyond the memory safety promises of rust.
Debian has a chrony package as well, another alternative ntpd.
uyrururu
ijghjg
Apologies for any snark.

What you actually said was, "Helmets are pretty universally known to reduce traumatic brain injuries."

This is wrong and not what you are now saying. You are now saying that among people who have suffered brain injuries, helmets are known to reduce traumatic brain injuries.

If the helmets make it more likely that you suffer an injury in the first place, it's not really a consolation that they mitigate the effects. There are actually reasons why many people oppose compulsory helmet laws.
The file is not written in Go. It appears to be a "hello world". Since all these commits predate their git storage technology, it's a form of back-dating...
I lived across the street from United Thera. a few years ago and met Rothblatt at a company party I walked into on the street. I googled her and read all the things in the article and was amazed at her life story . This happened before the party, as I was curious about the company right in front of my window. Was great to talk with her about the insane amount of hard work she had to do to save her daughter, etc.
Everyone I met at UT said she was the best boss they ever had. They have a very startup type vibe at United Thera, and the buildings they constructed are amazing too ! Everytime I saw Rothblatt, there would be a circle of people waiting to talk to her, and fawning over her.

Its great to see this years later on yCombinator
Lifting up constants into defines/consts and DRYing up C code makes for shorter, less error-prone and easier-to-understand codebases. Eg there's no reason to continue writing code like it's 1960's because we can steal good software eng and maintainability lessons from everything that has come since. (If one must maintain absolute portability.)

PS: I would like to see a toolchain for Go that emits portable C instead of statically linking in a giant runtime... Lightweight camping vs. YAGNI hoarding. Seriously, the weight of runtimes would be the biggest barrier to serious systems deployment, outshining the slowdown, productivity and safety tradeoffs. (Eg Go would need to play nice with embedded constraints including memory usage as well.).
It really isn't. Take a good long look at Java generics and ask yourself if they really came straight out of type theory research. They didn't, that's why they're so botched, and why Odersky wanted a do-over with Scala :]

More seriously, Scala and Rust are the only things in your list that would actually claim to be influenced by academia. I'm sure Apple is not going for the type theorists with Swift, despite having some mildly interesting type structures like sum types, and C++'s "lambdas" obviously have very little to do with type theory, unless you want to make the very weak claim of "anything that has anything to do with the lambda calculus = type theory".
Or perhaps very few people are in a position to use a very recently Open Sourced OS that has no file system or network stack, or write these things for it?

Presumably you'd want formally verified versions of at least the network device driver... otherwise process isolation might be violated.
A big problem with Rust right now is that the documentation is awful. This has two implications. The less important one is that the language is harder to learn. The more important one is that there's no architectural document that prevents Rust from becoming a collection of features in search of an architecture. If you have to clearly explain in writing how something works, and the explanation is overly complex, that's an indication that simplifying the design may be necessary.

The basic concept of ownership in Rust is simple. Everything has either a single owner, or a reference counted cell as owner. Things which cross thread boundaries have a locked reference counted cell as owner. Temporary references to single-owner objects are allowed, but must have a shorter lifetime than the primary ownership, and this must be demonstrated by simple static analysis. That's straightforward.

Making those restrictions usable seems to require many features and much churn within the language. It's too soon to tell how this will come out. As I'm mentioned before, I'm bothered by the need for "unsafe" code in pure Rust that's not calling hardware or C code.
What evidence do you have? Excess gas is routinely burned off nearby oil derricks to this very day because it's not cost-effective to capture for resale.
I agree. I went from dot-com Unix admin to investment bank Unix admin in 2000. Luckily it was via a consulting company. They said my interview process was unusual, because every internal interviewer passed on me, while every interviewer from a dot-com gave me a strong recommend. I was interviewed by them many, many times and finally accepted.

It was very different. At the dot-com's that I was at, web servers and application servers were Red Hat Linux, and only the databases were Sun boxes, with E4500 being a high end box. At a post-IPO dot-com there might be one E6500 and maybe a few Sun E4500's, and lots of Red Hat machines. At the investment bank they were all Solaris on the Unix side, and had dozens of E6500's in my city, and hundreds of E4500's. The investment bank had admins in the OpenBoot PROM all the time, whereas I had barely been in it. The investment bank was always replacing disks in the hundreds of external RAID arrays they had whereas only our database had a large external RAID array. They used NFS extensively and you had to know it thoroughly. My knowledge about Red Hat Linux, Apache web servers, Java application servers etc. didn't amount to much.

It was qualitatively (and quantitatively) very different, and in interviews it sounded like I didn't know what I was talking about.

On the developer side, the bureaucracy is very different. If a minor change in a software package is being pushed to New York, London and Tokyo, which often it is, you might have five meetings about it, and the code push might take weeks or even months. No matter how trivial the change. Three different divisions might have to sign off on the change. It's definitely not an agile code process, with code going from your fingers to the production web/app within the week.
I seriously think the C-hater crowd on HN is just disappointed that they can't reason well about pointers. They can't write good C so no one can! It needs, like, more javascript, man.

(Preemptive response to downvoters: please have a sense of humor about yourselves. :P)
From the guidelines:

> Otherwise please use the original title, unless it is misleading or linkbait.

[...]

> It's implicit in submitting something that you think it's important.
On the other hand, this program is going to take a year or so before anybody seriously considers using it, simply due to the fact that few people are going to do something other than their distro default for such a small part of their system.
LittleBits Hue Lighting Controller
Just checked out your github page, you are like my brother from another mother. If I am in Berkeley I will drop you a line and we can code on some Forth JITs in Lua.
In a dense city like SF/Manhattan you may need to constantly circle vs. being able to pull over and wait.

However, this leads to an interesting idea: prioritize new fares to drivers whose GPS says they are moving < 10mph.
In the Seattle area it was bad enough I started my own business, moved my family of 3 into my parent's house and tried to make do on my income tax refund.
FastMail have really been pulling it out of the bag recently. I'm impressed.
Ag is amazing. Thank you for such a useful tool. I don't have to use find + grep after using ag.

One thing I wish for is to cache the search result of a search term so that next search of the same term would be instant. This is good for large static file set.
The "called from C" case isn't the interesting one, even though it's what the grandparent mentioned. It's the "called from a scripting language" case. You can call Haskell or Ocaml or even Java code from within CPython or Matz Ruby. However, if you do this, you bring along an entirely different runtime system and memory layout. Usually this means that you face some very odd memory management bugs and lose any speed advantage you gain as soon as you have to marshal objects across the language boundary.
Any institution can fail at any time, given the right trigger. The difference between a stable institution and an unstable one is the range of triggers that will destabilize it. When the legitimacy of an institution is threatened, this can only broaden that range.

So you're right to point out that there is no "threshold" as stated by the OP, however the frenzy with which the US government is undermining its own legitimacy as well as that of many other Western governments, does not bode well for our civilization (Western or otherwise).
>A big problem with Rust right now is that the documentation is awful.

Wha? Steve has been putting a ton of effort into it and it shows... When is the last time you looked? If you're one of these people that wants to announce your opinion in every thread and remind us that you've said them before, it would be worthwhile to keep up with the evolving language.

How you can understand Rust's lifetime tracking requirements and not understand why "unsafe" is needed...

Just grep through std lib for usages of "unsafe" and see why it's needed.
In a perfect immutable system, I'm still going to want my code to be as DRY as possible, because I don't like typing the same thing over and over again.

In this perfect hypothetical world, you wouldn't eschew abstraction; you'd just know exactly what abstractions to use to perfectly model the problem you're solving. Those ideal abstractions would be different, since the problem is immutable.

Ask yourself this: in this perfect world, would you code with a magnetized needle and a steady hand? Why not?
In terms of enrolling and tracking children, didn't the Early Childhood Longitudinal Program tackle a lot of those same issues? They managed to track my brother between kindergarten and eight grade which for my family spanned three states over five moves.

http://nces.ed.gov/ecls/
> Any stock trader that uses linear graphs will lose his shirt.

Can you show me a stock trading platform that uses log values by default?

Yes, log graphs are very useful when you're looking at developments of stock values and many other financial variables - predominantly over longer terms when the changes are high enough that the difference matters.
I call BS.

The reason very few people care is that "works" is not a binary, but obviously a continium -- and people inherently understand diminishing returns...

Especially when the "works" they care about is getting shit done, by having access to software (including proprietary), drivers, a community, vendors, etc.

The "is formally verified" they could not care less, and rightly so, if their other demands are not satisfied...
I'm getting 7.21.3, reading here[1], but that's the draft spec for C11. I couldn't find the official one anyhere.

[1] http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1570.pdf
The Mi'kmaq were also very important to the extermination of the Beothuk. As was the common case across Canada, groups of indigenous people who were in earlier contact with European traders and colonists and who were better able to utilize iron tools and other European technology diligently set about exterminating any hereditary enemies in the vicinity. Read any early ethnographic account from Champlain on and you will find detailed reports of this.

The tale of indigenous extermination is not at all simple, and while European diseases certainly played a role, many other factors were also very important. One result of this was that some groups were wiped out almost immediately when Europeans entered the area, while others persisted and even thrived for some centuries after contact.

The most devastating effect of disease was likely in the West Coast groups, who left a large number of abandoned villages a few decades after first contact, where contact was very late (in the late 1700's) and colonization played a relatively small role in their destruction (the Interior groups were probably more strongly affected by colonization rather than disease, having had more contact with Eastern groups over the preceding centuries and therefore likely some immunity to disease.)
The creation of the ice trade is covered in entertaining detail in chapter 4 of Bill Bryson's At Home [1], including a story of how the first speculative shipload to London was held so long by Customs trying to figure out how to tax it, that most of it melted.

[1] http://www.amazon.com/At-Home-Short-History-Private/dp/07679...
In the current scenario, where the definition of 'Rust' changes on a daily basis, that's a major pain-point, but once Rust hits 1.0 then all future changes will be backwards-compatible (until version 2.0, in the distant future if ever), so it should be much less of an issue.

That said, it's definitely a thing the Cargo devs are thinking about: https://github.com/rust-lang/cargo/issues/1044
https://github.com/rust-lang/cargo/issues/837
7 years ago broke my back.Is now inspiration for my first iPhone game
Centaurs, Soviets, and Seltzer Seas: Mariner 2’s Venusian Adventure (1962)
I'm not sure that's true. The same kind of mechanical transformation that gives await/async also leads to Python-style generator functions, and I wind up using them all the time for all kinds of iteration tasks, not just I/O (or at least, not just async I/O).
I entered the job market at 19 years old in 1998.

I did what's now called DevOps, automating server and code deployment, monitoring, etc. I could do no wrong. Got promoted, ran a team before I could buy a drink. Got treated like a rockstar with every role I chose to take. People needed to scale and I knew how to do it without hiring a room full of network admins. Serious stock options. My compensation felt like it was following Moore's Law.

The startup I worked at failed. My friends, colleagues, former managers, almost entire network all got kicked to the curb around the same time. Recruiters dropped off the face of the earth. There was no one out there to reach out to.

I collected unemployment for a few months.

I ended up taking a basic IT admin job for a drug trial company at about 60% my salary. A friend of mine landed at a small business Windows IT consulting shop with a bonus structure I could kill, so I interviewed there. I ended up as a local field engineer driving around to different small business clients fixing windows desktops and printers, but with an extra hours bonus structure that had me back up to my previous salary in a couple of years.

In short, I went from a Unix/Linux rockstar to Windows network guy. Now I own my own language learning business and I'm back doing part time DevOps consulting (what's old is new again). I bill out at $225/hr because people want to scale again. It's nuts because just a few short years ago there wasn't a company on this earth that would touch me for $30/hr.

How does it relate to now? I just spent the past two weeks consulting at a couple of startups, including directly for a startup accelerator and wow, yeah. It's the same vibe.

I got back on my feet. Most of my friends did too. I had to fix Windows XP desktops for pipe supply companies and law firms for a while. I had to launch my own non-sexy business to really get out of it. Now my tech skill set and interest happened to be popular again, so I'm taking advantage of that and doing some consulting. I don't expect the tech stuff to last, so I prefer to look at my own small language business as my long-term gig. I don't trust this.

My advice... Industries go through ups and downs, so you will experience it at some point. I survived by becoming OK with helping businesses outside of the bubble. I built my own more or less non-tech business on the side that grew to where I can live off of that if I need to. I advise maintaining a good network across several industries. If the tech startups bubble pops, you can write code for industrial robot control panels or billing systems. Network in industries outside your comfort zone. My sister-in-law wrote systems on contract for a hotel. A friend of mine works on enterprise tax software for Mexican companies. If the bubble pops, have a diverse network to reach out to. The front door's going to be jammed with resumes from people like you, all at once.
It's a human emotion called jealousy.
The average speed on Netherlands bike paths is 8 MPH. The US runs around 20 MPH.

There are several videos of cycling in the Netherlands on YouTube. Most of them have been speeded up because they look so slow.
Interesting. I wasn't aware there was a choice between "learning enterprise" and (other?) in school nowadays. Back in my day, you'd come out with a solid foundation, equipped to make those choices. Hey, another perspective thing. Fancy that!

But, I'd say, yeah...get you some "enterprise" while you're there, especially if they're offering it for the same price. ;)

Glad you enjoyed my life story. Happy to share.
The earlier bust had a lot of fluff bursting from the bubble, but there were solid, growing companies as well. GoTo (later Overture, then a Yahoo purchase) was ramping up its pay-per-click ad model and several brick and mortar companies were still trying to gain a presence on the web, and were willing to pay for it. Google launched Adwords in October of 2000 and its growth since then needs no recap. Basically nascent companies that were ideas sans business plan fell by the way side, but there was still active investments being made and a growing ecosystem online. A lot of capital shifted into that ecosystem--track newspaper closures with Adwords' growth. Valuations took the biggest hit, but the work didn't.
Try out TexStudio (http://texstudio.sourceforge.net/). Free, open source, integrates with MikTex, ctrl-space autocompletion for bibtex entries, can easily switch build chain from latex-dvi-ps-pdf to xelatex-pdf or pdflatex or latex-dvipdf.
They'll hire you, exploit you, and then fire you when the funding dries up. Your "customers" will whine endlessly about every change you make, and every change you don't, and then cry out at having to pay more than nothing for your game. The industry mostly only has big publishing houses and captive studios left, and has bar none the very worst sort of customers you'll ever get--just go read through the user feedback on the Steam store.

Importantly this:

http://www.puppygames.net/blog/?p=1574

And this:

http://www.fdg2013.org/program/papers/paper06_zagal_etal.pdf

And this:

http://www.developereconomics.com/mobile-gaming-dirty-secret...

I would never in a million years recommend anybody entering the industry at this point unless they are making an independent game by themselves--and even then, only as a hobby.

If you want to learn something, keep it as a hobby. It'll be a lot of fun, you'll learn a lot, and maybe you'll even get to sell your project. But don't don't don't try to make a living from it.
Looks interesting! Will it be on Android too?
You really believe that just because their parents failed the children decided not to try for themselves? Perhaps it has more to do with seeing how their parents failed. Specifically since the article is geared towards men, maybe it speaks towards a generation (or few) of boys watching the system screw their fathers over.
I'm hoping NOT.

"a nice UX" is what killed the rest of usenet (google groups anyone?)
Sometimes when I hold down space the reindeer jumps reliably and sometimes it just doesn't... needs to be perfect in order for high scores.
Compare:

Non-logarithmic: https://upload.wikimedia.org/wikipedia/commons/0/01/United_S...

Apparent conclusion: Highest bracket is growing much faster than the others!

Logarithmic: https://upload.wikimedia.org/wikipedia/commons/archive/0/01/...

Correct conclusion: All the brackets are growing identically.

The scale actually matters a lot.
Styleshedding: bikeshedding on programming language style and declaring only a particular one true way is the only "universal correct" answer. (The tech equivalent of the Islamic State (because Godwins Law is deprecated since Nazis are now no longer the worst possible butchers to which to compare people.))

(Common sense from experience > style guides.)
I'm not sure I follow what you're saying exactly and you may have misinterpreted what I meant.

So you're saying if the ruse of creating dummy transactions is successful in attracting speculative interest[1] and driving up the price, that is no big deal because what attracted the speculative interest, the raw transaction count numbers, actually occurred in a kinda sorta way, if what those transaction numbers are often painted as, genuine utility, is not actually there, well then that's just like 'circular' man..., is that what you're saying?

Consider if a public company 'X,' conducted its finances in such a way that they set up a bunch of shell companies, transferred money to these companies in a non-visible way then had those shell companies send that money back to company X in exchange for some nominal goods or services. Then they repeated this process over and over such that the company's public filings showed a steady increase in revenue quarter after quarter, such an increase that they attracted considerable investor attention, resulting in a stock price that rose steadily on the back of these circular accounting tricks. As the stock continued to rise, the company's major stockholders cashed out their shares.

Would that be 'circular' or would that be illegal? Would that feel "fake" or feel like "an illusion" to you?

-

[1] Yes, we are talking speculative interest here, this is a metric that is more interesting to a speculative investor than a non-speculative user/'adopter,' a non-speculative user is just going to use it for what they are going to use it for if they have a genuine use beyond speculating.
Changes create new winners and losers.

At the time the crash was just starting to happen, I interviewed at Sun for a job in the Java compiler group.

Their office was just off the De Anza and 280 exit in Cupertino. They told me how their neighbor Apple hadn't been doing well,and how they were gradually taking over all the office space near them. The folks I interviewed with thought Apple would be history in a few years, and being a hardware company that was doing well, they would deal with the crash just fine. I believed them.

Apple made a complete comeback.
Sun went through many rounds of layoffs before it was swallowed by Oracle.

Luckily for me I ended up taking another job at a company that was one of the few to do relatively well during the crash.

Till this day I am grateful I did not take the Sun offer.