skysight-inc/HackerNews huggingface dataset:
It depends on what the role is and many other things, the same as it is in any field. Of course, highschooler in Brazil who recently read a half of 'COBOL for dummies' in two weeks would not earn much more than other who choose 'J2EE for dummies'.
Deep knowledge and experience could bring significant profit, but the same is true for almost any other industry - maybe J2EE performance consulting for z/OS with CICS would pay more than J2EE performance consulting for AIX with TXSeries but not too much more.
It makes me wonder why we really need such a huge lattice (the silicon bulk) really. Can't we somehow deposit small pieces of lattice in places where a transistor is needed?
Because it is likely that a poster on an imageboard made the video themsevles, rather than reposting in an environment that may only permit simple image links, it encourages them to save it as webm instead of distilling to a GIF (not easy to do properly, very bandwidth intensive on view), which allows the videos to be longer and higher quality while file size caps can be lowered.

Mobile users are also thankful for this trend.
28-30% of monthly income is one of the ratios that is looked at when you apply and you can't exceed it if you're trying to get a mortgage. If you exceed that it's a no-brainer that you will get denied the mortgage.
The April one was.. disappointing.
So is it drinkable or not?
I was asking about industrial IoT specifically as the parent mentioned experience with that.
That sounds like the cyclomatic complexity is too high.
10 Optimizations on Linear Search
This comment shows a baffling level of arrogance. And it can hardly be considered a happy accident, compression methods are tested against real corpuses
If Zillow is to be believed, yes. Let's take two cities:

- Seattle[0]: Median sale price for a property classified as a condominium, $413k; median sale price for a single-family house, $672k.

- San Francisco[1]: Condo, $658k; single-family, $1.14m

0 - http://www.zillow.com/seattle-wa/home-values/

1 - http://www.zillow.com/San-Francisco-CA/home-values/
Cynicism works, but not for the bearer. Cynical people are easy to manipulate, their smug worldview notwithstanding.

"Cynicism masquerades as wisdom, but it is the farthest thing from it. Because cynics don’t learn anything. Because cynicism is a self-imposed blindness, a rejection of the world because we are afraid it will hurt us or disappoint us." - Stephen Colbert
Show HN: 1) Build Team 2) Interview 3) Offer
This is why all the smart MBA kids who wanted to get rich quick don't go to wall street anymore. They go to silicon valley instead. Which is where we get bro-grammers, and an emerging culture in tech that doesn't understand or care about historical values like open source. When all the shallow people move to tech, tech gets shallow.
You're invoking a stronger "technically correct" interpretation of the statement I'm making. Let me qualify. In a blob with many short repeated sequences, the algorithm as presented is better. In a blob with many long repeated sequences, a marking bit is better. Honestly, neither example is that farfetched.
Show HN: High-level Python 3 library and CLI tool for creating .torrent files
Artificial Intelligence Is Making Everything Replaceable, Including Uber Drivers
Thanks for making it open source!

I hope I'll be able to contribute some commits, I wanted to build a similar tool but was still in the learning stage. :)

One idea I have right now: a simple mode similar to Radio Silence, but with folders like Photos, Videos as targets.
Zika is a close cousin to the Dengue virus so good luck, people have been working on a Dengue vaccine forever.
First Survey of Afrika's Angel Investment Landscape
Before You Buy Kurta for Men – Here Is What You Need to Know
AWS Weekly: ECS Available in 5 More Regions, DDoS Resiliency Whitepaper,
Game Theory, Second Edition(2014)
There's a reason why Germany/Austria/Switzerland don't usually have state-indicating toggle switches and it's because toggle switches make no sense in multiway switching [0] systems where multiple switches control the same lightsource.

I'm not sure how common multiway switching is in the US, but it's certainly super common in Europe and I guess that's why we use non-state-indicating switches, even in circuits with a single switch, because so many circuits are controlled from multiple switches that there's no point in having them indicate state.

[0] https://en.wikipedia.org/wiki/Multiway_switching
Note that I'd expect to see the influence of ice floe in the Bering Sea (=from Alaska to Russia, the most used channel should change latitude depending on the ice coverage in winter), but I don't see where the ice limit could be. Do they have icebreakers to keep the channel open?
I never said happy accident. Like most algorithms (the reallocation size of a vector when it reaches capacity, the widths of slots in a timer wheel, the hierarchical sizes of a generational gc, etc.) the "correct" answer is determined experimentally. My point is that the choice of encoding small lengths is just a decision, like every other decision and is no more or less elegant than encoding a payload determining marking bit, and shouldn't be celebrated independently. Calling me "bafflingly arrogant" though is a bit perplexing. Can we disagree without resorting to petty jabs at character?
Does this course include semiconductor physics?
But systemd relies on dbus; indeed, a major reason for its existence is to dbusify every aspect of your system. And the fact that dbus, which has been around for ages, is still exhibiting strange behavior like this does not bode well for the reliability of such a system.

The whole fd.o ball of mud is well beyond the complexity threshold. It's a pain in the ass to attempt to even understand the workings of, let alone maintain. Expect to see minor to moderate shitshows like this every few months or so, and box-breaking flagdays when the maintainers decide they don't like the current interface and throw it out to write a brand new one.
The solution is to vote someone in who will loosen the law around building homes. More homes = more supply = reduced price (assuming fresh supply outpaces fresh demand).

This is not magic. This can be fixed. It needs the knowledge, organisation, and will to fix it.
The stove where I live right now has knobs whose full range of motion is a quarter-turn, and the flame goes out if you turn it more than halfway down, so effectively you only have one-eighth of the knob to use. If you try to set it to low heat, you'll usually go too far and put the flame out unless you pick up the pan and watch the burner while turning the knob a millimeter at a time.

It's absolutely amazing what people can manage to screw up.
That needs to be fixed, OSV should be owned and run by the OSM folks.
I think by "poor imitation" he's referring to this. Would you trust this over a smart device created by a software-first company? http://yourhome.honeywell.com/en/products/thermostat/lyric-t...
Adding any type of compile time switch adds extra maintenance burden and adds one more thing to test, one more thing that needs to be checked for regressions. One more thing may not seem like much, but increasing the maintenance burden on a project that had nothing to do with the reason something was broken in the first place seems incredibly one-sided and wrong.
Only Samsung Can Save Android from iPhone Domination
Touch buttons are so much better on stoves than rotating knobs. Its not just a design gimmick. I used stoves with both, and with the touch buttons cleaning the stove after cooking it's a matter of wiping once. With the knobs on the other hand it's really hard to clean, you might need to remove them clean them and replace them.
Really enjoyed reading this, I think I'd like to look more closely at an implementation to understand it further.

Reading the article, I was reminded of a nagging question I've had in the back of my mind for a bit.

The ASCII table was invented in the '70s, when the cost of disk storage was much higher than it is today. But it's a shared dictionary, a standard that we can all agree upon, something that's already on every computer.

The thing I've wondered about is whether there could be any advantage to creating new generations of shared dictionaries that are domain-specific, and much larger.

For example, in the specific (and over-simplified) case of transmitting large quantities of English text from a server to a client, you could reduce the amount of data sent over the wire if both parties shared a lookup table that contained the entire English dictionary. In that case, you wouldn't transmit a book as a collection of characters, but rather as a collection of words.

Furthermore, it would seem like you could apply the same traditional compression methods like what's described in the article to furthermore reduce the amount of data being sent. Rather than identifying repeating patterns of letters, you would identify repeating patterns of words.

Of course, the obvious drawback is that an English lookup table is useless for transmitting anything other than English text. But again, disk storage being as cheap as it is, I wonder if it wouldn't be such a monumental problem to store many domain-specific dictionaries.

Of course, you'd always want to keep the ASCII table as a fallback. Much in the same way that a conversation in sign language (ASL, specifically) is largely composed of hand gestures referring to words or concepts, but the language still includes the complete alphabet as a fallback.

The thing I don't understand well enough is whether modern compression already incorporates concepts that are similar enough such that a shared-word dictionary would be useless. It seems like the "LZXX" style of compression essentially includes a similar but dynamically-generated sort of dictionary at the beginning of the transmission, and subsequently refers to that in order to express the message itself. Would the gains of having enormous shared dictionaries cancel out the advantage of that approach, only in a much more "wasteful" way?
Did I miss the part where they answer the question?
The only technical comment I have is that it continues to be amazing to me that destructuring binary data is so stupidly verbose in so many languages. I think C and Erlang are the only two languages that got this right.
It might seem so, but we don't know how many similar things were fixed by moderators. Perhaps the more egregious offenses that you saw were simply overlooked?

In any case, dang was more than reasonable in his explanation and even included OP's original title and link for those who were curious. It seems like a good teaching opportunity.
Hedge-Fund Manager Kyle Bass Was Wrong on Japan and the Yen
> C doesn't scale when you have projects where modules are written all the time by different people that got hired to work just on piece A and then leave.

That is true for any language, C, Java, Rust, Go. Continuity from team members is important.
If they have (A,B,C,D) = (0,1,0,1):

A sees 1+0+1 -> guesses (2+0)%4 = 2 (wrong)

B sees 0+0+1 -> guesses (1+1)%4 = 2 (wrong)

C sees 1+0+1 -> guesses (2+2)%4 = 0 (wrong)

C sees 0+1+0 -> guesses (1+3)%4 = 0 (wrong)

EDIT: This is twice incorrect, as indicated below.
In London the cycle super highways are painted bright blue. Seems to work.
I wonder if there is a reason for the high cost. In Australia some of the infrastructure is being upgraded for the NBN, maybe that's part of it? I don't know but I'm curious to find out.
The thing is, we're not actually all in the same industry. Companies that sell phones might not be so happy if sales level off or decline, but others will do fine. On the software side, there are plenty of ways to innovate without the hardware getting better.

If people stop upgrading phones, all the companies writing software to run on phones can still do their thing. Uber and AirBnB aren't really going to care; their apps already work. New businesses can come along based on mobile phone apps that put today's hardware to good use, even if the specs don't get any better.

Or looking at entertainment, the game industry doesn't actually depend on better hardware. If the VR thing turns out to be a fad, game designers will still manage to come up with innovative new video games for existing platforms, and people will keep playing them. (Minecraft doesn't require the latest hardware.)

Also, the design of phones can improve even if the raw hardware specs for CPU or memory aren't any better. You can see hardware innovations in other areas (like new sensors). Most recently, the fingerprint sensor is a good improvement.

There are all sorts of opportunities for innovation and refinement that have nothing to do with Moore's law.
Anyone know what the business models of Telenav and OSV are?
Sounds like she could do with a drink.
> This is actually a good thing. Besides, the sentiment "no need to optimize, just wait a year and computers will be fast enough" died over ten years ago and was stupid to begin with.

Ruby, Python, PHP :-/

Maybe with the next few years of performance not improving developers will wake up to the fact that doing stuff in a slow language limits the scale you can push it to.
Deflate is so ubiquitous (being a web standard) that I'd like to see a hardware Deflate encoder/decoder.

It really needs to be in the core instruction set of x86 & ARM.
I always thought it was a clever play on "Go-for-JS". If not, you should change the backstory retroactively! ;-)
> Things used to be done kernel up. But these days it seems that things are happening DE down.

The software hierarchy in order of importance, starting with most important:

1. User's needs/wants

2. User's applications

3. User's operational environment

4. application APIs

5. OS services

6. OS Kernel.

The point of a OS is to make it easier to write and run applications. That is it.

The 'kernel on up' design is fantasy and is NEVER how it was done in Linux or GNU or anywhere.

GNU knew that User/User applications were primary importance. This is why they designed the OS following established APIs designed to help with application compatibility. Those APIs and GNU environment dictated the design of the kernel. Now as the requirements on OS rise so does the complexity. New needs/wants/desires dictate new design choices, of which filter from application on down.

Besides that it is pretty obvious that the standardization of systemd and the elimination of distribution-specific scripts and services has resulted in massive reduction of bugs and complexity in the Linux OS. Accounting for each distribution individually, counting those bugs up, adding all them into one lump sum... I am willing to bet that for every 1 bug that systemd introduces into the OS it has resolved at least a 1000.
Well, I hope over next years more artists will think the way we do. You know, people apparently can ignore the reality, but not forever. The music industry has changed a lot over last couple of decades because of the technology, and it will change much more and for the better, I am pretty sure.

I am 100% with you. Especially regarding the direct support from fans. Bandcamp, Kickstarter, Patreon, and other similar online projects proved the validity of their models pretty well. I mean it's not necessary to force people to pay. If you are good at what you do, if you are open to directly communicate with your audience, if you can developer your "brand"/"name" online well, you have great chances to succeed, and to get supported by people who love what you do. I believe in goodness of people in general. :)
He was talking about local development environment.
I agree they're nauseating, but it's somewhat amusing to watch them become popular again.

The funniest part, IMO, is that the people who have "Watch this GIF of me entering code! OMG!" on their Github README are more or less the same crowd who were complaining how low brow and annoying GIFs were ~10-15 years ago.
very surprising. not like we all do that
Yeah seriously. Eradicating mosquitoes would be vastly cheaper, save millions of lives, and improve quality of life everywhere. What good have mosquitoes ever done?

One plausible way to do this would be to engineer a male mosquitoes that can only produce male offspring. Eventually the female population would be reduced to 0.
Responding to a student's request for help
There were a lot of encoders at the time using this general scheme (a few more values to indicate match length or distances). PKZIP won at the time because it was faster, and PK had the name recognition from his PKARC, which was a superfast implementation of SEA ARC (the dominant archiver on PCs at the time).

PK had to stop working on PKARC because of a C&D request from SEA. He wrote the first algos of PKZIP, which were on par with SEA ARC on compression (and with PKARC on speed), but weren't much better. (And have been deprecated since the 1990 if I'm not mistaken).

Then, the Japanese encoders started to rule the compression ratio (and had comparably reasonable compression times) - LHArc, LZAri, don't remember the rest of the names. LHArc or LHA (don't remember which), had basically the same scheme that PKZIP converged on, except it used adaptive arithmetic coding. PK replaced that with static huffman coding, trading a little compression for a lot of speed, and the format we now know and love as "zlib compression" was born (and quickly took the world by storm, being in a sweet spot of compression and speed).

There's another non-trivial thing that PKZIP had going for it - it put the directory at the end, which meant you could see the list of files in the archive without reading the entire archive! This sounds simple, but back then everyone adopted the tar-style "file header then data" appendable style, which meant that just listing the files inside a 300KB zip file (almost a whole floppy disk!) meant reading that entire floppy (30 seconds at least). PKZIP could do it in about 2 seconds.
From the individual perspective this makes sense and a mindset everybody should have. Collectively, when you add these sorts of things up it has a measurable impact on reducing the total number of injured cyclists.
The thing that always impressed me was how good Unreal looked with CPU rendering at decent frame rates. I wasn't able to convince my parents of the necessity of a Voodoo or TNT card, but Unreal handled my rig far better than most other games.
Not sure if you're from the US, but condos are usually apartment like dwellings that people do own outright.

They are cheaper than houses of a similar size, but, at least where I live, the HOA fees negate about 50% of the difference in price.
Is there really not a good and robust solution to this? Like, say, a condensator that charges for up to 20 toggles and a tiny motor that actuates all the switches that aren't depressed manually? I'd have this over digital switches any day.
It sounds like what you're thinking of has been included in the Brotli compression algorithm, which uses a relatively large initial dictionary. There are similar ideas with a more limited scale in HTTP/2's HPACK algorithm for header compression.
Reminds me of many of the first VOIP softwares often mimicking physical phones (some didn't even accept keyboard input for punching the number, you had to use the mouse). Applications skinned like photographs of physical items => horrible UX.
"American cyclists die only 7x more than Danish cyclists."

reason that this is so 'low' is a difference in the population that cycles.

I don't know for Denmark, but in the Netherlands, about 60% of cyclists dying in traffic are over 65 years old (106 out of 185 in 2014).
Try this link:

http://translate.google.com.hk/translate?hl=en&sl=zh-CN&tl=z...
What does Arnold Schwarzenegger has to do with web development?
Would be fun to do that in Haskell

Edit: https://github.com/GaloisInc/pure-zlib?files=1. Beautiful they've done just the decompression! Challenge awaits
It's the same in Vietnam. Coming from the west, the driving there looks verifiably insane. After a few weeks you learn their rules (or how to compensate for lack thereof) and it doesn't feel as unsafe anymore.
Flipkart's ex-CEO Sachin Bansal admits he was replaced due to performance
I should explain my reasoning since it went away on racism(!) accusations, even if it is so late no one will read it. :-)

According to what I've read, the biggest difference in social parameters from my native Nordic place and Romania is trust. Trust in other people, in the state, in the police and so on. It is a quite logical result in an ex dictatorship that had a brutal secret police.

I assumed the complete lack of trust in others was a large reason behind the lack of foresight and planning. "A stranger, let's get his money!" But -- it is not everyone that do this.

That said, as long as no money is involved it is like being on Ireland. People are really nice and friendly. Less violence here than in the North. And so on.

That this attitude is international will make me reevaluate my thinking.

(Next time someone implies racism as the basis of something, I'll just call them "pederast" -- with as much support... :-) But I will admit to racism on one point -- I am deeply convinced that people from Hungary and from Asia are all good cooks. :-) )
JS NaN and typeof
Finding Opportunities in the Mistakes We Make
+1. I read an anthropology article years ago that helped explain this from an evolutionary point of view. Men tended to make strong bonds with a few men for life, while women tended to have more mobility in their bonding. Men needed intense trusting relationships that their lives depended on: if you're going to organize and go hunt big animals, you needed to trust those you went with. Women needed different things during different periods of their lives. Vulnerability really is the need for community to help raise children. So you made friends maybe before you had children, then different friends who were also raising children, then you made different friends and had different relationships when you were finally a grandparent and not having children yourself.
Microsoft implemented large pre-shared dictionary for their binary XML format. When used in WCF, the XML is a SOAP envelope with some data-contract serialized messages. A lot of XML elements/attributes/values are known in advance. Works very well in practice, here's my blog post about that: http://const.me/articles/net-tcp/
Weren't there also (alleged) patents on arithmetic coding back then? Huffman coding had that as an advantage, too, especially when GNU were looking for an alternative to Unix' compress program.
IT infrastructure consumes a non-trivial proportion of global electricity production, ~10% by some estimates. That consumption is growing at an alarming rate. Most of our electricity still comes from coal.

Performance-per-core may have stagnated, but performance-per-watt continues to improve at an exponential rate. Without the efficiency dividend provided by Moore's Law, IT infrastructure could become one of the biggest obstacles in our transition to sustainable energy.
Wet Code and Dry (2008)
Or maybe most developers aren't worried about the scale you can push something too. Most projects never go anywhere. If one turns into a runaway success you can deal with performance later. Designing everything as if it is going to require Google scale infrastructure is a good way to get distracted by cool technology and procrastinate on actually solving any useful problems.
The article mentions LZW. In terms of algorithm elegance LZW should be head and shoulders above 'deflate'. LZW got patented which (aside gifs) screwed up its popularity. 'defalte' allows custom dictionaries that adds some extra complexity.

I'd strongly disagree with In many people's eyes compression was still synonymous with run-length encoding as arj was extremely popular to the point it was used to cure full stealth viruses (v512 for example).
hard to provide references now but wiling to search some old bbs

Other than that - fairy nice/nostalgic article.
Come back tomorrow to see the answer!

But where?