skysight-inc/HackerNews huggingface dataset:
Think about effort in vs results gained. Example:

You can drive nails with a knife by holding the nail and hitting it with the side of the knife. It takes work to do right with you occasionally cutting yourself. Some people will even loose a hand.

You can use a hammer. You will get the nails in smoother with less rework required. You occasionally hurt yourself but not as bad as a knife. You can also smash the nerves to point you don't feel anything.

You can use a nailgun with safety switch. It's ultra-fast and can't hurt you if you're aiming where the nails go. It cost a bit more. It can hurt you if you turn the safety off or aim it at yourself. Simpler than mental effort into using knives or hammers safety. Less tiring, too. Some people even think they're fun.

That's C, C++, and languages that are memory-safe respectively. Rust's advantage of no GC is like a nail-gun that costs same as a hammer. It has the benefits but not the primary disadvantage. If you're a craftsman, you're time and energy are valuable. Use the best tools you can for whatever work you're doing. That is, what gets it done quickly, done right, and easy to fix later w/ smaller problems.
صور+حب+رومانسية+جميلة+2017+اجمل+صور+عن+الحب+الحقيقي
Also, many eBikes bodies I've seen are made from aluminum or even carbon fiber rather than steel, to account for the weight added by the battery I'm guessing.
That is a great resource.

Here are some I've used:

Inside Microsoft SQL Server 2008 T-SQL Querying: T-SQL Querying https://books.google.com/books?id=FZlCAwAAQBAJ&printsec=fron...

Good resource for designing high performing queries and investigating performance problems.

PostgreSQL 9.0: High Performance https://books.google.com/books?id=OWOAu0GcsqoC&printsec=fron...

Greg lays out a great foundation for doing performance analysis that is largely applicable to any rdbms platform.

Optimizing Oracle Performance https://books.google.com/books?id=D7ElCwAAQBAJ&printsec=fron...

Another great book that explains the process of approaching and solving performance problems.

Joe Celko's SQL For Smarties https://books.google.com/books?id=i-19BAAAQBAJ&printsec=fron...

Everyone writing SQL should read Joe.
> this is WinXP-IE6 all over again.

This is logical. If you have limited developer resources, it makes sense to target the most popular combos first. Until we have true "write once run anywhere" it will always be this way.
Maybe if housing/land didn't appreciate over time then investment dollars would stop chasing it, and the overall price of renting would stay flat or decline due to the lack of capital inflow to the underlying asset. Who can say?

The problem with these thought experiments is you have to assume some reason why housing prices have stopped increasing, but also that nothing else about the economy has changed. Otherwise the thing that stopped housing prices increasing has probably also had some other pretty serious effects on the economy.

It's like asking "what if World War 2 never happened"? Well, why didn't it happen? The same forces would have pushed us in the same directions. If it didn't happen, well, that world doesn't look very much like the one we live in, so who can really say what would have happened?

In general, making as tiny a change as possible, housing still would be priced the same as it is now - i.e. based on what the market will bear, rather than some weird idea that landlords would get vindictive and crank rents just because their asset is no longer appreciating. To the extent possible that's what they already do, and they would price themselves out of the market with further increases.

But if landlording is still a revenue-positive activity, then people will do it, and housing prices would continue to increase in anticipation of future gains. People would still want to move to desirable locations like big cities, and that increases housing prices too.

So I don't see how exactly this happens without a major, major shift in the housing market - something like "landlording is a revenue-negative activity" or "there is a significant chance of losing your asset value in a fashion that it will definitely never recover within the span of several generations". i.e. nothing like the world we live in.
The best way of dealing with cavities is to do your darndest not to get them in the first place! (Although: read below...) Stay away from sugary and starchy foods that stick to teeth. Don't expose teeth to mixtures of sugar and acid (such as sodas).

Brush teeth carefully once a day: small, circular motions that cover every tooth surface; it's the mechanical action that removes food debris and plaque. A light touch is crucial, so you don't damage gums. Spend about 15-20 minutes on this in the evening, either while watching TV, reading, or just lying back in bed. Don't floss too often, because that can also damage gums.

Anecdote: I had a small cavity on a rear molar. I completely stopped chewing on that side for 2-3 months(!). During that time I dramatically increased my intake of calcium (yogurt, milk, green vegetables, supplements). When I later returned to normal chewing, the cavity was healed. From the medical literature I've read, this doesn't happen. But in my case, it most certainly did happen.
Just as an FYI, C# is more strongly-typed than C++.
I understand the sentiment but the best game I ever made was done in exactly the opposite way. So I don't know if it is the best way, unless maybe you are making a sequel.

Chris Taylor used to say the "game is the design document." There is obviously a lot of problems with that approach. But I have also seen terrible results from teams who plan on paper and neglect the reality of the work product.
Because that's capitalism in today's world. It's the "free market" at work. I don't think the focus should be on preventing people from using "bad labour" but rather on making it so that there would be no reason to use "bad labour". As much as people on HN especially would be so critical of Socialism, they often shy away from these topics - beacuse they are uncomfortable to think about.

The fact of the matter is that it's not good for business - neither for the people in government, nor for Apple, to be force Apple to make their products where there is some guarantee that the workers are being treated fairly. It's worse for Apple, of course, but politicians don't want to lose their lobbying money or their power.

Lots of people will be saying "it's horrible what they're doing" without realising the cause - the unustainable model of global capitalism that is forever requiring higher and higher returns. Such growth for this kind of labour is much harder to accomplish where it costs more, such as in the US.
"I think most interview questions are similar nonsense."

It's probably a good idea to be careful with your words when you admit that you don't know the answer to a question.

First off: your example (random permutations of the same four words) doesn't require much memory at all. So if you think it does, you're wrong. You might overflow your counters, but that's a different problem.

A stream of random gibberish is certainly more challenging. But the cardinality of the English language isn't infinite (the OED has about 230k words, and that's with lot of words that nobody ever uses), so even a naive solution doesn't require "unbounded memory", as long as you take the problem statement seriously and don't do something ridiculous. That would be good enough to pass an interview.

But OK, let's say you do have a stream of random latin-encoded gibberish. What then? The problem statement is that you have to determine the top-10 words (or in this case "tokens") by frequency. The cardinality of the set is infinite, but the probability of duplication per token is small, and the output set is tiny. Do you really think you need unbounded storage?

In any case, even if you think a problem is "nonsense", it's probably true that the interviewer has thought about it more than you have. The part that frustrates you is highly likely to be the bit worth probing. A bad candidate will bomb out immediately; a decent candidate will provide a solid, if not perfect solution; a great candidate will solve the problem, see the broader theoretical aspects, and investigate those as well.
Nahh, that's not why. They got rid of the idea of the X protocol and network transparency.

I like being able to log in to remove Linux machines, and run programs that show up locally on my desktop. And since it's not some framebuffer, I know the X commands are being send and then rendering on my side. That's loads better than some dumb pixel maps.

And X is extensible. Plugins aren't easy to write, but you can do it. We have Screen for X (Xpra), mpX (multiple pointer/keyboard), OpenGL, and loads more. Yeah, some could be considered cruft, or multiple ways to do the same thing, but that's the Unix Way.
Education at least, the best chemist, economist, physicist or whatever fresh out of school probably wouldn't do to well against even a poor graduate today.

Relativity, quantum mechanics, crystal growth, there is just so much they didn't know. In any field, really.
i have plans, but limited time. the base system is starting to come together, but i need to do a couple more iterations before i'll be willing to move on. i should probably do some write-ups while i'm working on the stuff.

base is arch, for sure.
I agree. Redux has fundamentally changed the way that state is managed for the better.
Since the parent is content to just argue, in the interest of transparency, we have made one or two small fixes so far.

Specifically, I'm thinking of https://github.com/rust-lang/rfcs/pull/1214 , which was a soundness fix that went through warnings in 1.4 and became an error in 1.7.

Code like this:

struct Foo<'a, X> {
f: fn(&'a X)
}

Would compile on 1.4, but not 1.7. The fix is:

struct Foo<'a, X: 'a> {

The compiler would tell you exactly what to replace, and that's all it took to upgrade. This was worth fixing a soundness hole. We originally thought that it would become an error in 1.5, but we monitored the ecosystem to see how many packages upgraded, and it wasn't until 1.7 that we were comfortable making the change. This meant that there was no effective break, even though code technically broke.

Those are the circumstances in which this might happen: very important, yet trivial to fix. We've only done it once or twice, and the vast majority of code written in the real world that built on 1.0 in practice builds on 1.14 today.
There were some comparable languages, but they usually made it harder to use C code.
Objectively, there are many health indicators that have improved dramatically. Elimination of many commonly fatal diseases, prevention of starvation, better communication, cheaper goods and services, fairer laws (i.e. anti-discrimination against minorities and women).
Message that does not appear (pending?)

Just look at the top reddit r/dataisbeautiful/ comment

Took me a minute to realize that Poland wasn't black because of missing data, but rather because that's apparently how dirty their electricity is.

And why ? Because of black color used obviously. Ok but lets leave this unfortunate color aside. Many other questions arise.

- What does it mean that the page has live data visualization. How often is the data updated ?

- How many sources of data are there. Does it cover all of them in every country ? Are they all online all the time ?

- Why is Estonia dark brown the whole time but when i click on it is see

wind ++
solar ?
hydro
biomass ?
nuclear
gas ?
coal
oil ?
unknown ++++++++++

and it still has 595 gCO2eq/kWh

- What does "?" stands for in the results? Are some sources unavailable or is the data corrupted or what ?

- Why there is nothing under coal ?

- What does unknown here mean ? Does it contribute to gCO2eq/kWh ? I mean, so much of unknown energy. Are you serious ?

- What is the metric used after all ?

Is this software even alpha ? What is the version ? That is all very important when you create "facts" like this in Internet.
So-called "intellectual property" is already valued on balance sheets, too. I don't know what relationship to reality that balance sheet representation actually has, though.

I'm on the fence about the "value" of the copyrighted work factoring-in to the equation. On first blush I tend to think the "cost" to the public of withholding rights from the public domain is high regardless of the "value" of the copyrighted work to its "owner". A "valueless" copyrighted work should be equally (and oppressively) expensive to withhold (for a long duration) from the public domain as a "high value" work. The point isn't the "value" of the copyrighted work, it's the term of "protection".
Enrollment drops to zero in 151 university departments, programs (Taiwan)
True, millions of similar jobs are created overseas, but that's when salaries are so cheap that automation is more expensive than just manual labor. As wages go up, automation makes more sense in manufacturing, and job losses happen to those countries too.

When looking at developing countries that are actually developing (instead of stuck in the middle income trap) what we see is a picture of a more developed country decades ago, except with access to modern tech. While the modern tech makes them move faster, you should expect them to be more like the US or the EU every year. Look at pollution: China has a huge pollution problem, but that's not unlike LA in the 70s and 80s. People are getting wealthy enough to demand environmental regulations, and in a decade their government will care about environmentalism.

So instead of thinking about how China or India have things that we've lost and try to turn back the clock, it's more productive to think that we have to deal with our own problems today, as China will also have them in 20 years.
Your previous two submissions probably weren't interesting enough—they read more like requests for favors. People come to HN to gratify their intellectual curiosity (https://news.ycombinator.com/newsguidelines.html), so you need to offer them something in that spirit. This one does a much better job of that!
No, because if you explicitly converted to another type, that's what you wanted.
Tokio runs entirely on stable, though 1.0 won't happen until some language changes land.

Diesel does work on stable today, but its nightly features will be on stable in five weeks with 1.15.
Winning Blackjack Strategy Simulator (OMEGA II Count)
> right now all they're saying is that there's a correlation in a study of less than 60 patients

Sort-of. Many recent studies had already suggested a role of sodium accumulation in brain tissue loss in MS. Previous work had also shown significant sodium accumulation in regions where there was no apparent cell death, suggesting that cell-death does not drive measured sodium concentrations.

What's cool about this result is 1) that sodium measurements from the brain are better indicators of cognitive defects than actual death of brain cells. 2) Abnormal sodium accumulation occurred in neocortex, which is the first place you'd suspect cognitive impairment to originate. That's a correlation across patients, and brain areas, suggesting at the least that NaMRI is a good tool for early MS detection.

I doubt it's dietary sodium. Likely, sodium accumulation occurs when normal processes are disrupted. I wouldn't expect increased sodium in your diet to lead directly to increased sodium in selective areas of the brain (could be wrong here).
TDD: "If you're not doing this, you're not a real engineer."

Rust: "If you're not doing this, you're a murderer."
Windows 10 is the new IE
I'll sum it up:

The inaugural “Secret Ops of the CIA” calendar was produced by the nephew
of an agency contractor killed in the line of duty and features
reproductions of the actual paintings that have hung for years inside the
hallways of the CIA headquarters in Northern Virginia.

(...)

The calendars are on sale for $28 at the International Spy Museum (...)

(...)

Toni Hiley, the longtime CIA museum director, said the gift shop can’t sell
the calendar because “it’s not an official work of the U.S. government.”
To answer some of my own questions, child birth is becoming tremendously safer:

Year Deaths per 1000 live births
------------ ----------------------------
1700 to 1750	10.5 (British [1])
1750 to 1800	7.5 (British [1])
1800 to 1850	5.0 (British [1])
1990 3.8 (Global [2])
2013 2.0 (Global [2])
2013 <0.09 (UK [3])
2013 <0.28 (US [4])

Though I can't find a source, some articles claim a 1% maternal mortality rate in the 1600s! [5]

From that same Slate article, child birth is still one of the most dangerous things for young women, despite it being far safer than ever in the past. This means that contraception is actually a health benefit. It makes it much safer to be a young woman.

[1] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC1633559/

[2] http://data.worldbank.org/indicator/SH.STA.MMRT

[3] http://patient.info/doctor/maternal-mortality

[4] http://www.nytimes.com/2016/09/22/health/maternal-mortality....

[5] http://www.slate.com/articles/health_and_science/science_of_...
Maybe he had a bad mouse and you had a good one.
Ouch. I don't think I've ever met a competant engineer who would agree with the sentence. The person who posted it is obviously very junior and I don't think I'll ever call him/her an engineer if they don't manage to mature away from that kind of prattle.
This comment breaks the HN guidelines by being uncivil. Please don't do that.

https://news.ycombinator.com/newsguidelines.html

https://news.ycombinator.com/newswelcome.html
Imagine the fun a hacker could have if they penetrated the systems running the drones.
Ask HN: How do you protect the IP of proprietary platform, toolset, and SDK?
Our scenario is such that we have developed a comprehensive SDK, platform, tools and processes -- toolset. Our toolset enables us to be competitive with regard to time, budget, and quality.
We have successfully used our toolset for our projects and we are exploring using our toolset to build software projects (SOW) for clients. Customers will need our toolset to maintain and operate the software systems we will build for them.

We do not want to lose control (ownership, right, etc) of our toolset. We do not want customers to use our toolset to build new products to compete with us.

We are thinking that a good approach would be to license our toolset to specific customers for use for specific products that we built for the customers or that the customers will build themselves.

How would you protect the IP of proprietary platform, toolset, and SDK when you have to use said toolset for contracting work or when you want to limit the scope of usage?

All your thoughts and feedbacks would be most welcomed and appreciated.

Thanks...
I hope Google are going to do continuing security updates for every enterprise release of Chrome for the next 10 years, LOL! At least limit the company browser to only internal apps (still not safe!). Perhaps they could de-feature the enterprise browser for better support&security? You would hope that using standards compliant web apps would make upgrading/testing less of an issue for corps.

Using ancient versions of IE to get work done was awful and in the current security environment, I don't think it's safe for a browser that's not in its own VM. Heck, you could use Chrome Remote Desktop!
> I remember seeing a more comprehensive report, which also had larger code samples and talked about the disqualifications, but I can't seem to find it right now.

Well that's precisely the vague stuff you were talking about in your original post, so that's very unfortunate.
English version of al jazeera has good info on ISIS/Syria/North Africa. Not without it's own biases, but definitely more in depth topics than we get in western papers.
Commercial open-source: Sentry
I think that rule is a little too simple, because it might be correct to retransmit but not to have the retransmission block processing of later packets. I'd say one should probably use TCP when any of the following are true:

1) The correct interpretation of later packets depends on side effects of earlier packets (e.g. commands in an SSH session, OpenGL commands)

2) Raw bytes-per-second throughput is a major consideration (e.g. file transfer, streaming video)

3) The application readily tolerates high latency and jitter (e.g. email, text chat)
The problem with fast eBikes is safety -- there's a huge difference in injury (and survivability) between a 15mph collision and a 30mph collision.

If a collision between an unprotected bicyclist and a stationary object is similar to that between a car and a pedestrian, the chance of death in a 15mph (25kph) collision is around 5% and the chance of non-minor injury is 10%. In a 50kph collision, that jumps up to a 50% chance of death and 95% chance of non-minor injury.

http://www.safespeed.org.uk/killspeed.html

So sure, build your 30mph bike if you want to, but understand that it's no longer a bike, it's a motor vehicle, and should be restricted to licensed adults and should not be used on bike paths and the rider should probably be wearing a motorcycle-style helmet. I know there's some debate on the effectiveness of bicycle helmets at preventing injury in the low-speed accidents cyclists are usually in, but for motorcyclists, the benefits are more clear -- a 37% reduction in deaths and 67% reduction in brain injuries.

http://www.iihs.org/iihs/topics/t/motorcycles/fatalityfacts/...

Oh, and make sure that your brakes are able to stop your 1000W+ motor if the throttle gets stuck wide open.
> As much as people on HN especially would be so critical of Socialism

Where do you get this from? Pretty much everyone from Europe is very grateful for the various safety nets the countries have built up there, especially in West-Europe.
I believe one of Apple's higher ups has talked about child labor before.
I'm not sure if it was Steve or Tim but the convo was that its impossible to handle without hurting the communities because the norm is child labor over there. So the conditions for the children are worse if they have no labor. It's really complicated and not something that you can judge from an arm chair position, you have to go over there and see it with your own eyes.
Case in point:

https://en.wikipedia.org/wiki/Cilk
> Many would love a better language. Matter of fact, they tell us in Rust threads here.

Absolutely, but my emphasis was on the difference between "love" or "want", and "need". Switching a programming language is extremely expensive, doubly so in systems programming. Organizations won't pay the price for something that doesn't make a big impact. Unlike many other new languages, Rust does have the potential to make a big, bottom-line impact, but that impact is almost entirely due to safety.

> They might benefit if the app is aiming for max performance (esp HPC), memory efficiency (eg embedded), or minimal latency

I don't think max performance is an issue at all, nor even minimal latency where you need it (there are realtime GCs, and GC languages do support arena GC allocation in embedded and realtime settings, like realtime Java), but definitely it's a big gain in memory efficiency.

But again, I said they could benefit. It's just that the main focus shouldn't be on those that would benefit, but on those for whom the language is indispensable, or tremendously beneficial.

> I think Rust might have good, network effects if it takes off.

Absolutely, it's just that if you want Rust to really have an impact rather than just be popular, you need that network effect to be in the right network, and for systems programming, that network is not well represented on HN and Reddit. While these venues are good for marketing, and while the message will get to some of the most important crowd, it may have a negative effect as it would attract many that don't really need Rust, and if they end up making up most of the community, they may slowly push the language in directions that may make it less appealing to those who really need it.
This isn't a puff piece. This is an advertisement for the calendar.