skysight-inc/HackerNews huggingface dataset:
Websites already implement their own scroll bars - Gmail, Google Spreadsheets, etc.

It would be nice if instead of having to reimplement _everything_ about the scrollbar to just add a feature or two, the native one was customizable. Because frankly, people are going to change it, so might as well make things less buggy.
Wikipedia 60 Minutes Story
Fabulous article!
What is the benefit of using classes rather than just bunch of functions, calling each other?
We do find it useful on http://Clara.io in the editor (you have to be logged in to see them) -- we have a complex UI and the standard thick scroll bar is ugly and much too large. So we thin them down and simplify the styling so that they fit more into the overall UI. It is a very pleasing difference.
Here's an audio interview with (I believe) the same person on the same topic:

http://www.functionalgeekery.com/episode-19-julie-moronuki-a...
hardcards have nothing to do with LIM.
Not using it to prepare for the post-oil world is way way worse.

I don't think current social - no it's not just political - structures allow for hitting the brake pedal before it is too late.
https://www.youtube.com/watch?v=VOMWzjrRiBg
The comment we're talking about isn't quite substantial. Even the meta-discussion that's happening around most of this stuff isn't all that useful. There have been a lot of people who haven't really gotten the hang of commenting here, complaining about the power of a downvote.
>Websites already implement their own scroll bars - Gmail, Google Spreadsheets, etc.

As an OS X user who enjoys not seeing scrollbars, I find Google's use of them downright intrusive.
Gmail uses webkit scrollbar styling, they don't reimplement scrollbars from scratch. If you go to gmail in Firefox it uses the stock scrollbars, which is really a major advantage to Firefox in my mind. It's kind of like when Chrome stopped supporting the <blink> tag even though webkit still supported it.

Basically all of the times that I see this feature being used it is to make tiny, mostly transparent, or auto-hiding scrollbars that don't match the system UI at all and are a significant nuisance. I'm sure there are some sites that are styling them reasonably, but it doesn't seem to be the norm, even for the major players that have experienced design teams.
FYI Windows XP will NOT be upgraded to Windows 10 for free. Only non-enterprise editions of Windows 7 and Windows 8.1 will be.
> how wrong he was about distributed architecture and the micro-services approach

Care to elaborate? In 2011 I think the approach was quite successful already (well, for big companies like Amazon)...
A note on the argument about the 'morality' of adblockers
Keep smiling and coding: Funny about programming
That's why people are developing magnesium-ion batteries, which has much higher capacity and charge-discharge efficiency.
I agree. I did an internship with them, and was told I'd get a return offer for the next summer. It took the recruiter months to get it to me, and they initially decreased my salary, until I pointed it out. I only actually received it after informing them I had competing offers. Recruiting seems very poorly managed.

That's not a reason to not apply though. I was in a great team, and they're a good place to work. I just wish they could fix their recruiting problem.
> "For the most part, the portable computer is a dream machine for the few."

I would say that 30 years ago, this was an objective statement of fact.

> He just couldn't imagine any laptop ever being more than a "niche".

And you'll see he was and is correct if you consider, as the author was, the usage model. People largely use modern laptops the same way they use desktop PCs. They simply transport them between their regular workspaces. Multiple devices have been collapsed to one, but the way people use them remains the same.

You are focusing very narrowly on the physical devices that the (then and now) inaccurate label "laptop" has been applied to. The article makes much more sense if you abstract to the concept of a laptop, particularly as pushed by marketers 30 years ago.
And this is why I stopped working in gov.
Sears 1981 Tele-Shop Catalog laserdisc [video]
And you would be wrong, because a scam requires a trickery and someone being fooled.
Food, water, shelter. Don't think you can deny prisoners those and claim it's not a human right's issue.
I thought people say learning Haskell as a first language is easy because

1) you don't have do a lot of unlearning. See, you still don't understand why you want things to mutate. Experienced programmers (in other languages) mutate things in every single line of code they write. They have to unlearn mutating things to learn this.

2) It's closer to mathematics which many people know.

I think the problems you faced are actually problems because you read a book that was meant for programmers. Hell, you'll face these problems even if you read a C book that is meant for programmers.

I still think, Haskell (as a language) is a good first language.
This is just my one experience (and you certainly know better the needs of your own product) but you are gaining "that looks nice" in exchange for "this is harder to use because the target is smaller and harder to click".
Learn to program and do it with Haskell — In the back of my mind I thought this was covered, but apparently I was wrong. Could an intro to computation textbook using Haskell be a good alternative introduction to CS?
I hadn't thought about including it in my profile so I went ahead and updated it. Thanks!

I purposefully didn't include a link to it in my comment, possibly to my own detriment, because I didn't want to come across as someone who was trying to hop on the topic of the article to simply promote my library.
I don't think it's accurate to say that those early laptops were nothing like today's machines. For starters, we've still got laptops that are every bit as heavy as that PC-5000. I think it's just been a clear gradual trend of reallocating the bulk and weight from the under-the-hood electronics to the display, and the minimum size necessary for a functional machine has been steadily dropping.
I'm working with a company in this space, so here's my responses:

1. It's very rewarding to feel like you're doing civic duty. I think we have a real shot at reforming the way government percieves what's possible in government contracting.

Healthcare.gov is very rewarding to work on, because even though I'm super apolitical, I'd like to see people inside the government see that an order of magnitude cost reduction is possible, and people outside the government see that the government can produce good software.

Healthcare.gov anonymous shopper is a go and postgres app that has served >250mil visits. How is it not rewarding to serve that many people in getting their health care?

2. I've had my lottery tickets at other companies, I'm not worried about getting mine in an IPO any more. I never was part of a good exit.

3. Some of this is true, and some is not. Yes, you're not in total control of the product, because you're working with gov agencies. However, there's plenty of latitude to implement good user-focused software, especially when you're small and nimble.

4. Just like there's a huge potential for your IPO lottery ticket to fail. No different.

5. Just like some component of your startup will have to become good at the "VC schmoozing game".
The general philosophy is that you're not wasting time fighting against the [monolithic] framework. In addition, in practice, one size doesn't fit all.

For every project and team, you [and the team] have the flexibility to choose the libraries that would be effective for said project. Thus, the ad-hoc framework would generally be different for every project.

In general, you [or the team] probably wouldn't re-invent the wheel, and you'll likely to find a decent library on npm.
I like to read about this, because I'm often confused about human behavior. Sometimes I'm tempted to leverage it, but I can't shake the feeling of how shallow and amoral it is, or just even dehumanizing. That said, there are times when you need to ensure certain things for yourself, free for all, and it become a competitive advantage.
Ehhh, "if" is a bit of a specialized case. In general programs don't map fully to true/false, just leave it as "error code".

It's not that we should use any other interpretation, it's that that interpretation is only mostly true. Don't overgeneralize lest you introduce mistakes.
Favorite part:

"The limitations come from what people actually do with computers, as opposed to what the marketers expect them to do. On the whole, people don't want to lug a computer with them to the beach or on a train to while away hours they would rather spend reading the sports or business section of the newspaper. Somehow, the microcomputer industry has assumed that everyone would love to have a keyboard grafted on as an extension of their fingers. It just is not so."

Makes me think they knew something about work life balance that we don't.. or maybe it's just not work anymore but a way to live.
People have seriously suggested that the Eukaryotes and Archea have a different DNA than the Prokaryotes:

http://www.ncbi.nlm.nih.gov/pmc/articles/PMC148579/

That is, DNA evolved twice on Earth. That seems like "life beginning more than once" or something very close.

Note that almost everyone involved thinks that mitochondria and chloroplasts are prokaryotes captured one way or another by Eukaryotes, so the distinction about two evolutions of DNA gets a bit messy.
Oh I see, I guess I was just struck by the difference in expectations of students in the west and even (some) of the ones in China - and I leaped to conclusions from there.
You are not alone, there are many people like you. But imagine if after all the hard work this is where you are in life, what would happen if you stopped working hard. Things would be far worse.

There are some people who have to swim through this and fight it out in the hope they will better off in the future.

>>When I look at my colleagues, friends I feel like many of them have it quite easy.

A million things matter in these sort of things, unfortunately luck is one of them. Different people get launched into life from different launch pads. Out of sheer luck, people get born to rich parents. Such people are always going to have an edge over the rest of us. There are people who are going to be simply lucky to get a good boss, or ride a economic wave, or just be the right person at the right time at the right place.

If you haven't been that lucky so far, unfortunately merely hard work can't make up for all things in life.

I would suggest you work towards your own goals than comparing yourself with your colleagues. Because remember no matter how fast you go on the high way, there will always be vehicles ahead of you.
I'm not a designer either, but I can see their point of view: they're being paid to make a website internally consistent, and if they can't style scrollbars, then either they're stuck with a bland, vapid style that looks reasonable across all platforms, or they make something that's cool and awesome and makes their clients happy right up until the first scroll-bar appears, at which point it looks ridiculous (in particular, think about a <textarea> where you can style the border to match all your other form-fields, but not the scroll-bar, so you wind up with two visual styles pressed right up against one another). Being responsible for something you can't really control is frustrating for anyone, so I have a measure of sympathy for the designers who want stylable scrollbars.
I'm not clear why it's good that you can style every other UI component except this one.
NYC’s Most Expensive Apartments Have the Lowest Tax Rates
Another to checkout: http://cytoscape.github.io/cytoscape.js/
> But I don't think it's a good idea to lump disparate things together under the rubric "JS frameworks". Saying "things like Angular or React" is not really saying much except that they're both written in the same programming language, IMO.

You're right; my underlying point was out of all of the frameworks or libraries I've tried that are supposed to abstract away from many aspects (DOM manipulation, AJAX calls, etc) I've found them being overly complex. I'll be more specific next time and expound on my thoughts.
I have always billed hourly, daily or weekly. I would never offer a "project" price. The client never really knows what they want, they just think they do. In order to properly estimate a project you have to know everything that needs to be done, then you have to draw up an iron-clad contract that prevents the client from claiming something new was, or should have been included in the price. It also gives the client no incentive to be economical with your time. By billing hourly their incentives are aligned with yours, they will want to waste the least amount of time possible in order to keep their billable hours down, they will drop features they really don't need, they will be unable to deny payment claiming the project wasn't completed. After all they are paying for your time, not for the result. The caveat of course is that you really have to deliver, and as you do they forget about the hourly billing. As long as they have problems and you keep solving them, they will just focus on getting their pain points taken care of.

Something else to consider, if you want to make real money you are a "consultant" not a freelancer and certainly not a contractor. Also create an LLC or corp, I have found that clients don't flinch at all when I am a real business, nor do they try to offer me a job instead of a consulting gig. For 5 years I could not pick up a single side gig because the potential client would always offer me a job, but refuse to offer me the gig they claimed I was coming in for. I would always explain to them that I needed to make "real" money, trading one low paying salaried job for another slightly higher paying salaried job did not help me one bit. I needed the ability to make 2-3 times what the typical senior software engineer makes. They would get offended, I would leave. Funny enough it wasn't until I quit my salaried job, with no gigs lined up, no plans to get another job that the gigs started to happen.
>>These self-pity parties are generally counterproductive.

While this is true, life is an unfair game. And we are all humans. So no matter how hard you try you are going to frustrated when you are treated unfairly.
Might be true, but I can't help but be nostalgic for it. I get the sense that for millennials and younger music is just another kind of light entertainment, take it or leave it. Music for many gen-Xers including myself was practically religion. You loved it so much you built a chunk of your identity around it. You were moved by it. I guess I can't really be sure, but I don't get the feeling people care about music like that anymore.

Of course it might have nothing to do with packaging. I routinely look for new music and I do find gems that move me the way the music of my youth did, but they seem really few and far between. So much of what I hear is so spineless and trite. Of course there is always a temporal selection effect in that only the best stuff of the past is remembered, but it does feel like I really have to dig hard for anything good these days.

At the worst I wonder if the golden age of music as a popular art form is behind us. How many people follow sculpture or painting? There's plenty of work being done, but only aficionados of those forms follow it. Is that where music is headed?
And what is being discussed is a person in prison having force used against them (that's what prison is, after all) to prevent them from accessing the Internet.
This is one of the few problems that still could be counted as open problems in Bitcoin, called "Blockchain fork" or "Orphaned Blocks". there are a few implementations that could resolve this issue but none is perfect and none totally works.
I liked the speech of Andreas M. Antonopoulos in Canadian Senate that asked to not to regulate bitcoin now, because there are things that quite don't work perfectly and now we are able to fix it with less loss than if it is adopted by many more (https://www.youtube.com/watch?v=xUNGFZDO8mM).

So it is a Protocol but still really young and immature in some senses, but it doesn't mean anything else, it is evolving almost everyday.
Ask HN: Would you use this technology?
Hi,

Consultation services are very expensive and most of small businesses can't afford hiring a consultant firm to solve a complex issue in their business.

Here is a video explaining the new technology that aim to make consultation more affordable and accessible.

https://www.youtube.com/watch?v=lLXhNBli40Y

The question is, Would you use it ? and Why ?

I would really appreciate your feedback.

Thank you
The point is that meeting a few people can be an "interview", which is really different than a hardcore structured technical interview.

In this analogy, its like showing up to that coffee and immediately start trying to make out with the person. Yeah, we both knew that might be where this is going, but that's not how the game was set up at this point.
How to Read Source Code
"Whatever happened to the the laptop computer?" may be the HN headline here, and the 1st sentence of the article, but if you read to the end you'll see the following:

"Sales representatives, service managers, field auditors of all varieties have not been adequately served by the computer industry in pushing laptop computers. As the technology of these machines, particularly of their displays, improves, and as their price declines, a lot of briefcase computers will probably be sold. And as the software that is capable of turning them into true satellite offices becomes refined, they will probably even be used - in fact, profitably so."

I'm hearing another prediction, that "a lot of briefcase computers will probably be sold." if things like displays and software improve.

Not sure who is calling this a wrong prediction, but the article leaves us with more than a gist of laptops weren't working out for the common business in 1985, but they did not explicitly state that they were never going to work out.
If I take my tablet and plug in a big screen and keyboard, is it self-hosting as long as the compiler is running on the device?
That's unlikely. Music has historically been fractured:

- radio stations only playing certain genres

- stores only carrying certain labels, hits

- releases only on vinyl or cassette, but not CD

- available on CD, but not digital download

- available for digital download, but not streaming

and so on...

Music flows through channels.
If you'd like to know what a custom CSS scrollbar looks like in practice, in 2015, log in to your Google Analytics account (I noticed you use it on your website) with Chrome. Not only do people want to change the scroll bar, but probably half the internet-using population sees custom scroll bars daily, since Google uses them heavily (Gmail, Docs, etc as well).
Maybe not, but I am afraid one consequence might be less really great music and less people pursuing it as a dedicated career. Not that it was ever easy, but it's only getting harder.
Another cool thing about NVMe is the smaller command set -- only about 10 commands (excluding admin commands), vs the 200+ that SCSI has grown to over the years. It's fairly quick to learn.
Major issues I have with angular:

1. Doesn't play well with jquery.

Digest cycles and event passing don't mix. With any significant jquery plugin you end up with $timeout(0) hacks (with or without the jquery being wrapped in a directive). Since jQuery is the foundation of pretty much everything, this is a torpedo that sinks the battleship. In addition, pulling in jQuery plugins (awesome ones!) requires a major hackathon of wrapping the code in a directive, figuring out why the events are always triggering, then throwing some $timeout(0) hacks in there. ship it!

2. No concept of M (model) in MVC/MVVC/MTV/M??

Data in the directives, data in the controllers, data in the services. oh my! Once your app reaches a certain complexity you'll be doing WTF's as to where a $scope.variable is actually being defined. (Oh i see it was defined in a controller inside a directive that was inserted into the DOM dynamically via a controller!?...)

3. When things go wrong you have to dig too deep

Want to make a recursive directive? Good luck reading the docs on the $compile phase. There are too many times that when something goes wrong with angular, you end up in a deep well of tears trying to figure out why it's not working. This creates a productivity problem.

Minor issues I have with angular:

1. DOM pollution

old schoolers see adding non-standard tags in the HTML as 'code smell' for the same reason that we no longer do 'onclick=alert('hi')'. Part of the reason that this stuff was replaced with $('id').click() was that it created tight coupling between the HTML and the dynamic code. By inserting non-standard tags into HTML which requires the use of a 'compiler' you are no longer separating the concerns of 'presentation', 'structure' and 'dynamic code'. I personally find it distasteful, however, I can live with it (like a stinky roommate).

2. Slow unit testing

One of the most touted features of angular is it's testability. However, 1) virtually every angular component out there has no unit tests and 2) testing directives and mocking out features is so time consuming that it brings development to a crawl. I find that the mix of time spent on testing vs coding is 50/50. That is that for 1 day of coding you'll put in a full day of writing unit tests. The reason is that testing angular is so complicated that it takes that long to get it right. Unit tests are always a good time investment, and that investment is not 0. However, if feel that a 50/50 ratio is too high. Testing should be faster to allow devs to be more productive.

3. Performance is easy to screw up

Reading some of the other comments I realized another minor issue. Performance in angular is great. However, because angular doesn't have any real organized (or patterned) way to create an app (you can make a controller or have a controller in a directive), you end in a situation where the way you have organized your code now creates performance problems. This is true in any framework and with some training can be avoided. However, it appears that the critical mass for this issue comes much sooner than expected due to the perl-like anything goes feel to application structure.
Full-stack JavaScript bootcamp
And what, exactly, is going to happen if people "abuse" scrollbar styling? Or button styling?

Are we here to fight lame design fads by preventing people from building cool apps?
Um, why did you get it? If you already regret it, why not return it for a refund?