skysight-inc/HackerNews huggingface dataset:
It is. There are a ridiculously large number of cancers and they are all different. Even something seemingly simple like "lung cancer" can be divided into several high level diseases, each of which have their own subcategories.

People who expect a one size fits all solution to cancer will be sorely mistaken
Thanks, looking forward to hear feedbacks :)
does the patent say it actually has to work? XD just saying...

i'm always in two minds about this but i lean very heavily towards culling people who think this sort of thing should be patentable. i think it would benefit everyone for the entire future mostly...
> How do you provide typing across modules? With type hints?

By only exporting simple functions (which only take DSL commands and return DSL commands) out of the modules - it works well with Racket and some other Scheme implementations, for example. In Clojure you can simulate this with namespaces and an explicit "(require ...)" which can be easily followed by the static tools.

This way every name is either locally defined or coming from one of the modules you explicitly required, and with no higher order functions allowed in between modules you can track everything to its source.

> let's say for a UI form case?

That's the most classic example of this approach, used more widely than any other message DSL case.

An UI frontend is forming messages (like "(button-clicked 'Save)" for the low level approach, or, for higher level, like "(ui-do-save)").

A backend is receiving nothing but a stream of DSL commands from the frontend (i.e., no API calls in between, the stream can even be serialised as text), and execute them one by one, replying with another stream of DSL commands for the frontend (like "(go-to-dialogue 'Choose-File)", or "(hide-save-options)").

The more abstract your command stream is, the less changes need to be propagated either way.
If I can't come into your office and have a copy of your software running or successfully compiling on my machine in less than an hour, something is very wrong with your documentation, tooling, or (lack of) build process.

So that's why your first project here is going to be writing up some stuff so that it's easier to bring future people on board!
You should read http://gavinandresen.ninja/why-increasing-the-max-block-size...
Never Trust a Corporation to Do a Library's Job
That's highly debatable: for example BeOS recreators/Haiku devs CHOSE to use a new exotic kernel instead of Linux or FreeBSD kernel.

But their reasons seems mainly because of NIH syndrome: those who like to create a new OS also to tinker with "their own kernel" instead of reusing something already existing.
For a language with macros it does not matter at all. You can add any type system you like on top of it. Metalanguages are infinitely flexible.
Two ideas:

There are gloves aimed at photographers that either have thinner material at the fingertips, slits to stick the fingertips out of or removable tips.

Glove liners made from silk (intended to be worn under thick gloves, like socks are for shoes) can be really thin, maybe combined with a fingerless glove?
You mean like California?
:-)
Indeed and the "I know you put it in quotes but I'm going to return none-literal matches as well".

I guess the fundamental problem here is that optimising for one group sometimes comes at the expense of another and statistically we (meaning developers) just aren't a big enough group to matter.
You could cut the fingers off a pair of cheap gloves.
Well, this is assuming a honorary doctorate isn't really a diploma
Mostly, but I'm pretty sure Clojure's range gives the integers from 0 to 9.
A UDP packet walks into
The end-products - games - do have linux support. But the support is not that great, for example the unity engine on linux doesn't seem to support vsync (it says it does, but it doesn't in practise) which results in horrific and annoying tearing. It has been like this for well over a year, with no sign of any urgency to fix it.

It is nice that "linux support" is a bullet point that companies feel is worth having, but it isn't a significant enough part of their market for them to make it work without glaring issues, often.
I understand the need for expressions-in-literal.

I really don't understand why the unnecessary extra "!rsa" modifiers are a good thing though.
Good documentation can do more than that I think, take http://knockoutjs.com/ there documentation is incredible, I went from not been able to use it at all to using it comfortably in a week or two and most of the questions I've had since have been answered by the docs.

It's pretty much the standard I'll aim in my own documentation in the future, lean, precise and covers the main cases with useful examples.
Why should we accept medics stealing the meaning of a title that was created for academics?

The real question is why are medics without any form of doctoral degree calling themselves 'dr'?
Onboarding is a people/process/docs/technology problem. To the limited extent that it is a technology problem, you really can't go wrong with a) treating it like it is an actual shipping product of the company (implying a minimum standard of care like e.g. a repository, documentation about it, and a dedicated place to put issues) and b) actively maintaining something with the goal of getting someone up-and-running quickly.

None of my projects are at the point where you can just "vagrant up and go", but the next-best thing has been READMEs in the relevant repositories with exact lists of "Type this, type this, type this, type this. You now have a fully-working system running on localhost and you should be able to type this to get a full green test suite. If you can type this and it does not come out green, fixing that is more important than anything Patrick is doing right now."

Here's, for example, what we have for getting someone up and running on Appointment Reminder (in preparation for me soon no longer being the engineer who keeps all of that system in my head): https://gist.github.com/patio11/a0b1063c5d33b5748da6 Feel free to steal ideas in terms of level of detail or useful things to include. (A lot of the magic is in the rake commands like "setup_site", which take care of "All that crufty configuration stuff which you would otherwise need a senior engineer to do for you prior to actually seeing the page render correctly on localhost:3000.")

Quick hack which helped us on making sure this guide was actually accurate: we had two engineers coming into the project at the same time. I wrote down everything I thought they needed to know. Engineer #1 implemented to the document I had written, filled in the blank spots where he needed to ask questions, and then we committed the readme. Engineer #2 then had to do it off the readme without asking me any questions. Given that he was actually able to do this, we have high confidence that there is not at the moment anything rattling around in my head which is absolutely required to get up-and-running and documented nowhere else.
Free Newsletter – Legitimate Work at Home Jobs and Opportunities
You can get pretty tough protection with address sanitizer (it works technically a bit different). It doesn't come for free however.
It's much faster and better than anything that was there before (e.g. valgrind), but the performance impact is still significant. Still I think address sanitizer is an amazing project that should definitely get some more publicity.
What is your other business? Why is it failing?

I appreciate you're trying to hang on in there, but it might be better to cut your losses and move on to the next thing.
I think there was a general perception that text based MUDs would die when graphical MMROPGs became mainstream because graphics were just ''better'' in every way. Personally I prefer text in many ways to graphics. It's like reading a book versus watching a movie. Although the most popular text based MUD only ever had a few thousand concurrent players, whereas (from what I remember) World of Warcraft peaked with close to a million.
Very cool - thank you for pointing me to this!
God's world is perfectly just.

Liberals love evolution.

IQ is inherited, obviously or the smart monkey wouldn't evolve.

Once meritocracy is established, it takes one generation for high IQ to go to top. Then, no class mobility because high IQ is at the top and their children are at the top.
This is not any different from a macro. You still translate your DSL into your host language AST, with the only final step different - runtime eval instead of a compile-time macro.

All my macros look like (defmacro something (dsl) (compile-dsl-whatever dsl)). You can always pass the same (compile-dsl-whatever dsl) to (eval ...).
One problem with the meritocracy is achievement laundering. For instance if you get through Harvard you really have run the gauntlet and worked very hard, it gives you more of a feeling of entitlement.
An ad blocker is important. I'm not a fan of ad blockers in general, but there are so many awful ads out there that young children definitely need them.
It's Skyler[0]: it's a fashion weather app. We are bootstrapped and can't raise money so we have to shut down at the end of the month... :(

[0] https://itunes.apple.com/app/id1011881829
A Peek Inside Mr. Robot's Toolbox
how much faster is 3d printing a mesh rather than a solid, you could 3d print a lot more, then chuck it in a bath to gain thickness and strength.
You can get built in decoupling capacitors: https://www.mill-max.com/products/socket/122-XX-XXX-41-80100...

You could certainly estimate the clock frequency in advance. The things that are going to cause trouble are transmission line effects (ie pulse length no longer >> wire length), and the usual digital logic critical path constraints: wire and gate delays; clock skew and drive strength; fanout constraints.

More decoupling doesn't help you once you have enough to prevent crosstalk through the power supply. Star-routing the power and ground may be a good idea.

I've done 20MHz. Coincidentally this is the limit of cheap scopes. This page claims 33MHz is achievable, and gives a good explanation of why: http://www.sigcon.com/Pubs/news/2_8.htm

Some good tips: https://www.pjrc.com/tech/8051/dev-board-wirewrap.html

Reccomendation to use the kind of board with built-in ground plane (sounds good if you can find it): http://www.williamson-labs.com/prototype-lt.htm

For IC availability, check your local Digikey. Note that 68k is still being manufactured as "Coldfire" by Freescale (with slight backwards incompatibility).
They tell people to avoid the things called objects in OCaml which essentially are just row-typed dynamic records and an inheritance system. Really it's the inheritance system people are taught to avoid... Same as anyone in OO is being taught now.

OTOH OCaml, as an ML, inherits an outstanding module story which is really the core of OO anyway. I'd happily say OCaml is a better OO language than Scala for that reason.
Happy to hear it! I partly made this notebook to convert my coworkers and collaborations to a Pythonic workflow, so this is promising... :-)
No, you do care about political leanings. There's always going to be office politics. What you perceive as "politics" is politics you dislike.
You may find value in appcatalyst by VMWare. It's in tech preview, so it's still free.

http://blogs.vmware.com/cloudnative/vmware-appcatalyst/
I don't think that fits the facts of this case, but then again, I haven't been monitoring the mailing lists. It does seem from developer reaction that it came at them cold.
I think connecting (carbon) tubes could be a way to go.
Coffee... lots and lots of coffee. :-)
This exists for years: https://msdn.microsoft.com/en-us/library/windows/hardware/ff...
You should not forget about oncoviruses (e.g. EBV, HPV), also many oncogenes have viral homologs (e.g. RAF genes, https://en.wikipedia.org/wiki/C-Raf)
This is not a one time vote. This is voting over a significant period of time and powers are not fixed.
This is pretty racist, "mon".
Be careful of the law of unintended consequences. Rainwater capture will be fine so long as only a minority do it (how small I don't know) or only a fraction is captured but if everyone does it then it will change the economics of water supply and give people incentives to use the captured water for other than lawn watering. For instance they might use it for flushing toilets or even bathing. the problem that then happens is that the local water table will fall because it is not getting the water that it used to because that water is now flushed into the sewage system.

I'm not arguing against the idea, especially as it is typically implemented in the UK where a house will generally only have about 500 litres of storage, but scaling it up and making it a requirement could cause some interesting problems.
I wonder if it's possible to 3D-print titanium mail (aka "chain mail") at a competitive price? Titanium is great stuff for high-end mail, strong, lightweight, shiny, and corrosion-free, but it's even more insanely labor-intensive than ordinary aluminum or steel mail, especially if the links are welded or riveted for strength; prices appear to start at well over $2000 for the equivalent of a T-shirt.

I think you'd want to print it in a sort of collapsed/"wadded-up" form, to reduced the print size and to insure you can get enough separation between the links that they don't bind together. You'd need some pretty fancy algorithms to translate the client's measurements into a wad of printed mail that will be the right shape/size when spread out, but once you got that down you could just plug in the numbers and watch it go. If you could get the price down to something decent, I think you'd get a lot of business from SCAdians/fantasy fans/etc.
you probably should rather ask those questions through OPs website? :)
As a proposal before they made the decision. Getting input on an already made decision isn't input on the decision.
Depends on application type and device.
I wouldn't hold my breath, e.g. in games - one of the most performance-critical apps - the best idea so far is to spin one thread for physics, one thread per AI, one thread per game logic etc.
Here is a good blog post describing how sad the things is: http://bitsquid.blogspot.co.uk/2015/03/multithreaded-gamepla...
Email Hacking – Is your business at risk?
Nowadays, everything is considered racist.

EDIT: See what I mean?
What!? Size of the array is always known to the programmer in C. In fact, if the programmer wants to get rid of that information, he/she must deliberately do so. Once one does that, the array becomes useless.

You also haven't explained how would that size information, which we already have, magically solve the problem.
According to source on GitHub, it appears support for Commodore 64 and 128 platforms is part of the 3.0 release.

https://github.com/contiki-os/contiki/tree/3.0/platform/c64

https://github.com/contiki-os/contiki/tree/3.0/platform/c128
I wish everyone took onboarding seriously.

I worked for one company for a month. From the get go they had 100+ staff but no onboarding. Nobody knew how to set up the development environment or even get the application working on the company laptop. Nobody could show me how to VPN to client sites or show me how the software worked. I was meant to support it...

I was in my manager's office every day letting her know hey I really need assistance here, nobody seems to have time, nothing is working, I'm not learning anything and this needs to improve.

She'd tell staff to assist and they just wouldn't. And rinse wash repeat the next day.

A month in we are in a meeting and some difficult software issue comes up and it's assigned to me to fix. I mention that I don't have it running, don't know how to use it, have no method of finding who the customer contacts are to call them and will sound stupid not understanding anything, but also haven't been shown how to connect in. That I'm happy to shadow someone else and learn it.

It felt shameful but I knew it was the right thing, I had a year of extensive help desk experience under my belt including programming and other development, bug fixing, accounting, you name it, I was even team lead. I was used to dealing with multi million dollar clients and had no qualms about doing so... but this place was dysfunctional.

Anyway the boss stared me in the face in the meeting and called me a liar, to shut up and get to work. I was stunned. I repeated myself and she turned to my coworkers who claimed they had "showed me everything". I hadn't spent more than 5 minutes with them in the entire month and had been in her office every day. She told me to start pulling my weight and stop lying.

I walked very calmly to the office printed out a resignation and left my keys and walked out the door. I didn't get paid (a funny side effect of walking out of a job) and the move left me penniless and ALMOST homeless.

Luckily I got a job just in the nick of time shortly after, at twice the pay, and being treated like a human being. I removed that place off my resume and rarely discuss it because it's so humiliating.

I still remember the recruiter calling me screaming how unprofessional I was - he only cared about his lost bonus. I explained I was extremely professional but that after being humiliated and called a liar in a meeting and having none of the promised training, or anything remotely capable of making me a functional employee, there was no recovery.

Now I take onboarding very seriously.
Well, they did try to push it for other things. That was their original intention.

Of course, it didn't catch on, so Firefox was stuck with an obscure UI language only it used.
Add Carin Meier Living Clojure to your reading list
http://gigasquidsoftware.com/#/books/index

Clojure for the Brave and True is a great way to get your Emacs setup.

If you are going the light table route then start here:
https://github.com/swannodette/lt-cljs-tutorial
or here http://clojurekoans.com/ with videos https://www.youtube.com/playlist?list=PL1p6TgkbKXqyOwq6iSkce...
Check the validity of the dates above. Both lessons are an easy win to gain syntax knowledge.

Watch this for a brief overview:
Frameworkless Web Development in Clojure by Andreas ‘Kungi’ Klein
https://www.youtube.com/watch?v=_LghX4oDWcY

After you get http://leiningen.org/ installed on your linux vm then start hacking on this:
http://www.luminusweb.net/

Next post your code review and questions up here:
https://www.reddit.com/r/Clojure/comments/3ibjfg/new_clojuri...
and here
http://clojurians.net/

Rinse and Repeat.
You know, they could always check relative watchers and other marks on GitHub for example.

Doesn't have to be an exact science. How do we know Knockout is less popular than Angular? And yet, we do.
BitCongress anyone?
Even if that were true, it wouldn't stop some things from actually being racist.
> Sierra just released a new King's Quest game.

Yes, but in a completely different format than the original. The value in the new King's Quest game is the story, as told by some excellent voice acting, not in the ties to the King's Quest franchise or the old style of gameplay.
Paxos is one of the simplest distributed algorithms out there.

For a proposal i with value x:

1. Ask everyone not to participate in proposals older than i, get a majority to agree and send back any previously accepted values.

2. Ask everyone to accept proposal i with the newest previously accepted value or x if none, get a majority to accept.

- On failure, restart with i > max(previous proposals)

That is the Paxos algorithm.

Its fault-tolerance comes from the fact that you can tolerate losing the minority (1 out of 3 / 2 out of 5). There's no magic. If the majority fails, Paxos blocks. If two proposers keep blocking each other's proposals by going through round 1, Paxos can take forever.

The goal of Paxos is to agree on 1 value. Once consensus is reached (majority agrees), the value can never be changed, since no one can complete round 1 without getting back the newest accepted value from at least one node. However, you can run Paxos again and again to agree on a sequence of values (e.g. transitions in a state machine). This is Multi-Paxos.

The Paxos algorithm is optimal, but Multi-Paxos allows for a lot of optimizations and there is no clearly defined implementation. A pretty typical optimization is to elect a leader (through Paxos) which makes the proposals. This avoids duelling proposers and ensures you have a node that is always aware of the latest accepted value. Making this optimization requires you to make decisions that fall outside the scope of Paxos, such as how long a node remains leader, what happens if the leader fails, and what happens if two nodes think they are the leader. These optimizations can easily cause you to lose the fault-tolerance and consistency guarantees that Paxos gives you within the scope of reaching consensus on a single value.

It's important to remember that Paxos itself is easy to understand and a lot of the problems in Multi-Paxos can be solved by running Paxos. You need to familiarize yourself with it as though it was a programming construct.
F# has pretty good IDE support, and type providers are really nice as code completion extensions. C++ has excellent IDE support in visual studio, note I'm including the debugger here also, as that is part of the experience!

Then there is objective C, Swift, Kotlin, Dart, Typescript, some versions of smalltalk. Many of those languages were designed specifically for IDE use (dart and typescript definitely).
I remember watching the original iPhone presentation thinking "this looks OK but touch screens suck" then having the UI-design-oriented part of my brain completely blown by the bounce-back effect. No other touch screen software worked that way and it is hard to think of something physical that bounces like that (unlike the swipe-to-open metaphor).

I am not a lawyer and I have no opinion on the validity of the bounce-back patent (although the German court rejected it based of publication date rather than merit), but from a business point of view I can see why Apple was so keen to hog bounce-back for itself. I didn't buy a iPhone for a few years but they won a customer that day.
Sure, but people who commonly tout it's "not one disease" miss the broader point of the common nature of the disease(s).
The Bundesgerichtshof is also Supreme Court for criminal cases.

The phrase "Supreme Court" is indeed problematic, since we have quite a few of them (administrative law, labor law, finance law, social law, plus BGH and BVerfG), but I think it's okay to call the Bundesgerichtshof so.

More okay than calling our Federal Constitutional Court "Supreme Court", at least, since generally speaking the Constitutional Court is not "above" the other courts.
I would like to see practical use cases. A step beyond the gobyexample site. Something more like the Perl cookbook
It probably is, I haven't looked. But I went west, and stopped at other places in between.
heh. You're probably right, except I wonder if I'd be helping to keep a business going when I'm not sure that is what is right thing to do here.
If he's on the West Coast, maybe he went to Kenya by crossing the Pacific Ocean.
The website's color: red, yellow and purple.

It's obviously a humorous reference.
I was, working in a niche role which you can't find locally. MySQL DB administrator - a role which is grown organically at companies which use MySQL, it's not one which is taught in school.
I can't find it right now, but at some point someone had made a kit of bike-frame joints, with the tubes to be supplied by the builder from locally available materials. PVC pipe and hand-whittled wood with bark still on were demonstrated. It was really cool.
How minimal can a Minimum Viable Product be?
Immutable Infrastructure: Fast and Reliable Scaling