skysight-inc/HackerNews huggingface dataset:
This is true. Though the perks and benefits that the govt provides for office workers are not going to be able to compete with top tech companies. Pension is delayed payment of decades while tenure at companies are dropping. I bet quantifying these forms of pay would make the comparison even worse.

There are a few things that I’m comparing it to that makes me say they are cheap (since it is a relative term).

1. How much money the govt has spent in other endeavors whether policy or contractors.

2. How much private sector (market) values top talent that the govt is trying to attract and retain. Value prop for private companies is high, but the impact these people can have on the US govt should be a lot larger.
Nobody has self-driving cars, not even Waymo. Every "self-driving car" has "disengagements" (a euphemism for "it stopped working") periodically every few thousand miles. That's simply unacceptable and needs to be sorted out. If a human driver was performing a panic stop for no reason or hitting a pedestrian or another car every 3 months or so we would take away their license.

Waymo is doing better than almost everyone else, a testament to their skill and their rigor, but they are still a long distance away from truly autonomous vehicles. The temptation is to say "well, they are so close, I'm sure they'll finish up the niggling details", but the reality is that the stuff they are failing at are some of the hardest remaining problems and will probably require at least as much work as they've put in already, if not significantly more, to tackle. I think we'll end up with self-driving cars eventually but probably not on a time scale of within the next 5-10 years, more likely it'll take that long or longer for the technology to reach maturity and then yet another decade plus for it to start seeing practical application.
That argument would create an insane precedent. By that standard, it'd be OK for air-to-ground missiles to be wildly inaccurate. As long as you design the missile to be really noisy in flight, you can assume that people will hear them and take cover in bomb shelters before it lands. Collateral damage avoided. Problem solved.
Our site does't work with js disabled. Serious question: is it common for folks to disable js?

vue is used only for the web app. No js frameworks used in the chrome app.
If cars which require no effort whatsoever to operate and cost significantly less than taxis are on the market, it's a safe bet that being slightly less dangerous per passenger mile will kill far more people than are currently killed on the roads due to more, longer car journeys. That's before we even get into the fact a car which is slightly less likely to cause a fatal accident than the average human driver on an accidents per mile basis is a lot more likely to cause a fatal accident than the average sober, careful and experienced human driver, the complications of estimating fatality rates from small test drive samples and the potential for new bugs to cause massive accident spikes.
There are certainly many definitions of “winning”. I can only speak for myself: quitting my old job lowered my pay, but resulted in my being a lot happier and having more time to spend with my kids. If anything, the current trend and the number of people willing to jump jobs has helped people like myself take the leap into something new — something I might not have done without seeing others do.
I expected a 3d printed Cartesian robot holding a pen, for the printer part.
I actually have a speech impairment (a stutter) and you’d think people would be willing to accommodate. I can speak just fine when I have complete agency over the words I choose to say, but it’s the absolute worst when I have to read out some long specific access code or account number and say it 100% correct. Stutter even once and they think I meant 2 P’s when I just wanted to say a single P. And then it becomes this long drawn out process of “after AF6, it’s just a single P, but the rest of it is right” because I really don’t want to have to read out the entire code again.

But sadly there have been more times than I can count where I told them I have a speech impairment, it’s difficult for me to say certain things in the way they need me to right now, and I’d prefer to send them an email (even offer to send them an email for them to open while we are still talking)... And they said no they cannot do that for one reason or another.
sorry for the confusion. a frozen package containing just two 4 oz Beyond Burger patties cost us $6.00. i.e. we paid $3.00 for each one quarter pound Beyond Burger.

so, if you can find hamburger meat for less than $12 a pound, you're paying less than we paid for Beyond Burgers.
The fish shell was primarily created to be a shell language with a nicer syntax. I tried it for a few months a few years ago, and while the syntax is nicer, it misses a lot, and I mean a lot, of features. Adding those features would have, of course, complicated the syntax and gotten us back to something like zsh, so... I've been back on zsh ever since.

Really, the only complaint I could make is why chose something silly like `fi` or `esac` to end compound statements, but such an issue is too superficial to abandon everything else that comes with these shells.
this is really weird, not sure what you are doing...... one of the nice things about vue is it's super easy to just add to any page, I've done that a lot with transitioning pages from a mish mash of javascript to vue embedded on the page.
Triple-Star Test Shows Einstein Was Right, Again
Cognitive Load Theory [1] breaks down our mental processes as storing schemata (information) in long-term memory. As of now, this is thought to be unlimited as its been difficult to disprove. Short-term memory, or working memory, involves retreival of information from long-term memory. Faster retreival is what we'd consider expertise. While long-term memory is used for the storage of knowledge, the actual information processing during problem-solving takes place in short-term.

Unlike long-term memory, working memory has a limited capacity and duration. This limits the number of schema (information) that can be managed at one time. CLT was originally designed to describe the interconnected-ness of worked examples when it comes to learning. Visual elements should have context, otherwise you are imposing more things for the mind to process (for example, an unnecessary puppy on a PowerPoint would require the mind to process its a puppy, determine it is not relevant to the information, and continue to ignore it). Long-term is uneffected by this process, but the stress imposed in working memory requires effort to maintain.

To answer the question of "What are the sources and/or studies that justify this claim?" - that's what modern Psychology is trying to figure out.

[1] https://scholar.google.com/scholar?hl=en&as_sdt=0%2C34&q=cog...
The framework is custom. But I was really talking about how great reactive was for my application. It is a control system with a lot of inputs and outputs. The graph is about a dozen levels deep.
No, you cant argue the same thing for parking, because you cant just magic creating parking spaces.

What you can do is facilitate (or mandate) an automated system that allows people to cancel your service with them.
I think Go will supersede python in a few years time as the more performant language useful for systems programming but also glue code as well. The fact that it builds to a single static binary is huge IMO.
They’ll cancel it over email if you’re insistent enough, or at least they did for me.
And who will get the tickets? The car? The passengers? The manufacturer?
No, none at all.
>Have you tried Netflix on Edge?

I don't have Netflix
I have a similar knee-jerk reaction to one-liners from a maintainability standpoint. I have this mental vision of Perl or Shell that looks like Brainfuck.
HN, collectively, has it's own opinions. I was curious (and asking) about that. I certainly know what the MSM thinks - but they are a bunch of hacks that have to churn out 3 articles/day (god save them), and have no time to develop any insight of their own.

Thanks, though, for impugning motive. That makes me feel all sorts of warm and fuzzy about you.
As above: Use Twitter. It isn't session-based, so you can come and go from the conversation as you please, and it certainly didn't take me 15 minutes. :)

In my case, I was considering an alternative provider, I tweeted them to ask if they could match a competing offer, they made a different offer that wasn't good enough to keep me. I checked in another time with them on Twitter to confirm my contract was not in effect, which they confirmed. And then after my new service was installed, I informed them that their service had already been physically disconnected, and to please close out the account.

None of this came with muss or fuss, and I just hit up their DMs whenever it was convenient for me.
Really good stuff and addresses many issues I had, eg documentation and jupyter compatibility.
I hope the static image export gets a bit streamlined - being able to quickly & programmatically export graphs to png is really something I did not find easy from python with plotly so far. Yet it is definitely crucial eg to send a high quality image to the boss for a PowerPoint slide or to save 100s of png images for quick visual quality checks.

So I am really looking forward to give the new version a spin!
> as soon as you're in the real world, you hit its limitations very quickly.

Isn't a good chunk of AirBnB, Facebook, Instagram, Netflix, The New York Times and Dropbox written in React?

The built-in state management has limitations, of course. I see it best for keeping state relevant to display-- React is supposed to be a "view" library, not a state management one.
Avoid "full stack" frameworks with JavaScript -- they are all gimmicks. This is something I wish I knew at first. Start with Node.js, because you will eventually end up using npm, Webpack and Babel if you are doing serious web development. I used learnyounode[0] to get familiar with the basics of async-first programming. Even though you have tools like async+await and Promises, I would recommend being comfortable with callbacks.

Avoid CoffeeScript and jQuery, they are obsolete. Make sure you are comfortable with Webpack (build tool) and Babel (transpiler), since they are essential in web programming today. I would go with React + JSX over Vue, because I find it to be more elegant and intuitive.

[0] https://www.npmjs.com/package/learnyounode
Actually that's my favorite thing about the Redux model.

The vast majority of our codebase is comprised of simple idiomatic React components. Our reducers and glue code (e.g. @connected containers) are a very small portion of the codebase. If I woke up tomorrow and decided Redux was the source of all our problems I could completely remove it while only needing to refactor a small portion (<5%) of our codebase that's mostly boilerplate anyways.
Next up: Ryan Zinke.
Sure, just like taking an elevator to the 2nd floor because you don't want to take the stairs.
Be sure to understand the event loop. Javascript as an asynchronous language often comes back to bite beginners. Here are two great talks to help you:

https://www.youtube.com/watch?v=cCOL7MC4Pl0

https://www.youtube.com/watch?v=8aGhZQkoFbQ

Your life will be easier if you learn to use Chrome Dev tools (or the Firefox equivalent) early.

In the beginning, you don't have to worry about browser compatibility - embrace modern JS (ES6+)!
Read GEB when I was 20. Absolutely loved it, and it had a big impact on my choice of studies and career. Since then I've had a lurking fear that I'd be grossly disappointed if I picked it up again now. Your review indicates I should probably let it be. Thanks!
Για μία θέση στα ημιτελικά Βραζιλία και Βέλγιο στο Μουντιάλ
How Segway-Ninebot Became the Go-To Scooter Maker for Rental Startups
That sucks. I guess "works every time" is an overstatement.

I'm currently 3 for 3 but I guess you have a lot more attempts than I do.
So I see where you're coming from. To first address Redux, etc, React has no opinion on state storage, it's a feature not a bug. Obviously you need to store state somewhere, and Redux, Relay, etc are just tools to address that concern. But that's really unrelated to what you're trying to address, which is coupling between leaves that have shallow common ancestors, but are themselves quite deep. Although in my experience a good website does group related pieces of information, and so well organized state often maps easily to a well organized UI, functional programming gives us the tools to avoid deeply nested expressions regardless of your application (or even your framework).

One thing to realize is that you always get to decide on the granularity of your compositions. It is not necessary to build a deep hierarchy if you design the granularity of your interfaces correctly. Another great tool is higher order functional programming, such as passing components to components (via children). In this way, it is easy to describe generic interfaces and supply specific pieces of data without having the intermediary interfaces know or care about that data. Another approach, akin to using something like the state monad, is to use Reacts context feature, but this is rarely needed, in my experience.

Personally I make heavy use of higher order components, and I find I rarely exceed a component tree height of three.
Typescript support has gotten much better in the past few months. In particular, the vue-cli scaffold provides the correct stubs so typescript doesn't freak out when importing single-file components.
I haven't heard much about cost overruns for wind farms and solar panel farms.

Solar thermal, yes, that's a startup industry.
I did something similar when I moved to get rid of my wired phone service. I told AT&T I had signed a contract with Comcast and told Comcast I had signed a contract with AT&T.
Sun Synchronous Orbit
Celluloid: Actor-based concurrent object framework for Ruby
I find Yasha Levine’s writing style often sensationalist (the Tor ‘exposés’ especially), and cringed a little when I saw his name on the article, but this peice contained some great history which I was unaware of.

I’d always thought of Gmail as a defining moment for surveillance capitalism, and not being in the US at the time, wasn’t aware of extremely prescient legislation about email privacy which EFF helped crush, and were extremely rude about (before the EFF staffer on the subject went off to do PR at Google).

I find it pretty amazing that EFF have said nothing about the California Consumer Privacy bill passing in the last week, an extremely significant bill for Californians, but strongly opposed by Google.

I’ll still support the EFF, but it’s clear that I should find some more genuinely pro-privacy organizations to support too.
As Aristotle said everything in moderation including cigars and pizza.

Going into a full blown mega health nut phase is not very helpful either because the end result is not going to be pretty anyways.

Now if/when we start making serious life extension progress beyond 120 years with high quality of life then we can start talking.
Why do you think the downvoters got it right?

When Paris was attacked, and Beirut on same day, only France was being remembered. Somehow we haven't yet learned to care about people being hurt in other places in the world if we're not living there, if it's not part of "us". We need to start thinking of people as equal regardless of where they live.

Anyway, when I saw that Facebook only let you put up the French flag I made https://customizeyourpic.com

And you can hear what I really think in the video there.
Well, this sucks for Germany. Intel's GSM radio division is formerly Infineon, AFAIK still located in Germany. There wasn't much state of the art microelectronics left in Germany anyway (correct me?).
You mean exactly like CoreOS Fleet ?
This doesn't actually solve the dilemma of where to put the logic—all you've done is moved the API code into its own object, but your component is still the one controlling the higher-level flow in this case.
IANAL, but just after that:

17602...
(c) In addition to the requirements of subdivision (b), a consumer who accepts
an automatic renewal or continuous service offer online shall be allowed to
terminate the automatic renewal or continuous service exclusively online, which
may include a termination email formatted and provided by the business that
a consumer can send to the business without additional information.

though it seems to only apply if the agreement was made online.
Meanwhile in 8 months in India they have built 648 MW solar plant that costs $679 million [1].

[1] https://youtu.be/gM-0lrIxCnE
Awesome Bazel
> To it's (partial) credit, Google is as open as it can be about governmental requests for its vast troves of information.

No credit should be given. Google and the states it works with are not adversaries.
It's particularly relevant to tech because there is the concern that technical interviews, poorly structured, are creating a culture that favors admitting candidates who optimize for passing technical interviews.
> I want to learn JavaScript as my next language.

Welcome!

> I have been observing JS community for some time and it seems like there is too much noise out there with dozens of frameworks and language variations (e.g. CoffeeScript, TypeScript, JSX, etc).

Yeah, this is a double edged sword. People are always looking to build the next best solution, which is great for you as a consumer, but it's also terrible for you, because decision fatigue sucks and your decisions can feel like they're outdated in months, not years. Just make an informed decision when you go out to pick something and stick to it as long as it works for you.

One thing to know is that a lot of this is caused by the challenges of trying to hit the moving target that is web browsers. My biggest piece of advice for cutting through the bullshit is to find your root problem, then pick the handful of tools that actually solve it. Don't just use something because everyone else is using it; no need for cargo cult mentality.

> I plan to go through Mozilla's JS docs and Vue tutorial, but not sure if it is enough to get up to speed with the modern JS ecosystem.

Go through the MDN JS docs, build fundamentals. Read through some library code like jQuery or a utility library like lodash to get a flavor of some interesting things that come up when building a frontend library.

> Which resources would you recommend?

Roadmapy resources:

- https://github.com/FrontendMasters/front-end-handbook-2018

- Ponyfoo has some great es6 resources as well

> Which framework should I stick with?

Find what works for you. Just try to avoid things that have so much tooling you get paralyzed looking at how it works instead of doing something interesting to you. If you start with react use create-react-app to figure out the fundamentals. I'm sure there are equivalents to create-react-app that correspond to create-<library>-app nowadays.

> What are some things that you wish you had known before getting into JS? Note: I am comfortable with Python (including Flask/Django), Java, HTML and CSS, so picking up JS as a language won't be a problem. Interested in your thoughts.

- Learn about the different environments that js is run in and how this can impact certain things like module definitions, e.g. why is there amd, umd and commonjs?

- Learn about functional programming in the context of js. It's a nice mixture between the two. Learn when to use one with the other.

- Understand the inheritance model, prototypical inheritance isn't that bad, just get it out of the way.

- Understand the runtime and event loop. This will inform you why you'll see things like callbacks, promises, generators and now async/await. Here's a fundamental breakdown of the event loop: https://2014.jsconf.eu/speakers/philip-roberts-what-the-heck...

- Learn about the browser lifecycle

- Invest in learning the chrome dev tools or ff dev tools, they're both wonderful and will save you hours
I'm a senior web developer now, started with other languages. This is a bit embarrassing but here goes:

1. I wish I had known how asynchronous stuff worked before I got into JS. OR studied it in JS a bit more formally. I had a couple of months where I was confused as hell, because I didn't really understand how to do async, promises weren't really a thing you could use if you had to do older browser support back then.

2. I really wish I had studied JavaScript. I didn't, at all. I was like "Yeah front end is easy anyway, lets roll" and just got started developing. I did so many stupid things, suffered so much, and really resented the language at so many different points exclusively out of my own ignorance. Once I got my head out of my ass, and actually studied the language in depth I felt like so many things started making sense.

To conclude with 2, I remember having a distinct realization that it wasn't JavaScript that was shitty. I had been a shitty developer for having not studied it.

Anyway, if I can give some advice those two would be it, understand how asynchronous flows work, and learn the language.
Skipping the first sentence would be a good step forward.
> Z% of seats by pure lottery.

I wouldn't elect any political official or moderator by pure lottery.
This is a transparent hit piece, e.g. Berman endorsing CALEA is supposed to be evidence of EFF supporting it even though he was promptly removed over it and their stance is clearly against it:

https://www.eff.org/issues/calea

Or it talks about their support for ISPs, but at the time these were the hundreds of small dial up ISPs that were each highly competitive small businesses with half dozen employees tying a modem bank to a T1 line, not the likes of Comcast and Verizon as we know them today. The EFF was consistently in favor of rules like local loop unbundling that would have prevented their monopolization of that market when it converted from dialup to broadband.

It just goes on like that, pointing to half truths and claiming them as evidence that the EFF is some kind of nefarious front.

The main claim seems to be that they should be lobbying against Google and Facebook on privacy, but that's just a policy disagreement. Privacy regulations -- most regulations -- cement incumbents. If you don't want Facebook forever then what you want is a decentralized social network, not federal utility regulation of Facebook.
Something else you can do with BASH functions is use:

declare -f function_name

to print out the contents of a function, in a format that can be directly evaluated with command substitution. This is useful if you want to send a function (or a number of functions) into another BASH instance (such as via an SSH connection).

A google search for "RPC in Bash" will take you to a GIST I put up on Github a while back that gives details of how this works.

You can do this in ksh93 also, I believe you use typeset -f instead of declare -f.
> To the extent that code is a tool, it's as fundamental as a pencil and paper

This is very clearly false. I'll sidestep the semantic argument regarding pen/paper vs a keyboard, but the bottom line is that reading and writing are fundamental communication skills that represent the bedrock of civilization and while computers are obviously a revolutionary and world-changing technology the likes of which we've never seen before, the same can be said of physics, chemistry, metallurgy, agriculture etc. These skills just aren't a requirement for being a productive citizen (like reading and writing); they're just not.

> I think people really overlook how fundamentally algorithmic thinking structures your mind

People overlook lots of important insights about psychology, biology, and physics, it doesn't mean those things are fundamental skills comparable to literacy.

> but coding is a good way to develop it

I totally agree that writing code is a guaranteed way to enhance logical and critical thinking skills but the same is true of studying logic directly, or physics, biology etc
TL/DR anyone?