skysight-inc/HackerNews huggingface dataset:
Thanks for your frankness.

> I know that you probably do much much more.... but it will be nice to gradually scale out the components.

Agreed. There are intermediate options.

To try a full Cloud Foundry that fits into a laptop, you can install PCFDev[0].

As an intermediate position, you can install BOSH-lite in the cloud. You lose a major advantage of Cloud Foundry, though, which is that it's a distributed system which BOSH can keep alive.

Similarly, the default installation for Cloud Foundry uses 20 VMs. You can, if you wish, consolidate these to fewer. It's a matter of copying and pasting some YAML. But not recommended in the interests of robustness.

> but it would be nice to have something more standard (like Chef, Salt or Ansible. Ansible would be the closest thing to BOSH). These are extremely flexible tools... but far more accessible.

I have not used Ansible or Salt. I did spend time with cfengine, Puppet and Chef a few years back.

BOSH's concept of operations is a complete inversion of those tools. cfengine, Puppet or Chef take a system as it is and transform it, through declared goals, into the system you want it to be.

This actually means they have to do with a great deal of incidental complexity. Different distros, different versions of distros, different packaging tools and so on and so forth.

The BOSH paradigm is: wait, why are you trying to automate the construction of pets? You want cattle. So it starts with a fixed OS base image and installs packages in a fixed, non-negotiable way. At the low level, very inflexible. But it allows BOSH to focus on the business of installing, upgrading, repairing and reconfiguring distributed systems as single systems. The single distributed system is where BOSH starts, not where it was extended to. It's an important distinction.

> Docker. I know that you have the Garden repository to run Docker.... but I dont think its production ready.

Strictly, Garden can run Docker images. It's an API with driver backends. The original Garden-Linux backend is being replaced by one which uses runC instead. No point replicating engineering effort if we can share it with Docker.

But the problem is not that its unsexy... its inaccessible.

You're right. We're in the classic position of other heavy, robust tech. Hard to tinker with. I've been jawboning anyone inside Pivotal about this for years. We're making headway -- PCFDev is a start, bosh-bootloader is under active development and BOSH itself is going to get major love.

But compared to docker swarm or k8s, it's harder to set up an experimental instance.

[0] https://docs.pivotal.io/pcf-dev/
Because you want to test it with it on and off and understand the impact it has.
Text (Javascript, HTML) compresses rather well (on average 3 to 1 or better) it's considerably more likely that you are going to hit a networking limit than than a CPU limit when not using GZIP or any other compression method.
So when you do stress or load testing you really want to issue the same requests with and without the Accept-Encoding: compress, gzip or any similar headers.

Also in some cases you want to disable accepting GZIP on the server side completely because if you accept GZIP encoded requests an attacker can send very large requests that compress very well forcing you to decompress them eating up a lot of memory and CPU cycles on your side only to discard them.
In principle you want to accept only non-compressed requests but send compressed responses to save bandwidth, but in any case you want to know how your service/application scaling works in with all cases and combinations.
Thr K8S project I was involved in last year used AWS postgresql too. At that time, figuring out how to have persistant data was too much. Further, AWS EBS driver for K8S storage wasn't there. And, PetSets have not come out. With PetSets out, I think figuring out how to do a datadtore on K8S or GKE will be easier. (I had mentioned to my CTO, I don't know how to do persistant store on GKE; he pointed out the gcloud data store; I told him, that was not what I meant ;-)
We see a couple of different bugs that are best solved by simply rebuilding the container host. To docker's credit these tend to decrease with high versions.

We also see them mostly in non-prod environments where we have greater container/image churn. We use AWS autoscale and Fleet so containers just get moved to other hosts when we terminate them. We have actually thought about scheduling a logan's run type job that kills older hosts automatically - it's in the backlog.
There used to be a cool chat application Odigo I think, where you could search for random people based on Location. I used to practice my Spanish with people on that.
ohh and "the ones who walk away from omelas"
Thanks for response cyphar, and thanks for taking an action. And glad to hear RMS reads email and even replies, I'd think one would need to chase FSF's legal advisers to bring up this matter.
This was a reason I put solar in after installing a standing seam metal roof. The roof will last 50+ years, and the solar just clamps onto the seams. Only penetration is for the cables to the inverter.
> The notion that an information processing agent can be understood in isolation from the ecology in which it operates (both in terms of energy/mechanics and information) is getting harder and harder to sustain

That is my main objection to the Chinese Room mental experiment. A room is not embodied, so it can't learn like us. But an AI agent could be embodied and develop intelligent behavior.
Avcılar Masöz Escort Olgun Türbanlı Dilara Sizlerle
Logging is definitely not an unsolved problem with K8s. It's trivial to set up Fluentd to snarf all container logs into some destination, such as Graylog, ElasticSearch or a simple centralized file system location.

The Github issue talks a lot about "out of the box" setup via kube-up. If you're not using kube-up (and I wouldn't recommend using it for production setups), the problem is rather simple.

The logging story could be better, but it's not "unsolved".
As someone who has worked at quite a few startups this is the wrong question to ask. Out right failure is pretty easy to detect, and it kind of doesn't matter. A startup failing fast is the second best outcome (after a nice exit) for everyone involved, including the investors.

Startups that fail slowly are the worst, because there is an illusion of success that can drag everyone along for years.

Always keep in mind that the odds will always be astronomically high that you are working for a startup that will fail. You're probably working for a startup that's going to fail. Most startups fail fast (but never employ many people), but the startups that hire the most people fail slowly, so the odds are very high that you are working for a startup that will fail slowly.

So what should your question be then?

It should be: Am I enjoying my job and/or does this job contribute to meeting my career goals? If the answer is no for too many months in a row and you are relatively sure the answer won't change and that you have no power over making it change then it is time to move on, with one highly unlikely exception: Your startup is succeeding and your equity stake is enough that riding the wave of a bad job for a year or two will result in a good chunk of money for you.

So what are the signs of a company that is succeeding? There really easy to spot actually, even though you've never seen them:

1. Everyone's hair is on fire. Micromanagement is not a thing at your company because everyone is desperate to meet the insane demand and growth that your product has.

2. The technical work is very enjoyable, because the growth is insane. When you achieve incredible growth it actually stops managers from making decisions that don't scale, because the technical team will have numbers on their side of the argument. Your company can no longer afford to hack things together, because it has to scale tomorrow.

3. Talented people are banging down the door to work for your company.

4. Founders aren't talking about exits in terms of goals, but in terms of certitude. They've already received offers and they now have strategies in place to get the kind of exit they want.

5. BS of all forms is not experienced, because no one has time for it, even the people who normally spew it.

6. Hockey stick growth in either user growth or profit growth is trivial for you to see in your position. The founders don't have to convince anyone that your company is doing well, it's just plainly evident.

If you are not experiencing these signs and you hate your job than it's time to move on. Founders hate to hear this, but if they haven't gotten traction in the first year-and-a-half they probably will never get it. There are notable exceptions, but it's important to remember that you are not the exception (does your founding team seem exceptional to you?).
"The Ones Who Walk Away from Omelas" is perhaps her most biting short story. It's not one of the Orsinian tales, although it could have been set in that world.

Anyone who writes fantasy should read her essays in "The Language of the Night". (Also Poul Anderson's "On Thud and Blunder".)
> K8S is flexible and extensible because it doesn't try to be a Heroku, more of a framework for building your own Heroku.

Agreed. Cloud Foundry is not a "competitor" to Kubernetes, in that sense. Diego is the Kubernetes analogy. The Cloud Foundry internals have become progressively more finely abstracted and teased apart to make it possible to swap components, so you never know.

That said, for those who want Docker + Kubernetes bundled into a turnkey PaaS, Red Hat went all-in on those two techs for OpenShift 3.
They used to be FCUK in the UK (maybe they still are).
Email Deliverability: The Ultimate Guide
I think it's probably not worth worrying about "fast" when "slow" is "ten minutes once a week, maybe, if you're really destructive" and similarly worrying about "light" when you have 16GB of RAM and a quad-core processor; the heaviest dev environment/IDE I can find (IntelliJ and a couple hundred Chrome tabs) doesn't use eight of it. It comes off as super-premature optimization to me, and those optimizations that you would otherwise do in Docker (which are just building base images, whatever, Packer does this trivially) exist in a virtualized environment too.

Running datastores in Docker is bonkers in the first place, which still leaves a significant place for an actual CM tool--so unless you are a particular strain of masochist, when you are replicating your local environment, you'll probably need it anyway.
A few other people (outside of hn) have complained about the dashes :) I'm considering alternatives!

I do still think that .com is preferable, both because it's the first thing a lot of people try if they only remember the name and not the TLD, and because a lot of the new TLDs (especially .club and others that you can get on namecheap's 88c deal) are being used for pretty crummy businesses. Obviously if I can get to top of Google results for a couple of decent queries, neither problem matters too much.
The "have you tried turning it off and on again" of DevOps. It makes a surprising amount of sense though, as long as your service is truly stateless, the restart can be easily orchestrated, and it results in no difference in operational costs.
OK - not to defend all professional programmers - but it seems quite reasonable that perhaps the tasks where people are hired specifically to write code are perhaps bigger and more complicated than programming tasks that are completed by people who do programming only as a small part of their job.
Thanks, agree!
Yeah, so sad, it just makes me think of all the code that could be cross-platform but for CString (MFC) and the like scattered through it.
It was just a temporary tourism campaign. I rang and one of the things we talked about was the campaign and whether we thought it would increase tourism. The guy I was talking to only signed up because it was cool.
As a french, I agree. Much talk only to assert the fallacy that someone disallowed to dress like she want could possibly be "more free".
Thanks, that worked. You're right, it's surprisingly slow.
Because then you always know you can always rebuild automatically and that's being tested constantly while developers work, a bit like how Netflix crashes everything all the time randomly to ensure they can always automatically recover from every dependency.

It also naturally rewards optimizing around time-to-redeploy, probably a lot of benefits there.
"Your call may be recorded."

Non merci.
Given that GE is its own VC for the context, they really don't need to be in NYC.

More importantly, industrial Internet of Shit developers, smart grid companies, and related activities are going on at the Seaport District, right where GE is setting up shop.
Posibly the taxi companies need to invest in some basic sms/gps tech.

How it works for me is:

ring ring "hi can I have a cab to location I am at location y"

Dispatcher asks my name and "says that will be 10 min" I get an sms when the cab has been dispatched and another when it arives that says ita a silver priaus licene plate no xxxxx.
I think that your separation is probably a useful framework for discussing it. However, I disagree with your conclusion. Work funded by the people should be owned by the people. That funding includes the payment of salaries which are the incentivization. Their role is to advance their fields, it is what they are paid to do, reviewed on, promoted by, etc.. I would see no bigger problem in requiring researchers to sign over rights than others do in asking employees to sign over rights to their employers. It is/should be an expectation of the role.
I have a lot of egg on my face for having introduced Docker into my company a year ago. I liked their vision, and I figured that there'd be some bumps in the road, but that it would be better than attempting to reinvent similar technologies in-house. I was wrong.

Docker hasn't done what I expected. I thought they'd really lock in their core use cases, and make those rock solid. Instead they're trying to do more, and more complex things, while the underpinnings are still half-baked.

My new prediction for docker is that they'll follow the same trajectory as a MongoDB type company. Useful idea with a few glitches -> add more flash instead of fixing the glitches -> raise more money -> end up with a monstrosity of a company and a mediocre product -> desperately hope that they conned enough enterprises into using it to become self-sufficient on enterprise support/licensing.

They've clearly abandoned the market of 'people who want good infrastructure', and are now selling solely to morons. Docker is hot garbage, and it is used almost exclusively by trend-loving idiots.

Sadly, and really annoyingly, my coworkers think I'm a trend-loving idiot because I used to believe that Docker would mature and turn into great software. instead, they've turned into a horrible tire fire.

Here's to hoping somebody else enters the space and executes competently. Docker could've been great... but instead it's fucking docker.
The Department of Energy's Small Business Innovation Research Program [pdf]
Can you elaborate on:

"you don't use it to store data" - What is wrong with Docker volumes specifically? What issues did you run into?

"wrap docker pulls with 'flock' so they don't deadlock" - I have never had a problem with docker pull, can you elaborate on this?
Caring about animal's/women's rights only when it comes to ritual slaughter/honor killings seems a lot more ethical than claiming to care about them except when it comes to ritual slaughter/honor killings. The latter seems more common among leftist Islamic apologists.
It depends on what you need.

In the past we used GTK and wxwidgets with OpenGL but we did not like it.

We started using Qt, much better(proper object oriented by design, and cleaner design than wxwidgets) and web apps. Now we use native libs with our own multiplattform lib with bindings for each plattform:

-javascript for the web.

-native cocoa and windows libs, with openGL, metal and directX.

-Qt for linux with OpenGL.

- Native mac(iOS and cocoa) and windows.
I use it, and then use it some more. I start with a specific objective and get that right. After that it's just a matter of getting familiar with the specific syntax.
Coming from the perspective of an excited child computer hobbyist in the 1980s and seeing it go mainstream (bigger than anticipated), alot of feelings, both positive and negative. Negative for instance the weaponization and corporate control. But -- overall more positive than negative.

What's funny to me though, we used to have this term "killer app". The specific app that made a platform blow-up..

Well, if you remember the 90s, the killer app for the Internet (we used to use capital I, too by the way) was porn. Clearly.. Porn. That always makes me smile when people get a little too carried away about the net's importance in the world.
> because governments are chosen by people

In some parts of the World...
It's hard for me to guess, maybe centralization of media makes it so attractive for governments to distort information. When there are at least two sides loudly confronting each other, the general picture gets much better.

A curious example: Ukrainian media channels are mostly funded by local oligarchs, but each of them has different agenda and interests, so they often fight each other, and that produces an external assessment of "partly-free" for Ukrainian media space.
The Lazy Engineer
There is a spectrum of "it just works" to "I've applied every best practice" bad programmers who spend huge amounts of time on best practices will end up wasting a lot of time over optimizing but it may have the benefit of reducing risk where they may have a lack of deep understanding or it may shine light on that risk, that is if they apply practices correctly.
The title of this article should really be "Why bad scientific code beats bad software engineer code."

It contrasts a bunch of bad things scientific coders do, and a bunch of bad things bad software engineers do. There's no "best practices" to be seen on either side.
Fruits and Wine GO the hilarious new drinking game
I watched it while working on other stuff. Must not have noticed that part.

But note that a small company will have correspondingly fewer dependencies. So I'm not sure a small company would need a dedicated upgrade engineer.
Assuming the remote is actually decompressing, and the origin isn't dynamically compressing for each request.
well, in terms of anecdotal evidence, I live and work abroad and tools like Facebook and WhatsApp make it possible to communicate with my friends and family back home at a cost of next to nothing.

A decade ago, international phone calls and SMS would have cost me an arm and a leg, and there's really no equivalent for Facebook which lets me keep in touch with the lives of people I care about on the other side of the world.

Yes, there was email but that doesn't really substitute for the short low-latency, ubiquitous worldwide communication of WhatsApp (and it certainly didn't 10 years ago when it was largely tethered to a desk) nor the ability to keep up with my friends unsolicited that is Facebook (what am I supposed to do, ask all of my friends to write me an email of what they're doing once a week?)

Are global migrant workers an edge case? perhaps. But while forfeiting FB and WhatsApp wouldn't make me a hermit, it would certainly make communications with my friends and family back home to be lesser in number and richness.
Didn't downvote but... At the very least, a suggestion for a cross platform library for "sticking webviews to your app" would be needed to answer OP's question.
I was expecting SETI to find intelligence on Earth before space. They've been looking at the entropy of bee hives and other disembodied signal-passing collectives for a while now.
But European countries would very much like to remain in control of their own markets, especially for agriculture. And they are right to do so: no one in the EU wants to eat the stuff that's sold in the US.
You paint a wonderful vision, but it'd also include Americans telling you how great Trump is and how they can't wait for him to get rid of Mexicans, Arabic men telling you about how it's totally fine to marry a 12 year old and for her to bear their children, French people going on about how muslims should all be imprisoned, etc ...

Of course if you're black, a woman, gay, or any other minority they'll be happy to insult and harass you for their entertainment.

And not to forget all the very mundane people who don't have much to tell you about except for their mind numbing day labor job and how they can't take care of their sick children.

The world is much less poetic and open minded than many techno utopians would like to think.
Many regulations are introduced with the implicit purpose of disadvantaging foreigners; one example of this would be Chinese restrictions on importations of electronics (similar to European RoHS, but more stringent and only applied to foreigners).

Regulations are often introduced to advantage large, coherent interests such as unions and industries.
In case you are looking for associates in the EU, drop me a mail. I'll share LinkedIn if you wish, and we can discuss matters privately. @gmail.com prefixed by my username.
Ask HN: Should i build an auto-parallelizer for C or for JAVA?
Assume that we focus on desktop and mobile type programs. Mostly OO source code, linux userland tools, Office, android software..

If you could choose just one language for your tool - which one would it be?!

I am specifically ignoring HPC, numerical workloads, and server tools. These are already hand-crafted, partially parallelized, and fairly efficient at what they do.
Europe's ageing population is set to wreak havoc with the economy
Won't validate whether this happens with Docker, but I've seen it other places. I won't name names, but I bought a commercial add-on to an open source project very similar to Docker, and when I had a support issue, I was pretty much told "tough luck, not my problem" by the project founder.
try http://www.hireahungarian.com/tablet/index.html

Disclaimer: I know the owner (friends with my wife who is from the area, we are living in Eastern US)

They are flexible and probably willing to be a proxy on your behalf.
Even if the remote is decompressing it doesn't matter a botnet owner or some one who compromised a few AWS accounts doesn't care it won't really slow them down.
CPU's are pretty fast at compression and when a site is easily 3-4 times the size when not served compressed you are going to hit your network cap limit faster than exhausting the CPU even with dynamic compression and no caching under most circumstances.
Certain classes of satellite (like remote sensing) use sun synchronous orbits which are slightly retograde. It allows the orbit to precess slightly to keep tracking the sun as the earth rotates on its axis.
dtmf.io gives errors for every option ?
'We're sorry, an error occurred. Please try again soon.'
I think you got the original article wrong. The author didn't argue against the connected life. He observed that the people who know life without the internet are starting to go extinct, and argues that we should preserve the unconnected experience by going offline for a few days every so often.