skysight-inc/HackerNews huggingface dataset:
I watched all his videos and my main take away was that there is actually no high level language besides C (and restricted subsets of C++ that don't use templates) that can be used to tell the computer what to do. Almost every high level language we have already abstracts away the idea that you are trying to control a piece of hardware. Game programmers are in an ideal position to have learned what is actually needed to make talking to a computer more efficient. The fact that J also has the vision to build the language to account for real world development processes is almost like an added bonus.
"Bell, in particular, justified it by claiming that it was unscientific to assume that experimenters didn't have free will. Okay, sure." You make some good points. I am not sure how Bell meant this, but read out of context, this is obviously false. Deterministic modelling (and therefore lack of absolute free will of the components of the system) is a long tradition of science.
> > Some people will point to language design characteristics, which are part of the story, but I think the deeper reason is that ruby does not have a serious corporate sponsor.

> Spot on. Biggest reason why I don't think Ruby/Python will grow bigger than what they are today is this.

While no major corporate sponsors may be the case for Ruby, its not for Python:

https://www.python.org/psf/members/#sponsor-members
This is a big problem for the industry. A developer essentially takes exams, under stressful conditions, every time he or she applies for a new job. However, the developer rarely gets any feedback whatsoever, and often gets a one-line brush off.

I completely understand why. Two very good reasons have been identified in the comments here: 1) it opens the company to litigation, and 2) the company's goal isn't to provide feedback, it's to find good candidates.

Here's the problem, though - none of this makes things any better for a candidate who spent weeks or even months studying, took hours of in person exams, and is brushed off with a one line "not a match at this time". And after a few of these experiences, the candidate starts to give up on trying. Tech interview exams may deter people from interviewing, and may play a role in why developers with potential give up on the field entirely.

http://www.fastcompany.com/3043082/most-creative-people/why-...

High tech employers almost universally claim that there is a severe shortage of candidates, and yet here we have a process that may be deterring developers from interviewing or even remaining in the field. There are solutions out there, but we're not going to get to them by saying "oh well, it would open us up to litigation, and that's not my job anyway". Well, true, you don't owe anyone a job or feedback, but the world sure doesn't owe high tech employers all the developers they want to hire either.

So far, I really don't get the sense that the high tech industry has come to terms with the depth of its own role in why they are having so much trouble hiring.
You "should" do what the license requires. Anything more is nice, but charity.
I think he's just thinking about it practically. Its potentially not worth your time and effort as a business owner to go after that tiny minority who abuse the free trials.
Because you have to maintain the app against known vulnerabilities. And in even a single year previous version of out app had multiple gems with vulnerabilities having to do a major version upgrade and I had to scrap the whole thing because older gems with fixes where unavailable or didn't build on modern rail/os

The whole ecosystem is frankly a mess, you need to stay bleeding edge all the time to have a chance to long term maintenance and suffer any capricious api update each of your dependency might have because staying on old release and relying on backports is not worth it.

I'm not paid to clean other people libraries. If the idea of open source is that, then no thanks. Core business is not maintenance and costs like those do kill startups.
Thanks a bunch for that reply and I too love discussing this material and I don't think we have much of a disagreement. What I am advocating is having answers to these basic questions like, "why have a reserve ratio?" So many times, even these basic questions haven't been thoroughly explored through debate so that people, new to the subject matter, don't have anywhere to go for context (except people shouting at each other).

With regard to your other reply I have some questions:

> I'm advocating a 100% reserve ratio on demand deposits only, duration matching of non-demand deposits and a citizens dividend for economic stimulus. Ain't no school gonna teach you that. :)

These would be demand deposits paying zero interest (not that they're paying much more than that today :) ?

"duration matching" sounds like those deposits are participants in the loan (e.g. share the risk)?

"citizens dividend for economic stimulus" not sure about this one?
The Cookie Butter Patent Wars
I didn't get the example in section "PeachPy as Instruction Encoder" to work for arm on the linked github version, the version currently on pypi, or the older bitbucket version. If the module loads at all, it seems to always complain about lacking function context.
Shameless plug: https://github.com/raksoras/luaw
I encourage you to lift weights. It's a different type of stress that your body is more inclined to deal with in a positive fashion; this translates to your mood positively.

Test getting more sleep to see what happens—doesn't hurt to test! I have a friend who requires 9 hours a day to feel fully rested.

I neglected to mention diet previously, but make sure you regulate your calories and macro-nutrients, and take a multi-vitamin (I take Optimum Nutrition's Opti-Men) and a fish oil (I take Minami's MorEPA).

With supplements, you get what you pay for; if your multi-vitamin serving is only one pill, it's probably not a very high quality. You don't have to go on a "diet" really, but keep track of what goes into your body and over time you'll get a bearing for what makes you feel best—added bonus is that the act of tracking nutrition typically causes people to eat a bit healthier. Sounds like your diet isn't bad though.

Mentally, I approach a "bad day" by taking a step back (sometimes literally) and telling myself the chemicals in my body are a bit off. A vast majority of the time, this is enough to calm down the dissonance in my head that can lead to lethargic or aggressive behaviors. Sometimes it's because I need to eat or hydrate; other times a 15-30 minute walk 'resets' me mentally.

Worth noting: a poor night's sleep can affect me personally for 2-3 days afterward. Sometimes I feel perfect the day after, only to feel a massive drop in energy the next.

It's amazing how powerful acknowledging cognitive dissonance is for eliminating said dissonance.

Finally, there's also the possibility you are carrying a disease or disorder you're unaware of. I personally have an auto-immune disease which caused me to feel very lethargic in spite of being athletic and having a clean diet and sleep schedule. As soon as I got my thyroid in check (hypothyroidism, or 'Hashimoto's Thyroiditis'), the lethargic spurts dissipated.
They have a drive-thru? :)
One of the best reads on this : http://www.amazon.com/How-Sell-Lobster-Bill-Bishop/dp/097310...
Material Design added to Onsen front-end framework
[Libertarians are the political group with the highest IQ]
Nice fact.
I've been bugged by the "Verified by Visa" thing in the last month when trying to add Skype credit for my parents. Completely stupid implementation that didn't even work; I clicked "cancel" and my Skype transaction still went through.
That's kind of like saying it's absurd to switch to a new social network because it is popular... as with social networks, languages/platforms are more useful when more people use and contribute to them.

Good libraries cover a multitude of language feature sins.
Well.... yes, he's obviously built his clock out of an existing clock, but he's also 14, and casemodding a piece of old junk seems like an entirely age-appropriate project. I don't know whether he represented it as being a more original piece of work than it actually was, but who cares if he did? Kids spend half their time in fantasyland anyway, and he's probably used to making things that the adults around him don't really understand any more than he does.

I "built a stereo" once, when I was around that age, by taking apart a stereo I'd picked up at a garage sale and putting it back together in a different box. I added some toggle switches and an extra bank of speaker outs and a little amp which was another garage sale find, and that was my four-way "surround sound" bedroom stereo. Could I have actually built a stereo from bare components? Hell no! I didn't know anything yet! I'd never waste my time on such a trivial project now, but I still think it was a cool effort for a young teenager trying to get the hang of electronics.
Ni dependency list: Shrubbery
How did you find or negotiate such an arrangement?

There seem to be very few non-40-hour software engineering positions available, even though many of us would happily trade away some salary for quality of life.
Everyone forgets that Gevent has been around for years, and lets you write completely synchronous looking async code.
> The most compelling reason not to use Ruby for a new company or product in an existing company is that the talent of the average Ruby programmer has dropped drastically in recent years.

That's a pretty good reason if your selection method is substantially equivalent to choosing "X programmers" (for whatever X is your technology base) at random.

But, beyond that, I don't see that it matters.
Let's Play 'Refactor the Mega-Controller' with Andy Matuschak
Powerful Xcode 7 Debugging
If all your old gems had vulnerabilities, what makes you think bleeding edge ones didn't?

Spoiler: the difference is, the new ones' bugs just aren't widely known yet.
Mental labor is hard, but learning I find fairly easy and quite relaxing. I only do about 2 hours or so productive mental labor / output a day, the rest of it I spend self training and learning. I honestly can't imagine how far I would be behind my peers if I didn't do that.

Sometimes I do a fair amount of training / mentoring for junior engineers as well. That can be pretty relaxing too and productive for the company.
It was a gradual change, but the big blow was probably Wickard, which essentially turned the states into satrapies of the federal government.
CakePHP is a clone, or at least so heavily inspired by it may as well be.

Django does its own thing, and while it has borrowed ideas, it is an entirely different beast.
if elb would use nginx, that wouldn't be a problem.
You can sell closed platforms which depending on gpl / agpl code and you would not need to release any code if you don't modify it.
Why? "Fine lady" implies that he and she work together, which probably fits the "ecosystem" of programming languages and programmers better. Unlike a mainly static inanimate asset like a car.
King's bloodline rules because god say so...
You're not a free man, you're a subject.

Do you see that as "legitimate"?
Sure, if you like to read while you're wading through butter. It's a usability thing.

Anyways, they do it on their whole site, and it's more cohesive on the other pages. It's better to view the release notes in readerview I guess.
Cool! It looks like they're using leaflet and hosting their own tile server from Open Street Map data. I really like that they opened up how to connect to their tile server (thanks to chippy for the link: https://www.mediawiki.org/wiki/Maps ). When I was looking at options for creating a side project with open street map data earlier I ended up using Mapquest's open data api because Google maps had API restrictions after a number of calls and it was easy to integrate with leaflet, but if I was making it again I would consider using wikimedia's option. (Fyi, the sideproject is a static site hosted at http://newsatlas.io - it takes a news/rss feed & attempts to parse the location client side by parsing the news article's summary text and displaying the location on a map - it was written in JS with angular and leaflet as dependencies - hosted on S3).
No, him only getting $700 illegally is capitalism for you.
A lot of companies basically hire in that way when their hiring means are through recruiters/job ads. Very few companies have the time/diligence or live in an area with enough of a developer pool to be finnicky about who they hire. Obviously there are ways (remote) to offset this but none of this addresses the fact of my initial statement.
Collaborative live coding in VR with three.js
> software engineering negotiations aren't adversarial

There's a certain book you should go and read... I think the fact that it does exist is proof itself of how adversarial relationships can get in Software Engineering: http://www.amazon.com/Death-March-Edition-Edward-Yourdon/dp/...

Metaphorically speaking, the only way a negotiation does not end up in a fight is when one side sucker-punches the other.
Small companies can be flexible. Large companies have to deal with rules written by people too far removed from your boss.
Not sure about the cheap aspect tho, in my area rails developers are one of most well paid.
If your content is fairly static, everything will scale.
There are many good reasons for choosing mercator, the best one being that it is mostly conformal.
> Some people say "verbose" I'd say "explicit than implicit" (or code is written once to be read multiple times)

That's also an argument against verbose. Verbosity hurts on each re-reading. (As does improper terseness.)
Following the bliss isn't supposed to pay the bills.

Following the bliss increases skill-sets, creates necessary connections between persons, and gives the bliss-seeker an out. Out is good.

The bliss is not the means to an end. The bliss is self serving and self improving, while also finding an escape from the daily grind and its deleterious effects.

Follow your bliss, by all means. But, at the same time, realize that it's not the end goal. You're not learning programming to make money. You're learning programming because you enjoy it, and or it increases your skill-sets.

Also, programming isn't bliss. Programming is an addiction. It's a sometime beneficial addiction, but an addiction nonetheless. Something to consider.
Thanks. I saw the mention of Windows XP and was a little confused about that, seems a little strange to spend resources on an old and unsupported platform imho.
> there is no reason to believe economies of scale exist for protective agencies

Seriously? There is a huge advantage to being the biggest, baddest agency. If you're substantially larger than the competition you just go to them and say "hi there, give me all your stuff or we kill all of you and your clients".

> It is unlikely that the agencies will fight with one another, as they have strong disincentives

You're completely leaving out the incredibly strong incentive of "Give me your stuff or I kill you". It's infinite profit!

There are two ways history has proven to prevent "Hobbesian War" as he calls it: One incredibly powerful military hegemony, or a delicate balance of multiple exactly equally powerful military hegemonies. Anytime neither of those exist in an area, you get war because it's a lot easier to take someone else's stuff than it is to make your own. To think otherwise is hilariously naiive.
Does anybody know which framework they were both inspired by at the time? I'd guess that the concept of MVC has been around for a long time but what kicked off the popularity in 2005?

CakePHP was released before both of them, in 2005 too.
i'm using it and it's nice as you said. i'm not a node expert yet, this is my first large project. i'm sure i'll get more fluent as i go along but this programming style was an unanticipated twist in the road.
In case you're wondering what this is about: the scale of Wikipedia makes it difficult to just drop in a third-party OSM tiling service, so they're rolling their own map rendering process using OSM data. This is a beta of the rendered tiles, displayed inside Leaflet.

If you're into maps and this kind of thing, I highly recommend checking out LocalWiki (https://localwiki.org) too!
AFAIK Nodejs is pretty damn memory intensive and does not do CPU tasks good as well. I believe Nodejs popularity is pure overhype.

Like no other language has async capabilities and implement it 10 times better cought Go, C# (and probably many others that I don't know)...
I still think Beating the Averages is an incredibly relevant essay for language choice.

http://www.paulgraham.com/avg.html

I couldn't be happier with Clojure and I don't really know what else I could want.
I Smoke with Snoop Dogg
"Couldn't afford" is a loaded term. I can afford a helicopter ride home, but I don't value its utility enough to pay what's being asked. Isn't that how prices are supposed to work?
Dynamic friction with dark matter? Interaction with the accretion disk?
But it wouldn't fool any text editor, right? Or even less?
First woman in space recalls mission's teething troubles
> Serious developers, particularly ones with CS degrees, look down on bootcamp programs as “programming light”. I’ve noticed a disturbing trend of experienced developers not wanting to work with rails now that it’s been “polluted” by this reputation.

In my book, this "jackass filter" is a feature, not a bug.

---

WRT performance, the actual performance in benchmarks of the language is, for the most part, thoroughly irrelevant in most web applications. You're going to be spending most of your time waiting on I/O and network calls. Making real-world applications fast consists mostly of in-memory caching, not blocking on I/O, and doing things in parallel. That Node was designed primarily around nonblocking I/O has far more bearing on real-world performance than any JS vs. Ruby benchmark.

I don't love Ruby, but Rails removes a dozen time-consuming decisions from the space between "starting an app" and "shipping an app" and leaves you building on a stack that is in use by a relatively large number of developers, which means that somebody has probably run into framework bugs before you did. And I've yet to see anything mount a serious challenge. Which is a shame, b/c I don't love Ruby, I don't love Rails, but that it's mature enough that most of the design WTFs have disappeared by now makes it hard to choose something else.
I don't know the pre-1.0 history for Django, but I started with rails 0.7, and 0.8 was [released](https://rubygems.org/gems/rails/versions) October 2004, with much of the core architecture in place.
> you need to stay bleeding edge all the time to have a chance to long term maintenance

yeah, github is a perfect example or that, right? </irony>
Cool! "The GitHub API is rate-limited, and this makes a lot of API calls. Don't be surprised if things start to fall apart under load." => consider self hosting with our GitLab
Cake was released first, but I'm not sure that it looked much like later Cake did. It's been too long to remember.
The author cites a graph of declining Google searches for "Ruby on Rails" relative to "Node.js" and then follows up with the statement:

You can see how rails is losing mindshare to newer frameworks.

I don't really think this proves anything. People who are already familiar with something aren't going to perform a vanilla Google search for it. For example, if I'm looking for a car, I'm not likely to perform a search for "automobile" but after overhearing somebody mention something called a Model S I might search for that.

A quick anecdote- I first learned about RoR circa 2008 from a colleague and performed a Google search for "Ruby on Rails" to find out what he was talking about. Fast forward three years and I was writing several web applications in it and don't recall ever performing that search again.

A far better metric I believe would be to perform an analysis of Stack Overflow questions by language and see whether it coincides with the chart the author cites.
If you're dedicated enough to follow the bliss, it will pay your bills, and also do the other things. If you have failed personally, please don't discourage others.

Programming can be bliss, at least seeing the results. I mean, why else would anybody program? Just for the money?
You might get over it! I feel I have, and now see callbacks as suggestions of where to break my code apart. For example, callbacks nested more more than a two deep are usually a remonder that I'm really trying to describe a series of steps with a common error and success handler, and the library "async" has a method called waterfall that does exactly this. Naming those steps keeps them simple, exposes commmonalities, and often leads to reuse.

That said, the thrust of this article is that you should make your technical decisions based on the absolute most trending thing at the moment, and I think that's bogus. Plain old syncronous programming has its place.
Still 12% market share!

http://netmarketshare.com/operating-system-market-share.aspx...
fair enough - if you really want to save money - youd go with php
I understand that, but how the company organize itself to reward managers with that kind of goals ? What kind of mechanisms sets in place to force managers to minimize expenses happily?
If the recipe is licensed with GPL, then yes.
Interesting interview with the same guy (audio).

http://voicesofvr.com/214-using-three-js-to-create-social-vr...
Talent that comes in because a stack is hot/trendy are there by virtue that they lack the experience to know it's nothing knew. They haven't seen other hot/trendy stacks fail yet.

Meaning they probably also lack experience to make decisions that avoid turning greenfields into a muddy hell. No thanks.
Couple of issues I have with this article

1 - This decisions seems based more on the fact that Rails isn't as trendy as it used to be

2 - Some of these benchmarks for performance are pitting interpreted languages against compiled languages which will explain some of the performance difference

3 - Saying that Rails is static makes me think that the author would prefer a NodeJS like situation where every release might contain backwards-incompatible changes

4 - You don't future proof your application by trying to predict what will be popular in the future, you future proof by investing in stable technology and ensuring you have the talent pool to maintain it
شركة تنظيف موكيت بالرياض
I think the technical aspects discussed in the article are there not to debate the relative merits of technologies but to support the main line of reasoning which is social in nature. It boils down to:

1. Use the platform which is gaining mindshare because some years down the road you will be hiring engineers and you will want to look hip not obsolete.

2. Use the platform with solid corporate backing so that someone will support it and help it mature.

Seems very reasonable to me. Smaller companies need some strong selling points to compete with the larger firms on the hiring market and hip technology can be one of them. But the hip technology needs to actually work so better have someone with lots of resources backing it.
Right. Just finding something that you can build on (and get started yesterday) with the team you have. Of course, it doesn't hurt to pick from one of the top 10 languages so that, if you do succeed, you have a talent pool to pull from.

But this is definitely a case of the perfect being the enemy of the good.