skysight-inc/HackerNews huggingface dataset:
It's too easy to cancel Netflix. Someone called in and gave my first initial + last name @ gmail email address and cancelled for me without any further verification.
The major disadvantage of the UK is:
Shoebox "houses". Or what we call them houses.
So its raining a lot outside, but we also do not feel comfortable inside, at home, because it is ridiculously small and normally very old. bad weather and cage-homes, deeply depressing combination.
Th main advantage of the US:
Big homes (if you choose not to live in SF or NYC) and good weather.
I call it "failure by success". Unix is so incredibly successful that we are bound by decisions made 40 years ago.
There is an unbroken chain from the Thompson shell circa 1972 to modern day bash.

The language wasn't designed; it was accreted over decades.

Looking at the difficulty of the Python 2 -> 3 transition might give you an idea of how hard it is to make incompatible changes, so that's what we're stuck with.

It's a little bit like asking why C has so many warts -- e.g. the insecure standard library, "holes" in the type system like silently converting pointers to bools.

But it's easier to "clean up" compiled languages than interpreted languages, and it was somewhat done with C89, C99, etc. You can have different compilation modes, and the user is more likely to fix things that a compile error flags.

With something like shell, you don't have a good chance to surface errors and clean up corner cases. It just evolved over time until it was out of control.

I'm working on fixing that with my Oil project: http://www.oilshell.org/blog/2018/01/28.html
His rationale is well thought out and has lots of merit. His ideas of how programming should be contrast strongly with what is taught in schools and the workplace, which I think is why people continually challenge his views on programming.

He is NOT an inexperienced developer. He has not been beaten down by asshole team leads in corporate environments for 2 decades and remains a free-thinker.
The Davy Crockett was deployed from 1961 to 1971, so we're talking '60s era tanks. There's a reason that modern tanks are radiation shielded, and similarly why tactical nukes are no longer considered part of tank warfare.
Not really. Handicap bathroom stalls are never handicap exclusive. Sometimes there isn't even a second, non handicap stall.

It isn't like parking, because 99.9% of the time, it's in and out in a couple minutes, and 100% of the time you are physically present in the stall.

But if you take the only parking spot, that person pretty much has to go home. The car could be there for hours, even the whole day. Versus two minutes.

This huge moral difference is accurately reflected in the law- it is absolutely, perfectly legal to use a handicap stall without a disability.
You could be in favor of more extra-curriculars, or more 'holistic' criteria. But why affirmative action? That is an orthogonal issue.
I was looking for Heapster and InfluxDB but I think I was supposed to find Prometheus...

This stuff moves very fast. You can be excused for blinking, IMHO!
Siraj Raval – 100 Days of ML Code Challenge
> ...commodity reactors would be a far cheaper approach in the end.

I've read claims that in the US, unfortunately there are no commodity reactors, with commensurately commodity costs in licensing, environmental and regulatory approvals. Each reactor is effectively a one-off effort, with a minority of transferable capital equipment, skills, etc. I've also read that France's reactors are far more uniform, and they reap many benefits from it.

I wish more research and engineering could be justified into ultra-small reactors like described in this Quora response [1]. Not really sure what he meant by a magneto-hydrodynamic power conversion because I didn't picture a conductive fluid involved from his description, but I wonder if the reaction can be scaled down even smaller than the proposed 100 GJ burst (I somehow suspect battery chemistries don't take kindly to those scales of bursts).

[1] https://www.quora.com/Is-there-a-micro-nuclear-reactor-that-...
It's probably not chitin you are allergic to. It is also in mushrooms, and if you can eat those without a problem it is something else.
Constantly impressed by the time you spend explaining your moderation suggestions dang, thank you for all the work you put in to make this place what it is :)
It is not guaranteed. The company has a chance to respond with the paperwork proving that you in fact received the item you paid for. It's then up to you to prove that you did not.

I am not a lawyer, but this is what happened to me.
This is all absolutely true! Redux and React-Redux, and their associated documentation make a lot of intelligent design tradeoffs that have a lot of thought put into them, and that's worthy of respect. "Overengineered" was too strong a term, and I shouldn't have used it. Sorry.

However, some of the things that have been traded are default configuration that represents typical use, standardisation across the ecosystem, and brevity. I think that for a lot of use cases, these tradeoffs make React-Redux harder to use, and that as a whole they make it easier to cause significant architectural problems for a newer or less technical user.

> If you _really_ want to, there's nothing stopping you from importing the store globally

What I've taken to doing is exporting a dispatch function that calls the store's dispatch, not the store. I think this better captures the intention behind Flux than a higher-order component, without much cost, since dynamically swapping between stores doesn't seem common.

> ...one of the key design points of Redux was to allow users to choose which approach they want to use to handle async logic...

This power and choice, while allowing a lot of freedom, comes at the cost of a fragmented ecosystem. The Redux documentation page for async actions lists six different packages that can help.

> the "dispatching an action === calling a function" comparison can be true, but only if you're using Redux with a limited mental approach and treating actions like "setters"

I may not have explained that very well. Actions themselves make perfect sense from the perspective of a reducer, and clearly they must be dispatched, but they're a state management detail that the UI doesn't need to know about. Something similar to redux-action could be the default.

I suppose my core problem with Redux/React-Redux is that I don't understand why a typical component in a typical app doesn't look like

import { connect } from 'redux'
import { deleteFoo } from '../actions'

const FooList = ({ foos }) => {
return foos.map(foo => <button onClick={() => deleteFoo(foo.id)}>Delete {foo.name}</button>)
}

export default connect(state => ({ foos: state.foos }))(FooList)
> Also, conceptually, you often have a lot of state that's very directly concerned with and specific to the UI, and isn't just idyllic, agnostic "data". Things like "is this menu open or closed?

The entire UI is specific to the UI. Trying to separate "entities" or "server data" from "UI concerns" is IMO a waste of time and just confusing.

At the end of the day, you have a state tree, and you project it to a UI. Where that data comes from and what it represents doesn't really matter. Events in the UI generate an log that can get folded into new state to then be projected again. These events could be generated by a button being clicked, or an XHR request completing, but that doesn't change the nature of the payload.

One important thing though, in most of these models, the state shouldn't be "is this menu open or closed". It should be "Is the user focused on an arbitrary task or not". The menu being open or closed is a projection of that. This way when your designer comes and says "No, this thing shouldn't be a dropdown menu anymore, it should be a modal", you don't feel the need to rename your arbitraryMenuOpen: true state key to arbitraryModalOpen: true instead. Saves a lot of time.

Elm is a pretty good example of how all of this works. Its fairly different from Redux and co (even though it inspired it a lot), but its interesting to see how all of these things absolutely can work. They get messy when retrofit into React and JavaScript, but it's not an issue with the concept, just the implementation.
Alibaba Says Its AI Copywriting Tool Passed the Turing Test
Would be surprised if the average IBM developer salary is around 50k. My guess would be higher, proabably around 90k - 100k for US employees.
This drives me crazy too, since a lot of the time I want a background show, and for that I need English audio.
Ah gotcha. It's been 14 years since I rented, so I don't really remember any of the details of renters insurance. As a homeowner, I totally get that.
FYI: WebAssembly is effectively starting to get WebAssembly only APIs. Chrome is shipping the WebGL commit API which is designed to support spin loops in native apps (others are expected to ship it too)

Most native OpenGL apps run in a spin loop as in

while(true) {
update();
render();
glSwapBuffers();
}

To support that model TPTB added a worker only `gl.commit` function that does effectively the same thing as `glSwapBuffers` so that native apps can keep their spin loops and don't have to refactor to be event based.

Of course if you decide to use a `gl.commit` spin loop your worker can no longer receive events (no onmesagge, no XHR, no websockets, no fetch) so you're supposed to use SharedArrayBuffers to communicate with a spin loop worker.

SharedArrayBuffers are being re-enabled once they are isolated to same domain only processes.

AFAICT this is the first browser API that is really targeted exclusively at WebAssembly. I'm guessing more will come. Not entirely sure how I feel about that but I guess it's inevitable.
> LendUp is run legally as a licensed lender in CA.

Okay? ... every company has the same licenses. CashNetUSA, Quickloans, Captain America Loans, and hundreds of other companies. Including even most with the shady legal structures, based in Malta, etc. Google won’t list the Deleware ones either. Advertising platforms don’t like them. Cities don’t like them. Regulators watch them closely and frequently press charges.

> I’m damn proud to have spent a couple of years trying to solve it.

Look this is probably going to seem uncivil, but given the poor ethics of what you are talking about, I have no qualms shaming.

I spent a few years founding a payday business. Ultimately, despite having the same “forgiveness” policies and “innovative” loan structures, and telling myself all the same junk you are telling yourself (CFSA PR propaganda) I couldn’t bring myself to treat poor people like a crop to be harvested. You know that forgiveness or not, the majority of borrowers are repeats, and that there is a huge incentive to maximize this. Essentially, people use you instead of a bank.

There is no escaping that this means you are in the business of siphoning 10% off of an already poor person’s wages on an ongoing basis, and that’s without compounding. (Sounds like 15% by your numbers)

Do you really feel good that you did this? You drank some silicon valley koolaid, worked as someone else’s employee and harvested poor people? And then acted as the company’s mouthpiece afterward? Because you want to feel congruent with your resume?

Before you say I don’t know blah blah about LendUp ... hear this: A great many Payday companies came before LendUp, attempting the PR of being “ethical” and “innovative”, with the same practices. And by far they have not been the last. They’re all still in the business of fleecing at least 10% off of the people who can afford it least. There’s always money in stealing from the poor. The only innovative thing they did was to con YC. (hi)

Do not deceive yourself or others. It is not an honorable business. It is a called a VICE INDUSTRY for a reason, and you guys didn’t do anything to “solve” it (by your own admission of the word “trying”).

I know ... you want to stand by what you did, but if I were you, I would put that one in the rear view.
It depends. Some use 10.0.0.x, some use 192.168.1.x and some use 192.168.178.x

There's also 172.16.0.x, which I have never seen used by default on any networking devices.. which makes it perfect if you have a piece of network that you visibly want to separate from the rest of the LAN.
> some days before the release of k8s v1.11, which made some stuff I wrote obsolete, oh well... :)

I've been through this! Did you decide not to publish it, because it's been outdated?

Let someone review this, I'd love to read it, and getting feedback will be cathartic I promise! Post the link source!
If the most interesting thing you can say about your project is which language you used, you might not have aimed high enough.
Sure, I understand that a driverless system might prevent accidents by strictly maintaining safe distances. But the benchmark still can't be unaided human, rather a human aided by the best assistive technology that can be built (say by the same company).
> Spend some time watching a group of primates or work with a group of them over time as I did a number of years ago, and you will start to see that humans behave in almost the exact same way, our brains lie to us about our motivations so we are obivious to the fact that we are acting from ancient primate social instincts, and worse you get stuff like this piece which pulls on the old great chain of being.

My friend was in the jungles studying primates during his college years. One day we went to a restaurant/bar to eat. A girl was sitting on a bar stool and her boyfriend stood next to her and was rubbing her shoulders. My friend looked at them for a few moments and then said "He's grooming her".
Hint: both sysvinit and BSD init are better. They are more mature, have fewer moving parts, are easier to debug without specialized tools, and are better understood. Plus the decoupled nature of init systems reap bonuses for system stability (unlike systemd).

Having a QR code parser as part of something that's tangentially related to the init system in concept but deeply embedded into systemd in practice is exactly what the post you were replying to is complainig about. It's unnecessarily complex.
I prefer the sandboxed PDF reader in my browser to the native one that's not sandboxed

https://www.theregister.co.uk/2016/10/24/apple_security_upda...
‘Access to Literacy’ Is Not a Constitutional Right, Judge in Detroit Rules
Yeah, for a while it seemed like there was a new Redux side effects lib coming out every week. At this point, though, it's pretty much standardized on thunks for basic use cases, and either sagas or observables for more advanced use cases based on your preference of writing async logic.

> What I've taken to doing is exporting a dispatch function that calls the store's dispatch, not the store.

Not sure I follow that train of thought - could you point to an example?

> Actions themselves make perfect sense from the perspective of a reducer, and clearly they must be dispatched, but they're a state management detail that the UI doesn't need to know about. Something similar to redux-action could be the default.

This is why we recommend use of action creators, so that a component is just calling `this.props.doSomething()` without it "knowing" that a Redux action is actually being dispatched.

Per your snippet there at the end:

- `redux` and `react-redux` are deliberately separate packages, because the Redux core is 100% vanilla JS, and independent from React (in the same way that `react` and `react-dom` are separate packages - the core React logic is independent of the platform-specific reconcilers). So, `import {connect} from "redux"` wouldn't be appropriate.

- The use of `deleteFoo()` that way assumes that it's pre-bound to a specific store instance, which limits the reusability of your logic, and also makes it a lot harder to test. `connect` abstracts away the question of "which store instance am I interacting with?", so that your components and logic are more testable and reusable.

> Something similar to redux-action could be the default.

For what it's worth, earlier this year I threw together a small `redux-starter-kit` package: https://github.com/markerikson/redux-starter-kit . The goal behind it is to simplify some of the most common pain points around Redux: store setup (including thunks and devtools), writing immutable updates in reducers, and having to install multiple packages out of the box. The biggest thing I know it's still missing at this point is indeed something akin to `redux-actions` - see my notes at https://github.com/markerikson/redux-starter-kit/issues/17 .

I haven't had time to push it forward further, but I would seriously like to get some more eyes on it, see if there's any other use cases we should be covering, and then make it an official Redux-branded package and update our docs to recommend that people use it.
What the article refers to as boilerplate is actually something I like about Vue. Standard component organization is a good thing.
Wouldn't it have been easier to change your home network?
Unless you're very much supporting very legacy stuff, don't bother learning about prototypes, at least beyond "well it makes objects but unlike classes its actually a function itself" stuff.
I think that the simple expression of this might be that Bash is a command language, not a scripting language.
It could also be the admission that you can't beat pure skepticism. That is, you can't actually beat Descartes' deceiving demon; you need to start any line of reasoning with an assumption that your reasoning is somewhat sound. When you're starting out to build a foundation, you have no basis for making that assumption.
I would love any such integration. But coverage-wise I think it's easier to do a simple upload at the moment.
Ah, It seems I was very unlucky as I started learning it right before 3.0 and tried to pick it up after 3.0. Upgrading my previous project gave me strange errors, and the documentation had changed with it, leaving me to puzzle over what had happened.
> To do so, a person called “the Gonker” entered data into an Excel spreadsheet known as “the Gonkulator,” while “the Planner” arranged magnetic pucks and plastic laminated cards on the whiteboard to indicate how long planes could stay in the air.

I love the names and vocab that comes out of unofficial military slang.
You don't have to be a chef to know you're getting bad food.
I believe a few times the US has also alluded to low yeild strikes as a possible action to take to against rouge states if they felt a nuclear strike against an ally or the us was about to happen.

At least before the things deteriorated between the US and Russia, Russia was silent in response.

I suspect both sides are pretty pragmatic as far as a strike on regarding non NATO or non Russian targets goes, at least in terms of weighing the outcome rather than going full MAD... or even responding at all.

Granted the US scenarios IIRC were hypothetical posed by reporters (or off the record policy talk) involving N. Korea and Iran and they were obviously military targets and the goal was prevent their use of nukes. Facing a nightmare scenery I suspect both nations expect the other would act to defend their people, and while not approve, wouldn't feel the need to respond with military action. Those situations seem tailor made to a limited smaller scale nuclear strikes.
What I read once: when you're a wild animal in the wilderness, just scarring over the wound sometimes gets you back in action faster than regrowing the limb, and that's a survival advantage.

If that's the main reason evolution usually went this direction, then maybe there's not much downside for modern folks.
Some uncanny similarities to my version - https://medium.com/@tanjent/refactoring-out-a-y-combinator-9...
Paket+Pernikahan+Hemat+di+Tangerang+dan+di+Jakarta+|+CIPTA+PESONA
> If JavaScript is disabled I just show a message saying the site needs it.

We don't complain, we just go somewhere else.
>As the article states, they lost their competency.

I think people undereatimate how bleak the short term future (50-100 years) is looking right now. We've forgotten how to properly build many of the things we once touted as the pinnacles of modern civilization and the current societal status quo is too fractured and stressed to ever pursue the kind of learning process needed to reaquire that knowledge. This is but one example among many.
Well, FWIW js is not the most friendly language for functional programming. I'd argue that the trend toward immutable.js and redux occurred partly because rest/spread syntax was/is relatively confusing, and so immutable patterns without a library feel less elegant until one really groks the somewhat visually opaque semantics of the rest/spread syntax.

Redux also offered a simple approach to the "action bus" idea from Flux, but omitted first class async support, etc. React itself also somewhat overlooked async patterns, which created the idea that their absence was by design and so an additional (opinionated) library was appropriate.

In sum I'd argue that React actually fights against js quite a bit and that it will truly come into its own once reason gets more mindshare.

For those of us who invested heavily in react as all this was becoming clear (and being ironed out) I hope we learned enough to allow better decision making in the future.

Also, React has a few "on by default" performance enhancements that are a bit conceptually confusing and create something of a mismatch with the functional approach.

But still it's difficult (and unpleasant) to imagine the world without React.
I mention this is pretty much any thread talking about frontend framework architectures. Check out ClojureScript's re-frame project. It's maybe not for everyone but in my opinion it's an elegant and distilled method for writing React-esque views and handling data subscriptions. The syntax is of course polarizing but it really gets rid of a lot of boilerplate.

https://github.com/Day8/re-frame
Fair point, you didn't actually need super computers to run LISP.
I've never been confronted with the "can't cancel service hell" but clearly it must be a problem if CA passed this law. I don't have cable TV. Where else besides cable does one experience this?
See also Adventures of Huckleberry Finn
I'd like to venture that you haven't really considered my argument.

Again: take a black family and a white family of equivalent income levels. The black family, statistically, lives in a poorer neighborhood than the white family.

The harms that come from being poor are not the same as those that come from being a member of a historically disfavored minority. Both sets of harms are real. But we if solely address the class-based harms, we ratify and perpetuate the race-based harms.

It's not a complicated argument. How are you rebutting it?
You might enjoy Zsh.
And I don't complain when you go somewhere else.
What garbage. Why is it that anything which attempts to improve the current state is derided as 'leftist' as if it is outside of a right wing/libertarian view is leftist propoganda. Do you really struggle to see the benefits in improved public transport and see this as a crazy socialist agenda, or do you think memes are an in-depth manifesto of a detailed planning on public policy..

Go back to discovering the truth about Pizza based paedo rings
i spent a lot of time trying to make nix the 'standard build environment' for an open source project. it was going really really well, even on top of standard distros like ubunutu, redhat, etc.

the problem is OpenGL and Nvidia. NiX doesnt want to deal with NVidia's closed source drivers, and i can't blame them, i got so depressed working on the issue, that i gave up looking into it. there is no good solution. there are only kludges and kludges of kludges.
Reminds me of the Danish Protest Pig[1].

[1]: https://en.wikipedia.org/wiki/Danish_Protest_Pig
I totally would share it. I do write my blog at my profile. It will take a while for me to organize my thoughts to write this down (in a month maybe?), but it is coming :)
Almost every single call center I've ever called has that, "This call may be monitored for quality assurance." disclaimer.