skysight-inc/HackerNews huggingface dataset:
> But if you straighten out trade balance and currency manipulation Chinese products become more expensive as they naturally should be

Can you explain China's currency manipulation? I don't get how this is different from the Fed printing money. Every country does it to an extent.
No they don't. That's why most Android earbuds only have play/pause and not volume. The volume is implemented inconsistently on different phones. I did research into earbuds for my Windows phone a couple years ago and learned that manufacturers were inconsistent. You could get earbuds with volume control for the Samsung Galaxy and they wouldn't work on LG devices. The same mess applied to Windows phones.
I strongly support Cloudflare's stance. If the act of providing hosting to a party is legal, then cloudflare should never intervene. If the act is illegal, then law enforcement and courts should do their job.

I have much more confidence in companies that follow the law than those that arbitrarily pull the rug from underneath me for what they perceive is morally "right". I will not trust cloudflare if it turns into another Github.
Not yet. We're working it during our early access program. Well be looking for lots of feedback from customers.
I don't think I'm reading that post wrong! The original poster said " But I wonder if a die that large is even fair." Then the response said it's "fair enough" because even if it only spins part of the way, you'll still get one of a group of dissimilar numbers.

but that's not fair by the definition of what a fair die is. (it has a definition, if you search google you get "In mathematics we say 'fair dice' when we mean that there is an equally likely chance of landing on any face.")

You're basically arguing that dice don't need to be fair. also you completely missed my jab at the NSA breaking RNG's while making them seem "random enough", i.e. getting to quite dissimilar next states while in fact having only a few possible next states.
How does that work?
Then you got lucky. If that practice was pervasive, 1) honest people wouldn't face as many issues with HDMI; and 2) the Hollywood DRM-lobby would go crazy on manufacturers
The CPUs are already impressively fast, they just suck tons of power to do it. There are a few games I won't play on my phone anymore because they absolutely kill the battery. (Same with the Facebook app.)

If there was any way to dramatically increase power efficiency or battery capacity it would be a huge draw for consumers.
This article is such utter bu11sh*t.

American food is gloppy, untasty shiat made by those incapable of flavoring beyond salty and sweet.

I say this as an American living in the US. Give me a nice Japanese chef any day of the week, and I'll happily eat that every day for the rest of my life.
Just wanted to mention that there are linux and posix man pages indexed as well:
https://man-k.org/linux/
https://man-k.org/posix/
I get so aggravated with other software's bugs. But at the end of the day, you have to ship.
That's pretty much how all class-action lawsuits work. You (the victim) get a check for a single-digit dollar amount that isn't worth standing in line at the bank to deposit, and the lawyers/firms on the case make millions. It's how the ABA can claim they're fighting for the little guy.
No, the future will be at least 2 USB C ports on every device.
And then when that $1 transformer (probably off by a factor of 10) fails, you have to replace your whole outlet? No thanks.
I always do the OS installs through iTunes so it pretty much gets wiped every time.
Sorry but, ehm, no. Maybe you don't remember it but I surely do. A lot more "it just doesn't work" 20 years ago than today.
They really serve very different use cases. Redis pub/sub consumers only receive messages while connected, whereas Kafka consumers can pick up where they left off. Event ordering, back pressure, etc.

There are many use cases Redis pub/sub can't serve beyond just scalability.
I know Gauche uses pthreads because I got a linker error about it one time ;)

Also, does Gambit not support native threads? That's surprising considering Marc Feeley did quite a bit of research on multiprocessing in Scheme, and he wrote the SRFI for threads.
Pepper spray? In a panic situation where the wind is blowing in her face, she sprays and... oh crap now she is choking and blind. Bullets don't have the problem.
There are some comments here about the difficulty competing with Chinese knockoffs, but there are many small companies making high quality 3D printers, and they have good reputations: Ultimaker. Printrbot. E3D BigBox. Makergear. There are probably many others too that have been around for years but I'm not really plugged in.

Thomas Sanladerer on youtube is a good source of information, and reprap.org, if you're shopping.
I haven't started implementing plugins yet, so details are still vague. General thoughts, they communicate with the core through a simple JSON-based protocol, so can be written in any language you like. I imagine Python will be one of the popular choices. Among other things, they'll be able to annotate the text with rich-text spans, for things like syntax coloring. Also, I'm planning for them to be async, so they won't slow typing even when they're busy computing.
That issue says that Homebrew is doing just fine. Not painful.
Scheme user here. I'm very excited about this, and I think I just changed my vacation plans for next week :D
The basic design may still be around, but if you compare the original with one that is used today on modern devices, you will find it divided into may more bands.

This because originally you had mono. Meaning you only needed two wires.

Then came stereo, but you could get away with using three wires.

So with the plug end being designated ground, they divided the upper band in two.

then comes phones and the idea of putting a remote on the headphones wire. "Simple", divide the bands again giving a total of 4.

Thus when you plug it in, you have ground down at the bottom, and then some arbitrary divide of left, right, and remote.
I think it's pretty easy in Python (things like Celery), but I think the interesting thing is that for Erlang this stuff comes baked into the language, so it's even easier.

So there's all this nice fault tolerance by default, whereas in Python you have to look for it (and you can forget it)
What a bunch of crap. Of course people spend a lot of time arguing, discussing, even getting emotional about prices. When talking with a company you are client with you basically have two things you need to talk about :

- what you are selling
- how much you are selling it

If I meet a company that does not talk about one of these two things, I'll move along.
All those words and none of them touch upon the obvious financial bullshittery of being expected to work as much as double time for the same salary.
"I remember what software, and the internet, used to be like 20 years ago. My user-experience, and expectations, has increased in almost every way imaginable during this time. From a 10,000 foot view, I'm extremely pleased with the way things have changed in the past 2 decades."

I have to agree wholeheartedly with this statement. I'm relying on software to basically help me run my life. Thanks to software, I can accomplish more than I would otherwise. (OTOH, I also take on more, which is a whole other post on making ourselves crazy by trying to do too much.)

Still, there is room for improvement. The problem is that no single point of failure exists. It's a layered problem involving economic incentive, unskilled people jumping into development to shore up the shortage of labor, an immature consumer base, a dizzying array of tools, methodologies, and standards for developing software, etc.

At present, I don't see any way out of the dilemma.
It is information...but if you read my original comment you will see that the benefit of such increased income is far outweighed by other considerations. As I recall, even Krugman himself described that gain as very small (small single digit percents), and potentially mistaken (depending on the average of small numbers across studies.) We, as a society, are paying huge prices for what may be a statistical anomaly.
Can't say (yet). I've used a number of implementations: Gambit, MIT Scheme, PLT/Racket, and played around with Chicken. But never Chez, because it wasn't free.
Deeplinks are not enough
In terms of software quality, websites are usually the worst.

Easier to patch and people and errors are usually less scary.
On the left edge of the screen. You can either force press there, or force drag it to the middle of the screen from there.
> That's not "pricing for the enterprise" you're describing, it's pricing for customizations.

This is not a very meaningful distinction. Big enterprise software deals inevitably involve customizations and integrations.
Show HN: Hindley-Milner Type Inference Algorithm in OCaml
Moving to China means more communication effort and more coordination which can really hurt your business if you do it bad upfront. Same reason why enterprise usually hires consultants rather than hiring everyone as full-time under their paycheck even though the enterprise itself has to pay more money to the consulting company: enterprise doesn't need to pay for health benefit, bonus and even travel expense; pay a premium for a package. Of course, a smart enterprise talent management should turn consultants into full time over time if when the consultants are critical for the growth of a given project...
I've never written unit tests in my life, and my code works most of the time. There used to be times where I'd write code for an entire week in Java without compiling (because it was taking forever) and back then we used pretty basic IDEs that didn't help as much as they to today to help you prevent stupid errors. And, usually, my code compiled just fine and worked. Today's developer is a trial-and-error one, tweaking a few lines of code, refreshing the browser, and seeing if stuff works or not. Today's developer spends disproportional amounts of time writing unit tests and, yet, producing buggy code.
>Because they feel entitled to the content

>Its simple entitlement

>they feel entitled to watch

You keep using that word. I do not think it means what you think it means.

>why do you feel entitled to consume content that you didn't create, in the first place?

Because it has been published, therefore it is public. 'Publish' is literally a verb that means 'to make available to the public'. And 'public' is literally an adjective that means 'open to or shared by all people'. Of course people have a right to access public things. Why would you feel otherwise? Do you feel guilty when you go to a public park because you didn't create the land? Do you feel the urge to surrender yourself to the police because you walked on a public sidewalk that you didn't create?

Copyright grants special privileges to an author so that they can be compensated for their work, in hopes that this will encourage people to publish things. If you refuse to use your privileges, that's your choice, you decided not to get paid. The public is still entitled to keep the gift that you gave them.

Where it gets ugly is that copyright declares that copying or transmitting something (even something already public) is itself an act of publication, and only the author is allowed to determine who may republish their work for awhile. So redistributing without permission is not allowed. But it has been published and therefore the public does still have a right to access it if it is available, they just don't have the right to republish it.

Which leads to the issue here. What is the correct result if something is public, and the public has every right to access it, but can't exercise that right because it's not available? In theory, the author should take advantage of their copyright privileges to get some money from the public in exchange for access. That would be a win-win, leaving everybody happy!

In the past, that could be difficult due to printing and shipping and international trade difficulties and various other legitimate problems. But today's tech makes it relatively trivial, cheap, and convenient to sell digital files online globally. So if the author chooses not to do so, then in the eyes of the public, the author has opted out of their copyright privilege, they have forfeited. It is a public thing that should be open to free access, since the author has chosen not to accept payment for access. Of course, that's not what the law says yet, but that's already what people believe is correct, reasonable, and ethical.

Authors who attempt to suppress access to public things, or make it unreasonably difficult and expensive to do so, or bully people who try to access them, are in the wrong, and they will lose eventually. That is an unethical and immoral stance, and it is an abuse of copyright, not in keeping with its intent.
I would add this to this as well to the new "forever leasing a phone" model, you have to get insurance which makes sense. However the monthly insurance premium can go up at any time. This just just happened to me. I received a letter from the insurance company the carrier uses - not the carrier informing me that the insurance is going up $2.00 more a month(it was $8.00 its now $10.00.) Thats not an insignificant percentage. This is despite never having to have made a claim for any damages or replacement to the phone.
Wrong. Eastern Europe is offshore, too.
The fact that he uses RAR, a non open format makes it even worse.
It's another great feature of LXD, recently moved many services to LXD using the same ansible scripts for server deployment, what a relief. Docker was a constant struggle fiddling between shell scripts, Dockerfile and probably init process hacking. For me bye bye Docker and complex tooling to manage it.
No, because it's possible to implement efficient hash tables with C's primitives -- in fact that's how hash tables in essentially ALL languages ARE implemented.

cons cells are not sufficient to implement hash tables. Scheme needs arrays for that. cons cells can be implemented efficiently using arrays, but the converse isn't true, so arrays are more fundamental in some sense.

If you don't care about algorithmic efficiency, then you could choose either cons cells or arrays as your primitive. But obviously we do care, so arrays were the right choice. IOW, C was the right choice, not Scheme.
It took me two days to read it, so I'll provide a summary:

In a corporate hierarchy are the losers (bottom), clueless (middle), and sociopaths (top).

Losers: Economic losers in that they prefer a fixed monthly paycheck over their fair share for their contribution. Risk-averse. They know they made a bad deal and don't do more than expected. They play social validation games with each other to feel better in order to stand their fate.

Clueless: They believe in the corporate story and work more than they're payed for. They're promoted into middle management where they serve as a buffer between the top management (sociopaths) and the workers (losers). They execute all ideas from top management, from the stupid over the risky to the good. If something succeeds, the sociopaths take the credit. If something fails, the clueless take the blame.

Sociopaths: Nihilists who emotionally broke under the realization that no true values exist in this universe, so they're free to make values and goals up as they like. Those stories are given to the clueless to believe in. In every corporate life cycle exist different sociopaths. In the beginning they're the risk-takers with a vision and the willpower to push something new through. In established companies they kill off new and threatening ideas to protect the successful products. During decline they milk the company for the remaining values, then leave the sinking ship and hand responsibility over to the clueless to let them take the blame.

One important part are the different languages of the three classes. Losers have "game language", the social games they play to validate each other, but the talk and the content are unrelated to reality and don't advance them in the hierarchy. The clueless try to speak like the sociopaths but don't realize that one has to have stakes in the game (i.e. something to lose or something valuable to offer) in order to be taken seriously, so their language is full of empty phrases and threats. The sociopaths' "power talk" is full of hints (without commitments) that are only understood by equals and when they talk about something they have to lose or gain something -- it's about the real things, not the empty phrases the clueless use.
Are you suggesting that an increase in unit tests is correlated with a decline in code quality? That would be a surprising correlation.
>> To me, programming is roughly on the level of calculus; for some professions/people it is critical. For others it may only be useful once in a while.

But programming is a hammer that turns almost everything into a nail (in a good they-really-are-nails kind of way). Many programmers may not realize this because their jobs have always been to program. Go work for a couple months at one of those terrible office jobs that require a college degree but you couldn't really find a compelling reason why.

You (assuming you can program) will have a bunch of scripts that do all your boring shit. You will run most of these scripts once a day in the morning, and spend the rest of the day on Hacker News pretending to work and waiting until a believable number of hours has passed before turning in the spreadsheet that one of your scripts produced. When you want to mess with someone you will give them something immediately after the script runs and not tell them how.

There's still plenty of stuff that you can't bespoke automate, but the boring automation-friendly stuff takes up most of the day in most jobs. When you don't know what a hammer is, nails look like twigs that rust.
It seems Google has been releasing employees' personal projects at github.com/google if Google owns the copyright. (I'm not a Googler, so I don't know if this just applies to stuff you hack on while at work, or anything plausibly in Google's business interests that you do at home while you're an employee.)
It seems Google has been releasing employees' personal projects at github.com/google if Google owns the copyright. (I'm not a Googler, so I don't know if this just applies to stuff you hack on while at work, or anything plausibly in Google's business interests that you do at home while employed by Google.)
I like the explicitly stated emphasis on performance and large file support in the goals. I look forward to seeing this develop and will be following the project (and test-driving it when I have time).
Synopsys definitely has offerings for all of those things. IC Validator also completely blows both Cadence's and Mentor's offerings out of the water when it comes to DRC and LVS, although Calibre from Mentor Graphics has more market share in that area at the moment (though I think ICV might be slowly picking up steam when it comes to market share).
One issue that separates software from most other industries is that software is not a physical entity. This makes the desire to change - refactor, add features, redefine use cases, etc - all the more tempting, since the only cost is getting someone to fix/alter some code (despite the fact that labor is obviously very expensive). In contrast, in aerospace for example, you have to get it right the first time, else you have millions of dollars worth of payload and equipment exploding. In these industries it means teams will probably be more reluctant to accept rapid change in development and deployment since the cost of failure is so much higher than software. This isn't the only reason for bugs in software by any means, but the sheer innate mutability of software makes the desire to pile on requirements, iterate frequently, and just generally not be averse to change a massive reason for buggy code
Indeed, one wonders why the government (of the US or of Germany) continues to tolerate the existence of this company at all. They've clearly conspired at the executive level to mislead regulators. The corporation is a figment of the government's imagination. It seems like the government should just stop imagining it.
So what exactly does 'native' mean for Linux distros?
MagicBus (YC W16) Is Hiring Operations Generalists
iPhone sales fall for first time
As a former user of Kafka, this is awesome and it would have been a huge help for our company if this was available then. I'm glad to hear that a company is offering Kafka as opposed to other propriety versions(AWS Kinesis etc).

One thing is odd though, there is no mention of disk space at all and only a configuration of retention time. One of Kafka's best features is the use of disk to store large amounts of messages, you are not RAM bound. Heroku seems to only allows you to set retention times? This could be awesome if they are giving you "unlimited" disk space, but could also be a beta oversight. Interested to see how this progresses.
Actually the pollutants in question are not greenhouse gases. Quite to the contrary, it is likely that these cars would have used more fuel and produced more greenhouse gases if they had been designed to meet the emissions standards.
I just spent half a week with the following... I re-joined as a contractor in a new role at (big corporation), I arrived my first day (only gone a couple weeks), was able to pick up my security badge (no problem), issued laptop, bag an accessories, no problem..

AD login was written down, missing the last character that was there before, tried as it was, finally tried with the missing character, still no go... three calls to cusomer support later, disconnect ethernet, and able to login with secure wifi.

Able to login, setup a couple things... hmmm, no access... Told my email address was now a different one, ask about original email address. No bueno... wait a day, call back (still waiting on response from original issue), decide I can't wait, needed to get in. No email access, no lync.

Finally get a call from email support the next day (weds), but it's 7:30pm and I'm out to dinner, didn't recognize the number, sent to vmail... the issue was that I had no email, the message on the voicemail said "email me", no callback number, no email address, how the hell was I supposed to email them.

Two days later, I come in, I'm able to send mail, but not receive... there were somehow two email addresses configured. After the weekend, I'm finally able to send and receive, but now have a 3rd email address, and have to manually fix my profile in a bunch of internal services that were auto-populated at first login. Not to mention a VP in another division (with the same name) getting a bunch of email meant for me, because my email was fubar'd.

It isn't just software, it's entire processes. I basically sat for a week, twiddling my thumbs (mostly), because I couldn't communicate... still waiting on access to our ticket tracking system (was told to wait until I had email and lync).

I'd cry if it weren't so funny.
Great link and article. I've always thought the NASA story is truly fascinating. Knowing that your bug could kill the person sitting across the conference table certainly changes the attitude towards being careful with software :-)

As others have said, software is a young field, and in many ways we're still pushing and exploring the boundaries of what's possible with software. All of us are still very much "early adopters" in this nascent technology experiment / revolution. The nature of demand and untapped potential for software systems creates a financial incentive for high-stakes rapid experimentation at the expense of sloppiness (in attitude and in software quality) we've seen for as long as there's been software.

I do think investing a little bit more time up front and using TDD combined with good leadership / experience is ultimately healthy for your product and team, if you can manage it. However, we shouldn't forget that being "cowboys" got us to where we are today, and continue to break open exciting new opportunities for software.