senoroink

What was the business? Stripe's not really making the rules here, it's the financial partners backing them. Just because something is "legal" doesn't mean it's not risky. As an easy example, from the page you linked, "psychic services" are banned.

Since it's relevant to the topic conversation, only use a Roku if you're blocking its outgoing requests. It sends out an insane amount of outbound data that goes beyond just your viewing habits (e.g. wifi name, "connection data") [1].

Installing pi-hole reveals how noisy a Roku is [2].

[1] - https://docs.roku.com/doc/userprivacypolicy/en-us [2] - https://imgur.com/a/n5zcAwl

> The done button is the archive button

True, but the point of Inbox was to treat your email like a todo list. By definition, it is the same, but training millions of Inbox users that this is new behavior makes it hard to grok.

> If you're using bundles, that's the one big feature that isn't ported, but it doesn't immidiately sound like you are.

Every Inbox is probably using bundles whether they remember or not. It becomes incredibly powerful when you have a trip coming up and your flight, hotel, rental car, etc. is all bundled up together.

I've been using nest as well on a project. It's nice, but it's miles behind Rails.

I don't disagree that there may be some kind of evidence to link to that action. But I do believe that evidence can be tampered with to create the illusion. Seriously, a chat transcript is what people cite as evidence? We as a society should doubt accusations until they've been proven to be factual.

There's been numerous cases of people being exonerated of a crime [1] after spending years of their life inside prison.

I'm not trying to pretend that Ulbricht is a saint. He deserves to be in prison for running an illegal market. But if that's all he was ever convicted of, then I believe that the punishment of a double life sentence doesn't fit the crime.

* [1] - https://en.wikipedia.org/wiki/List_of_wrongful_convictions_i...

Regardless if it's convincing or not, he's not guilty of the crime.

Imagine this: you steal a bag of Oreos from a 7-11. You are sent to trial. Then the prosecution says you also killed some dude. When all is said and done, you are convicted of shoplifting and receive an insane amount of time in prison but were never actually charged with murder, wouldn't you think that the jury was manipulated?

For everyone mentioning Ross hiring hit men to kill people. He was never charged with that. Prosecutors commonly fabricate a story to paint a picture of a defendant for the jury. We will never know for sure if Ross actually did this but he's innocent until proven guilty.

Stuff You Should Know recently put out a podcast vaping [1] that provided some insight on the subject. The conclusion was that better than cigarettes slightly worse than doing nothing.

* [1] - https://www.stuffyoushouldknow.com/podcasts/is-vaping-really...

Hey, I got pretty excited when I heard of Strava's move to Denver since it's the one app I use nearly every day (and would love to work for). I'll be moving to Denver from Boulder later in the summer, can you comment as to whether you all will be in the Galvanize office for the foreseeable future or if you will be moving somewhere else? Thank you.

I don't disagree with any of your points. React is faster. React has a larger community. All of it, I agree.

But. When it comes to productivity (actually building something and maintaining it), I can achieve way more in Ember.

I'm still convinced that in the world of frontend development, Ember is the only framework that hasn't screwed over its users.

My guess is that at Facebook there's too many smart people with differing opinions. Hence, we have to do an insane amount of research to construct the grab bag of pulling things together. And once that grab bag is complete, Facebook says "here's the new cool way to do it".

Ember on the other hand has happily given you the grab bag and has helped you support your production happens with the most professional, enterprise release structure.

Disclosure: Used to do only frontend development with Ember but switched jobs and now use React/Ember

Good point! If you managed to capture all this information, it would theoretically be possible. However, being able to get this much control is essentially impossible. We emphasize "pseudorandom" because nothing is ever truly 100% random.

For context: https://www.zdnet.com/article/github-says-bug-exposed-accoun...

He literally could have said just the first sentence and been applauded. Adding the second sentence adds nothing but arrogance.

> Using the word "addict" is a cop out to take away personal responsibility.

It's not a cop out. It's a fact. Social media can fit the exact definition of "addiction" for some people. Personal responsibility is present if you're abusing a drug or social media.

From your comments, it appears you aren't affected. Great. Similar to how you probably can't relate to a heroin addict means you can't relate to a social media addict.

None of your links seem to work. Is this a private repository?

I legit think this guy has been killed. Why would someone do this? This will likely lead to a witch hunt [1].

[1] - https://www.reddit.com/r/CryptoCurrency/comments/8d8hz2/was_...

Twitter always scrubs exif data.

Definitely sounds cool in theory but where's the call to action? There's only a form to sign up for an email update on the home page. Where is the source code? How can I try this now?

Sure they could but they haven't, yet.

And there doesn't seem to be anything on the radar to do so. While I've played with enough boilerplate projects in the React/Redux world, there's nothing considered to be officially supported and even the most popular ones have stagnant development.

I switched jobs to get something closer to home and the new job was a React shop.

As someone who has moved from using Ember daily for 2+ years to now using React/Redux, I miss Ember on a daily basis. React suffers from lack of standardization like no other. I hate starting a new project or working on an existing project and having to think about where to put things. Ember grew from developers who existed in the Rails space and understood that convention over configuration is the way to go. React devs likely came from Express land where everything is composed of tiny modules that you'll spend days carefully putting them all together.

The React world is the wild west. Libraries come and go so quickly that you're better off building it yourself if you see your app as long living. Ember, on the other hand, does a great job of keeping everything in check. Because the community is so small, things just work because there's less things to maintain.

Admittedly, when I first got into Ember, it was pre 1.0 days. Even prior to v2.0, Ember struggled to keep things working as intended. Now that the framework has matured, most pain points have gone away. The way they do their versioning is the smartest in the industry. React has been around for years and still the community seems fragmented.

What it boils down to is:

Is your app fairly small and intended to only last about a year? Use React

Is your app core to your business used by many and intended to last for the foreseeable future? Use Ember

Bravo for pushing helping people reinvent the wheel less but this just emphasizes how badly React needs uniformity in the community.

This article resonated with me fairly well. As someone who has had an extensive background in Rails and has more recently switched to 100% javascript, this kind of pattern is what the community needs. There's something to be said about getting up and running as quickly as possible. Sure you can make the argument that not everyone's application is the same, but there's a ton of similar patterns that would have been better suited to having less mental gymnastics with a simple config while still leaving the door open with FP for those that want to fine tune.

Why? It's not hard to do if you start a fresh project.

It's funny you mention that you had difficulty having your team write tests. At my company, the CTO has difficulty writing tests and the team has consistently written adequate test coverage.

I fixed this in a new project by starting with jest [1] and failing the CI if the test coverage wasn't at 100%.

[1] : https://facebook.github.io/jest/

Really cool demo. One suggestion is to make the dropzone more obvious. I didn't realize you had to scroll down to find the dropzone.

Location: Denver/Boulder, Colorado

Remote: Yes

Willing to relocate: No

Technologies: Javascript, Ruby, Elixir, Elm, Ember.js, Rails, AngularJS, Phoenix, MySQL, PostgreSQL, Redis

Résumé/CV: http://elmthomas.com/resume

Email: eric.l.m.thomas [at] gmail [dot] com

Passionate full stack engineer with an attention to detail. Have worked with large enterprise companies, smaller startups, and everything in between. Totally open to learning new technologies and expanding my experience.

Location: Denver/Boulder, Colorado

Remote: Yes

Willing to relocate: No

Technologies: Javascript, Ruby, Elixir, Elm, Ember.js, Rails, AngularJS, Phoenix, MySQL, PostgreSQL, Redis

Résumé/CV: http://elmthomas.com/resume

Email: eric.l.m.thomas [at] gmail [dot] com

Passionate full stack engineer with an attention to detail. Have worked with large enterprise companies, smaller startups, and everything in between. Totally open to learning new technologies and expanding my experience.

As far as I know, yes. If there's another way, they don't make it obvious.