skysight-inc/HackerNews huggingface dataset:
Or, to get a continuous loop with timestamps:

function talk { while read line ; do echo "$USER [`date +%T`]: $line" >> $talkfile ; done }
Taking that to the logical conclusion, if everyone spent 50 years doing hard labor in jail I'm pretty sure the rate of violence outside jail would decrease even more.

I'm not sure that putting more people in jail for longer is a great solution.
1) Paul Irish is a former jQuery team member and he has blog entries about how much he's learned from reading jQuery's source code, not sure exactly how he's "wrecking jQuery".

2) Semicolons are still in debate amongst the JS community, I don't think there's a consensus on whether they're needed or not and it seems to boil down to personal preferences.

3) This reeks of ad hominem, how exactly is Paul Irish "hipster"? Strikes me as someone who's done a lot of work to make the web a better place for all of us, fine with me.
4. Add NodeList.on, which adds the event listener to all nodes in the list
Well, ok then. Except... in that particular case schizophrenic people usually have a poor sense of reality, heck even words like "hellban" and "dead" may have religious connotations. Not really sure what a better solution is.
Yes "document.querySelectorAll(selector)" is a bit verbose, but jQuery API is no better, do you know what would "$(selector)" actually do? You can't - it depends on what "selector" is.
I'm not really sure what the point you're trying to make is; What other purpose would a software blog have than to share information gained through experience?

Is it that the information is not helpful to others, because it is not helpful to you?
Yes, you can re-implement jQuery in 10 lines of code... if you only support 0.1% of the functionality of jQuery.

jQuery was a game changer for web client side development. Thousands of work hours have been spent on it. It had a specially important role of dealing with all the inconsistencies between browsers. If you don't use all the features, nowadays you can just create a custom build with the stuff you want.

If you don't need jQuery, maybe because you only care about modern browsers, or you use another library or you don't mind a bit of extra boilerplate for DOM manipulation, that's perfectly fine. But these kind of posts seem like mockery on the developers of a library that has provided extreme value for thousands for developers over many years.
While I don't disagree that wpa_supplicant has been spawned from hell, I find it strange that the existence and popularity of NetworkManager is given as a clue for why {Net|Free|Open}BSD is better. You know, connecting to a WPA protected Wifi network is not the only problem users have. For example, another one would be connecting to a VPN, a task that NetworkManager greatly simplifies, assuming that such integration is available of course (e.g. if you think connecting to a Wifi network is problematic, try connecting to a L2TP over IPSec VPN).

There's also the issue that the simplicity exposed in your example is a little misleading. Will the system persist that command and re-execute it on boot? Will it remember my previously used Wifi networks and connect automatically should I want that? How can I view the available Wifi networks in range? Being able to connect to a Wifi network using a simple ifconfig command is great, but the notion that your 80% of use-cases is the same as everybody else's 80% is misguided at best.

> If I ever need them -- OH THE HORROR AND THE BLASPHEMY -- I have a Windows laptop, which for all intents and purposes is by now about as closed and as hard to wrestle with as Fedora

And therein lies my problem with your entire comment. It's not that I disagree with your usage patterns, but I disagree with your assertions in light of these usage patterns. So you're saying that xBSD is simpler / better, yet you can't use it on your laptop, as it lacks things you need. Well, no shit.
Can someone explain the new trend to not use jQuery?
DOS, wasn't really multitasking OS anyways. I think my main point is, is it hard to preserve and give OS high priority over all other applications?

If it is not hard, is a big downside for app developers if they don't get 100% control over the CPU cycles? Why is it necessary these days that apps have the ability to push 100% on multiple cores?

At the least with multiple cores, shouldn't 1 core be dedicated to the OS, so it never hangs due to another app? Something sacred, with a lot of gates so devs cannot mess up the entire OS and user experience due to their app.
Crontab UI: easy and safe way to manage your crontab files
that is a point, but a point I disagree with. I would rather have good experience now.
Reserving CPU for itself will make all third party app run slower. And third party apps are a huge selling point (look at Windows Phone), you don't want to be behind your competition because you want a smoother experience on your stock applications.

Also there is feature creep, the longer the system goes on the more feature, security checks, fixed, etc... your basic system does and that will exponentially increase the weigth of your system, requiring you to serve more and more, and making everything else slower.
Thanks, that is my concern. I think the "SHOULD" should have been a "MUST" (or should still be changed to a "MUST") to ensure a forward upgrade path for larger MTU in future. Otherwise, the network is going to be limited by the lowest common denominator, namely those clients which do not implement any path MTU discovery because it's not a MUST, and only support an MTU of at least 1280 (but no more).
Co-founder/CEO
(var | let | const) $ = ::document.querySelector;

with experimental ES7 syntax :D
https://github.com/zenparsing/es-function-bind
I would agree with your comment, but the author is not claiming to be reimplementing jQuery in 10 lines of code. He's merely providing a way to benefit from the syntactic sugar ($) to avoid using the verbose vanilla JS API (document.querySelectorAll) and solve the issue of NodeList not supporting the functionality available on Arrays (forEach, map, etc), which doesn't make any sense in the first place.
Tips for Web Design Freelancers
IMO jQuery is one more thing the end user has to download and process, the more stuff we can strip out while keeping the same user experience is a good thing.

Though I think most the people moving away from jQuery are doing it because the browsers have become more consistent in how they run JS.
I suppose this article is about iOS apps, so I should stay away.

Nobody is "shipping" anything on the web. I've never understood the use of the word, even for apps. Something that is shipped cannot be touched or modified after release. This isn't the case on the internet.

For the normal operation of a website, needing to make only one image per product item is obviously more economical for whoever is making the content, not to mention the technical hassle faced depending on your CMS and how it handles image assets.

Making the image slightly more hi-res, say 1.5x, and then compressing it more aggressively has the benefit of satisfactory sharpness and quality on high density displays, while compressing to a size similar to the low res. I've confirmed this and use this technique, as others have.

For example instead of the normal 800 pixel wide product image, you make it 1200 wide but compress it more when making the jpeg, say 55 instead of the usual 70. The result is a nice lean and sharp image without the bloat of a "2x" file size, and without any perceivable quality loss from increased compression. The increase in resolution serves to hide the compression artefacts surprisingly well.

I'm talking about responsive of course, so there is no fixed width specified in the tag.

iPhone 6 has 3x res? So what? It's an iPhone with a physically small screen. People hold those screens in their hand - arms length from their eyes. You won't see any difference between a 1.5x 1200px wide jpeg photo and a 3x 2400px wide image on that screen. Not until you get your magnifying glass out, or pinch and zoom will you see a difference.

Not a fan of "srcset", it's not well supported and promotes a clumsy multi-res production workflow, which isn't needed for regular jpeg content images on the web - the point I'm getting at.
BOMBO: A tool to automate the AWS cloud mgmt integrated with config. management
Are virtual investment advisors better than the traditional ones?
FWIW John Resig himself originally wrote jQuery without semi-colons but it caused all sorts of issues very quickly!
"IBM said it will put more than 3,500 of its developers and researchers to work on Spark-related projects."

That is impressive. I wonder how that will be split among core contributors, consultants, etc.
There is an interesting article on how F2P monetisation works:

http://www.gamasutra.com/blogs/RaminShokrizade/20130626/1949...
> but even better is using negative values

Honest question: Why?
Either it or another similar one was floating around my university back in the late 90s. The IT department started sending round emails asking people not to run it on the elderly Lasyjet IIIs; the results looked great but would block the print queue for about three hours.
> 2) Semicolons are still in debate amongst the JS community, I don't think there's a consensus on whether they're needed or not and it seems to boil down to personal preferences.

They are needed.

This

var func = function(x) { console.log(x); };
func;
(42);

is different from this

var func = function(x) { console.log(x); }
func
(42)
Yeah, I tried Harry's as well. Seems like they have a couple of serious faults:
* head doesn't easily pivot so it follows your face less well.
* they back too many blades into too small a space, so it packs up easily. Even strong stream of water doesn't clear it.
* their shaving cream stinks to high even, for a long time.

Generally it seems like Harry's requires twice as much cleaning and twice as manys strokes to match the normal gillete or similar brands.
tunnel netcat through SSH :D for fun, but probarbly not profit!
So what's the word to use and what concepts are trivial enough to be just moderated instead of censored?
Adding on, to another person mentioned, "if you reserve CPU to the OS, it would make third party apps slower ..." In a sense, reserving CPU for the OS might speed up hardware progress then.
I've always seen jQuery as an additional layer to handle browsers' API inconsistencies. If browsers you need to support have consistent APIs now - there is no reason left for adding this layer to new projects anymore.
It's a general trend in programming that we've seen forever. Once a successful monolith/monopoly is established and once it becomes all-encompassing (and maybe too far-reaching), people tend to want to be able to cherry-pick the different bits without having to rely on the whole. It's not a mark of disrespect to the fantastic work of the people who created jQuery in the first place, but merely a sign that jQuery is not godly anymore, people want to appropriate it and make it their own, have it cater to their needs and use cases.

I think that's a good thing.
Frédéric Gros' Philosophy of Walking is a great ramble on the subject. There's a little preview in this Guardian interview from 2014: http://www.theguardian.com/books/2014/apr/20/frederic-gros-w...
Minimalist Text Editor with Multi-Tab Writing and Productivity Boosting Tools
David Simon says that homicide is the hardest crime stat to fudge, since there's a body and the different rate changes between homicide and other crimes is actually used to try to measure how much the stats are being fudged.
Your lost airline luggage probably ended up at this store
Isn't one of the best experience of buying a new product, phone/laptop/desktop is that it is "fast"? Press the home button, and things appear instantly. Click on a input field, and keyboard appears instantly. Open the app store, it opens instantly. Switch between applications, happens instantly.

I would have these function fast over anything else. I can live with the internet being slow and a page taking minutes to load, or an application running a task on the background while I switch around and doing other things and coming back. But when the OS slows down, you are locked in the App itself being slow and not being able to fluidly switch between other apps.

As the user of the OS, I wish nothing has precedence over what I want to do. The app should not have control or power over my OS.
You see waves of technology adoption based a lot on language barriers. We're seeing this with Larval right now in India/SE-Asia, we've seen it with VB6, then .NET into Russia/South-America, and we're just starting to see node.js picking up in China.

People forget, documentation needs to be written, interpreted, then passed down through different channels, like programming communities, schools, person 2 person. This can take 4 years+. As soon as English speakers have mastered it, China is just starting to for example.

Node is here to stay, and it's already at a point with decent enterprise adoption, meaning it's going to take a lot of money and time to reverse the trend.
On a related note; I really enjoyed this[1] podcast. It's an interview with Olivia Fox Cabane - the author of a book that explores the science behind creative thinking.

[1]http://theartofcharm.com/podcast-episodes/olivia-fox-cabane-...
The Earth Is Round (p &lt; 0.05) [pdf] (1994)
"Does Magna Carta mean nothing to you?"…

https://www.youtube.com/watch?v=JNZosqiJISs
What I absolutely hate is minute picker. 60 items is just too much to scroll. For most usages 5 minutes step is enough and 12 items much better.

As for calendar, I never had any problems with it. Of course it's not standard way that most people get used to, but I think any person will understand what to do.
Cool, how does it work?
Problem is not the writing, but pronunciation. The word "battery" is the worst in my experience. Everybody understands my pronunciation (Spain, Norway, Singapore) except all of the english-speaking world.
But Google Talk to the rescue, it is prounonced "Bäätdrii", but I have zero clue why.
I use Emacs to write everything. So, in the last 12 months at least C, C++, D, Haskell, Ruby, and Python.
For Python I use rope and jedi. Auto-complete, goto definition and refactoring.
For C/C++ I use my own package cmake-ide. As the name implies, it only works for cmake builds. But it does work. Similarly to Python, autocomplete, on-the-fly syntax highlighting, goto-definition, ...
For D I use another one of my packages, flycheck-dmd-dub.
For Haskell I can't remember now but it'll all very good.
For Ruby I use flycheck, rubocop and rsense.
Without the eminently useful support for delegation.
Mobile phones used to be an easy score. Today they're trackable and lockable, making the more desirable models — particularly iPhones — worth almost nothing. Criminals know this, which is why iPhone thefts have plummeted.

A friend recently had her phone stolen right out of her hand. They police were able to catch the kid fairly quickly, and return the phone. They said that they call it 'apple picking', and it is fairly common. I was surprised because smart phones are so easily tracked/locked.
If anyone’s looking for a mostly idiomatic American reading, I made a recording of a variant of this poem at some point several years ago, after a discussion on IRC with several curious non-native English speakers who: https://soundcloud.com/jrus/english-pronunciation

Also see SJ Klein’s page about it: http://blogs.law.harvard.edu/sj/concordant-chaos/
Design advice from Apple... no, thank you.
not strange since stringer was not written yet.

https://github.com/golang/tools/commit/2c5c896732f6bfdcc0360...
Zepto?
Free download and update computer drivers
You can always report an homicide as a suicide.

You will have an increase suicide rate, but it won't effect the criminal rate.
> Why do I feel that "be competitive" is a euphemism for "nailgun users feet to the ground by locking them into everything possible"?

Then create an open protocol that supports what the users want
> you discover old v4-only devices late rather than early

Could you explain what this means?
A lot of developers originally used jQuery as a cross-browser compatibility library when that was still a major concern. Along the way, jQuery has added tons of extra helper functions and wrappers (ie, .ajax(), .post(), event binding helpers, etc). This has been amazing for web development, but it's also been such a major pillar of web development that a lot of front end developers don't actually know what's happening under the hood when they use jQuery.

jQuery as a library has now become huge, and a lot of projects probably don't use the full feature set. With modern browser support converging and older browsers being edged out of the usage stats, there's not as much need for the cross-browser portions of the library anymore. Enough so that newer versions of jQuery have dropped support for those browsers as well.

So if you can cut down your cold cache loading times by not including the full jQuery library, that's probably a win (especially on mobile). You can do this by using a custom build of jQuery, but I guess some developers are taking this opportunity to go "back to their roots" and see how Javascript has changed since jQuery became a de-facto include in every project.

I think there's a lot more maturity in the language these days, and by using native JS methods there's probably opportunities there for browser optimisations that aren't available using helper methods written in JS that accomplish the same functional goals.

But I'm not a browser devevloper or a JavaScript expert, just a long time web developer who remembers the times before jQuery was in every project. If it's a crutch, it's one I will remember fondly.
I agree. I walk all of the time back and forth between home and the office and it's great to have time to reflect and reconnect using an idle mind.
Wonder how long it will take before Facebook attempts to shut this down.
Having worked in a first world school I was surprised by the lack of vandalism and theft.

It did exist but was very minor. But this is still enough for a large body of students to destroy a small lab over a few years.

But the main issue was game playing and entertainment. Kids will do what kids do everywhere, just play games when left to their own devices.

If you're taking away from other time this becomes detrimental time.

Here's a negative review on the hole in a wall scheme for instance -
http://donaldclarkplanb.blogspot.co.uk/search?q=mitra

Not to say you can't design a system for kids to actually learn in unsupervised at a reasonable cost, just it's yet to happen.
Lots of custom solutions in this thread, but there's already inbuilt commands for talking installed by default on every Unix box.

Log into a box, use 'who' to see which terminal they're using, and use 'write' to send a message there.

Or be lazy and just use 'wall' (write all) like I do.
This is basically how Apache Storm fault tolerance worked. The problem I have with it is what do you do when one of your workers failed and you're not sure if it failed before sending a job completion message? Storm just restarts everything I believe, which is not great. If you just restart that job you could be left with 'dangling' acks.
> I can say with some certainty that the only "calamity" we are going to see is increased use of PAT on clients, and somewhat more expensive IPv4 addresses for those who need to act as a server.

Quite the calamity if you ask me: Users have to actively ask for the permission to act as a server. And at a significant monetary cost, if I understand the constraints correctly. Sure, right now, nobody has a server at home. But if we did (and this is certainly technically possible), then centralised spying-ridden services such as Gmail, Facebook, and YouTube would be mostly useless. (Assuming peer to peer distribution, you don't need a server farm to scale.)

This would also help with routing by the way, by keeping communications more local.
Most small values in programs are positive (lengths, counts, etc), so it's possible to write a value to something that should be initialised to a constant by mistake, and you'll never know, since the ranges overlap.

But if you use negative values, and you write a positive value, when you see it, you'll know.

Of course this is a very trivial thing, but it helped me many times.

Sometimes it's better to use typed constants with a custom type, then the Go type system will help you and not let you assign things of a different type. Note that I only said sometimes, in many cases it's better to use untyped constants (or use primitive types rather than custom integers), and positive integers because you can calculate the constant corresponds to some value from a delta, or from some other criteria, like here:

https://github.com/golang/go/blob/54789eff385780c54254f822e0...

with the definitions of constants here:

https://github.com/golang/go/blob/54789eff385780c54254f822e0...

Another thing useful when debugging is using constants with non-overlapping peculiar ranges, rather than small integers, then simply by seeing a value in a debugger (or in a print of a value without a String() method), you'll know where that comes from.
Named parameters are nice in this case, e.g. in Python

def calc_formula(a, b, is_gain=False):
...

calc(a, b, is_gain=True)
Pareto Principle: don't treat all of your code as if it is "hot." It isn't.
That comes up again and again. For me, named arguments solve that problem.

float CalcFormula(int a,int b, bool isGain) {..}

var x = CalcFormula(4, 5, isGain: true);
You are arguing against a strawman - no one is claiming otherwise. All paul_irish wanted to show is that people often use jQuery without realizing that most of what they do is also possible with the current browser APIs. jQuery does a ton more (animation, ajax etc) - the point was not to "rewrite jQuery in 10 lines" (that's Zepto)
They aren't needed at all. Semicolons in JS are optional.

Knowledge about how ASI works, on the other hand, is mandatory.
Xamarin: Working with backdoors