skysight-inc/HackerNews huggingface dataset:
My wife and I were just talking about this today but in a different context. She is a recent PhD grad and the new PhD students entering her research group email her quite often asking things like "I am TAing course X and I heard you did as well, what should I be doing?" They ask one sentence questions and expect some rich essay of an answer that is going to solve all of their problems. Just lazy if you ask me. So this pattern seems to extend beyond just software (as pointed out in the original post).
One perspective is you pay to have the adverts removed; the other is Amazon sells an optional lower-price kindle at cost and subsidizes it with advertising.
Japanese is a terrible language. I tried speaking it for a while, but I can just get my ideas across so much more easily in English. It's just easier. This must be because Japanese is terrible.

That seems to be the basic reasoning at work here.
Well it looks like they have an approval process so I feel that they can easily ban users that abuse their service. With that said, I'm sure that's an issue they will have to eventually face, but that is the liability that all hosting companies have.
مشاهدة مسلسل حريم السلطان 2 الحلقة 75
مشاهدة مسلسل حريم السلطان 2 الحلقة 75

المسلسل التركي مسلسل حريم السلطان الجزء 2 الحلقة 75

مسلسل حريم السلطان الجزء الثاني الحلقة 75 اونلاين

مشاهدة مسلسل حريم السلطان الحلقة 75 - تركي مدبلج
Cannot agree more with Tom Friedman and Van Ton-Quinlivan on this subject. Job skills are changing so fast that the only way to stay relevant is to be a continuous learner. I want to add that people need help figuring what to learn. This is why LearnUp.me (I work there) is working with California Community Colleges to help those that are "ready soon" and "far from ready" figure out what they need to learn for open jobs.
Just today I devised a pretty solid method to build a fairly complex node.js app while keeping it simple, maintainable and scalable.

I like the way node kind of enforces modularity, but for something as complex as the backend (super-flexible api for a frontend dbms) required for my project, it would save a lot of time/effort/ugliness-of-code to have a few objects on the global scope while allowing individual parts to be split up into their own files; e.g., a few utility functions, String/Array.prototype functions, a socket.io instance, and a redis client instance, among other things.

And to make things manageable and more extensible all while minimizing duplicate code, I ended up using John Resig's "Simple Javascript Inheritance": http://ejohn.org/blog/simple-javascript-inheritance/. I like being able to simply call Class.extend({}) to create/extend any class with access to its "super" functions. Each class is contained within its own file, of course.

The method is pretty simple:
1) Organize and order the files like you would on a client (web browser) where "global" variables are allowed.
2) Use some program to concatenate the files in the correct order into a single node app.js file for testing or production.

I'm currently using a batch script (yes, I use Windows :P) that looks something like this:

del app.js
type global.js >> app.js
type appBegin.js >> app.js
type loggur.js >> app.js
type classes\Class.js >> app.js
type classes\Client.js >> app.js
type get.js >> app.js
type post.js >> app.js
type set.js >> app.js
type socketsOn.js >> app.js
type appEnd.js >> app.js

Don't get me wrong, node's module system is used when it makes the most sense. But for what I need to do, this works perfectly. It doesn't promote spaghetti code the least bit; everything is easy to read and follow (could even call the code pretty!); it's 100% clear which objects are shared (especially since most files contain a single object or class); and as long as the method is used consistently, you get all the benefits of node/socket.io while maintaining cleanliness and scalability.
There seems to be confusion between the filesystem and the metadata.

The filesystem is for storage... it's only important to be able to group tracks together in small batches (releases - albums/singles/EPs) to be able to manage the files

The metadata is for searching, grouping and locating in your music player.

With that in mind, a lot of the problems he's cited vanish.

I have ~84,000 tracks from over 6,000 albums. The result of a 5 year ripping spree after a decade worked in the music industry.

Every track, with no exception, has been scanned by MusicBrainz Picard, had it's PUID generated and meta data normalised.

I've allowed my definition of genre be influenced by general opinion... I simply learned how the mass tag things.

The result is that I can find everything in my interface (Squeezebox) within seconds.

The file storage I only need to care about for management of the files, and copying to my portable player or deleting old releases (which I do rarely, but it does happen).

The file storage starts with file type:

MP3|FLAC|FLAC_9624

Below those are folders for high level type of content:

Artists|Classical|Spoken Word|Compilations|Soundtracks

Within Artists I used

Artist/Release Name[ - Catalogue Number]/[Volume/][Media/]Track Number - Track Name

I only fill in catalogue number if I have two versions of the same titled release... i.e. Quadrophenia by The Who I have a couple of versions of.

I only fill out Volume if this is a multi-volume release.

I only fill out Media if this is a release that spans multiple CDs or DVDs.

So the short version of that might be:

FLAC/Artists/The Who/A Quick One/02 - Boris the Spider.flac

And a long version might look like:

FLAC/Artists/The Who/Quadrophenia - Polydor 2777840/CD2/01 - 5.15.flac

I have no problem at all storing and finding tracks, and I've no problem at all searching for tracks.

One of the good things about Squeezebox is that when you search it searches all metadata and the full file path. So a search for "quadro poly" would turn up the Polydor version of Quadrophenia.
So you've never bought a newspaper or magazine? Bought a ticket for a sports competition? Pay for a TV subscription? Watched a film with product placement in it? Ever seen product advertising in an aeroplane?

Ever bought a paperback book? They all come with adverts for other book at the back, loose-leaf inserts etc.

The concept of partly subsidizing the cost with additional advertising is hardly a new business idea. It would seem almost impossible to never pay for a product with ads as you claim.
Node.js is one of the worst things to happen to the software industry in recent times, a whole generation of programmers are being taught the worst of all ways of doing concurrency, in a system that doesn't scale either in performance or project size and with one of the languages most plagued by pitfalls ever created.

JavaScript was already painful enough in the browser, why on earth anyone ever thought it was a good idea to use it on the server boggles the mind.

We will be paying the price of this misguided hyped fad for decades to come.

Of all the ways of doing concurrency, callbacks are by far the worst, Twisted was plagued by them and is the main reason why it failed, and that was with a much more sane and reasonable language like Python (stackless Python was a much better alternative and used a model similar to Go's CSP).

And the sad thing is that there are much better alternatives around with much more sound models and environments, Erlang and Go are the two obvious examples, and that is for the highly specialized situations where you have great concurrency needs, for any other problem anything else will be much better than Node.js, even PHP.
Offtop: Why clicking your link leads to downloading an application on Nexus7?
No, because the differentia of the definition of cloning does not reference maturity (age).
Sounds like an answer from an affluent, white male college student to me!
I recently heard in a documentary, that John Lennon detuned his Guitar a bit all the time.
Those are the problems of giving free money, they will give money to people that can't pay it back and will inflationate the cost of services for all, because demand has been artificially expanded.

The law of unintended consequences. You make something to "help" and you destroy society in the process.

I can't understand that someone who is $55.000 in debt has a SUV, like the woman in the article. I prefer to live poor but free, in fact I had to in the past.

In Spain something similar happened with real state. In the bubble I saw banks giving 300.000 euros to a 18year old with a yet to pay Mercedes at the door. Those people will pay refinancing their debt. This made houses prices to skyrocket. Now this banks needs to be "saved".
I understand node is quite good at those scenarios but is there any real advantage over say Ruby/EventMachine or Python/Twisted or if you're serious about it scaling, Erlang/OTP? Evented systems are great for those scenarios but I can't work out if there's some secret sauce in Node I'm missing or whether there's a lot of excitement from people that don't realise there are mature solutions to those scenarios in other languages.
Whatever scheme it was encrypted with will then have to stand up to decades of advances in algorithms and computing technology.

So will the block or stream cipher you encrypted the data with.

Quantum computers will probably break most currently used factoring-based schemes (including elliptic) eventually

That seems extremely optimistic to me. Given the current state of the technology, it's a little like an astronomer discovering a distant new star and then promising to open suntan parlors from its concentrated rays.

Try this thought experiment: For a given set of security and speed requirements, take the money you would spend on a pair of quantum key exchange devices and spend it instead on accelerator hardware for non-quantum ECDH operations. How much longer (and more secure and reliable) can we make the key exchange parameters with this conventional hardware within the same time limits?
What bothered me is that I couldn't find a way to find out what code had triggered an event, or what listener was attached where. So, suddenly you're getting an error in code and you can't figure out why it's even being called, because it was attached from one of eight libraries that you picked up as to not reinvent the wheel.

...and grep emit isn't an effective solution. :)

I put a question up at SO and never received a response. http://stackoverflow.com/questions/12215273/how-are-event-tr... -- the problem itself I finally worked through, but then I ran into another. And another. And while I know my fair share of JS, and have no problem with async programming, node.js still felt awkward after a month. So long as I was in my own code, I was fine, but reasoning about code I hadn't written was painful not because of the language, but because of the flow it took.
Yes and yes, but not necessarily. Customers do not have perfect information about the market, and especially not about the inner workings of your company.
I think at least part of this phenomenon can be attributed to what I call the StackOverflow effect, that being point-based incentives. People on SO answer questions much of the time because they believe their answer will earn them karma (or whatever it's called on SO). In fact, I'd be lying if I said Hacker News karma didn't have at least a little influence on my decision to actually take the time to write this comment.

Because of the StackOverflow Effect, people will choose to answer even the worst questions as if they're fair play, simply because they have an answer they believe will earn them a couple points. If points were not involved, I'm willing to bet a lot more people would get told off for their poor quality questions, and a lot less people would continue to post them.
Node is not for everybody. Node is not for everything.

2 hasenj: try using coffeescript to get expressiveness if you're coming from Python(like I do). You'll be much more comfortable with it. Especially when you're using it for both frontend and backend.

Node was a "why not?" choice for my last small inhouse realtime analytics. I could write it in python, but I've been writing LOTS of CoffeeScript recently so I've tried to go with node and redis. And it was a perfect fit for this task.

I'm pretty sure I wont use it for some complex business logic or number crunching. But that's not because I'm afraid to loose maintainability or peace of mind. It's because that would be just stupid, there is a lot of better tools for this. You should keep in mind whats your platform nature, whats it good for.

Every contending platform or language has it tradeoffs. I like ErlangVM features and philosophy, but I can't pass over the language weirdness. And VM speed sucks. And the community is much smaller. Nodejs is booming, you should agree on that.

Go is great, I'm planning to use it for my next "why not?" project. But it takes a lot of things you love in dynamic languages away. You choose between "program performance vs programmer performance". And again, the community and adoption is taking its first babysteps.
Everything is terrible unless it fits. Period.
If anything Node is much more limited than the alternatives, both because of the language it uses, and because of limitations of the implementation, which basically (rather ugly hacks aside) doesn't scale at all beyond one core, and if any of your code turns out to be CPU bound, your performance goes right out of the window.

Go and Erlang are much better both in the concurrency models they provide and in their performance and scalability. Not to mention they are real languages carefully designed over many years by talented language designers, not the result of unfortunate accidents of history hacked up in two weeks like JavaScript.
I think one reason the conclusion doesn't satisfy is because the question of "What do we do in a post-work world?" is horribly open ended. I believe the question is relevant as technology and automation increasingly penetrate manufacturing, business administration, and (soon to be) transportation to name a few.

To put it bluntly, for most programmers, it's our job to put others out of a job. The things we build make it easier to automate, streamline, and other buzzwords, which generally means that a company doesn't have to keep as many workers on the payroll. The business administration side is fairly decimated, and I believe the falling prices of 3D printers and robotized factories will lead to automated on-demand manufacturing. This means more people won't be able to find work, which will depress the demand for products. It's an interesting problem.

> shouldn't it follow that there are potentially a myriad of possible projects which might be amazing and worthwhile things to build, even if they obviously won't turn a profit?

Yes. I would argue that the artifacts of human culture (portraits, frescoes, symphonies, statues, etc), in many cases, have no obvious financial benefit at the time. They exist because they appeal to our aesthetic side and the creators lived at the pleasure of rich sponsors.

Many programs of the Open Source universe started as an annoyance or a fling without any thought of profitability. Several tech companies started as research projects or "the itch" with no money in sight. Much of our software is still built pro-bono by an army of volunteers.

In this way programming starts to mirror the art world. The mindset to adopt is to create for the sake of creating, and letting others critique the work. Think about a programmer version of art hostels in Paris of early 20th century. In fact, go watch Midnight in Paris and see if you can picture (hah!) programmers drinking and talking instead of artists and writers. There are programmers out there like that, like Mr. Bellard and his DIY cell phone base station [1] or John Carmack's Armadillo Aerospace [2]. They build for the sake of building something cool.

[1]: http://news.ycombinator.com/item?id=4469424
[2]: http://en.wikipedia.org/wiki/John_carmack#Armadillo_Aerospac...

For your second question, I can only assume that many entrepreneurs enjoy the challenge of building successful companies. Being wildly successful means they have additional capital and can chase larger and more complex problems. SpaceX comes to mind. Granted I can't think of a founder that was very successful start something trivial (I'm sure they're out there).
Giving out loans to people who shouldn't get them because they can't repay them? Sounds familiar
I honestly do not - I fear for China.

Over the past 150 years this past generation is the only one not to suffer some horrific war, genocide or starvation. China has a revolt somewhere almost daily, it has none of the institutions we are pretty sure are necessary to managing power (independent judiciary, enforceable contracts etc) and has worrying signs of becoming a mafia state, with none of the benefits of one guy in charge ala Putin .

So basically there are a huge number of ways it can go wrong, very little to hold it together except the fear that if we don't keep on this course it will be a lot worse.
Is your tablet password “235673″? I think I saw it on the news yesterday.
I don't think they grew back; they are probably the result of modern irrigation.
> why iPhone was so popular in Japan while the bleeding edge Japanese headsets were relegated to the home market? Surely it wasn't just marketing on apples part.

[Not sure what you mean by "relegated" to the home market -- Japanese phone makers have never shown much interest in foreign markets, because their attention was pretty fully occupied with the huge Japanese domestic market which they understood well.]

Of course the iphone wasn't just a marketing success. As I noted, it really did offer a vastly improved experience over previous (and current non-smartphones) Japanese phones, which were often very functional, but confusing, inconsistent, etc. [This isn't really just a phone thing... Most Japanese software, especially that written by hardware manufacturers, has pretty much always been like that.]

Worse, there was a tendency to try to nickel-and-dime the user to death, attempting to charge for all sorts of little services and features one could access from phones, often without a good indicator of how much the actual cost would be. The iphone/android's concept of mostly limiting such payment to a well-defined place (the app-store) is pretty refreshing by contrast.

Until the iphone showed up, makers concentrated mostly on adding new "functionality," without putting much effort into actually improving the base experience. There was little incentive for them to do differently, because everybody else was doing the same thing, and Japanese companies tend to have both a laser-like focus on constant incremental improvements and an aversion to riskier large scale changes.

The iphone upset this cozy little arrangement, and android has allowed other makers to react to it pretty quickly. Still, smartphone adoption in Japan is only half that in the U.S. or the U.K., which I suppose is due to the more functional nature of Japanese non-smartphones compared to those in other countries.

But, anyway, yeah, the iphone changed things; my point was only that Apple's innovations were mostly in software, and less so in hardware.
All I know that whenever I needed a help, the SO community generously came forward and helped me. Thanks Joel and His Team
Why am I getting downvoted for this? I am not making any commentary on price discrimination but instead, saying that the artificially created scenario could at least be more approachable for readers.
Do you mean this SFS? http://www.fs.net/

That appears to literally be the official website.

Sorry, but your post just sounds like "get off my lawn!" But good luck trying to convince everyone to write their web apps in C++.
You go to a room and are given a two page contract, written in fifth grade English.
صور ميلا بنت نانسى عجرام - منتديات حركة
Just a little while ago a family member who has signed up for a Coursera statistics course was asking if I could help "Download an R program". It took me a minute to figure out she really did mean the programming language, she didn't tell me straight off it was a statistics course, and she's about the last person I would have expected to take a course that involved programming of any sort. But the class does say it's "quite literally for everyone", so good on her.

When I asked if they have instructions on how to do that in the course material, she told me there's a thing that says "click here to download" but she hadn't tried it yet. She literally hadn't even tried clicking the thing that said it did exactly what she was asking me to help her do. Not "I tried it and I got an error" or even "I tried it and it didn't work", or better yet, "I downloaded something and don't know what do with it" no, not even tried.

I'm now dying of curiosity to find out what happens the first time she has to actually write code vs. just typing stuff in she's been handed. I might have to send her this article, we'll see! I've never done any R programming, though it now seems inevitable that I will be doing some in the near future.
Google-backed Pashash wins Startup World: Cape Town
By messes up terminal history do you mean when you push up in terminal the previous lines that show up are rendered badly or that your actual history is effected in some way?
I'm going to start by saying I really don't know, but here are my guesses. It's all about the way they collect data for advertising and for analytics.

For example, Twitter gives you the option to tailor itself (its ads?) based on the websites you visit. http://i.imgur.com/EWU2l.png
Facebook tracks you with their Like button, I imagine Twitter is doing something similar. And while they can track you while logged out, they would probably be better off if they could tie that information to all the followers, followees, and behaviors associated with an account.

My second example is embedded tweets. Although I can't find the article or blog post, I remember seeing a while back that Twitter wanted to start pushing people to use their embedded tweets rather than images.
https://dev.twitter.com/docs/embedded-tweets

Aside from providing the user with a better experience (like being able to click on the users' names to go to their profiles) or letting Twitter control the user experience, this also allows Twitter to embed tracking pixels.
Highlighted in this picture are the tracking pixels loaded in Chrome when I embedded the latest tweet from the Twitter account on a web page. http://i.imgur.com/SeVaQ.png

And this next example wasn't made for the web, but it plays into how they're trying to boost their own analaytics. While wrapping every link with their t.co url shortener does give them control over thing like killing spam links, it also lets them track which links became popular from which tweets. That's why they'll still use their t.co links on already short links (reminder: in my opinion). I believe this solution works out for them because if someone clicks a link from their official Android app or from a 3rd party app like MetroTwit, they can still track the referral came from a tweet.

To summarize, I believe they're trying to boost their advertising relevance and trying to improve their analytics offerings to business accounts by using browser cookies.
"are you doing that out of a need to have control and order or because you really think it is a worthwhile use of your time?" both actually. For example I also do some woodworking, bicycle maintenance etc, requiring a bunch of tools. When starting some work I really like that I can think of any tool and just pick it up without having to look for it, could even say it makes me happy, while at the same time not finding something can seriously get on my nerves. At the same time, sometimes when putting back all tools after some job, I really think "ha, this may take some time now, but it will be worth it next time". Does all this affect my life? Not really since I'm used to it and it takes only a fraction of time/thinking in comparision with the rest of it.