skysight-inc/HackerNews huggingface dataset:
So, one of the reasons why people like syntax standardization in the form of formats like s-expressions, JSON, XML, et al. is that the parsers are already there and you can just load them in, do some processing, and emit a transformed version.

But when developers go to write their own configuration format they often lean towards a custom syntax so that the end-user, who is expected to be a human being with a text editor, has a more comfortable working environment. And the resulting syntax is write-only, with comments, syntax sugars, etc. that would make it hard to impossible to automate data manipulations and also emit a document that resembled the original.

Tooling like this carves back a mix of both worlds - because it's just operating on the parse tree, it doesn't convey the final meaning of the data as it would be used by the thing being configured, just the "look" of it as a human would read it - but that's still enough to get an automation job done, for most kinds of job.

If you are a developer who wants to ease this job for your own configuration formats, of course, there are plenty of ways to go about this - provide more config formats, or your own extracted parse tree, a scripting API, or the ability to change parameters live. But for pretty much any solution, there is an engineering tax to be paid, and often a new surface area for security risk. So nobody goes about this stuff the same way, and many projects just never really solve it. Hence we end up with a third party like Augeas that comes in to fill the gaps.

My own policy tends to be to start with an XML format and then add a custom syntax to it later as necessary. The initial parsing job becomes straightforward with little chance of catastrophic error, and subsequent custom syntax can emit XML, so you get a twofer on the development time. The downside is basically that XML is a pretty big dependency and nobody is happy with it as a primary UI.
Huge amount of VC funding during the dot-com bubble, not from any actual profits.
This is what I hate about Starbucks, and the fact that it's pretty much the only place I can go to work / get out of the house when the library isn't open.
...particularly when a self-driving Tesla slams into it!
As it was mentioned in another comment, you either leave out Safari or Edge, since there is no OS where both are available. Obviously, in order to obtain a meaningful comparison, you need to run all your tests on same OS and same HW specs.
If it's not wrong for being illegal, I wouldn't argue that law abiding hotels especially deserve to stay in business.
His arguments are still sound, I think, and until that post I'd assumed that avoiding unstructured flow of control was still received wisdom. (I've certainly found it a very sound policy; million-plus-line codebases of other people's code, plus surprises, equal misery.)

Joel Spolsky had much the same to say: http://www.joelonsoftware.com/items/2003/10/13.html . If I'm going to have to argue about this, I'd rather use Spolsky than Dijkstra as a starting point; what, if anything, do you see that's wrong in his article?
If you mean anything more specific than "we do stuff for the government we can't tell you about", probably not. Look at Boeing, Northop-Grumman, Booz Allen Hamilton, etc.

Hell, for that matter, look at AT&T, Verizon, and Level3 -- the companies that we didn't really expect to be doing the kinds of things they were doing.
Much of the complexity is likely in building and managing such a large botnet.

There also isn't a lot of details here on the exact nature of the traffic. They say it was hard to distinguish between legitimate traffic and this malicious traffic. So the botnet is at least rotating their requests through lists of customers hosted with them (though that isn't complex, but it is forward thinking. If the botnet was all making non-stop requests for just a few domains, that would be a strong signal to start filtering traffic, first internally, then pushing ISPs to block it upstream).
> and a DC1.8XL costs $4800/hour to "compute" the data.

Is this a typo? A single DC1.8XL is $4.80/hour. 8, like the article, would be $38.40/hour.
I think you dozed off there...
Makes sense. And thanks for your persistent questioning, I learned some new stuff!
My girlfriend also told me to stop talking about Tesla. She would actually get angry when I started talking about Tesla news :(
Pretty much. Airliners have actually gotten slower since the 1960s because it saves a nontrivial amount of fuel.

That said, there probably is a market for supersonic commercial aircraft. The problem is it's not large enough to develop the hardware. When Boeing or Airbus comes out with a new subsonic mid-sized widebody they're expecting to sell thousands to the commercial market, plus an air freight version, plus tanker variants for military use.
Creating Laws for Computer Security
CBS' "60 Minutes" did a story on him that was itself entitled "Patient Zero":
http://www.cbsnews.com/videos/patient-zero/
iPhone 7s or maybe iPhone 10 will ship around September 20th 2017.
As stated, on demand pricing was used. Both products have special pricing at higher usages and flat-pricing tiers. It would start to get compilicated to compare them at that point.

Numbers on https://aws.amazon.com/redshift/pricing/ used.

dc1.8xlarge - $4.800 per Hour
A Comprehensive Guide to Debugging Optimized X64 Assembly
So 4B for a selling stickers business model?
The API seems bad to me, the ioctl() is ridiculously overloaded (disconnect, connect, read, and write all go through ioctl(), for example). As an API, this doesn't pass Linus' "good taste" test. As a solution, it's more complicated than necessary.

On messaging in general: this is yet another IPC api from RedHat. They really want to get an IPC api into the kernel over there. However, their proposals seem 'ignorant,' in the sense that plenty of IPC research and work has been done over the last half century (or more?), and their proposals seems focused on their own small use cases. They seem unaware of how others have tried to solve the IPC problem.

On why Linus doesn't want to integrate it: no kernel team is going to want to have yet another poorly-designed IPC stack to maintain even though hardly anyone uses it. That's been done, and IPC in Unix is a mess as a result. Any sane kernel dev would be resistant to this, unless the new proposal is absolutely beautiful, and you can look at it and say, "yeah, that is really great."

RedHat should go out, investigate the research that has been done, become experts on the topic. Learn everyone's IPC problems, not just they problems they have in their own insular community. Only then create an API that actually is in good taste.

Then begin the political work of getting people to adopt it. Start with the BSD teams. Start with the hobbyist OS devs at osdev.org. When the whole world agrees that it is a good thing, then Linus will put it in the kernel too.
A desktop with a rear camera? Interesting...
Affordable housing > low hotel prices. In Traverse City, Michigan we are facing a drought of affordable housing. Low rent spare rooms are being rented out on AirBNB et. al. for more money and because of that those rooms aren't available for service workers and students. The most unwelcome side effect of this is that several businesses could not open this year for lack of labor and many others operated below capacity for the same reason.
> Kylin was the Chinese FreeBSD fork (if you can even call it that) started in 2001.

Oh, wow, that was a while ago. I can see why they picked FreeBSD, Linux wasn't really all-around usable back then. Did it even have any security capabilities?

> This predates the privsep OpenSSH, W^X, chroot Apache, and all that. pf wasn't even released until the end of 2001.

Ha.

> There was no support for SMP until 2004, and even now it's far behind everything else.

The SMP thing confuses me to bits. I was talking to the author of MirBSD a little while ago, and couldn't fathom why "no SMP" was a feature (although since MirOS was decented from OpenBSD, maybe it's related to how OpenBSD's SMP is "far behind anything else" as you describe). In any case, SMP is kind of important, if you want to be commercially viable and considered real...

Maybe these are toy UNIXen. Which is totally fine, our brains need a chance to zone out and have delineated spaces to play in that are free of responsibility so we can mess around and learn, but still. Maybe throw in some parodies or something, so that's clear.

> It's not surprising. OpenBSD isn't suitable for a lot of server tasks now let alone back then.

Hmm.

I feel like I'm missing a lot of context here, I wish there was some way I could just go get all the history of it all...

(I discovered Linux in 2006, started running it properly in 08, have felt out of place w/ UNIX ever since)
> Your "smart TV" or "Smart refridgerator" all contributed to this, over YOUR bandwdith.

Makes me wonder when we'll start seeing reports of people getting hit with data overage charges because of hacked smart devices. I only have 4 Mbps up, but if an infected device used all of that 24/7 it would chew through my Comcast 1TB monthly cap.
Model 3 is going to cost $35k, and like $28k after incentives. It will SAVE about $1500/year on gas and $500 on maintenance. This is cheaper than a Honda Civic.

Are you sure you aren't interested at this price?
Yep, I used it heavily three or four years ago for the same thing -- system configuration files on RHEL boxes -- when I was first getting involved with and deploying puppet.

Nowadays, though, I primarily use Ansible and its core "lineinfile" module gives me pretty much the same end result.
>I often wonder what kids can dream of, today, given all of this happened.

Holodeck-type VR, I'm guessing.
To be honest, all metro style apps have the problems you described. Also, there are minor oddities that bug me. For example, while switching desktops, the edge window will appear blank for a split second before filling up with the content. This happens every time. I don't think it has anything to do with memory.
Writing any code is fraught with risk, but writing a parser in a modern and reasonably safe language is not something to be greatly feared. It's more likely that you'll introduce a security issue in what you do with the JSON immediately after you parse it.
Not just that they mentioned that they could push that to a million cars annually but that it would be very unwise/taxing for them.
Also, not sure if this is still the case, but Docker's daemon ran as root on the host. Any vulnerability has the potential to give root on the host machine to an attacker. I don't think this has ever happened, but rkt's approach of using a process per container just makes much more sense in a security context (and for containerization in general).
Nice resource

https://react.rocks/
Do you have a partner or children to account for when working while travelling?
"White goods" is a British English phrase for major household appliances (fridge/freezer, washing machine, tumble dryer etc). "White appliances" seems to be a slight corruption of that.

White goods don't have to be white, but it is still the most common colour.
Have to take HN anti-parser comments with a grain of salt.

I wrote a parser for a format that everyone here would crucify me for. When I went on the job market, I removed it from my github, fearing employers would see it as a black mark. Soon after I got email from the creator of a YUUUGE project (as in, 5 digits of stars on github) asking why I had removed this parser that they were using ...
The AI Conversation Has Exploded This Decade with Big Advances
It is passive. The revnue quoted is not sustained by the regular work. That I put into the service. As I stated, if I stopped working then that income would stay, and be considered passive.
There is a section that says customer deposits.
I thought that's where the Model 3 Deposits and pending order deposits went.
>All the major browsers perform well enough for the great majority of users.

I guess I'm in the minority then. Firefox is markedly slow in rendering and navigating large pages. Even searching inside the page is slow. Chrome doesn't even notice a difference. Edge is similarly indifferent to the page size, but it's buggy as hell in general.

It's infuriating that after all these years Firefox is still so much behind on basic performance.
All the time. Customer service is handled by the sellers directly.
Here you go: https://developer.apple.com/library/content/documentation/Ma...

It is higher level, though, it is not something you would integrate into the kernel (like bus1 intends to be). OSX has decent IPC though, since it is based on the Mach research kernel from CMU, which was kind of based around the concept of messaging to begin with.

Applescript has interesting IPC concepts as well.
Windows Internals:
https://technet.microsoft.com/en-us/sysinternals/bb963901.as...
That's my favorite setup too. I have made really good friends that way.
since edge has gotten lastpass and adblock, I have been using it more and more. I haven't noticed pages looking fuzzy. it seems to work well but the fact that you can't right click and search in a new tab is frustrating.
Absolutely blame the people who are renting out their apartments. Bring it up at the association meeting. I'm in favor of AirBNB but rules within the building you own is legit.
Me too. Never seen an error.
> $4.800 per Hour

That's four point eight dollars, not four thousand eight hundred.
> If Spotify's networks are all down, what good would a functioning DNS do?

Email would still work. You can't receive email if the sending server can't look up your MX records. Since spotify.com uses Google Apps, their email would survive a total network outage if they used third-party DNS.
Heaps of people in NYC live in buildings without a doorman without being viciously murdered.
You can't really send a different double-spend to each miner. In my experience, the transaction will be propagated in 1-3 seconds. Each miner will pick the one it prefers (some prefer first seen, some prefer highest fee)
>
There's a tiny ISP (US Internet) in Minneapolis that's already wired half of the city with fiber with some loans as capital, they're not a public company and they don't have billions in CoH and they still figured it out. They've already started offering 10Gbps to home users. Yes, ten gigabits, that's not a typo. And they're profitable.

That's not entirely correct they have about a quarter of the city wired with plans to finish in 6 or 7 years[1]. The linked image is pretty small but it's all I can find. Note the linked map only shows 40% or so of Minneapolis. Also they have been providing Business services like dark fiber for the last 20 years, so it's not like they are completely dependent on home fiber income or new to the business.

I just recently got US Internet fiber, we have the 100 Mbps plan for $39.95 a month and it's great! I noticed that when I ping 8.8.8.8 latency went down from 33ms to 22ms. Also we have more bandwidth and cheaper internet than when we had Comcast. Of course the best part of US Internet is not having to deal with Comcast anymore!

Finally US Internet forced Century Link and Comcast to launch their own fiber services[2].

[1] https://fiber.usinternet.com/wp-content/uploads/2014/08/Scre...

[2] http://www.fiercetelecom.com/telecom/comcast-fires-back-at-c...
I don't understand how you calculated how much it costs to compute on the Redshift cluster. $1100 would be ~28 hours of the 8-node cluster.
Elastic Stack 5.0 released
When changing configs, the unit of change is often less than a file.

Using diff/patch and things like Ansible's lineinfile can apply the change, but the result is not guaranteed to be semantically or even syntactically valid.

With Augeas, it is going to be valid.

Also the big promise with a tool like this is that changes are bidirectional.
See the Boomerang project for more on this. http://www.seas.upenn.edu/~harmony/

My own experience with Augeas has been mixed.
It's quite prickly and uninformative in use and probably unintuitive to many. For example augtool by default handles the entire tree of config files. So if you just want to change maybe /etc/fstab you might encounter errors on files that you don't care about. Also I've often found that the lenses aren't quite complete, at least in standard distributions. For instance, the Centos6 Augeas's (version 1.0.0) xml lens didn't handle PCDATA or the DOCTYPE declaration.

Luckily its improving and more examples are becoming available.
Both are correct, one is considered better based on a subjective assessment. People who disagree with that the version a person selects is objectively better have no taste.
There's also this:

http://gizmodo.com/these-little-electric-wheels-will-save-ai...
You're math is wrong - DC1.8XL costs $4.80 per hour, not $4800 (which would be ridiculous pricing).

8 instances of DC1.8XL = $38.4 which means you can run the redshift cluster for 28 hours (edit: for $1100, which is the cost of scanning 220TB of data with BQ, used in previous comment).

Redshift does win on price when you are continuously running queries and scanning entire datasets, although there is enterprise pricing available for BQ if you hit a certain amount.
Is this filling a void in the current venture space...?
We're also never building the same software (or at least very rarely). The industry is such that we're always trying to invent something new, something that hasn't been done before.

If you build the same (or near same) piece of software 100 times, you can know almost exactly how long it'll take and you can do it quickly, same as if you were building 100 buildings. But we don't do that, because you build software once then just copy it 100 times.

You only build software if you're making something new that hasn't been made before.
http://longbets.org/
Fixed! Used to seeing 4.800 being 4800 apologies!
Kakao's business model history is actually rather fascinating, and they keep grabbing sizeable market shares in unlikely or previously inexpressive markets to great success.

> In 2012, KakaoTalk's $42 million revenue is broken down to 67.5% ($31.1M) gaming, 26.2% ($12.1M) advertising, and 6.3% ($2.8M) emoticon sales. [1]

[1] https://en.wikipedia.org/wiki/KakaoTalk#Company_Business_Mod...
If you come here, CA taxpayers will pay a fortune to host you, if you play the system right.

For a specific example, for one local government (I think San Jose or could be Santa Clara County -- check the article[0]), 2800 chronic homeless cost taxpayers $83,000 per year EACH in "homeless services" alone. (That's not counting state aid such as welfare, SSI, Medi-Cal, etc.)

[0] San Jose Mercury 8/15/2015, page B1, "Rolling dice on homeless"
Hmm. Yeah, it definitely would have been. All I can say is - I was frustrated with the way someone functioned, and rather than patch it, I "fixed" it. Where "fixed" is less complete and stable and...

Well, I also wanted a YAML parser, and had the weird need to handle JSON inside XML (oh, industrial sector, and your SOAP), and to not care about things like trailing commas, and then at some point to deal with weirdly large amounts of data.

Each iteration only took a couple of days, and I learned a bunch about tokenizing things, and then dealing with token streams.
Australian desert telescope views sky in radio technicolour
I run BitPixels (http://www.bitpixels.com) that provides automated website thumbnails. I purchased Bitpixels from another HN member a few years ago and have continued to build and market it.

BitPixels currently makes ~$1k/month which is enough to cover the App Engine and DigitalOcean bills plus a bit extra. I'm working to find 1-2 more marketing channels that can drive sustainable growth.
I don't have much of an opinion on how good this particular proposal is, but it is important to have a sensible IPC system for Linux. I see a lot of resistance to this, with claims that Unix sockets and POSIX are good enough. As the maintainer of Rust's ipc-channel, which wraps all this stuff, I strongly disagree. The complexity of the Linux implementation of ipc-channel [1] has been absurd compared to the Mac implementation, which uses Mach [2]. Don't let the similar lines-of-code count fool you—90% of the bugs that I've seen go by have been in the POSIX backend, necessitating things like manual fragmentation to get around size limits in the kernel, weird structure alignment rules in the cmsg API, file descriptor limits, ENOBUFS stuff, etc. etc. By contrast, the Mach implementation has more or less "just worked".

At this point I don't really care what the Linux kernel decides on, as long as it decides on something. kdbus or Binder or anything would have been fine; the people who are truly hurt by kernel politics are us developers.

[1]: https://github.com/servo/ipc-channel/blob/master/src/platfor...

[2]: https://github.com/servo/ipc-channel/blob/master/src/platfor...
Did Apple buy Pixar?
I thought my point was clear - don't get involved parsing JSON; I agree with the OP, parsing JSON is a minefield. I went further by implying that it is also unnecessary when ease of reading isn't needed, and called out some alternatives. I think it's amusing that you mentioned protocol buffers - were you aware that when I mentioned flat buffers that they were built in relation to performance inefficiencies in the very protocol buffers that you mentioned?

We didn't just "hackathoned the biggest thing since sliced bread", btw, we took a real world example of exchanging a human readable format for a human-with-tools-readable one and saw a significant win. High-bandwidth also isn't as prevalent as you think, and yes, you're generally paying both performance wise and occasionally monetarily for the laziness you mentioned. But then, if you've known this for 40 years and don't know how to measure it, there's not much I can do for you in a comment.
The Next Generation Wearable: Aladdin Lucid Dreaming Stimulator
Completely correct! I apologize, used to seeing a different notation and the extra 0 in 4.800 threw me off. I removed the misleading data because judging by the points, not everyone caught it.
Cheers! https://www.youtube.com/watch?v=nWoWHzq21tA
He is taking the party in a different direction -- one that favors the working class over Wall Street. Meg Whitman a Republican who ran for governor of California and Head of HP said Trump would make it harder for HP to hire H1-B visa workers. He is anti NAFTA anti TPP and TPP trade because he is trying to protect working class jobs. They are pro illegal immigrants amnesty.

When Carrier air conditioner closed a plant in Indiana moving the jobs to Mexico Trump and Sanders spoke out vociferously. No other Republican cared at all because they were receiving Wall Street funding. Hilary also didn't speak out about Carrier. Like the Republican candidates she is close to Wall Street. She received $675,000 for 3 talks to Goldman. Sanders repeatedly asked her to release the text of the talks but she refused. Wikileaks finally released the text last month.

Trump is for paying H1-b at least as much as Americans.
I figured. It's easy to forget that there's really no international/intercultural agreement on number punctuation, particularly combined with a service that wants to price down to tenths of cents.
GOLD Vulnerable to the Downside on Bear Pressure
Yup, I'm a fan of protobufs and the more recent flatbufs. Definitely like the tooling around being able to seamlessly switch for readability. I'll check out ion.
I think that's somewhat fair - but not totally true. Getting featured and getting some initial traction is really important - otherwise no one can find you...
Housing shortage is what makes prices high. AirBnB is not why prices are high or why there is a housing shortage.
Database researcher here: TPC-H sucks. TPC-DS is the thing to use but sadly practically nobody does it.

See point 9

http://www.exasol.com/en/newsroom/blog/10-questions-the-tpc-...

Note: Exasol has been dominating TPC-H for a while but it's kind of werid they don't publish much about what's under the hood (unlike Actian Vectorwise, for example, who has a huge library of amazing papers)
“DevOps is a management problem”