skysight-inc/HackerNews huggingface dataset:
You may have missed these three points the author listed, favoring Rust:

* memory safety without garbage collection,
* concurrency without data races,
* abstraction without overhead

Go has garbage collection, doesn’t statically prevent data races, and somewhat infamously allows for only minimal abstraction.
Ah, fair point. I've been around X for so long that I'd forgotten that being a point of confusion. I do think it makes sense in the sense that the "server" provides the resources and the client connects to them and uses them, but it definitely takes a bit of getting used to.
There is only one model AFAIK - https://www.trulyergonomic.com/store/truly-ergonomic-mechani...

It has the spacebar split with an enter key in the middle.
Indeed, http://grammarist.com/usage/heroin-heroine/
I suspect that "But at that time (early May), I was interested in learning Rust" was a big consideration there. But I can also vouch for Go's excellent cross-compilation support.
Good post and an interesting comparison with some intriguing parallels.

FWIW, this was previously discussed at https://news.ycombinator.com/item?id=10381015 (126 comments).

Also, related sidenote: I'm a Redux maintainer, and I love seeing what people are building with Redux and on top of Redux. Per the author's comments about later abstractions on top of WndProc, there's been a lot of interesting abstractions built on top of Redux, ranging from reusable reducer logic to higher-level libraries that try to simplify some of the setup process. I actually just gave a talk yesterday at ReactBoston on the growth of the Redux ecosystem, which showcases some of the variety of Redux-related tools and addons that are out there [0] [1]. In particular, libraries like Kea [2], Redux-Subspace [3] and Redux-Tiles [4] try to make it easier to define and reuse chunks of logic in a Redux app.

[0] http://blog.isquaredsoftware.com/2017/09/presentation-might-...

[1] https://github.com/markerikson/redux-ecosystem-links

[2] https://github.com/keajs/kea

[3] https://github.com/ioof-holdings/redux-subspace

[4] https://github.com/Bloomca/redux-tiles
Elixir Lang – Testing the GenStages Under Umbrella
"So unless you work at Google or Microsoft you can’t meaningfully impact the technical direction of the web"

If this is truly what you believe. You are the problem. Killing the current system does not solve anything, proposing a solution and building it does.
Better Software with Entity Systems
> Well of course - it's easier to build something like this into a clean-slate language isn't it? It's harder to build it into an existing language and VM spec with an incomprehensibly large volume of existing code to be compatible with. It's bizarre to say it's not impressive because someone else with zero constraints to work with also managed it.

I hope my original comment was relatively clear on this, but sure, it's a big accomplishment and will be a quantum leap for the ecosystem. However, given that languages elsewhere have had better systems for quite some time now, it's not like they're advancing the state of the art in dependency management.

But again, it wasn't an easy thing to do (a very hard thing even) and everyone involved deserves major felicitation.
Very off-topic:

... At the Ramada Inn in Tuscaloosa I sat outside by the swimming pool about five o’clock one afternoon ...

It looks like the illustration at the top is supposed to depict this part of the story, but I wonder why an artist illustrating an event in 1970 would include a 1986 Dodge Ramcharger[1]?

[1]http://www.cardomain.com/ride/422423/1986-dodge-ramcharger/
I remember listening to a 30 year old manager say you can't turn a C player into a B or a B into an A. That's a poor attitude for a manager.
I think the dichotomy you introduce here is false. My experience with continuous deployment is that the faster you can ship, the smaller projects get.

Instead of bundling a lot of hypotheses about possibly-valuable changes up into a big release, you focus more on the next step in the direction you're going. You release those steps one by one. (User-visibility of larger features is controlled by feature flags, but you ship and user-test in small slices.)

In that context, the whole notion of distraction is different. You have to hold a lot less state in your head. Instead that state lives in your unit tests, your acceptance tests, your backlog, and the world at large. If a given developer is releasing a couple of times a day, it's just not a big deal to find a natural stopping point, release something small, and then pick up the next slice of some longer-term effort.
Beautiful math equation rendering on iOS and MacOS
> modern thinking is "not primarily logical" and this is what I'm driving at.

Is that because "logical" thinking makes sense in one context, but fails in a better context? (ie. Pink vs blue: Change the context, understand it, and then later the knowledge is found?)
Great article. I very much agree with all the points made, and see a lot of myself in the author's hindsight about themselves.
Must watch for anyone into crypto currencies
Hackaday Prize Entry: Inexpensive Emergency Button
Yes, but the thing is you can't just do web design. Most digital agencies are more that that. You have to be able to provide SEO, marketing, and other capabilities.
Etymologically, doesn't "literal" just mean related to written word? I thought the implication was that "literally" is like asserting something is true to the extent that you would document it that way in official records.
I think restaurants would be happy to pay 30% for new customer, but for subsequent orders, Deliveroo should take smaller cuts. I wonder if something like this part of agreement.
Tables are pretty much the worst thing to use if you want it to look right on mobile.
Technical interviews: how to prepare
It's back up, for me at least.
Must have been deeply humiliating for the press to have Trump win the election after their spending most of 2016 biting his knees.

Citizen Kane Hearst days of selling wars to the people are long gone. I doubt they'll ever recover, no matter how many billionaires sugar daddy legacy newspapers. Bezos has the WaPo, Carlos Slim the NYTimes, and I don't care enough to look up the rest.
My wife and I really enjoyed our Novaform when we first got it however it has developed a lump in the middle where we usually don't sleep so it bothers the wife. We will be in the market for a new one soon.
During the last 20 years I used to prefer web apps over native (C++, Java, C#) for banking and trading applications. (although most developers didn't like to fight browser incompatibilities).

2 years ago I changed my opinion. We've developed two different user interfaces for trading at the same time. One with HTML5, Typescript, Angular, WebSockets, and the other one with JavaFX. The developement of the JavaFX based application was way cheaper, faster, pleased users more (due to multi-window!) and had by an order of magnitude fewer glitches in the UI. (But the web application was prettier).
That's the crux of this whole gig economy debate - for some people, these kinds of jobs are ideal: zero hours contracts, with the ability to work more or less depending on what else is going on in your life.

That being said, some people take these jobs because they're the only ones they can get. I don't know your circumstances, so I'm going to guess here, but from what you write it sounds like you have the safety net of your parents if things go wrong. While you study you may also have access to a student loan and/or support from your parents mandated by law (let's not get into an argument about how crappy student loans are, but at least they're an income during your studies). Since you're attending university, I might guess you're at an age where you don't yet care about paying into a pension. Again - making wild assumptions here - but if you don't have kids, you probably don't care if your work-life balance is skewed heavily towards studying and earning, at the expense of sleep and general health.

For some others, though, their job is all they have, and "gig economy" jobs are the only ones they can get. This creates the perfect environment for exploitative working practices, where dodgy loopholes are used to underpay and overwork staff, who can be dropped at an instant if the company needs to save money or if workers start to complain about conditions.

If Deliveroo and other gigs were worked by students in their free time, I don't think this would be such an issue. The problem is that, increasingly, people without safety nets are joining these companies and working effectively full time, and no longer just for occasional "gigs" a few times a week. That, in my book, requires that they are given the same rights as any other full time workers: holidays, sick pay, pension contributions, grievance procedures and other benefits.
The door handle of the Mini Cooper affords doing the Dutch Reach.

It is a circle with a shelf that faces forward in a way that makes it awkward to use the hand nearest the door to open. So, you reach across your body with your other hand and in doing so, you turn your body and head and your peripheral vision can catch a moving cyclist.
That might be the theory. In practice, even if I click the "only on Deliveroo" option, I'm looking at a list of restaurants that spend a fortune on premises and their own marketing campaigns (including at chain level); they're selling on Deliveroo not because they don't already have high marketing and premises costs (to pass on) but because they're really not expecting enough takeaway orders to justify running their own delivery operation.
I'm disappointed that all of the open-source tracing systems have adopted the Dapper [0] model. It's understandable why: it's extremely simple to implement, as it handles scaling challenges by doing client-side sampling.

A bit of background about how Dapper-style distributed tracing works. Things typically start with an RPC call of some kind (typically from an external source like a public load balancer). At that point, you must decide whether to trace this request or not, which is typically done as a random sample (say, 1% of requests). At that point, the request gets assigned a _trace id_, a random identifier for that request.

The trace id is stored in some request context and propagated to each subsequent service. Each service, meanwhile, divides up its request processing flow into a series of "spans" which represent some piece of computation. For example, a span cover an RPC call or a DB query. Spans are identified by a random _span id_. Once a request has been sampled, all spans for that request are sent to a central span collector where they're stored for later querying.

This model is simple but very limited. It's often hard to know whether a trace is interesting at the outset, hence the reliance on random sampling. For example, you might want to understand why your 99p latency is high, but if you're just sampling 1% the 99p requests will only be 0.01% of your sample.

More generally, interesting events (like errors or slow requests) tend to be rare, and sampling a random, small percent of requests is unlikely to turn up the interesting cases.

A better model, as implemented by lightstep [1] (and an in-progress distributed tracer I've been working on) is to collect all spans. Even with very high request volume it's reasonable to store all spans for at least a few minutes. Doing so opens up all sorts of interesting possibilities, because you can start tracing a request at any point during that window. For example, you might want to trace all requests that have errors in them. Or all requests that take longer than a certain time. Or get a google sample of requests across different latency buckets. Or requests that violate some application invariants you've defined.

Ultimately, though, distributed tracing is so helpful for understanding complex distributed systems and webs of microservices, and it's exciting to see more open-source competition for zipkin.

[0] Dapper is Google's distributed tracing system. The paper (https://research.google.com/pubs/pub36356.html) kicked off a lot of interest in distributed tracing in the broader community.
[1] http://lightstep.com/
I like this idea.

I've used a similar method to explore differences between design and implementation for verticals, as those often have stringent requirements on how to process data and what data/algorithms can be used.
BH Liddell Hart's tomes on WWII. Brilliant books. Although he clearly was a little "too sympathetic" to the German cause.
I may not be there. I might not be there.

The former, using old meaning, indicates that you aren't permitted, which is the negating the latter sentence that indicates a possibility of being there.

But "may not" in the old sense seems slightly weird, in the way that "permitted not" is weird.
Show HN: I'm building a IMDB for tech events and tech speakers
Eventil [1] is a (yet another) website that lists tech events [2] and their participants: attendees, speakers & organizers [3]. You can filter events by topic [4] & location [5]. You can find events where Call for Papers (CFP) is open [6]. Speakers can list their talks [7] along with slides & video [8]. Users can access this data via a RESTful API [9] as JSON (I'm working on GraphQL implementation). If you're an event organizer, you can create an event page and enable CFP form. You can follow people to see their event activity (as attendee, speaker or organizer) as weekly email.

It's a side-project. I've been working on it almost 2 years. In my spare time I organize various tech events myself. I'm most proud of PolyConf [10]. I've created Eventil to solve my own problems with tech event organization. There are many organizer features that help me be more efficient. My focus is on speaker profiles. I'd like to help fellow organizers out to find interesting speakers. I'd like to also help tech speakers easily find related events.

A business model is being built around my insider knowledge. It could result in consulting projects through the platform. This is already the case to some extend. Eventually it could be automated.

The project is in alpha stage. There are bugs, but there's also a consistent cycle of weekly iterations. Please bear with me. I usually fix everything quickly. I'd be happy to have your feedback. You can also submit issues via GitHub [11]

[1]: https://eventil.com/
[2]: https://eventil.com/events
[3]: https://eventil.com/users
[4]: https://eventil.com/events?q%5Bwith_topics%5D%5B%5D=JavaScri...
[5]: https://eventil.com/events?q%5Bwhere_scope%5D=London
[6]: https://eventil.com/events?q%5Bcfp_open%5D=cfp_is_open
[7]: https://eventil.com/users/eryno
[8]: https://eventil.com/presentations/bL1sJe
[9]: https://eventil.com/docs/api
[10]: https://www.youtube.com/watch?v=8aYSKeAvvu8
[11]: https://github.com/eventil/eventil.com/issues
Show HN: GitHub Version Tags – Chrome extension to show a repo's current version
Show HN: Serverless Polaroids.. GitHub star posts a polaroid via Twitter bot
Embarrassingly, it took me until halfway thorough the article to notice this
Continuous deployment works differently. Your approach focuses on reducing MTBF; continuous deployment focused on reducing MTTR.

For CD to work, you can't really depend on QA for regression testing. You need to have really good automated test suites. You still do want exploratory QA, but that doesn't have to happen before release.

Code review works similarly. As your quote says, he did proper code review. It was a very small change, so it doesn't take long. Strong test coverage means code review is less about finding possible bugs and more about design issues. There's no urgency to getting those before release; people can watch changelogs just as well as they can service a review queue. And with frequent releases, developers return to important code often, meaning that design improvements happen over time.
1 visit every 6 months based on location
and software
I get what you mean, but I was more referring to build issues that are strange or unusual. Something that even a senior dev would raise an eyebrow at.
If I said "he is literally as high as a kite" that would pedantically mean he's a hundred feet off the ground, but these days "literally" just adds emphasis.
Is there a pros/cons comparison to Zipkin? Browsed the docs and couldn't find anything.
Fuzzy logic as such didn't really go anywhere, just as predicted by actual scientists and engineers. Zadeh was widely cited, but with little real-world "impact factor" outside the context of the journals themselves.

Still, I suspect that's because the core idea was ahead of its time. Fuzzy logic attacked problems that already had conventional solutions. You don't actually need fuzzy logic to minimize the time derivatives of position when starting or stopping an elevator, or to run an electric razor, or to do constraint minimization with linear programming, or in any number of other commonly-cited applications. But if you were to pin down a member of the AlphaGo team and ask him or her exactly how the machine beat Lee Sedol, the answer you'll get is going to sound a lot like "fuzzy logic," in the sense that our machines and the algorithms they implement are reaching a point where they're no longer entirely accountable to their human programmers, or understandable by them.

That makes me think that in another 50 years Zadeh's reputation may look somewhat different than it does today.
This is genuinely good advice.

I'm a bit surprised that so many commenters here are reacting to the second paragraph as if it described an extreme lifestyle that would inevitably lead to ruin, or as if you need to make a choice between having these kinds of experiences and being a successful, fulfilled adult later in life. Neither of those things are true.

Here's what I believe the parent post is saying, but stated differently: try all the things that life has to offer, and get outside your comfort zone. Let yourself make mistakes. Explore. Try to connect with many different kinds of people, especially people who aren't like you. Push the boundaries a little. When you find something you're passionate about, dive in, but be sure to come up for air regularly and enjoy the simple pleasures of life.

Don't let the anxieties or negativity of others stop you. If you do those things, I promise you you won't regret it.
What's the performance hit for using Jaeger in production? Are there benchmarks?
Another nice thing about pull is you only pull from the authoritative source. If you have a daemon that has gone rogue your load balancer or naming system can throw it out of the named group/job/whatever even if it can’t shut it off. With push you might have zombies pushing duplicate data for what should be a unique target.
Correction: I'm not sure Apache 2 and GPL work that way. IANAL and please read the licenses yourself (and consult counsel if needed).
You know you're in for a good ride when,

"This is so pronounced that if I were to evaluate myself 15 or even 10 years ago, I wouldn’t recognize myself as an A-player. I simply wasn’t one. And yet here I sit looking down at my previous self."
"Deliveroo seems like my best bet at the moment with flexible hours"
"I probably wouldn't be making any more than minimum wage elsewhere"

I wonder - and I'd be interested to hear your experience in this - how in-demand you end up becoming. Do your available hours coincide with other students, in which case, is your time mostly spent sitting around waiting, competing with a number of other people for a small number of deliveries?

Do Deliveroo guarantee minimum wage for your time spent available, or do you effectively earn less than minimum wage, because you spend the majority of your time waiting for an order?

I can see why Deliveroo may appear attractive, but wonder whether the appeal might wear off once you have first-hand experience of their operation.
Eve Online Political Betrayal Results in Record-Breaking Theft
Heavy water is more effective, but light (ordinary) water moderates neutrons too. That's how light water reactors work: https://en.wikipedia.org/wiki/Light-water_reactor
Yeah I've kinda been that guy. Went from university straight into a green field project that allowed me to grow very fast and I was smart and competent enough to handle it. I knew the project inside and out and everyone liked me. They billed me out at $250 and paid me $40. So I switched jobs after 1.5yrs for a 40% raise. Then the same thing happened, so after 1yr I got another job, also through a guy I had worked with who had seen I was good, for another 15% raise. It's funny how a company can get hung up on relative pay-raises instead of considering actual value added.
Lego Clash of the Heros Set ReviewithSpeed Build
Can someone with an idea about this post other languages that actually attempt to modulerize it's own API? I'm not aware of any.
Jigsaw was what held up the Java 9 released, due to some members rejecting the proposal. It was changed and revoted upon, but it's hard to follow what was modified to make it acceptable.

Is there anywhere the design goals and constraints for modules are? I'd really like to know how they ended up in their current form.
If I understand the 5th amendment correctly, and its caselaw, you would be OK storing evidence of your own crimes overseas, but evidence relating to other people you could be compelled to turn over.
He isn't considered "real" critical theory, but a lot of the most interesting elements in postmodernism -- questions about language, identity, randomness, representation vs. reality -- are present in Borges, whose work is the opposite of exhausting.

If you haven't read him, I'd recommend the "Labyrinths" collection as a great place to start.
Packers vs. Bengals Live Stream
I think you might be overzealous in using the word fascism here. While fascism does lead to the oppression of minorities and has historically lead to the oppression of the disabled [1], I do not believe that my view is a fascist one.

There is positive discrimination, telling quadriplegics that they should be euthanized. And there is negative discrimination, failing to provide an ADA compliant restroom. The former is fascist, however the latter is not in my opinion. Of course it is best if all venues have restrooms that are wheelchair accessible, however the idea that any which does not provide accessible restrooms is fascist is a logical absurdity.

Lets take your argument to its end. There are 1 million wheel chair users in the US [2]. Lets just say that any venue that negatively discriminates against 1 million or more Americans is fascist. How many restaurants are there in the US that provide separate gluten free work surfaces in order to prepare gluten free food for the 3 million with celiac disease [3]? Another million people have a milk or egg allergy and need separate work surfaces for those ingredients as well [4]. I know, it's just 120 000 people in America that are actually blind [2], but not a single grocery store provides braille packaging on all their produce. All in all there are 2.4 million who are visually disabled, they should be given well lit venues, no darkness and light shows at concerts for them, they might trip and fall in the dark. But if things are going to be well lit, what about the 3 million Americans with chronic migraines (which causes photo-sensitivity) and therefore cannot bear the bright light [5]? Its literally impossible to not negatively discriminate against someone, and I've not even gotten into religious or ethical diets and norms. So is everyone who tries to open a venue a fascist?

[1] https://www.ushmm.org/outreach/en/article.php?ModuleId=10007...
[2] http://codi.tamucc.edu/graph_based/.demographics/.statistics...
[3] https://www.cureceliacdisease.org/wp-content/uploads/341_CDC...
[4] https://www.foodallergy.org/sites/default/files/migrated-fil...
[5] https://migraine.com/migraine-statistics/
So I occasionally find myself looking up a dependency's version after visiting its GitHub page. I built this to help instead of clicking and searching while juggling other thoughts. (At least until GitHub does this kind of thing natively. I'd be happy to have this become redundant.)