skysight-inc/HackerNews huggingface dataset:
I do this as well. I break apps into "components" -- each component has it's own CSS and JavaScript file. A component covers a logical domain, such as administrative functions, or a reporting piece.

Then I have an application level CSS&JS that has everything generic in it. This is for a reasonably big app, so the overhead of having a single CSS/JS isn't insignificant - particularly when supporting mobile devices.

The other useful thing is a I as a dasherized version of the controller name and action to the body tag - as an id and a class respectively. So the body tag is something like
<body id='my-controller' class='show'>

I also expose these as JavaScript globals CONTROLLER and ACTION (I also have LOCALE and COMPONENT).

These constructs are to be used sparingly -- you don't want to mash everything together too much -- but they're very handy when used right.
It's called HyperDB, and they did indeed release it: http://codex.wordpress.org/HyperDB
I agree. There's a sort of categorical imperative here: imagine if everyone who had a trivial problem with a site posted a comment about it — HN would be nothing but meta.

I'd also do away with submissions about sites being down. The Internet is so large that at any moment something is down, and it'll probably be fixed before people have a chance to pile on with unhelpful comments anyway.
The tech industry is heavily reliant on the recruitment model. Its actually a great model, how many people can say there is an entire industry out there dedicated to getting you hired? But it has its underbelly. Spam, lowballing, misrepresentation, and some of that results in a lower than expected best match scenario for filling positions. I agree that many developers dont want to deal with the noise of job boards, and that may be a sense of hiding, but its also a sign that a high percentage of recruiters are not selling you into a good job, they are just resume bombing a hiring manager they have no relationship with, have never talked to and will probably never fill a seat. These kind of shops are to be avoided like the plague and only reinforce bad hiring practices because they submit consistently low quality candidates for positions which the candidate does not match.
The first design rule would be not to have the wallet file on the same server as whichever stack was used.

Secondly the client facing stack can not interact with the server holding the wallet file directly. It would have to go through a third server which would run sanity checks on any transaction requests.
Google’s President of Brazil Operations arrested over YouTube video
That's somewhat true. However, using Google does have an advantage over your own CDN -- it's more likely to already be cached in someone's browser.

On these occassions the hit to download JQuery (or something big like JQueryUI) is zero.

This is more a consideration for a landing page than a heavy-use application though.
TIL: YouTube keeps the orignal files
N.B.: yes it's the same layer. HTTP is at the Application layer in the Internet layer model (and this is the Internet, not your school's Network class where they dream about OSI layers).

It's irrelevant which layer this is happening at. The point is that there is a resource address and a resource version. Decoupling those allows you to retain the same resource address for different resource versions - whether this is done for backwards compatibility, multi-language support or other reasons.

"All that the author is going to achieve is to have broken client codes every time he's going to bump his API version because most developers won't bother to check the content-type."

The point of the article was in fact to teach those mediocre developers who "won't bother", to actually bother to understand these concepts.
Agreed. Also just generalizes type I as "the type you're born with", which technically isn't true - you can get type I in your teens, 20s, 30s, etc...
If this is just about load balancing, then they could probably get better performance from haproxy, right? Anyone should be able to exceed 200 req/s with haproxy. In fact, you should be able to get around double that or more.

The point is the title is useless. It tells you almost nothing. That blog is a joke.
Long forgotten? I'm sure he reminds people all the time.

He does have some fascinating projects though. Xanadu[1], a sort of visual hypertext browser & editor, is something I'd like to see a "real" implementation of. Any decade now...

[1] http://en.wikipedia.org/wiki/Project_Xanadu
Sorry, just generally ranting, not in your direction. :)

My personal (strong) preference is to use semantic IDs as JS hooks (or just for markup readability), and keep all class names content-agnostic. Obviously there will be cases where you need to use (CSS) classes in your JS as well, so a good practice is to prefix them with js- and not base any style definitions on them. Separation of concerns and all that. You should be able to refactor your CSS, markup, and JS independently and not have anything break.

Additionally, you should be able to copy paste a chunk of markup and have it look identical no matter where you put it, which definitely won't be the case if you are using long, content-referencing selector chains. Keeping your CSS flat, low level, and generic increases reusability and prevents CSS bloat, which can quickly get out of hand even in a medium sized app. Of course, all this is probably overkill if you are making small, static sites.
Like the ones I mentioned.
Just wondering why you specified offline mode. That is definitely the third party app problem.
They have two thousand servers total; that includes database servers, memcached servers, regular backends, and load balancers.

Peter Westwood gave a talk on WP.com's infrastructure in London in January; I've tried to find slides online but I can't, which is a shame because he went into quite a bit of detail about their nginx/HyperDB/memcached/mogileFS setup.
On the plus side, the way transactions work, the vault never needs to be connected to any networks at all. Hot storage is risky but cold storage is extremely safe.
He's also being naive about live coding as a whole:
http://toplap.org/?p=212
I'm trying to take duplicity out of it. I'm more interested in the "willingly" part, which I probably articulated a little more clearly when I edited my initial response to kevinpet with a similar question. Your example about unwittingly installing Folding@Home is an interesting counter point and figures into where I was going.

By willingly I was implying an unscrupulous person installed a program which they knew to be detrimental to a 3rd party in order to utilize some functionality would still be considered "malware"; despite others having the view that if a user, with complete knowledge of all aspects of the software, installs it it cannot be "malware".

You state that the intended target doesn't matter, which I disagree with. Which seems to leave us at agreeing to disagree. Everybody has their opinion on advertising and its boundaries (or lack thereof) and value (or lack thereof), like I said in one of my first replies, I've never seen anybody change sides on this ;)
Merlin Mann: Speaking for Yourself
...both of which are domain specific languages, or developed as such.

I really think C++ is going to gnaw "market share" from C in any low-level domains and fight back Go and other competitors in high-level systems programming domains thanks to it's recent C++11 standard and upcoming standard library extensions which being the transition of making it much more on-par with other modern languages. Bjarne Stroustrup(the language creator) has also hinted for much faster standardization process than last time around(when it took some 13 years to come up with a new standard), and would hope for a 5 year cycle instead, so perhaps C++16 is coming up next. Oh, and the standards committee is already working on it.

The only major setback I see with C++11 in comparison to many other languages aimed for large-scale software development is it's very small standard library which completely lacks support for modern technologies such as hierarchical filesystems, sockets, XML and HTTP and so on. They are coming up later on, though. The core language is very solid and doesn't lack anything special. Yet, it's not any more "bloated" or complex by it's standard(in terms of page/line/word count) than say C# 3.0 or Java 7.

tl;dr: I think many people think C++ is "old" or even dead and we need something more modern, yet now C++ evolves faster than ever and tries to meet that demand.
The problem with your idea is that Alzheimer's disease is not easy to study.

1) There is no good diagnostic test for Alzheimer's outside of a brain biopsy (although Lilly just got a diagnostic approved). Today, it's usually diagnosed by a process of elimination (i.e. you don't have any signs that it's another organic brain disease, thus it must be Alzheimer's).

2) The time of onset to the time of death for Alzheimer's is often measured in decades. You'd have to run a REALLY long study to be able to capture that data.

The other issue is that analyzing data from studies retrospectively (studies that weren't designed to test your given hypotheses) are generally regarded as "lower quality". It may support your hypotheses, but it's pretty weak support.
As a counterexample to shoving bits I can point to two things mentioned by Bret: Morphic and Smalltalk. It just so happens that Morphic (referenced in it's original, Self implementation) was ported to/implemented in Smalltalk (Squeak, Pharo). These are things that exist and work today, I had a pleasure to work with them and have to say they live up to expectations. It's worth trying them out.

Another curious example is Erlang, which lets you update the code responsible for some behavior (I mean of an object) live, without any hassle at all. Then there's ClojureScript, which lets you do the same in browser (I think, don't know it very well).

Foundations of what Bret says are not new, and they are not purely theoretic either. The programmer of 2012 could have been using them for years if he wanted to.

I think Bret is right when he writes that technical possibilities are not a problem - programmers mentality is. Both Lisp and Smalltalk programmers would welcome - I imagine - Bret ideas without a shred of hesitation, because they are working in a similar way since times immemorial. It's just that there are so few of them and Bret wants to influence programming at large - that's why it seems to be difficult or novel.
This post has too many dashes, it interrupts my reading flow.
I was trying to take "advertising" out of the equation because we were no longer talking about the ethics of the megabox business model but rather what constituted "malware".
Linking Alzheimer's to insulin is a new one to me - I've heard about plaque on the brain and toxic proteins called beta amyloid…the question around all of these is still whether they're a symptom or a cause.

To simplify the path to a cure: they've found the genetic predisposition towards Alzheimer's and dementia, step two will be narrowing down the epigenetic markers that trigger the condition, and step three will be preventing the condition being triggered in the first place. I predict within 10 years we'll have a pill. (I hope! I spend a lot of time in a high care nursing home visiting a much loved family member, and the cost of this devastating disease affects not just the afflicted, but family members and society as a whole as our population ages and resources are stretched).
Deploying apps in Dropbox
Read the mouseover text.
Well, it certainly is the past, I see no problem with it becoming the future. At last.
I do like the idea. Is there any particular focus on genres? Any feedback / recommendation mechanisms?
It is called TrackBack and it is a standard feature on blogs.
HTTP versioning is part of the HTTP protocol which is at the Application Layer in both the Internet Layer Model and the OSI Layer Model.

Educate yourself: http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol
Sounds interesting, I signed up.
What ever happened to app.net? I keep waiting to see it resurface in comments related to Twitter, but it never does. Not a mention of it in any of these comments either.

What gives? End of the hype?
This article is quite thought-provoking. However, I disagree with the notion that there's something wrong with "unlabeled" programs outside a learning environment. To learn a language, you need to associate unfamiliar words with concepts. A text written in French isn't broken because the words aren't all labelled with their English translations, much as that might be a nice UI for people learning the language. Nor do you think in a language by translating each word into English first.

We do a lot of programming using API's we're not yet fluent in (and may never be), and that's why IDE's can be so helpful and this isn't black and white. But at some point you do need to get some core concepts into your head and communicate them in a reasonably terse language.
New CSS Hat version is out, with LESS, SASS Support
99% sure that remark is in regard to C++. If it's about java, then it's just not true...
Micro-virtualization
It says 12 datacenters distributed around the globe.

I think we can safely assume each datacenter holds a dedicated load-balancing server. Let's assume they have only one of these at each datacenter, it gives us 70000 / (4 * 12) = 1460 requests per second per CPU, which is in line with reliably handling over 10,000 request per second of live traffic to WordPress applications from a single server.

and

In April 2008 Automattic converted all WordPress.com load balancers from Pound to NGINX. , which points to the fact that they're only talking about load balancers and they have several of them.

This link implies that one NGINX load-balancing instance cannot handle 70k r/s.
SupportBee looks great, we've been using HelpScout.net for a while and love the shared inbox method of support. It is perfect for small teams. I do wonder how it scales up with dozens of people handling support, it seems like it might result in some clashes.
When I gave my talk on live programming in OOPSLA/Onward! 2007, one of the gang of four (of Design Patterns fame) criticized me on not mentioning smalltalk enough. You know, I think we are all aware of Smalltalk and its ability to reload code on the fly, or the "live" eToys demo Alan Kay was giving in the late 90s/early 00s (I saw it the first time at his ECOOP 2000 banquet speech). But there really is something special in Light Table (and other projects, including my own) that go beyond that; they are working on a practical tool for programmers, they are really focusing on an interactive UX, which to be clear, Smalltalk environments never really had.

Yes, get your history and citation right to avoid being flamed. But no, it didn't end with Smalltalk (or Lisp, or whatever) and we are not just going back to that.
One of the ill advises wandering on the Internet is that you should do whatever it takes to learn about the company’s culture. This is also wrong, and it’s merely a waste of time.

Severely disagree -- I think having an understanding of the company culture is vitally important.

Being a good personality fit is a major component of being the right person for the job, and demonstrating not only your understanding of their current culture, but also how you would be a great fit for that culture will go far in showing why you're the best candidate for a position.
The first twelve paragraphs boil down to:

* Qualified software engineers are hard to find, it's like hunting or detective work, but they do exist. Not really a myth-shattering revelation, I think we all agree with this.

* People are afraid of the unknown. This applies to hiring practices. Sure, nothing new here.

* Interviewers do not ask the right questions. OK, what kinds of questions are "not right", why, and what would be the better approach?

* Companies standards are too high. They do not need a team full of geniuses. Not sure I agree, have any evidence or supporting arguments? It is admittedly hard to measure, but most of the evidence from people who actually work with them points to the 10x or 100x engineer being a reality. Hiring that guy is a much better investment.

The next section (10 paragraphs):

* Candidates can come from anywhere. Sure, nothing new about that.

* Networking and legwork are the staples of a successful career in recruiting. Nothing new here either.

And the next (14):

* For a recruiter, finding an engineer is like finding the "very few really big fish" among a whole bunch of sharks. Wait, doesn't this contradict what we said earlier?

* Those looking to hire need to drop their false requirements like Ivy League schools, moral character. Hm. OK. Other than obviously exceptional anecdotes, why are these bad? Any other false requirements? How are we supposed to filter candidates?

The final section (8 paragraphs):

* Startup culture is often unhealthy. Run it like a business. OK, I suppose I agree with this in principle. But the opposite it true too: business environments can be unhealthy too (Office Space-esque?). What makes each unhealthy and how do we combat this?

* People are afraid of the unknown. Did'nt we already do this one?

* Ageism and sexism are related to this fear. OK, sure. What do we do about it? How do we combat that fear? Also, not new or myth-shattering.

----

The title reads like it should be a persuasive piece, but I think it is mostly fluff and history. It has a number of unsupported positions and suppositions thrown in, but many of the ones that ring true are nothing new and do not "shatter the myth".

What about the real issues that created this so-called myth? How do you address FizzBuzz problem: a majority of applicants fail to meet the most basic of "can you do the job" type of requirements? How do you account for atypically high salaries? What about the large amount of head-hunting happening at places like Google and Facebook? If there is no shortage of good engineers why can't these extremely attractive companies seem to find enough of them?

I have been in several teams full of both, the 10-100x engineers, and the good-enough engineers. The former have outperformed the latter in profit and productivity every time. My experience is that it is very hard to find the engineers that make up the 10-100x teams and this article has done almost nothing to shatter that "myth".
I think this could be fairly easily harnessed in a semi-scalable manner too.

Two computers, A is trusted and B is untrusted. B is networked and hooked up with the rest of your system, A is in a vault and completely air-gapped. A has your wallets.

Give both a printer and webcam/scanner to both. B prints a transaction encoded as a QR Code (or something custom, if those don't hold enough data?) as well as key details (transaction amount say) in giant black bold capitalized English.

The human operator checks the english description for sanity, then gives it to computer A. Computer A reads the QR code, does OCR to confirm the key details (or lets the operator confirm them on the screen) and the QR code match, and preforms the transaction.

This could work at a "local bank branch scale" I think, but getting it up to "website scale" would be... improbable.

Not sure if I would trust this with my money, but it would be fun to implement.

(technically A wouldn't be air-gapped, it would just be operating over a QR-code sneakernet.. Should be reasonable though I think.)
I imagine the following are relevant concerns:

http://en.wikipedia.org/wiki/Sodium_nitrite

http://en.wikipedia.org/wiki/Nitrosamine

http://en.wikipedia.org/wiki/Advanced_glycation_end-product

A hot dog is going to be both high in Sodium nitrite and AGEs for example.
Depending on what your requirements are, you may not need to support every outdated HTTP library in existence.
Well, my line of argument is that any driver in a self-driving car is going to be completely inattentive (think available-to-public, not a test-phase car). For any self-driving car to be considered safe enough for public use, the car will need to be proven absolutely safe in "emergency" situations (i.e., auto-shutoff, etc.).

So, if the car is proven to be absolutely safe, then why do we need a driver? To pull it off the road after it shuts off or stops?
Bret has written an amazing article, but the world he inhabits is soooooooooo far away I can't ever imagine getting there in my lifetime.

True, he doesn't seem afraid to take big leaps. Brilliant, visionary essay. But I don't think it's unrealistic. In my day to day (game dev) I spent very little time optimizing (and very rarely need to write any sort of bit shifting), but instead a huge chunk of development is spent slingshotting variables through loops into abstracted rendering directives. The hardest part in my job is by far understanding and visualizing program flows in my head. From the essay:

Wait. Wait a minute. Were you trying to answer those questions by doing arithmetic in your head? The computer somehow drew that picture, so the computer must have calculated all those scaleFactors itself. Are you seriously recalculating them in your head?

Sadly, yes, very often I am. Depending on the mood I also use a convoluted combination of notebook + pencil, breakpoints, printf statements, and/or isolating the problem by working on a separate program with the problem simplified. And having aids - like some of the great solutions suggested like the timeline and other state/flow displays - would give me tremendous gain today, if they could be integrated in my toolset. I'll give you that I imagine it being quite a bit more challenging technically to make it work with my C/C++/Objective-C environment, but with other more dynamic languages - like Javascript or as suggested: Clojure - I imagine it to be much easier.

This article is by the way, most likely the best argument I've heard so far for me to move to a higher level language. I like how Bret Victor talks about language (and API - see the autocomplete argument) choices as enablers to better environments; I think we instead usually think of language choice as something that mitigates how hard this work is to begin with with the tools we have (see the time and energy we spend in in this community on language choice). If I had access to tools offering this level of abstraction but had to adopt a language that I didn't particularly like, I think the latter would then become be the least of my concerns.
And I would encourage you to use http://PostCongress.io to express your displeasure to your representative.
Vennaver Bush invented the blogosphere :-)

> The historian, with a vast chronological account of a people, parallels it with a skip trail which stops only on the salient items, and can follow at any time contemporary trails which lead him all over civilization at a particular epoch. There is a new profession of trail blazers, those who find delight in the task of establishing useful trails through the enormous mass of the common record.
This reminds me of a browser extension I'd like to see. It could watch over your browsing and construct a graph of the sites you've visited, then allow you to spatially navigate your navigations. Throw in some auto-categorization and you have a nicely organized breadcrumb trail that you can then use to explore new spaces & fill in gaps in your knowledge.
There are plenty of high value targets e.g. Amazon, Apple Store, eBay, banks just to name a few. So to claim that Bitcoin services are unique in any way is just ridiculous.

And just because you get root access to a server does not mean that it should be trivial to gain access to the bitcoins. And why are they being hosted on VPS in the first place ?

The point is still valid that a true PROFESSIONAL is desperately needed.
It's about time that governments actually intervened and forced regulations on any company/entity that deals with Bitcoins.
You didn't mention any VPLs. I would throw in a few...ThingLab, AgentSheets, LabView, Prograph, Fabrik, and so on. These were the original live languages.
It got rejected by Nissan, not sure why...
Age 20 for me.