As a person who has been censored by Facebook for wrongthink, watching them stare down the barrel of Apple "being a private company, and doing what they want" is like watching a kid step on a lego brick that he refused to clean up.
431 karma · joined December 2, 2010
This was the hacker ethos from the 90s. Where did that go?
(The definition of "inappropriate" being "whatever people on Twitter dislike today".)
OpenEMR exists because during the summer of 2000, with the dot-com boom in full swing on the left side of the United States, four high school students in Cheshire, Connecticut spent the humid part of our year in a basement writing PHP code to manage documents for an internal medicine practice that belonged to one of the students' mothers.
It worked well enough. The four of us were all college-bound in different directions, so instead of trying to sell the software to medical practices, we released it under the GPL. Open source contributors took it from there.
A very well-researched book that challenges, adequately in my opinion, some of the fundamental assumptions about nuclear weapons. First and foremost, that "the atomic bombs ended the war with Japan".
J. Robert Oppenheimer and Leslie Groves were a fascinating team, Oppenheimer being a physicist and Groves an Army general.
A must for anyone in technical management.
This is a decent way of mixing an event loop and multi-core processing, but with Node, you're forced to marry the HTTP server to the application, which is a dangerously tight coupling of responsibilities.
If you really want to do something silly like write your application in server-side JS because you're familiar with it, then it should be through some interface like WSGI in Python (or even CGI in days of yore), which properly separates HTTP connection handling from application serving.
So Node is reduced to the trivial work? Then why make it unnecessarily hard on yourself?
> I still don't know why people are so maximist with their tools.
Because moving parts = risk.
What I was showing was that if your request handler does a nontrivial amount of CPU work, it will hold up the event loop and kill any "scalability" you think you're getting from Node.
If you Node guys were really that irritated by this, you're going to be super pissed when you learn how computers work.
I ain't even mad.
There was some really horrific things in there - this was before I knew what a JOIN was, so I'm glad some of my shame is long gone.
Still, it's awesome to see that the project is still alive.
http://armsofamerica.com/ak47762flatwithrailstrunnionholes19...
You do not need a license or a permit, just access to machine tools. Oh, and $22 for the flat.
> Disaster: MySQL 5.5
> MySQL
I found your problem right here.