skysight-inc/HackerNews huggingface dataset:
Note sure what you're arguing against. I stand by my claim.

I'm actively working with Scala's macros and played with Scala LMS. In fact working with those convinced me of how much all LISP alternatives suck for expressing macros.

Do you know why? Because in these languages macros are not first class, hence (1) they tend to be an afterthought, (2) hard to use and (3) filled with bugs because, wouldn't you know, they are targeting "library authors" and not users.

Scala's macros for example are exposing the compiler's internals. And boy, I can tell you stories. Like how it wants an "untypecheck" call on the AST if you modify it, because those ASTs happen to be mutable (the horror), but then "untypecheck" has a bug in it, crashing the compiler if you have an implicit "unapply" in a pattern match, so you have to rewrite your AST first to get rid of implicit "unapply" calls to work around it. Behold Sincron, an otherwise simplistic library, for which it took me a whole month to achieve inlining Function0 literal arguments, with help from others and copy/pasted code, between cries that I crashed the compiler, again and again: https://sincron.org - and btw, this rewrite for getting rid of unapply, this was the still-dangerous shortcut I took, because the general consensus at this point is that if you want to workaround the bugs of "untypecheck", you need to fix that AST manually.

You can't blame Scala too much really. This is definitely preferable to hacking your own compiler plugin or to forking the compiler. And eventually beautiful solutions can emerge from that.

The alternative to something like this is to expose a limited form of macros. For example F# quotations, or Rust's macros, since you mentioned those. The problem with these macro systems is that they are very limited, only applicable to a narrow set of use-cases. Sorry, but I personally think Rust's macros are next to useless as they needlessly complicate the language without that big of a gain. And the irony is that macros are basically used for error-handling in Rust. You know, if they added higher-kinded types, there wouldn't have been such strong demand for those macros in the first place.

LISP is the only language (family) exposing macros to users.
You are correct (Datawire.io employee here) and I work with the author of the article. Most of our shared frustration stemmed from the API gateway. Lambda as asynchronous event handlers for SQS etc are great. I used it at point to automate DNS assignment for autoscaled servers not behind an ELB.
Rich provided the Haskell translation at https://www.reddit.com/r/haskell/comments/2cv6l4/clojures_tr.... His point was that some aspects of transducers were not possible to capture well in a type signature.
> My guess is that you haven't actually had to deal with any large rails applications,
> The abstractions Rails uses are fine for a relatively small app (up to 10 models). Beyond that is where the complexity mushrooms and the framework starts dragging down the project.

I've worked on several rails applications with a lot more models than that. Some with over 100 models. ActiveRecord has flaws, but I never felt it was a great impediment to getting things done.

A bigger issue (as you mentioned) is the large number of gems that are abandoned or sporadically maintained. I don't see that as a rails specific issue, but it seems to rear its head most often with gems that interact with rails.
If you want the best, get Canon's image-stabilized 15x50 binoculars. Image stabilization is a miracle technology.
For the older folks in the crowd ... https://www.youtube.com/watch?v=Y04CtbRKAPY
> Because it’s always about other programmers when the value of sharp knives is contested. I’ve yet to hear a single programmer put up their hand and say “I can’t trust myself with this power, please take it away from me!”. It’s always “I think other programmers would abuse this”. That line of paternalism has never appealed to me.

Well, then, I will put up my hand and say "I can't trust myself with this power." It is why I prefer languages with rich and static type systems and languages with a compilation phase (but it isn't just about type systems or compilation). I often want to trust myself in the present, but I know that trust is often misplaced; I don't trust myself in the past to have written stuff I continue to understand and be able to make changes to, the more that I've used sharp knives.

(Perhaps this is a sample bias, in that people who don't trust themselves with this power are unlikely to use Ruby unless forced to. I will admit that I am not a Ruby programmer and don't see myself ever choosing to start a new project in Ruby, though I'm not opposed to working with an existing project in Ruby.)

I deeply understand the value of monkey-patching. I worked for many years on a product that relied on IAT patching/LD_PRELOAD/DYLD_INSERT_LIBRARIES to intercept all reads and writes. My personal domain is ldpreload.com, and I've written an LD_PRELOAD/DYLD_INSERT_LIBRARIES library for Rust. But using a preload library is being very explicit about opting in to monkey patching. The option of spooky action at a distance is great; having it without any clear opt-in to what spooky action is happening and at what distance is an entirely different matter.

Similarly, I have sharp knives in my kitchen drawer, but they're all in blade guards/sheaths. I know how to use them safely, but when I don't want to use them, I want no risk of them cutting anything.

On another note, dismissing this as "paternalism" is sort of wrong when the objection, as I hear it, is generally "I have tried to maintain codebases from other people, and they should not have been trusted with that power, it turns out."
How I'm Making a Mid-Life Career Change to Information Security
"Sir, I promised the client that it would have Feature X, and the developers are refusing, saying it will take too long!"
The mention for HN is good. The characterization of Bill Maher as centrist is questionable.
How hard is insider trading to catch, really? I'd assume a high level conversation between two executives over golf and bourbon is pretty damn hard to audit.
> All forms of interruptions trying

Yes, exactly. What really struck/scared me was how this kind of AR would really prevent me from concentrating on anything for more than 1 second at a time.

I'm sure commercial interests would want this type of thing, but presumably they'll need some humans to actually pay attention to things so that they actually have some pool of people to recruit programmers from... but maybe they aren't thinking that far ahead. Maybe the 'dead end' for humanity will just be some type of AR where there's no way out because there's nobody outside AR enough to do anything else than just sit there in rapt attention. Hmmm... maybe I just had an idea for a dystopian sci-fi novel.[1]

[1] Yeah, somebody must have thought of this before.

EDIT: Just grammar and things. Plus, I discovered that I actually really like the word 'actual'.
Campaign to Open Source VB6
That was in the early 90's, when most papers were still distributed as, well, paper. Back then, someone had to build and run an actual printing press.
Diving Atlantis – Roque Del Conde. Mountain of Last Heroes of Guanches
Well, it's really a feature about Medzhitov when you were expecting the typical "A New study says!" type of article.
the point is that if you are interviewing 30 people for every hire you are spending way too much time and effort on interviewing. if you had better recruiting funnels you could easily get down to 2 or 3 interviews per hire
So, $2,257/mo for 15Mreq/day ≈ 174req/sec

Practically any smaller instance type (i.e. m3.medium) can handle this small of a load all by itself, without even breaking a sweat.. and instead of paying $74 per day, it would cost less than $74 per month.

In fact, ELB + an ASG of three t2.micro's running continuously would cost around $49 per month, not per day, and possibly around the same amount of effort (or less) to create/maintain/manage.

It's somewhat apples and oranges, but there's no doubt that lambda is expensive compared to plain old EC2, and that cost disparity increases linearly with scale.
We've built a CSS based language to enable designers to easily make their SVG graphics dynamic and customizable. You're right though, it makes no sense to put it there while it's pending, I'm removing it. Thanks for asking!
Or NYC. Or another major urban area with plenty of tech jobs. Anecdotal but everyone I know here in tech (varying roles, skills, and levels of experience) gets plenty of recruiter spam. By contrast, I do know similar people who have had a tough time with the only difference being they're in a smaller market in the interior and are not willing to relocate.

I think location really matters a lot. Telecommuting has not made it irrelevant. There's strong network / market effects for an industry with frequent job hopping and frequent changing of company hiring needs -- employees want to be somewhere with a lot of employers and employers want to be somewhere with a lot of employees, so the top few cities end up taking the lion's share of the tech work.

If anything, easier communications maybe has made it easier for companies to just open up an office somewhere just because that place has a lot of prospective employees. Maybe in an earlier era slower communications with colleagues in other offices might have made this less attractive, but it's so easy now. E.g., tech companies starting in SV but then also opening up an Austin, Pittsburgh, London, Seattle, NYC office because there's plenty of prospective hires there. What you don't see them do much is also open a St Louis, Tampa, or Little Rock office. It's just not worth it.

DEFINITELY consider trying moving to a major tech hub, or just a bigger city at least, if you have persistently had a hard time finding a job locally.
I do read posts, and I wrongly implied you end up preferring other means to email because people don't answer to emails, sorry about that, but let me expand on my thoughts.

I get that too, people not replying, but I don't think this is only a technical problem unfortunately. With IM systems where you easily get notifications on your phone you have more chance to get a faster response, also when receiving large amounts of emails one tends to skip many of them.. frustrating, for the sender, but that happens to me too from time to time.

I do work in tech though, also in academia, and email is still the first choice (well, from my experience, also I am in Europe.. maybe this counts?)

As for the technical aspect, SMTP and mail transfer protocols are part of a distributed system, and a distributed system must be open, this of course leads to the SPAM issue, but after what, more than 30 years? we have a couple of strong server side implementations that work well.
And let's not forget TLS... emails travel in the "open air" as every other protocol that does not use encryption.

I agree that a redesign would be helpful to eliminate some basic issues we still have with emails, but it looks like that at the moment most are busy inventing new proprietary protocols for new way to chat and send emoji around...
I agree, there's a balance. I don't personally think that sales people have no value.

I think my point is that with sales people, there's usually actual numbers involved (that the salesperson has visibility of), which can help anchor perceived value. But it's still potentially hard to actually determine value.
Why the Future of Work Is Remote
But why _force_ it with different APIs?

Is it impossible to imagine a set of applications (ie: generic Bank of America banking app: take pictures of checks and send them in sorta thing) where the UWP model doesn't help?

If you need a 2nd application for your task, then write two different UWP applications. If you don't, then write one application with two XAMLs. If you want a very cheap program, write one application with a "responsive" XAML that works on all systems.

By unifying the code base, you have the flexibility to do whatever code you need. Different code paths if the applications are grossly different, or the same code path if you need to save some money.
It's kind of weird, that we're starting to get a generation of new programmers who weren't even born when that essay came out.

I'm starting to feel that teaching a history of computer science (in terms of sociology and insights, not just programming) would be a great addition to the curriculum in college. Some familiarity with classics like The Cathedral and the Bazaar, Fred Brooks' The Mythical Man-Month (which predates even my old-timer ass), The Agile Manifesto, and other masterpieces would teach students a lot that they may otherwise have to learn the hard way, or won't learn at all.
Yeah, but India has more than a billion people and they have nukes. As the parent comment said, Holland is tiny and not only geographically or in population.

- It's barely in the top 40 military world powers: http://www.globalfirepower.com/country-military-strength-det...

- It's 17th on GDP: https://en.wikipedia.org/wiki/List_of_countries_by_GDP_(nomi... (actually below India and Brazil and not so far from Nigeria)

As part of the EU, Dutch people live in the (arguably) world's biggest economy. Outside the EU, they're just 17th and far from most of their neighbours.

You punch above your weight in football though :)

The EU is far from perfect, but we're the ones building it.
Unfortunately, the pairs that I have are all no longer produced. If I was in the market today, I'd probably look on Craigslist for some high-quality second hand binoculars. That way, you can go and test them in person after you've researched them online, and you should be able to get more for your money compared with buying a new pair.

For astronomy, you want a large objective lens:magnification ratio, because the higher the magnification, the dimmer the view. For daytime use, this doesn't matter, but for looking at faint objects at night, light-gathering power is everything. Get this ratio at least up around 5, or ideally 7, so 7x50mm binoculars would therefore be better (and lighter) than 10x50mm. I'd start with those before possibly getting some larger (e.g. 15-16x70mm) ones, or just moving straight to a telescope.
Not sure it makes sense to say this is American vs non-American. Normal American newspaper stories adhere pretty well to the inverted pyramid structure, and the wiki article even suggests it first became prominent in the US:

https://en.wikipedia.org/wiki/Inverted_pyramid

It's really about news vs. human interest pieces, and many outlets (like the NY Times) feature both. Seems possible to me that American outlets produce more of these, but it'd be hard to disentangle this from the general dominance of American outlets on the English-speaking internet, such that non-American pieces are more likely to be directly local and, so, news rather than human interest.
This same person did another movie along the same lines a while ago - this one in the home. I think the hyper-reality got quite a bit more hyper since last time...

https://vimeo.com/8569187

There's an interesting mechanic there. The person is seen modifying the advertising intensity while something to do with money comes up on the UI. It looks like you get paid to sit in crazy ad land, use the "service" for free with less (but still ridiculous) ads, and presumably, you'd pay for ad-free.
Hey Sam, great to see you commenting on this :) I started contributing to DM when Dan was already in charge but I was a DM user when you were still working on it.

Anyhow, you made really good points here. I've worked on ORMs for a couple of years before I concluded the same - NOT WORTH THE EFFORT.

My approach with rom-rb is functional, as in this project works more like persistence libs in functional languages, rather than an O/R mapper. I removed the whole idea of mutable objects and managing their state using UoW etc. This simplified the stack a lot, and despite a complete lack of any performance-related tweaks rom-rb is already faster than ActiveRecord.

I also agree with your opinion re validations. I removed this concept from rom-rb as well and built a standalone validation library instead. This works very well.

Cheers!
"We want to change the world, by finding a more efficient way to bike courier organic Nicaraguan coffee beans to your doorstep in the Mission or SoMa."
Modern graphics hardware isn't optimized for drawing bitmapped lines. It's optimized for drawing textured triangles. This means that it's not actually a good fit for GDI any more. Given that Windows Phone was, as far as apps were concerned, a clean slate, there was little reason to retain USER and GDI.

win32k.sys is also rife with security flaws, so scrapping it has arguably reliability benefits too.
This is nonsense: the commissioners are not a self-appointed oligarchy. They are appointed by the European Council, that is to say by the head of all EU states. It is called indirect democracy, and is certainly not anti-democratic by any stretch of the imagination. If you don't like the EU commissioners, the fault resides solely on whoever we (European citizens) collectively picked as a our respective head of states (in my case that would be François Hollande, the French president).

Don't get me wrong: I would prefer for the EU commission to be elected more directly by the European citizens. And I certainly wish that the European parliament had more power. But keep in mind that the only reason it's not happening is because the various EU governments don't want to give up too much power: they have full control of the EU commission, but not of the EU parliament / EU citizens...

TL;DR: power in the EU is held by the European Council, that is to say by the head of states.

EDIT: typo
What's new since (Debian) Jessie?
Cheaper? How so?
ESR has said some wacky stuff over the years, but this was a hugely influential bit of writing, and I'm very grateful to him for it.
And what if a candidate has a good background in computing, computer science, AI, and pure and applied math and, then, also a good STEM field Ph.D. degree from a leading research university.

Do you want to "hire the best" or do you want to reject anyone with a Ph.D. degree? E.g., how many STEM field Ph.D. holders have you hired to date?
I don't understand why Christians get anxious about applying events in Revelations to the current day. Do they not believe that they aren't going to be here for it?
That's just mild racism. The answer would depend on the competency of the individuals involved, not their nationality.
Could someone explain what the paragraphs under "Map specs should be of keysets only" are getting at?

I'm trying to map it onto my experience with Clojure and plumatic/schema, but nothing is clicking.
See e.g. https://hackage.haskell.org/package/foldl-transduce

(That's just a random package from a 5 second Google search -- I think there are several at this point. Some of them even generalize transducers, I believe.)

EDIT: Thanks for the link, btw.
Possibly, but I can have my client delay-submit successful work as to game the system.

And when Ethereum switches to Proof-of-Stake, bad shit will happen. (Mainly, its when you wager eth coin on the fact you have a correct-work. Its not hard to see the badness from that...).
I believe that's open to tampering by miners (more easily than a sybil attack, IIRC).
I worked at a company who almost passed on a candidate because the company thought the offer was too low, and they were worried he'd get frustrated and move on.
> Instead of encoding constraints as type signatures, the Clojure folks (true to character) encode them in data.

I've never bought this line of thinking when the "Clojure folks" also say "code is data", because then a syntactic type signature you write down is also just data. If you want to consume the type signature (or spec signature or whatever) as syntax (as a sibling comment suggests), use a macro or any other program which consumes programs.

The thing I do see as being important is not how you write these things down, but whether they have an accessible representation at run/read/compile/whenever time.

Lastly, I strongly disagree these approaches are meant as a replacement for static typing or formal verification because (as far as I can tell) a value can be checked against a spec on demand, but makes zero guarantees as to what that value does in other parts of a program. This is also in contrast to Racket contracts, which will give you the correct blame information between parties using and not using contracts.
I get that it's necessary for running them on Linux, I just question the need to do that in the first place, instead of creating new, Swiftier APIs. NSURLSession's delegates have optional requirements, for example, which aren't supported in pure Swift code.
(Sorry about that, but we can’t show files that are this big right now.)

Uh oh
Ask HN: Passive Income Suggestions 2016
Similar questions have been asked in the past, but things change quickly. What are some passive income strategies that have worked for you in 2016?
Well, one of the secrets is this:
https://en.wikipedia.org/wiki/Greenspan_put

Which is a form of subsidizing speculative bubbles.
This is a very good idea. Are you planning to make it marketplacable? So that there can be creators of SVGs as well.

Also, right now, when I look at the pricing section, only an empty modal dialog shows up (el capitan, chrome, ad blocker off).
Yup. Cigars, Masons, Yacht clubs, Golf clubs, vacations to Ibiza. There's an endless list of rich only completely private locals. If people can just keep their damn mouths shut then it's all good.

And I would suppose that there's an acceleration with wealth, right? Like a cosmological constant of wealth gap, reset in some places every once in a very rare.
I'm assuming the vision you're trying to sell is to make the philosopher king wealthy. (Your stated vision is probably irrelevant.) You need to make your employees' incentives align with that proposition.
Visual Basic Turns 25
They should do some research on tree pollen and why my body thinks trees are trying to kill me.
Does any one have a guess as to how future-proof these current chips are? Just like other new tech products, I can't imagine that they will be fully compatible with the majority of the payment ecosystem in 10 years.
You lost 90-something percent of your territory, 90 percent of your population. You used to be the largest economy but now you seem impressed to be 5th. You used to impose your influence on all others. Now you are mostly in the receiving end.

One of the reasons you didn't wither any further is the EU, another is pax americana, as long as it lasts. As is the case for most of the other weaker economies that do 'just fine'.
Unfortunately I don't remember exactly how I did it at past but I'll try to help:

On my previous machine, with zsh, I could define my .zsh_history to be created per dir. That way I could see the history per dir.

The downside is multiple .zsh_history files per dir plus no universal .zsh_history (the default)

EDIT:
I think I have found how I have done it. I have this currently on my .zsrch
HISTFILE=~/.zhistory

removing the ~, will force zsh to create a .zhistory file on your current dir.

Hope this helps.
The thriving Russian black market in dissertations
Whoa you had a great start then ;)
This makes me think of an observation an old colleague of mine made to one of the revolving-door CTOs at our former employer. He said there are three things you can offer to get good engineers... high pay, an interesting problem, and a great work environment. If you can't offer at least two, you really need to excel at the last one.

Problem with former employer was a lousy work environment for uninteresting work...