skysight-inc/HackerNews huggingface dataset:
yeah but that's the problem exactly with the article, which is that there is no incompatibility with automated, greenhoused, hi-tech, and sustainable, local, organic farming. They are compatible. Given that, local and organic (not the label, but the true meaning, which is things grown in living and decaying matter, not awash in chemicals and subsidized by non-renewable, fossil fuel based supplements) The argument is that conventional mass production farming is superior to local, hands-on, organic farming. I don't think this is true, but I know a lot of pretty deeply invested corporations that would like it to be true.
Welsh village adopts multinational tax tactics
Its actually worse. Only this Saturday I searched for a ice cream shop and it directed me 2.5 miles away. So now I am riding the prescribed route when I see a different branch of the same shop in 0.6 miles. Baffled I looked again at the search results and for some reason this nearest branch was listed at number 5 and I had to scroll down to find it. This when I had GPS and 3G on.
People asking questions, lost in confusion
Well, I tell them there's no problem, only solutions
- John Lennon

The other solutions proposed here work at the wrong level. The approach taken by I2P[1] does away with the concept of globally squattable names[2], leaving public keys as the global identifiers and letting individuals define local nicknames or delegate to trusted lists.

[1] https://geti2p.net/en/docs/naming

[2] Even http://www.aaronsw.com/weblog/squarezooko is susceptible to squatting by those who can invest (or rent) computing power.

PS: I had a chance recently to talk with a "DNSquatter": the doorman at a building I frequent. Poor guy bought tens of thousands of domain names, years ago, with money he had available for investment, and asked me for advice on how to cash out his investment. It seems to me that he's the victim of a chumpatron[3], rather than the scammer himself; although his actions do help keep the scam alive. I advised him to consider the money lost.

[3] http://www.loper-os.org/?p=1446
Answering my own question, the sidebar on the right says:

> Shining Rock Software has only a single developer doing all the software development, artwork, and audio.

I'm blown away. Really cool.
Google Maps to provide offline navigation
Harvesting Spider Silk
C and C++ have both passed the threshold of immortality. There's so many billions of lines of code in both those languages that the likelihood of either of them ever disappearing is very slim.

The question is about new development, and to what extent C and C++ are evolutionary dead ends. Nobody would design a language like C today, would they? They'd be laughed at.
Depressing to read. Somehow I can not find a language I really like :-(
Agree. The unstated conclusion is nothing is close to being a C replacement. A good analysis of the languages anyway.
I went the other way: last year I converted an OS X app to Windows. I hadn't used Windows for six years, and had forgotten most things.

It took two weeks to get the code compiling and running. That turned out to be the easy part. Getting the application performing well, feeling "native", and getting the bug count down took another six months.

I love Banished and I'd like to see a completed OS X port. But I'm not expecting this to be done, like, tomorrow!
Labels is something that's tricky to implement on top of our IMAP-standards-folders-based server, but we have some ideas on how to do it. Sort unread to the top is easy on desktop interface, though there's no UI to do it on mobile.

search is:unseen works nicely to find them on mobile as well, and you can save it to your sidebar/folders list.
It's indeed not a nice situation, I'd love for my mailserver to insert a line into the message subject something like: 'TLS not used' when this is the case (or a plugin for Roundcube (Next?) that colors the subject, how cool would that be?). Just so I know and are aware of suspicious things. Enforcing TLS (and valid certs + strong encryption) is just not very practical yet, although it will definitely not affect mayor players' connectivity (Google, Apple, MS). Still, a lot of problems will arise, to see how many exactly, this is a rough indicator: http://www.google.com/transparencyreport/saferemail/

I predict in my group of friends I can receive/sent from/to almost everyone if I would enfore TLS on my server. Except to/from that one guy that is savvy enough to have his own domain but hosts his email at a cheap, crappy provider.
Sounds like someone needs to rigorously define a good subset then write a tool to verify that a program uses only that subset.
Off topic...

Text after a blank line that is indented by two or more spaces is reproduced verbatim. (This is intended for code.)

Is this what you've done here? Because it makes the text annoying as buggery to read because of the horizontal scroll bar. The feature is intended to not line-break code.

Better to use asterisks to italicized.
The first problem is pigeon-holing it as a blogging platform that you have to bolt stuff onto. There's a lot more to WordPress than blogging these days. The origins are still there, sure, but fewer and fewer sites these days are using that as a starting place.

> On the funny end of the scale, I've seen five page static websites with a landing page, a few info pages and a form done with WP. Unbelievable. Are developers that lazy today that they throw WP at everything?

I see some version of this question all the time. The main problem is that you're thinking about it from a development perspective only. The major thing WordPress brings to the table is democratization of publishing from the user perspective. You see a five page site some dev built and wonder where the benefit is. The benefit is that the actual owner of the site, the "user" can easily control, modify, add-on-to, or remove that content. They can easily turn it into a 10-page site if they want to.

With some of these other less user-friendly systems (such as static site generators), control largely rests in the hands of developers, with WordPress, it rests with the content owners.
hi from over in twitterland :)
Because a large portion of massive security holes in recent history have been due to archaic C libraries that have security holes a-plenty. A lot of these issues that plague C don't happen in modern languages.

It's 43 years old (times have changed), and while I'm sure C still has its places, I think it's time to come to terms with the fact that people suck at handling memory manually and making sure type conversions are safe & a host of other security risks.

Other, safer languages can accomplish many of the same things C does these days.

Again, I'm not calling for the end of C, but in a lot of situations, it's just asking for it now.
(def mymap {"asd" 1 "qwe" 2 "rtz" 3 "foo" 4 "bar" 5 "quz" 6 "bnm" 7})

(let [ints (->> (filter (comp odd? count key) mymap)
(sort-by (comp int last first))
(map (fn [[s i]]
(+ (count s) i))))]
(reduce + 0 (map * ints (reverse ints))))

Gives me 341
The registration fees are very low and they're a yearly fee which doesn't make that a big burden.

>"keeping desirable domains available"

Eh, they're more like keeping the domains and selling them to the highest bidder. You're defining the "really really want" here as the entity with the biggest pocket. Domains cost so little for a reason, so everyone can afford them but obviously some people abuse this and it's why we need more oversight. IMO of course.
Well, one of those things is not like the others.

Golang competes more with gc languages/runtimes like Python/Ruby/Nodejs. To a lesser extent it may compete with Java JVM. (However at this point in time, the JVM GC technology is still far ahead of Go's GC.) If one is writing a networkish service such as REST API endpoint, Golang's combination of language featurs & quality libraries (http) is positioned very well for that. Go isn't suited for system drivers or tight loops that depend on controlling exact memory layouts. I've heard several times to think of Golang as a "DSL for networking apps" and I think it's the best succinct soundbite for that language.

That leaves D-minus-the-gc and Rust which Andrei Alexandrescu provided very reasonable analysis. I don't think either will replace C. In 1995, many predicted that Java would supplant C++ and that never happened. For the performance domains that C++ was good at (e.g. AAA games, commercial software like AutoCAD and MS Office), it became even more entrenched. In terms of being forced to make bets, I'd say Rust has a better chance than D because Rust has the momentum behind it that D never had.
XCode reference finding doesn't work fantastically for me. When I look for a symbol it puts in some strange characters that might be wildcards, but doesn't change the search mode. Means I end up doing string search most of the time.

VS is okay, not perfect. But I'd say it's better than searching for strings when you really want a type or function.
Isn't the verbosity all about job security? ;)

http://harmful.cat-v.org/software/c++/I_did_it_for_you_all
One reason I've heard is, that it;s still possible to get caries below the the sealing but the dentist (or you yourself) won't be able to see it by a purely visual inspection.

At least here (Germany) you won't get an x-ray at every checkup.
Google Updates Its Container Services
They'd only be laughed at because they were accidentally recreating C and it'd be easier to just use C. C itself is a great language doing the job it was made for very well.
What a fantastic, thoughtful post. If anyone is skipping to the comments here based on the title, you should read the article, not least because it's by Andrei Alexandrescu.
You're right. It keeps on giving us heartbleed, slammer, sasser, kernel null check eliding holes, and literally thousands upon thousands of other memory exploiting, remote executing, security breaking bugs.

But I'm sure, Real Soon Now(TM), if teams just adopt (best practices / better libraries / better code reviews / better static analysis tools / better testing) all those problems will be solved and C will be a great language to keep using.

After all, saving a few extra CPU cycles is totally worth breaking all SSL encryption and leaking private keys, quite literally putting the security of EVERY SINGLE FUCKING HUMAN WHO HAS EVER TOUCHED THE INTERNET in jeopardy.

So sure, let's just keep using C. It's fine, why change anything amirite?

(Sarcasm aside: In the general case it is not possible for humans to write security-critical code in C. So far the history of the internet has proven me 100% correct.)
Not really. One of the major parts of the OSX port is opengl support which he has been working on since at least March. http://www.shiningrocksoftware.com/2015-03-14-porting-opengl...
It was slightly tongue in cheek - C is good at what it does, but I agree that there are plenty of good options going forward.

I just don't think C will be 'replaced' across the board though, but I suppose that's obvious.

Of the languages mentioned, I've only got experience with Go (which I use for APIs). Rust looks interesting though, I need to have a proper look at it.
Since the NSA increasingly knows everything about everyone, it is only a question of time until they will be able to blackmail just about anyone. How politicians, who are naturally especially vulnerable in that department, can let this cancer grow unchecked, is beyond me.
Will recommend fastmail.
"do more damage"

sorry, that's the claim that is not substantiated by evidence and it isn't close to being accurate. Conventional farming is a toxic mess, and it's heavily subsidized by unsustainable resources and practices at every level. It may be the case that the cost of doing farming right is high (and that is not necessarily meeting the "organic" standards which are themselves heavily biased by conventional interests, but by farming using truly organic methods) but that's because it tends to include costs to the planet, or not include cost savings that are causing extinction level changes to the planetary chemistry. There are people who will tell you that sustaining our population is not possible and that we are headed for an extinction event, however other people say that it is possible to live within our means, if we start factoring in the real cost of things like conventional farming, and therefore change our practice.

And technology is definitely a factor in that transition, so if you buy the phony trolling argument going on here that greenhouses, and automation is incompatible with sustainable, organic, local farming practice, then you are being sold a bill o' goods!
If you can see a DNS request going out and can send a fake response that arrives before the real one, you have enough resources to pull off a MITM.
We won't come out "better". We'll have made a trade-off. For some situations, it will have been a trade-off that benefits. For others, it will have been the wrong choice.

Just use the right tool for the job given the circumstances.
If C++ couldn't do it, D won't. They are of the same ilk.

Go kinda is already, but is too sucky on too many levels to really break through.

Rust is still alpha and seems to be going backwards at times, but looks like a strong contender.

Assuming Go fixes its many problems, and Rust is eventually delivered, I think they will both have a strong role to play, Go in the networking/systems space, Rust in the large scale app development space (like making a browser).

But C will still be around.
Surely that means they are topological maps?
The real question is that if the CEO somehow knew for certain that cutting the soda would allow him to earn that 21,800,000 but keeping the soda would boost productivity earning him 22,500,000 instead, would he cut it anyway because that's just the way things should be done?
The Blockchain Explained with Cake
Domain names can only be rented from the domain authority.
They can never be sold, just released back to the authority when finished with.
> the catastrophic career-ending political fallout from a major terrorist attack

Any rational person would consider preventing a major terrorist attack far more important than keeping their job for four years. People with the opposite motivation do exist, but generally I'd consider them pretty close to evil. Someone like that would probably have had a different 2 terms to Obama, in my opinion.
Again, the evidence of this is rather slim. It's basically impossible to create safe, code in C as evidenced by the fact that nobody has every managed it.

You're making the mistake of assuming that because you know something really well, that makes it good.
As if by magic....

https://isocpp.org/blog/2015/09/bjarne-stroustrup-announces-...
I am working as a software engineer in Sydney too.

There have been many times people forget to pay, or they pay less than they owe, or they low ball a salary offer. I've found by sending a friendly reminder their payment didn't go through, or they sent a wrong amount or insist you're worth what you're worth, and usually I get what I'm supposed to. But on the other hand, when stuff like that happens and if I choose to not speak up, then I'd lose out. By the way, your programming skills are a lot more valuable to people trying to start a business involving technology but don't have any technology skills themselves. People who know programming already are quite cheap in terms of what they offer for work. I started at a low rate freelancing $25 per hour, and as I improved my skills and my sales ability, I increased the rate to $100+ over a period of 5 years. Now that I've graduated I work in a fairly paid full time job. Make lots of money for your customers and you'll make lots of money yourself.
I suspect it'll end like this: http://xkcd.com/927/
Attach a PDF?
The whole article is a little spurious. None of the languages mentioned (C, C++, D, Go, Rust) target exactly the same space (even though they all overlap).

Go and Rust in particular have been designed with very specific clients in mind (replacing Google's use of Python for server-side work and safety-paranoid multi-threading for Mozilla's Servo, respectively).

Rust is the only new language mentioned that resembles C in its capabilities but then again: C++ resembles C in (theoretical) capabilities but never de-throned C (mostly because when you use C++ like C, you might as well use C).
I have a free GApps account, but I ditched it in favour of FastMail - primarily to extract at least some of my life from the Google juggernaut, and also to support the little Aussie battlers. Thanks for offering an awesome, rock solid service, and supporting Open Source so well.

I'm seriously looking forward to JMAP, I hope some other big services adopt it when it stabilizes. Give your JMAP dev(s) a hug from me, please!

Oh, and I hope the DDOS doesn't cost too much - any chance we could have a blog post about the costs of the DDOS attack after it's all over? I know most companies don't like talking about operational costs, and I'll understand if you guys are the same. Cheers!
I've been using XCode daily since version 3 and I still miss VS. XCode (IMO) is a festival of UX badness - can't change positions of navigator windows, can't change fonts/colors outside of source/console, the 'assistant' window (or whatever it's called this week) frequently opens up unexpected or unrelated files, refuses to stop trying to automatically balance square brackets, spews truncated errors and warnings over the top of code then shows a tiny version in a mouseover for about 3 seconds before hiding it, truncates said warnings in the issue navigator, tiny fonts almost everywhere, severe weirdness with variable inspection and no integrated 'watch' in the debugger - which likes to show disassembley even when you ask it not to.

Lack of refactoring support for Swift is currently baking my noodle, as is the lack of a supported plugin API (with which I could solve many of my own problems). Very crashy.

All that being said, it has a lot of good stuff. The analysis and profiling tools are great, there's a bunch of really powerful tools for games and 3D, view debugging is a thing now, the UI builder is super powerful (once you get used to it) and the unit/performance/UI testing tools are (IMO) pretty awesome. Lately integration with all things App Store (provisioning, entitlements, etc) has got a lot better and most of my pain points there have gone away.

It's hugely subjective though, some people would disagree with much of this. Like any IDE, you end up in a love/hate relationship. The main difference being that if you hate VS you can hit up the extensibility API and make your pain go away, whereas Apple don't really care if you hate them.*

*I'm aware of Alcatraz and it's neat, I'm just not quite sure I want to introduce unsupported hackery into my production environment.
Every one of those problems you mentioned occurred in C code, not C++. That might seem like quibbling, but many of those bugs are caused by C memory management bullshit like malloc(that) if (error) goto: free(that), which isn't a problem that C++ has. A scratch reimplementation of OpenSSL in C++ would probably be 1/3rd the lines of code and entirely devoid of both goto and malloc.
Interestingly OYO is selling all rooms at a loss. In an effort to build demand side market share.

A room on OYO that costs approx Rs. 1000 is purchased on a guaranteed basis from the hotel at Rs. 1500.
Except that for historical reasons, js is a very rushed/badly designed language. More precisely it mixes moment of brillance and very stupid design choices.

Ruby, Python, Lua are in term of language design way superior. Coffeescript and co emerges because it was more reliable to have a complex stack than to use the JS language directly.

That's the only high-level language that produced this situation. Python/Ruby & co are not perfect but good/reliable enough. You don't program in a another language that compile to python to avoid its verbosity and its traps.

If python had been choosen for the browser, we would have used for the last 15 years : module, sane scoping rule, classes, iterators, etc. Yep, that's something that it ecma6 without the ugly baggage.

15 years, damn it.

So no, please give at least Python in the browser and let people experiments with other language design choices and let them find something superior to Python. At one moment, it will be obsolete like any other tool. I don't want to be forced to use it because it is the only choice.
local, organic, small-scale farming is certainly practical, and it's also imperative for a sustainable model to support our immense population. So is automation, and greenhouses, and transporting food from far away places. What is incompatible with a sustainable future is conventional, factory farming, where the fields are awash in toxic chemicals, pesticides, herbicides, fungicides, and supplemented with bare fertilizers manufactured using toxic processes out of fossil fuels or harvested from unsustainable sources. That can't go on. Fortunately organic holistic farming methods produce higher yield and healthier foods, and are compatible with the best and highest tech in automation, greenhouses, and etc, and increasingly the old and new tech is coming together on the small scale, local farm.
Rust isn't alpha anymore.
Seems like a good opportunity for a company that genuinely cares about employee health to make it easier for them to eat well by stocking the kitchen with healthy snacks.
I bet the soda cut was more about keeping up the appearance of doing something. His compensation is probably more directly affected by his perceived effectiveness than from the subtle productivity benefits more soda would bring.
Try Here maps. This is the old Nokia maps now owned by Android. I use this as my go-to for driving. It's much better interface and route selection is as good as Maps. Also I love the GPS speedo and speed warning. I tend to use Maps for location based searches like restaurants for the better reviews.
> "There's an old saying where they say the goal is to pluck the feathers from the bird with the least amount of squawking," said Chamberlain. The less visible the cuts, the better—even if it means taking money out of employee pockets. "Changes to contributions to employee retirement plans," he suggested as a less disruptive cut than emptying the snack larder. "These are highly obscure from a worker standpoint."

That's some cold shit right there.
There is a slightly disingenuity here. "a large portion of massive security holes in recent history have been due to archaic libraries that have security holes a-plenty".

The fact they are also C libraries is because that was the only real option of the time when they were written; rather like saying most car accidents were caused by black ones when the only option was a model T.
The article clarifies the issues that exist with SMTP encryption nicely.

Regarding the issue with certificates for the servers that the MX points to, I disagree with the author.
If the MX for example.com points to mail.example.info, it implies that example.com trusting the handling of its mail to mail.example.info, therefore there is no issue with letting mail.example.info present its own certificate.

The article also suggests that DNSSEC with DANE will solve all issues with SMTP encryption.

However, DNSSEC is a crappy standard. It doesn't do encryption so a surveillant can still collect metadata; it has unsolved issues that facilitate amplification attacks, it's overly complex and has slow adoption.
In fact, before DANE arrived on the scene, there was hardly a good reason to deploy it.

If we adopt DNSSEC now we'll be stuck with it (including its lack of privacy) pretty much forever. Instead, I suggest we work on more promising initiatives such as DNSCurve (https://en.wikipedia.org/wiki/DNSCurve)