skysight-inc/HackerNews huggingface dataset:
Yes, we need greater precision, ideally floats, but maybe 16 bits would be enough (haven't tested this or thought much about it.) But for multiple passes of processing floats are definitely the way to go due to rounding errors. I don't think you'd get worse performance when using floats on current hardware.
Devtools of WeChat Mini App(macOS, Windows)
Yeah, I've taught pretty much everyone I know that I answer messages at random, but I'm instantly reachable in an emergency. A big part of that was also teaching people that I rarely pick up the phone - if it's important, they can text me, and I'll happily call back.

The way I see it, people will communicate with you the way you allow; if you let everyone expect that you're always available, you'll be spammed with trivialities all the time. Many people don't have the manners (for lack of better word) and self-awareness to understand their issue is trivial and not worth breaking someone's focus by forcing synchronous communication on them.
> The whole point of finance is maximizing profits; I think that people need to understand and accept this for us to have a meaningful discussion.

You haven't factored in your thought that there are no monopolies in the financial world, unless they're state backed. Competition is everywhere. Competition decides the profit, not the firm.
So in the UK can you deliberately stop all your big investors from selling by telling them inside information? Like if you were about to announce bad news and wanted to keep your stock price up?
> So the solution is Unix or (God help us) Win32 forever? I think the nature of the unix user space is one of the things that could stand improving. How about doing something a bit more structured than piping bytes (ascii? UTF8? Latin1? Some binary format? Who knows!) around? Or making tools that don't run in one-shot mode when that's not how they're used (compilers, etc.)?

The solution is incrementally improving these things. What you're talking about is absolutely the kind of thing I'm interested in. Arguably PowerShell is one piece of the right direction. Show me a better way with compilers etc. and I'm interested (I work in Scala and compile time is a big issue, but I couldn't stand to have SBT as my framework).

> This need not throw everything away that we have today. Why not make the equivalent of higher level bindings over a C API for command line programs? Or maybe any of a hundred other options that might improve over what we have now? Is unix really the end stage evolution for user space?

If you've got a way to introduce one of those things incrementally, I'm interested.
In 1988, the skeleton of a child believed to be contemporary with Mungo man was discovered. Investigation of the remains was blocked by the 3TTG [ie. Three Traditional Tribal Groups] with the remains subsequently protected but remaining in-situ. An adult skeleton was exposed by erosion in 2005 but by late 2006 had been completely destroyed by wind and rain. This loss resulted in the indigenous custodians receiving a government grant of $735,000 to survey and improve the conservation of skeletons, hearths and middens that were eroding from the dunes. Conservation is in-situ and no research is permitted.

Sounds like the local aboriginal tribes are claiming ownership of remains that predate them, that they never knew were there anyway, and blocking further research. Thanks guys.
I repost here the 39th comment, which gives a possible explanation of the issue:

Storm in a teacup
Date: 2016-09-22 09:17 am (UTC)
From: [personal profile] cowbutt

"Intel have not submitted any patches to Linux to support the "RAID" mode."

Such patches are unnecessary, as mdadm already supports Intel Rapid Storage Technology (RST - http://www.intel.co.uk/content/www/uk/en/architecture-and-te... ) for simple RAID (e.g. levels 0, 1, 10) arrays, allowing them to be assembled as md or dmraid devices under Linux.

However, it would appear that the version of mdadm in shipping versions of Ubuntu (at least - maybe other distros too) doesn't support the Smart Response Technology (SRT - http://www.intel.com/content/www/us/en/architecture-and-tech... ) feature that's a part of RST and is used by Lenovo to build a hybrid one-stripe RAID0 device from the HDD with a cache on the SSD (I'm sure Lenovo have a good reason for not using a SSHD). Dan Williams of Intel submitted a series of patches to mdadm to support SRT back in April 2014: https://marc.info/?l=linux-raid&r=1&b=201404&w=2 . Perhaps now there's shipping hardware that requires them, there'll be the impetus for distro vendors to get them integrated into mdadm, and their auto-detection in their installers to use the functionality provided sanely.

---

I should add that mdadm is not present in Ubuntu live images by default - one has to pull it in by issuing "sudo apt[-get] install mdadm". BTW, I don't know if mdadm would detect the RAID controller/disk immediately upon installation, or it would require a reboot. In the latter case you may wish to use a USB key with enough spare room to save the system status and reboot. I'd use UNetBootin to prepare such a USB key.

The main issue here is, a user who doesn't even see a disk, probably wouldn't know to go as far as installing mdadm.
IMHO, given the broadening diffusion of NVMe and RAID devices, Debian, Canonical, REDHAT, Fedora etc. might wish to make mdadm part of their live images by default (and eventually strip it from the installed system if it's unnecessary).

Edit: clarified
Telegram was borderline dishonest.

Facebook is dishonest which is why consumer watchdogs are threatening to sue.
How I Rewired My Brain to Become Fluent in Math (2014)
Rethinking madness: inside the world's oldest mental asylum
> I think that the list of things I wouldn't look into tweaking would be shorter.

So can you give maybe a top 3 concrete examples of things you would change?
No chance, modern compilers spend most of their time in the optimization stages. Lexing is peanuts.
Socialism isn't the answer. In fact over government caused the epipen debacle by reducing competition. If an epipen costs $5 to produce, competition means that the price would eventually approach $5 -- it would commoditize it. Doing things like price caps only result in shortages: see Venezuela's economy for a case study.

Look at the FDA process: you reform that and drug costs will decrease dramatically.
Top rated plunger for toilet
The single-source government decree stating that Stentex/Medtronic should become single supplier of stents in Russia in 2017-2022 was signed by the prime minister. See the links above.
Earley parsing is simple and general.
We use atime at work as a proxy for "does this file really need to exist?" on our cluster's scratch disks.
But what percent of $.05 options expire?
The earth is round but HN users aren't evenly distributed across the globe. The time on the US west coast matters because that's where the majority of users seem to be.

Has anybody ever studied HN demographics?
Even for 2006, thats some old fashioned design. But doesn't mean that it's bad - no distractions, leads straight to the content. I like it.
The Definitive ANTLR4 Reference
All well and good saying "you can't generalize" to dismiss criticism of US healthcare.

Here's a generalisation for you: The US has lower life expectancy than most of the 'developed' world and yet spends twice as much (OECD 2007).

See Meeker's USA Inc. slide 111 https://s3.amazonaws.com/kpcbweb/files/USA_Inc.pdf
Speaking of non-traditional applications of Gamma...

In the 3d printing world, we have a filament of PLA (corn based plastic) with wood dust mixed in the plastic, of around 20%. This gives a filament that feels, machines, and colors like wood.

And if you extrude at varying temps, you can give the part lighter or darker colors (darkness dependant on higher temp).

I can almost guarantee that there's no gamma correction, let alone darkness calculation, being done for filaments like that. And it would follow an inverse power distribution - the more heat, the higher the power and the lower the final energy result (burnt = lower potential energy in wood).

So yeah, even if you don't do graphics, it still applies. Damn...
God is perfectly just.

God says...
demonstrates Carmelo's auditioning jackknifing Atlantis railed tropospheres annual's Kane grotesque redcap's proms galvanic hijackers awareness's tornado's storks announces probabilistic contracting sentinel's rotunda's deader sahib onto helpings approbations forecasters talker jeweling regent inputted
Rust uses LLVM, a heavyweight backend with fearsomely thorough optimisation.

It might be that for non-optimised output, the parser becomes the bottleneck again. Or it might be that LLVM just imposes overhead even for the unoptimised case, that pays for itself in the optimised case.
> the only problem is that if every buyer does the same thing, the supplier goes bankrupt (as it can't cover its fixed costs).

The government is responsible for using a fair price, both for itself and the supplier.

His non-profit nature ensure that it will not try to lower the price too far.

If a politician is dumb enough to make companies go bankrupt, it's the responsibility of the people to vote him out of office.

That's the only way to have a fair price on drugs. A free market cannot exist in these industries and the inelasticity of the demand will always, always distort the prices.

Yes, America will have to face its demons and trust its government. The alternative is to continue paying exhorbitant prices to greedy scumbags and let fellow citizens die as a result.
Sure, here's the entire list from my last clean install:

http://pastebin.com/raw/hrYYMJPi
Mysql Commands
Wow everything is smart in that kitchen, even the water.

Can you inject SQL into the Smart Water, or use a DDoS on it?
yeah, i doubt the thesis. The egyptians certainly left africa in several waves, and it's unbelievable that there wasn't genetic mixing between egypt and subsaharan africa.
Honestly, having written a few a parsers, i prefer PEG with recursive descent, or parser combinator.

I find recursive descent parsers are easy to understand, write, debug(you can drop in a breakpoint a follow it through), and the resultant code is actually readable and clean. It's also fairly easy to add error reporting and recovery. As long as you don't do complicated stuff, they're really fast to.

You don't particularly need to be an expert to write recursive descent parsers either.
The evolving road of beacon tech
Yahoo expected to confirm massive data breach
I'm not so sure about that. There is something called the Foreign Corrupt Practices Act (FCPA):

https://www.sec.gov/spotlight/fcpa/fcpa-cases.shtml
yes the npm commands
They both embed chromium, though, which will perform much worse than say native GUI widgets.
> Out of curiosity, where would one find an explanation (potentially dry, long, and complicated) of the algos you mention here?

> In other words - how did you get to know them?

My book recommendation: Dick Grune, Ceriel J.H. Jacobs - Parsing Techniques: A Practical Guide (Second Edition). Many people will also recommend the "dragon book" (Alfred V. Aho, Monica S. Lam, Ravi Sethi, and Jeffrey D. Ullman - Compilers: Principles, Techniques, and Tools (Second edition)), which is not a bad book.

If you want to dive deeply into parsing and want to read about all the details over hundreds of pages, the Grune-Jacobs book is clearly the recommdendation. On the other hand, if you just want to understand the theory behind the parsing stage of a compiler (as one part of a compiler - and there are lots of other parts, too), you will probably prefer the dragon book.
You have a point, I'm from Western Europe :-). But this is what you get when you try having everyone a decent life I guess.
Not all parsers do a lexing step. Such ones are called "scannerless parsers" and can be much, much faster than parsers with a separate lexing step.
For reference, 2.42 cents per KWh is 10x lower than commercial/residential prices in sunny Hawaii https://apps.axibase.com/chartlab/9e548f6b per data.gov https://catalog.data.gov/dataset/hi-electricity-prices-815fa
Not sure what you're trying to tell us.
This rant should have been written in a diary.
I would like to know how long it "thinks"- it is clear the camera is paused for a while while the robot parses the image..
I know it's an introduction, but it misses a lot of the interesting points that are actually important even for people just buying LCDs --- like how intensity gradation is achieved (FRC/temporal dithering vs. pure DAC) and why inversion/AC driving signals are necessary, and how they can contribute to flicker and odd artifacts when displaying certain patterns.

Those wishing to know may find the answers in here:

http://web.nchu.edu.tw/pweb/users/fansen_wang/lesson/7043.pd...

http://www.techmind.org/lcd/

http://www.solomon-systech.com/files/ck/files/Application%20...

In my experience, panel and driver IC manufacturers seem to give the best explanations of the technology, and it's often quite readable even for someone without experience with LCDs.
Also, they have written a unit test to make sure this cannot happen ever again.
The Age of the Superbug Is Here
Is it reasonable to assume that more advanced civilizations would use technology like this for communication instead of radio transmission meaning that SETI is doomed and the Fermi Paradox may be no paradox at all?
Best List of Ultrawide Gaming Monitors
Humans are a part of the environment.
Not exactly, you would have to save all registers all the time.

For caller-saved/scratch registers in interrupt handlers, not only do you have to avoid stomping over registers, anything you call has to do too. You have three options here:

- Save all the registers in each interrupt

- Only call "save all registers" functions in your function, enforce this somehow. Since things like pagefault handlers can get pretty involved, you probably don't want to do this.

- Just compile your kernel with most extra registers disabled.

There is the fourth option which involves whole program taint analysis or something to track the registers stomped on by all transitive calls from the exception handler. Requires special compiler support though.
> their agreement with OEMs requires OEMs allow for diabling SecureBoot

Nobody ever goes from one extreme to the other. Restrictions are added a little at a time to minimize the outrage.

Look at Gatekeeper on OSX. "Oh it's just an option", then it's enabled by default. "Oh you can just turn it off." Now it automatically turns itself back on every 30 days. Their next move will likely be to require all apps to be signed. Again, if I'm wrong, great! As someone who releases OSX software but won't pay Apple for the privilege, I hope I am.

Further, you don't always have to go 100% restrictive to achieve the same effect. Look at web browsers and self-signing certificates. Sure, you can still accept and install them, but it's been made such a pain that nobody can really pull off a self-signed website.

What serious OSX developer is going to release unsigned software that requires people to go in and turn Gatekeeper off every 30 days? It might as well be mandatory for all the choice developers looking to earn a living on that platform have these days.

> Are you equally upset that iPhones and virtually all Android devices also have locked down bootloaders?

Yes! There's not really much of a market for alternative phone operating systems; but even still, I buy Android because I can sideload regular applications without hacking ("jailbreaking") my own property.
I like your set of principles.

Many people seem to polarize on their issues; either they're falling for the "digital crack", or they treat this as unnatural and will get angry if you so much as look at your phone when in their presence.

Principle 1 is fortunately widely recognized. Laws and social pressure seem to be doing a good job enforcing this principle even on people who for some reason don't recognize it on their own. Anecdote - the other day we had a cow-orker admit to using phone without a headset/loudspeaker while driving, and man, I've never seen so much social pressure I saw there. Instant and strong (but polite) disapproval of our entire room.

Principle 2 - the way I see it, it's not really about focus. I can talk with people while playing 2048 on my phone all day long. It's about signalling and manners. Most of the time, if you pull up your smartphone to do something unrelated while talking with people, you'll be signalling you don't think they (or what they're saying) are important. Even if you can focus on them but you have some kind of ADHD like I seem to have. It's not about your focus, it's about their perception.

That's why I don't have a problem seeing (usually young) people talking while each doing something on their own phone. They all know that smartphone use doesn't preclude paying attention. But it works only with people who share this belief, so when in doubt - keep the phone in your pocket.

Principle 3 - couldn't agree more :).
I don't remember who's quote is but sounds relevant for this article :

We won't have cure for diseases until first we have a cure for greed.
Expecting developers to allow you to report bug is hardly something that warrants idiotic sarcasm.
Yes, originally they (Vekselberg/Medtronic) wanted to get $200M loan from a Russian state bank (VEB) to launch the production in Russia, but due to all the mess we have now instead of economy here in Russia VEB went into almost bankrupt state and their plans have never realised. Though single-source decree is still active and will be enforced on Jan 1st, 2017.
Last month I saw a machine similar to this [1] at a trade show in Guangzhou, I asked some kids after they finished playing, they all loved it very much.

[1] https://detail.1688.com/pic/536274760161.html?spm=0.0.0.0.J0...
What would be better would be FRAND-style licensing requirements on prescription medications and the application of patents on medical devices.

Beyond this would be a requirement of two sources for ALL medical prescriptions and devices in order to sell them in the U.S. (or whatever country you, the reader, are in).

This would ensure at least competition, even though there's still greed there can be momentum for competition.
Depending on how source programs are split up into files, parsing can be easily parallelized (think one thread per file), while other compilation tasks are harder due to interdependencies. E.g. semantic analysis requires building type representations, global namespaces, etc. Code generation is (usually) parallelizable as well, but there are a couple very serial steps in the middle, too.

My experience is that parsers for source languages can reach into the 1-10mb/s range, and depending on how complex the IRs and transformations are after that, code generation is usually around 0.5mb-5mb/s. The stuff in the middle (dealing with IRs) is harder to measure in terms of bytes.
The oil and gas we have already tapped will take us past 1.5°C
17 Best Resources for Rails Developer
This is the first edition. The current edition is the second edition.
Not sure if relevant, but in Oslo today a half-foot sub-of-the-day with no drinks runs you $5.50 canadian.
A big mac with a menu is $14.50
Scott Alexander at SlateStarCodex wrote a nice article about this:

http://slatestarcodex.com/2016/08/29/reverse-voxsplaining-dr...
I am not saying it needs to be young, Norwegian women, but who would you expect to see cleaning toilets?
Who will own the intellectual property rights on the discoveries ? If it's Zuck, then I'm not interested.
I doubt it. Health care CEOs, like their money guaranteed just like everyone else.

If HIV/AIDs is cured, it'll be at a $500,000 payment that can be paid in instalments for the next 20 years---20 years of actually productive life that they may have not had if they had to suffer through 'treatments' where too many setbacks will lead to death.

What will likely happen in the US, is the government will guarantee loans for these treatments and the prices will skyrocket. It'll be worse than the student loan crises of today, but hey... at least less people will die.
Don't compare numbers with EQ. Use = or EQL.
Unfortunately the "monopoly" in this case is as a result of our IP system.
> Maybe it was the tone that got you banned?
You have no basis for this statement.

> BracketHighlighter is a third party plugin, so nothing to prove some ST3's supposed "crazy architecture".
BracketHighlighter is forced to do things in a certain ways by ST3's crazy architectura.
At this point the only thing that keeps me on Windows are the games.
A virtual memory system for a kernel.
Secure distributed information and password management (Verizon patent)
Part of the confusion for {c,m}time probably comes from

[c]time: [c]hange [m]etadata
[m]time: [m]odify] file [c]ontents
How do you even end up wanting to use Guile if you hate Lisp? The value proposition of using Guile is essentially that you're now using Scheme. You'd be hard pressed to find all that many features that are unique to that system that aren't there specifically because it's Scheme, so how do you even end up wanting this if you find the idea of Scheme/Lisp so offensive?

Also, what is it that you find so repulsive about Lisps?
A full time shift job with no overtime at a normal grocery store (40 hrs/week) should earn you about 350 000 - 400 000 nok, or usd 42-48k

Keep in mind the cost of living is high in Oslo.
Don't underestimate the complacency of the public.. Most of this information (campaign funding information) is publicly available in the US as well... it's just that most of the population doesn't care... they're more worried about one of those damned (insert other party here) getting into office.
Because await import() can be used inside if statements or similar.
See it the other way round. It costs him $1.5k plus lawyers' fees to bring it to court, and the burden of proof is on him to prove you registered it in bad faith or are using it in a manner likely to benefit from confusion with his trademark. He probably wouldn't win even against a letter drafted by you that simply states that you registered the domain prior on $DATE prior to his registering the trademark, your development plans for the domain involve are in $INDUSTRY and there is no realistic expectation of confusion with his newly registered service mark. So you can probably interpret the threat as a bluff, and if he actually did follow through with it, it would cost him a lot more than the $200 he's offered so far.

That said there's probably little reason for you to turn down a less insubstantial offer for a name which generates you no revenue and presumably isn't integral to your development idea if you ever choose to pursue it.

I'd have thought that calling his bluff was the right response, along the lines of
"I registered the domain X years prior to your decision to adopt a variant of that name for your own purposes. My development plans for this domain in $industry do not involve financial services in any way and thus no possibility of confusion with your financial services firm exists. Any move on your part to pursue this via UDRP would therefore almost certainly be a waste of your money and time. I have invested my own money and time in the domain and my development project for it, and have no intention of changing my business plans unless it is financially worthwhile for me to do so."
I suspect that modern languages try and fix some of this by making the syntax unambiguous. Means you only need to tokenize each file exactly once. Compare with older languages where if you change a header/module/etc you need to reparse the whole shebang.

Possible with rust that moves a bunch of the grant work into the code generator. AKA where as in C/C++ by the time you're generating code all your type information is set in stone, possible in rust a bunch of stuff isn't resolved yet.