skysight-inc/HackerNews huggingface dataset:
Actually in India, I am really grateful for Uber. Previously talking to an auto rikshaw or taxi is pretty painful. They are rude, not reliable, charge a lot if you don't know the city or area. Also atleast from my talking to lot of Uber/Ola drivers is that they are earning a lot compared to their previous taxi service. So to answer your question, both drivers and public.
Progressive Rock App
The goal was to enrich a smaller number of people higher up the chain than the employees who actually committed the fraud. Your argument also is a strong case for why leadership is almost certainly to blame, since they are the only ones who were enriched or helped at all.
I dont' see why, they'd have been able to integrate the various buts of Solaris that where ahead of the Linux curve and since RH has been good about open sourcing stuff the rest of the ecosystem would have benefited.
Taxes aren't the core issue. It's more fundamental than that. Imagine taxing bill gates at 95%. He's still thousands of times more wealthy than your average individual. That's not going to change much, other than that America is going to become highly avoided because of the tax pressures.

The real issue is that the fundamental structure of our economy aggregates wealth towards the top. Employees who add millions of dollars in value per year to a company get paid a fraction of that. Look at per-emoloyee profits for all of the major corporations. Our economy very heavily favors people who own capital over people who do work on the ground floor.

If you want to fix income inequality, you have to look at structures like the stock market, like corporate equity distribution, and pretty much everything we have in place in society that allows the rich to increase their wealth without actually working.

Increasing taxes is like taking aspirin to cure Ebola. Sure, you feel better, but it's not going to make you healthy.
From my understanding many years ago, solving the heat dissipation problem is the real problem behind higher transistor density. Is that still the case?
Score on IQ tests is a far better predictor of SES than parental SES. Someone in the 95th percentile for IQ will, on average, earn more than someone with parents in the 95th percentile of earnings.

See: http://www.emilkirkegaard.dk/en/wp-content/uploads/Intellige...
[100% Free] Udemy SEO Crash Course Udemy SEO for Instructors -Unofficial
For someone who works on site at Apple in Cupertino, the minimum wage is not a liveable wage, even with four or eight to an apartment. We could try a per zip code minimum wage, that would even raise teachers' salaries, then we'd need a per zip code tax for public employees. Or some other solution. http://www.mercurynews.com/2017/04/22/in-costly-bay-area-eve...
The End of Fossil-Fuelled Cars
All Unicode encodings require intelligent indexing. JavaScript uses UTF-16 because that (or rather its predecessor UCS-2) was the standard when it was being created. Same reason Java and Apple's Objective-C frameworks use it.
In Soviet Russia you get even more. Not kidding. Do you want to move there?
So another UI to their FAQ page.

Better than the drug store I called and had to sit for 3 minutes while their phone bot read me the entire FAQ before I could even "press 1 for...".

Store hours, pharmacy hours, "We now offer" specials, "Did you know?" ads... jeez.
Does anyone remember the alleged time traveler that came back to get a machine that could somehow handle the 2038 problem?
It's not even the point of the example and they address that in the article. They point is that the janitor at Kodak had opportunities to advance her career, whereas the janitor working at Apple has none because she doesn't even for the Apple.
Not quite, the US isn't remotely socialist yet, and the thing Lenin did was try to force communism on society instead of wait for it to come "naturally" as a response to capitalism, which is what Marx predicted.

So this warming up to socialist ideas is pretty much in line with Marx' predictions and has little to do with the Soviet Union I think.
Not sure if front line customer support is designed to be enjoyable (outside of outliers like Apple).

All in all this makes me think of Manna, as customer support was pretty much already about humans following scripts with no allowance for deviation...
The Wikipedia page didn't seem to mention other similar systems created historically to impede modification/miscomprehension.

China has a separate set of accounting number glyphs specifically for this purpose, as the regular numbers 1-9, 100, 1,000 and 10,000 (一二三四五六七八九十百千萬) are obviously easy to change, for example 一 to 十 or 千, 二 to 三, 八 to 九, etc. The replacements are 壹貳參肆伍陸柒捌玖拾佰仟萬.

See https://en.wikipedia.org/wiki/Chinese_numbers#Standard_numbe... for background.
You mean the Sears-Roebuck era of tax evasion.
At IBM, I review hundreds of resumes and interview dozens of candidates each year (mostly students or new graduates). I used to ask tough algorithmic questions, require a small coding assignment, etc. I no longer do that.

Today, I have technical conversations like you describe. I don't need you to remember that 415 is Unsupported Media Type. But I need you to be able to discuss how REST works, the difference between 400s and 500s error codes, and maybe even REST vs GraphQL advantages and tradeoffs, if you mention the latter on your resume.

Occasionally I get a surprised "This was so nice. I was expecting a coding interview". It was a coding interview, just not the kind the candidate is used to.

You can look up specific answers on Google, but you can't quickly google your way out of a conceptual discussion, your involvement with past projects, technologies that excite you, etc.

Generally speaking, I can tell within 5 minutes who is a great candidate.

Luck might have played a part, but I have not had a single bad hire with this method so far. In fairness, I'm selective with the candidates I decide to interview, from usually large pools. For these, I also tend to review code they've written in the past if they specify a GitHub account on their resume.
It's great that, as Facebook offers you no value, you've chosen not to use it. Commenting on that in order to encourage others to do the same is great, as frankly, Facebook is a toxic company and the more people move off the platform the better.

However, your experience is not universal and your comment, rather than criticising the platform itself, actively disparaged current users of it, which is unconstructive and offensive.
That's the classic KISS/YAGNI vs. (not sure if there is an initialism for it) robust extensible modular best practices etc. debate, for which there has been much bikeshed from both sides.
>Thank you for calling it a strawman when the person I was arguing just admitted that communism does call for forced confiscation of property.

Yes, it is a strawman, when you attribute something to someone who did not say it. That he agrees with you or not doesn't have bearing on what makes an argument a strawman. The discussion of property arose after you made your comment.

>You people are delusional.

Very consistent with strawman-like behavior. Tell me how I am delusional. Not the other commenters in the thread. Me. In what way am I delusional?
? Not sure if you're making a point or trying to be funny, but socialism is far from a Soviet (or even a Cold War) thing. European countries pioneered mandatory paid vacation and paid medical leave over a century ago, a fundamental workers' right which the US still does not give its citizens.
It's stop-the-world garbage collection, where collection only happens when the world ends.

Side note wrt deallocations being somewhat slow: could something like Boehm conservative GC speed that up, by grouping all the deallocations together, or by doing them on a separate thread?
> No. These is no sale in Communism because the conceptions of freedom have changed

Oh yeah, the conception of freedom has changed so that slavery is freedom. It's amazing that there are people that actually fantasize about living under a dystopian government.

> Hilariously false. Please actually read Marx; I'll quote the relevant part here:

Marx says a lot of stuff in his worthless books, every implementation of communism has assigned labor.
If it's terrible as this says, and I think it is, then it's going to create opportunities for innovation and disruption. Maybe the next way to get hyper-rich isn't to build Uber-4-X, but to figure out the customer service platform that could be broadly effective for a number of industries, and be affordable. You'd certainly be reaping rewards on par with the challenge if you figured that one out!
Thread from last time: https://news.ycombinator.com/item?id=15070596
Since when do we need investment to come from one person?
The ultimate in garbage collection indeed!

Highly recommend reading that short tale! This lore is slowly being forgotten, thanks for that link.
Over in D-land we've embraced the concept of using D as a "better C" :-)

https://dlang.org/blog/2017/08/23/d-as-a-better-c/

This is not in the sense of tossing away C coded programs wholesale and rewriting it in D, but incrementally using D here and there for parts of a C program. That way, you've always got a working, usable program.
Github's search went the other direction, where it's decidedly less useful than grep. Case insensitive, and drops search string characters that provide context. Like quotes, =, $, etc.

https://help.github.com/articles/searching-code/#considerati...
>It's cool, but it has some major downsides too. For example, MPS stores the source as XML, not text (since it isn't text, it's a tree). This makes lots of basic tools we've taken for granted a lot harder, such as git merging etc. They've had to make a custom mergetool just to make basic collaborative coding feasible.

Doesn't solving this just require a text-to-AST, AST-to-text input and output step?

Anyplace outside the editor the programmer just sees regular text.
> A string is a series of bytes.

Incorrect or wildly inaccurate. A string is conceptually text which may be (is) represented internally as bytes, through some means of encoding that text. And thus the concept of encodings are introduced.

That (and how) text is represented should be an implementation-detail though: Strings represent text, not bytes.

I think most people miss this distinction and that's the main source of confusion for encoding-related problems among programmers.
a machine that can make licence plates

Isn't that basically any decent sized metal press?

If it only has to look the part, 3D printing plus paint will likely do it without the outlay.
(On the off-chance you're not being tounge in cheek): No, "used positively and negatively with the same meaning", as in the two differently phrased idioms mean the same thing:

http://www.dictionary.com/e/could-care-less/

http://www.slate.com/blogs/lexicon_valley/2016/04/05/the_rea...

https://xkcd.com/1576/ (!)
"We always overestimate the change that will occur in the next two years and underestimate the change that will occur in the next ten. Don't let yourself be lulled into inaction."

- Bill Gates
Applying the Saga pattern for managing failures in AWS Lambda functions
I did enjoy that ending. Everyone always seems to force a neat tidy conclusion to their writing.
This just leads me to believe that Node and it's followers never learned the lessons from their stint with php.

Also, "Encoding is the process of squashing the graphics you see on screen, say, 世 - into actual bytes." No it's a way of representing one value in a way a system can more easily handle in a hopefully lossless fashion. Encoding has nothing to do with what's on screen other than that being one representation of the data.
You're quite righty but imagine if they didn't have janitors at all - then they could have been AppleGooglebook!
are you using react native?
Indeed.

https://linux.die.net/man/1/watch
There is a paid upgrade model that some publishers use, but it's a hack.

Say they charged $5.99 for Foobar v.1 and then they also want to charge $5.99 for Foobar v.2 but allow their current customers to upgrade for $2.00. They keep both versions at $5.99 and sell an "app bundle" of both products for $7.99. That will allow current customers to pay $2.00.

Of course the developer needs to put in big bold writing in the description of v.1 not to buy that product.
> silly options for fussy people

That's just your opinion—which I guess the Firefox devs and most users don't share.
No incentive beyond personal satisfaction these days. Most people write and jump ship, which is so sad.
Not just OCR. I read the first word as "Growing"
Not to justify his overall behavior, or the idea of 'closing' a beach when nothing is wrong with it, but being in his backyard is not really an abuse of power.
>Oh yeah, the conception of freedom has changed so that slavery is freedom.

No; if anything, capitalism is the closest to slavery if we consider the case of the slave abolishing the ownership of slaves (the human component) of private property, the proletarian is the same in that he must actually abolish private property in general to be free.

>every implementation of communism has assigned labor.

Does capitalism not have assigned labour? You are free to move between jobs to some degree, but you are assigned labour in general, for without that assignment (by the capitalists) then you are liable to destitution or poverty or death or the charity of the State.
Not to the same extent as UTF8. It's not like UTF8 invalidated all other encodings; they still fill a purpose and UTF16 seems to still be a popular choice for internal processing, despite the misguided push to use UTF8 for everything.
And, due to deductions, literally no one paid that rate. Realized tax rate was lower, combined with a bunch of dead weight losses as people optimized for tax avoidance.
We call that a libertarian POV.
My question comes from the fact that how we code and how our tools look like and what is code and what structure it[code] is, says that we are coding in most stupid way possible, most error prone way there is and most slowest one. No to mention we are hitting walls in darkness.
>'Instead, the male gene copied the healthy sequence from the female gene. The authors don’t know why it happened.
[...]
“We were so surprised that we just couldn’t get this template that we made to be used,” said Shoukhrat Mitalipov, director of the Center for Embryonic Cell and Gene Therapy at Oregon Health and Science University and senior author of the study. “It was very new and unusual.”'
https://www.nytimes.com/2017/08/02/science/gene-editing-huma...

>"We did not find any evidence of HDR using exogenous ssODN, suggesting that HDR is guided exclusively by the wild-type maternal allele."
https://www.nature.com/nature/journal/vaop/ncurrent/full/nat...

I really don't see why this is so hard to understand. You added an enzyme that damages the DNA when it contains a certain sequence. The cells containing that sequence died more often, leaving behind a larger proportion of the ones without (it started out at ~50/50 in this case). This technique will always be doing this selection process to some extent (imo it could account for the majority of published "edits").
Resignation of GitHub's CEO Offers Lesson in Emotional Intelligence
Sage advise I've received re: lawyers...

"You don't pay lawyers to tell you what to do or not do, their job is to tell you the risk in doing or not doing the action. It's your responsibility to decide what risk you're willing to tolerate."

Sounds like you agree!
Janitors at Kodak in 1987 lived at a great time when there were jobs and the rent wasn't half of your monthly income. They likely bought their home long ago and are retired now, sitting on comfortable assets.

Janitors at Apple in 2017 can barely pay rents and they will never own their home, likely owned by the Kodak janitors from 1987.

Feel free to replace janitors with any other job title.
I think it helps in more ways than one, users might use it more which in turn improves the AI if its a learning system or in general because devs gets the product tested out more.

Moreover, customer support will get more automated in the future and the differentiating factor will be how human or nice it feels to use which will in turn make the company stand out.

I'm a good example. I hate it when I phone banks and they give me a lot of automated phone waiting and redirecting. It makes me not want to keep phoning in the future and also dislike the bank because the experience sucked.

The caveat is of course now you have to put more work into it to create that experience but I believe its worth it. I wouldnt train customer support stuff before automation to be emotionless so why should they be emotionless after automation.
Psutil 5.3.0 with full Unicode support is out
Capitalism is a solution for allocating scarce resources. None of your other examples are solutions to that specific problem. Apples to oranges...
Setapp Offers Numerous Mac Apps for One Monthly Subscription Fee
I would argue for something in the middle. Big companies put all sorts of unsavory clauses in that you might want to negotiate. Indemnity for millions of dollars, for example. At the very least, you would want to know what the additional insurance to provide that would cost and negotiate the pricing. Or, non-compete clauses that keep you from selling to customers in the same space. So, yeah, don't nitpick everything, but don't sign a blank check either.
I forgot about the whole NetApp thing. Good point.
There seems to be a big jump between being a "coder" and being a "software engineer."

One slaps together basic frontends, the other scrutinizes over architecture and performance.
it did this in 1954?
I kept it around for dating apps and keeping in touch with friends on their messenger. That's all.
The other part that annoys me is they can send you down courses like "no refunds ever" because company policy says so, with no chance to get to the stage of "Well actually a refund is legally required here because <reason>". This is likely a unspoken benefit to the company's decision maker, because the amount of times people will give up if they can't see a way to work around "computer says... no" is much less than the amount of times people will take them to small claims etc.
I don't really believe that. The documentation doesn't mention that it's not meant to be used. It talks about it being used multiple times, and you posted it multiple times.
It's a lot easier than you think. The basic outline is:

>people want money

>we give them money

We already even have debit cards by hiring other people to set them up.
I wonder if there is ever going to be an encoding that replaces UTF-8? Or have we hit on some sort of permanent local maxima (not a global one in the sense that UTF-8 carries the baggage of being backwards compatible with ASCII ... though maybe you could argue that's more of a unicode problem than a UTF8 encoding format one).

At this point UTF-8 seems pretty permanent, what would come along to replace it? And if it is likely to be permanent shouldn't node / javascript in general be moving towards deprecating UCS-2 / UTF-16 and giving first class support to UTF-8?

I saw all this because a couple of years ago I had to write a UTF-8 converter before ScalaJS natively supported for a serialization library I had written. I was kind of surprised that the javascript support was so lacking, luckily writing a UTF-8 encoder/decoder isn't that hard of an endeavor.
The Netherlands has become an agricultural giant
I always thought the people that left Europe for USA did it for a different life, not to get socialism and get back in line with the herd. But it seems that the people in California had afterthoughts about this and decided to go commie. Not kidding, Hacker News commenters are very much biased towards socialism - take it from a guy that was born and lived in a socialist country and had the chance to feel it the hard way, not dream about it.
> do you really need to analyze compilation logs to arrive to the conclusion that you should use an IDE and that types are helpful ?

Yes you do. That's the point of the article - we should apply basic scientific method to programming (that's what distinguishes us from magicians).

> There is also no real hint into why getting this error...

This part of the story is better explained here https://blog.buildo.io/http-routes-at-buildo-1424250c41d3
>We can't just replace all the existing interfaces with 64-bit versions, of course - we need to continue suporting the existing interfaces for existing code.

The backwards compatibility problem in a nutshell. You can put off breaking stuff today and kick the can down the road some more, but where does it end? January 19, 2038?

I think it boils down to a philosophical difference, not really a practical difference, despite the inevitable arguments that "we can't just go around breaking all the shit that's already deployed." Even though the pain would be greater short-term, the benefits of breaking stuff today almost always outweighs the hazards of putting it off indefinitely, since there's almost never any motivation for going back and removing the workarounds once a stable solution is implemented. As evidence, OpenSSL is Exhibit A.
I avoid systemd like the plague, but have hit these bugs anyway:

They keep having embarrassing security exploits (like remote code execution in the dns reimplementation, or handing root to strange usernames by design).

Many people say they broke logging because the binary files create administrative nightmares and are flakey by design. Ubuntu LTS' systemd logging subsystem definitely broke a bunch of production machines I work with by stealing control from rsyslog during a botched update. We have a bunch of tooling for log processing and shipping. The systemd binary format is a usability nightmare compared to .gz files.

Being a member of the "video" group is no longer enough to use DRI or the new rootless X11 stuff. One of the crucial system calls has been hardcoded to only work when invoked by UID zero. The kernel maintainer rejected a one line patch to fix it. The argument is that systemd can launder the call through its own authentication subsystem, so the kernel doesn't need to implement workable permissions for /dev/ anymore. I have no idea how far that brain damage has spread. Just "chown root:root /dev/video; chmod og-rwx" if you want systemd! Don't proactively break every non-systemd distro out there by intentionally crippling the kernel API!

I've noticed that systemd debian-derived desktops age poorly -- uninstall a bunch of packages and reinstall, and you will find you can no longer log in correctly. I never managed to root cause it. It looked like init issues with multiple repros across multiple OS vendors.
I have a very small sample dataset (just mine) for the statement I'm going to make - when I used Facebook it was pretty much exactly what OP said.
I use to run a super popular sneaker encyclopedia and collected shoes. Mostly lost interest in shoes and then the site slipped from popularity, but it was an interesting time. I had every Nike Dunk colorway name and Air Jordan memorised hah.

I still appreciate nice shoes just as people like art. Some of the sneaker designers like Tinker are truly artists.
There is a slight risk but I think it does make sense. There has been papers on the advantage of 5x5 and 7x7 convolution filters and the consensus seems to be that 3x3 are probably the way to go.

If this was out, right now, it would have tons of use. The field moves fast but it is credible that in one year the field will still uses 3x3 and it is certain that being able to do todays applications for a few percents of the energy used now to do them is going to have business applications.

Research moves fast but user usage move at a different speed. The first GPU came out when people were not sure if we would be doing triangle-based renderings, realtime raytracing, or something more funky.