skysight-inc/HackerNews huggingface dataset:
I appreciate that the author distilled his thoughts about software down into porno terms we can all relate to.
> Can you elaborate why they are correct with this view? What is inherently superior about 1 process per container?

At sufficient scale, horizontally scaling is complicated and involves implementing the things I avoid until I have no choice [Dynamic Service Discovery on a per-process basis, etc.]. I'm mostly deferring to stuff I've read about it since I haven't really worked at companies that are larger than $XX million a year.

It generally is things like principle of least privilege, the fact you already have to bite the bullet on managing your service discovery through yet another tool, etc.

Personally, I've never dealt with anything larger than 2-3 datacenter locations with a rack of equipment in each.

> And why should Docker containers only run on bare metal?
That you can just ignore.

I really just meant don't do:

bare metal -> Spin up Xen VM -> Spin up docker containers

Any of these are valid imo:

AWS -> Docker Containers

Bare metal -> Docker Containers

[Insert hosting option X] -> Docker Containers
> Let frameworks do everything for you

I'm happy to let a framework do everything for me - assuming the 'everything' you speak of is done well.

Implicit in your statement is an assumption that this will be bad - I'm not disagreeing that there are downsides, but please don't hide these inside implied reasons. Bring them out and let's debate them explicitly.
Google 'created' Cardboard which is an exact knockoff of the research done 2 YEARS ago by USC (it even won an award then at IEEE VR).
One tiny improvement to the article would be to change the "visualization of the surface" images to to show the part of the surface where the solution is eventually found. The 3D graph cuts off at y = -2, which makes things a little harder to understand.
Not really. There was no need in OOXML to begin with. Especially in the ISO mess that MS created. It was born in the old MS, which was heavily into standards hijacking and vendor lock in. So it remained the child of that idea.

Current day MS is still strongly dominated by the lock-in mentality. So this change is welcome, but they have a really long way to go to repair all the damage they caused and gain some trust.
We found that neural networks can solve CAPTCHAS much better than humans, 99.8% on the "hard" ReCAPTCHA instances: http://arxiv.org/pdf/1312.6082.pdf

This is why visual recognition is just one of the signals you need to use to tell humans and computers apart http://googleonlinesecurity.blogspot.com/2014/04/street-view...
That's basically it yes. Well there's no way to apply aftertouch to a laser harp nor is there velocity so it'll be hard coded velocity (might have a pedal control in future). At the moment it will just sent note on and off down the wire. It does this using three shift registers (74LS165) and some extra bits for start/stop bits.

I've got it sending notes to my Triton so far which is as far as it has got. The harp front end works with one note as I don't have a laser galvanometer at the moment (will build one). I imagine it'll take another 6 months yet at this rate. Plus I keep getting distracted playing with the nice green laser I bought :)
Overlaying hover effects is really pretty easy though, no?
they also kill their partner's ability [http://pni.osumc.edu/KG%20Publications%20(pdf)/109.pdf] to fight off viruses and cancers

Woah. This is as interesting as the article itself.
just takes a little time to get used to them. before you know it, people will move away from just pure .com.
I generally agree with him regarding the picking your tools part, but some of it seems a contradiction.

Tools where you build the app by writing code in
JavaScript files, not by trying to declare too much of
your app logic in your HTML (no AngularJS, sorry).

The DOM is simply a view of the state and reacts to
changes in the model layer.

That's pretty much Angular's philosophy as well.

that said, this:

People who already know JavaScript should be able to
work on the app without lots of knowledge about a
specific tool or framework.

IMO trumps all.
There's nothing more loathsome to my eye than an 'innovative' user-interface produced by someone who thinks creativity trumps UX.

The number of times I want to be 'surprised and delighted' by an interface can be counted on the fingers of one hand. Most of the time I'm trying to achieve something other than appreciate the genius of the designer involved.
Segment.io (YC S11) is hiring Integration Engineers
We’re looking for an engineer who’s extremely organized and who gets a kick out of talking to customers. If you like shipping code, this role would have you shipping multiple times a day, every day, with a happy customer at the receiving end.

We add about three new integrations each week, and we don’t see that slowing down any time soon. Enterprise customers and self-service customers alike ask for new integrations constantly — their apetite for data is apparently bottomless — and they delight in being able to simple “flick the integration on” once it’s released.

You’d be in charge of the technical side of integrations: understanding what the customer really needs to get from the integration, spec’ing out how the integration should work, writing the code for the integration, merging pull requests in our open-source libraries, fixing issues reported by customers, and testing each integration to make sure it solves the customer pain point.

You’d be joining a team of talented engineers that are in love with open-source (we have more than 200 open source projects[1]) and who care deeply about their users and partners. If you really love seeing customers delight in freshly shipped code, this is the place on the team for you.

[0]: https://segment.io

[1]: https://github.com/segmentio

---

To apply, email us at jobs+integrations@segment.io with:

1. a description of your own favorite software project (code is a bonus)
2. a story about the last time you taught someone something technical
3. a link to your GitHub if you have one
4. why you think you’d be a perfect fit for the job
Can this be used with Mono?
Do not forget Zarafa!
Single purpose is a role.

Single process is a single process. [e.g. Nginx]

I think you are confused by what I meant.

Stateless single purpose containers is good.
One process per container is bad because it involves more service discovery before you actually need it.
Good riddance! Photos come with all sorts of biases (age, gender, race, etc.) and really serve no purpose other than help some "SEO guys" game the system.
Get a keyboard with a trackpoint [1]. It will take some time to get used, but in the end you will not need any mouse anymore with the advantage of being pretty comfortable using laptops in trains, aircrafts and on walking desks.

[1] http://shop.lenovo.com/us/en/itemdetails/0B47189/460
> your monolithic app explodes in terms of number of processes.

There's no reason it has to, is my point.

You may have a point in instances where you start with an application that actually already wrapping a ton of unrelated functionality together in a single process - I didn't really think about it in terms of that scenario. But then I'd argue that an increase in the number of processes will be an operational godsend over having to try to track down problems in a monolithic mess. And even then you're not forced into splitting things up into tons of little pieces in one go.

The scenario I was thinking of, on the basis of the discussion here regarding baseimage-docker, is splitting up services that consists of a bunch of interrelated processes. E.g. Nginx + Apache + Memcached + the actual application + various cron jobs + Postgres is a typical example. Starting by splitting that up into separate Docker containers for each existing processgroup doesn't introduce any new application processes.

You can then gradually break up the actual application if justified/needed.
You're completely right. I made 99 cents though to validate first if people would actually buy based on icon/keywords/screenshots. I submitted an update yesterday to make it free though, seeing how little reviews I am getting.
The treasure you have, and that I wish I could have, is that you know what love looks like on a day-to-day level. You have been habituated to it, even. There are many people, I think, who want to achieve what your grandparents did but don't actually know how, not because they don't know that they should be kind and generous, but because they simply don't know what kindness and generosity look like in the mundane details that fill up most of life.

The article included a quote that said that even in bad times, usually one or both partners are trying to do the right thing but failing. You have the blessing of knowing what the right thing looks like. I envy you that experience.
Not sure. I guess it's useful as a reference implementation (if it conforms to the specification that is), but not beyond that. Actual editors and office suites which could potentially use the code aren't written in C#.
Ahhh of course, I keep forgetting how incredibly lazy people are.

They cant even imagine someone would type that.

Thanks for explaining.
Why stop there? Be suspicious of existing programming languages and network protocols. Let's write assembly and push raw bits over the wire.

Reductio ad absurdum...
Actually I haven't updated the blog to use that yet. We just include videos with every single release. Don't try to draw a particular conclusion—it's mostly just for fun :).
> The classic parts are still going strong.

But there are very good alternatives for them, be it low cost mcu's,50 cents fpga's, or even lower-end programmable chips from sillego[1][2]( going down to $0.2/10K + probably $0.1 more for programming - and that's without competition). Those are smaller, more reliable(less soldering) and can do quite complex functions including analog.

So i wouldn't bet on simple gates holding on for 500 years.

[1]http://www.eetimes.com/document.asp?doc_id=1279013

[2]http://www.silego.com/buy/index.php?main_page=product_info&p...
Well spotted. I'll leave it in for posterity :)

However I expect our Surface 2095 will run Office 2097 and it'll still have VBA jammed in due to some legacy clients moaning that they can't run their financial app in it any more :)
Its a flag. There's not much to manage or setup.
They always post a video at the top of their blog entries.
Thanks for making it. I'd like to give it a try some time. I certainly share your feeling about the awesomeness of fail2ban, as well as the slight awkwardness of interacting with it (I tried a couple of things with the client, but it felt rather awkward somehow. I'm not entirely sure why).

As a developer, the stack you're describing sounds great. As a sysadmin / devops, I'd be a little careful installing something with this level of component complexity on top of fail2ban. Ideally you'd want something very lean with as few moving parts as possible. (after all, if something goes wrong, you can end up locking yourself or your server).
Netflix's first original anime series 'Knights of Sidonia'
Nice to see an admin panel that doesn't require PHP or Apache/Nginx installed. I'll take this for a spin.
Requirements: https://github.com/Eugeny/ajenti/blob/master/requirements.tx...

I seems to be licensed under the AGPLv3 (desc here: https://tldrlegal.com/license/gnu-affero-general-public-lice... )
I'd like to comment on this remark: "Tools that are "just JavaScript." Not tools where you describe your app in a DSL (no Sencha). This is to avoid requiring too much knowledge of the framework itself before being able to contribute. Focusing on JavaScript also offers some protection against investing too heavily in framework-specific knowledge."

I've been using ExtJS since 2008, so I can give some experience here. What he says is absolutely true. The DSL of ExtJS does slow down ramp-up for new developers and requires an investment in learning the framework before you can use it.

However, I would like to point out there is a reason for the DSL. The DSL abstracts away the low level details of HTML so you can think at the level of ui elements. HTML's controls are very basic. Instead of comboboxes it has selects, which are quite inflexible. Instead of grids it has tables, which are also quite weak. The date field is minimal and in fact missing in older browsers. The list goes on and on. HTML is simply not rich enough to express desktop-level ui's elegantly. You can deal with that in two ways: embrace it and dumb down the ui (hence the trend towards minimal ui), or work around it and build a DSL on top of HTML. The core theory behind the rich DSL of ExtJS is that by bumping up the abstraction level developers can be more proficient. It is OO encapsulation at the UI level.

That is the theory. In practice it is a mixed bag. You have the same problem with ExtJS on top of HTML as you have with an ORM on top of a SQL db. You need to understand both what happens underneath and what the tool does on top of that. The cognitive load is higher, not lower. Some people thrive in that and are more proficient in the DSL than they would be in a raw templating view-driven environment. Others struggle with the larger amount of layers involved and are slowed down by the approach, and then some people fall in between and see no productivity difference. YMMV.

Update: one additional thing that I'd point out is that being opinionated and investing deep with a framework is not a bad thing when you're building a large long-lived codebase. If you're going to be living in a codebase for years, it makes sense to have as much application backbone (pun intended) as possible before you start building code on top of that. If you assemble a hodge-podge of smaller modules you're essentially constructing your own big framework anyway, so you might as well bite the bullet and choose a consistent one. The notion that you're ever going to switch js frameworks on a large single-page-app codebase is silly. The cost will always outweigh the benefits.
>>But...why is it paid?

Because he wants to be rewarded in a small way for his efforts? Geez it's 99 cents - 30% Apple cut.
Shougo is quite prolific as well
The appeal of “pickup” or “game” is a failure of education and socialization
Better Games Through Playtesting
This is exactly the kind of visually appealing and easily navigable Vim plugin directory I've been searching for ever since I started using it last year. Thank you for sharing, this is fantastic!
whoa, we have a milionaire in our midst. Is that 30 million!?
Nice! I will have to give it a go sometime. unbanning from fail2ban is always a pain.
Thanks for posting this! Grateful for the Adioso links.

I'm for the trend of people at start ups talking more openly about what their experiences are like, Australian or not.
The submitted title [1] was upworthyesque linkbait, so we cribbed the title from the previous submission of this url [2].

1. "This Site Shows Who Is Hacking Who Right Now – And The US Is Getting Hammered"

2. https://news.ycombinator.com/item?id=7943681
I had the same inspiration :)

I'll document it when complete and submit to hackaday.com. There have been many dead ends so far so I'll probably just depress myself if I write it up before I'm done :)

My objective is a parts cost of less than £100 and no programming of devices required.
5 Tips For Negotiating with Suppliers
Letting frameworks do everything for you usually means you're not doing anything interesting.

For many products however, these days an "interesting" interface doesn't sell it unless you are pinterest or something. 99% of the time, users are at your page/app for some level of function. Rarely is the function essentially the form.
Wow, the portrait of this woman is so photoshoped that is disgusting.
Hmm. I guess what I'm getting at is that I typically start building a web app by writing model objects that get turned into db schemas by the ORM (in Python, this is usually the Django ORM or SQLAlchemy), and the ORM turns attribute access into joins (either eagerly or lazily).

So an ORM that usefully interpreted model subclassing etc. and created self-joining tables and could query the resulting model using RECURSIVELY WITH as appropriate would be a real boon.
Depends on what you do with it. If you develop on it and the domain is a logical, obvious descriptor of the app or service you offer then it can act as a multiplier of the underlying value of the product.

The new TLDs are doing really poorly in terms of end-user adoption: http://www.ricksblog.com/2014/06/rick-schwartz-equation/
You still need to compile the assembly. Do you trust your compiler?
Why doesn't someone have a cap on domain name sales? What sense does it make to make this some sort of land grab promoting squatters.

(note that ww.com was not squatted on, i know that. i am just asking in general why a price cap is a bad idea for resale.)
Wow, you weren't kidding.

http://newgtlds.icann.org/en/program-status/delegated-string...

Jesus - who came up with these?

Also - anyone know where you can register any domains with these new delegations? Is it on a registrar-by-registrar basis?
This is wonderful. Thank you for sharing. And I'm sorry for your loss.
I've always just pulled in the contributor's branch, made additional commits to fix things up, and squashed all the commits before pushing up to GitHub. Not very difficult
No bitcoin, no money. You can see the CSS code on my sites. Change .css to .sass for the source. You should have take it as a challenge: a minimal CSS module that can be used from web apps to presentations sites. That's my idea. 50 lines of code is a good start. It should be a bit more than a CSS reset, it will have a basic grid system, one basic form style, etc.

I don't want to learn Bootstrap or any another framework, I know that there are other designers who think like me. Designers like to make their own custom stuff. That's the reason you see millions of WordPress themes out there. Everyone is different and want to see and use something different.

Doing everything with Bootstrap is not efficient. Most of the people here don't have a designer mindset, yet they flag anything that is against their way of thinking.
The repo doesn't contain any P/Invoke or C++/CLI, so I don't see any reason why it wouldn't work with Mono.
> And why should Docker containers only run on bare metal?

The "point" of Docker is to be a lightweight replacement for virtualization in some cases. Layering Docker on top of virtualization, while fine, adds layers rather than removing/replacing them.
Everything old is new again.

Cardboard stereoscopes were very popular in the late 1800s and early 1900s. Here's a patent for one from 1902, for example: http://books.google.com/books?id=2jN9AAAAMAAJ&lpg=PA849&ots=...

That's what Google Cardboard is; a stereoscope, traditionally used for viewing static 3D images (a left and a right, e.g. this meta stereogram of a woman looking through a stereoscope: http://commons.wikimedia.org/wiki/File:Stereograph_as_an_edu... ), instead being used for a dynamic 3D image courtesy of a cell phone. You could literally tape any modern cell phone to any 150 year old stereoscope and you'd have Google Cardboard, or USC's equivalent.

(Personally, I backed the Poppy on Kickstarter, which is made of nice plastic: http://www.poppy3d.com )
I don't see any reason why it would be Windows only. All the code appears to be spec-compliant C# that doesn't use P/Invoke to call native modules or rely on C++/CLI. The only sticking point I see is the PowerShell script, and that's pretty trivial to replace since it's just a build script (you could use xbuild/msbuild, since mono supports that, or just use make)
> Does not overwrite your config files, options and comments. All changes are non-destructive.

I'm wondering how this works exactly. Does it mean it comments out changes it makes? Or keeps a backup somewhere?
Great. Thanks for answering. You are right, as a business owner I do like getting all that info.

It is something we will consider we will consider using.
That isn't what MicroServices are about.

MicroServices are an generally about application architecture where you break your application into a very finely grained interacting services.

Your eCommerce store web application for instance becomes a shopping cart service, a stock service, a category service, a login service, a user profile service etc. You can take it even more fine grained so your user profile service becomes a user profile update service and a user profile rendering service.

The point is, one application becomes tens or hundreds of distinct and distributed processes. This is a massive rise in development and operational complexity before you seperate out your web server, database etc.

http://martinfowler.com/articles/microservices.html

FYI We are heavy production users of MicroServices within Docker and would put tools such as NGINX, MemCached, Postgres into Docker images as a matter of course so they can be built, deployed and versioned in the same way as our services.
Congrats on the app. Looks pretty good.

My suggestion: make it freemium. Give away the basic functionality, and charge for extra features.

I believe this will make your app much more popular and also be more lucrative to you in the long run.
https://github.com/OfficeDev/Open-XML-SDK/pull/3 suggests that there are issues with use in mono
I wrote this how do I categorize this? http://vimawesome.com/plugin/numbers-vim
Professional Social Engineer AMA
A DDoS Emerges That Busies A Cipher with CPU Intensity
Why your startup is probably breaking the law
The IPO is dying. Marc Andreessen explains why.
A Conversation With Google’s Larry Page and Sundar Pichai
Low cost MCUs have FLASH which has a finite life. Same with FPGAs which need to have their brains filled from something.

I worked on a project a few years ago that had a PIC part. They never got the software working right so we looked at the original spec. The entire software could be crunched down to 7 gates and a comparator. So we did a rev2 board with a flip flop and a NAND and a LM358N and there hasn't been a failure since. To be honest with some bastardising to get hysteresis out if a 555 and a couple of transistors would have done as well.

The BOM was £0.09 more expensive but the part never failed in production.

The most interesting thing is that PIC part no longer exists so there is no service option other than replace which costs more down the line.

(This was a watchdog monitor for signalling systems)

Edit: yes I know the 358 isn't a comparator but it was fed just before saturation to get hysteresis avoiding more parts.
"One way to practice kindness is by being generous about your partner’s intentions."

This stands out to me as being profoundly true about all relationships. Communication is hard. We humans are powerful storytellers so we tend to be able to tell most any story to fit the facts on hand. In most cases I find what I am looking for. This is what DFW talked about in his terrific commencement address[1]: we all ultimately choose which story to tell ourselves. When you choose to assume/believe/hope your partner is a good capable person who is trying hard, you find yourself a part of a much better story than otherwise.

And this principle extends beyond our most intimate personal relationships and can even be applied here, where most often the only thing we know about the person we are responding to is the brief couple paragraphs they hurriedly wrote in-between trying to get things done. How easy it is to tell a story that they are foolish or mean, if you choose to.

[1]: https://www.youtube.com/watch?v=8CrOL-ydFMI