octalmage

Same here, been using docker-compose for development and testing and it's been great. Spinning up 4 servers with docker uses much less space and memory than 4 vagrants. It's also much quicker to provision and get started.

For me around 1 in 10 is fraudulent. I'm selling a project as pay what you want to pay, and the fraudulent charges are always much more than most people pay. I've lost a bunch of money this way.

Came here to say contribute to open source! I started contributing to open source around 15 and learn a ton from a bunch of people that were way smarter than me. For me it's become harder to contribute to open source projects the older I get.

Same here, this conversation is happening right now since we've built a pretty large application using React. I would much prefer to use React so this couldn't be better timing.

Everything should have automatic payments, and if they don't then they don't deserve to get paid. That said I use Prisim to take care of the rest that don't.

I'm currently using it in a pretty large project and it's been awesome. Having the CSS related to the component in the component is really nice (which is found in other frameworks). When refactoring you don't have to wonder what this class could be tied to since it's all right there. You also benefit from dead code elimination so unused CSS classes get removed.

Cryptocurrency support is something they're very interested in.

I've used and written a ton of bots that read the screen, sometimes it's the best option.

That is exactly what aimbots are. Sometimes you can make bots easier by using an addon system to export information(WoW), or themes to color your targets (CS), but at the root you read the screen and control the mouse.

Yeah this just doesn't scale, especially if you're pulling from GitHub.

That's a really cool feature! We could really use that!

I think I like the way HipChat does it better. @ing is suppose to be quick, if you have to click on a dialog every time you want to message someone that's going to slow you down. Hipchat just doesn't allow duplicate display names.

You've got web interfaces and mobile apps. I use 1password and don't have this problem.

I also use Google Analytics for tracking usage in my desktop applications (opt out) and it's great. I think most just think about web stats (page views) but I just use the event system. This allows me to identify unused features or possible confusing UX. I also started using it in a project at work and the data has been extremely useful.

They're probably referring to web hosts. Many hosts have timeouts for the web, but not the cli. So for long running tasks you write cli scripts. In the WordPress world this is easily done using WPCli and eval-file.

To be fair this is how most pre-release software looks. I'm sure it works great on their test servers, but it takes time to document and fix all of the edge cases.

That sucks man. Have they begged you to come back yet?

Very scary. He left the project and development hasn't picked back up. Found this in the comments of the article:

https://www.reddit.com/r/storj/comments/6llxpn/so_long_frien...

The WP REST API is a new way to detect if a site is running WordPress. If you hit the homepage of a WordPress site it will return a link header with a location to the REST API. They can also just hit /wp-json/, or /xmlrpc.php, or many other files that WordPress requires. Like looking for assets served from wp-content, or wp-includes.

It was very slow to first paint around 1.0 which made me use something else. But it's become so much faster since then.

I love single file components. I used Polymer before React and that is the thing I miss the most. I've also been using CSS-in-JS for the same reason. I landed on JSS for now, but I'm hoping we'll see a solid scoped CSS solution soon.

You can include a babel script that compiles everything on load. There's a performance hit but people do it because it's easy.

Edit: more information: https://github.com/babel/babel-standalone/blob/master/README...

I used the Payment Request API in a project and it was great. Chrome currently has it implemented for Android, you call a JavaScript function, a prompt appears asking the user if they'd like to pay, they enter the security code and hit pay.

All this feature actually does it give you the users credit card, phone number, and billing/shipping addresses. You still have to give that information to someone like Stripe.

They're focusing on mobile since that is where the checkout experience is the most painful. https://ride.lyft.com has it implemented if you want to check it out.

For us this is the product owner. They are the ones that do the user studies to backup feature requests with data. It's important to test assumptions about what users want.

This way we don't end up building stuff because someone random thought they wanted it.

A big part of it might be lack of testing utilities. Things like mocking HTTP calls or stubbing methods will be difficult without modifying the code you're testing.

The thing other languages lack for me is a clean way to execute other programs. With bash it's just "grep whatever", in other languages it's "exec('grep whatever');". Then piping that output to another program is a lot of work.

Bash makes for really good program glue.

I've considered creating a library that scanned your PATH for binaries then created dynamic function signatures to allow calling the function by name. Then that dynamic module can be included, and you'll be able to grep by calling "grep". You could make it chainable and get something like: grep('something').cut('args'); or whatever.

Of course this would only be used for personal utility scripts.

This is usually referred to as functional or acceptance testing. The goal of these types of tests is to confirm that the overall application works as expected from a users perspective. This is easy with bash. Testing individual units of code inside of a bash script is more difficult. This can be useful for pin pointing which function introduced a bug.

Edit: want to add that difficult does not mean impossible. Bats exists, and you could structure a bash script to be more easily testable.

Paper ballots leave a lot of room for doubt in my mind. How you can you recount the ballots and come up with a different number? This shouldn't be possible, but it happens all the time: https://en.m.wikipedia.org/wiki/Election_recount

Thinking out loud here, how about a blockchain based solution? Each user gets a new address, and that address is printed on a receipt after you vote. This way you can verify your vote at anytime, and the votes can be counted in public.

At defcon this year they had a bunch of the popular electronic voting booths set up, and they were all hacked within 6 hours. A big problem is having physical access to the booth. All of the hacks involve picking a lock.

I just want to note that as a developer you can run any code you want on your iPhone through XCode for free. You just can't distribute it in the App Store without a license ($100 a year). You can distribute the code though, and users can compile and install it. This is how Kodi distributes on Apple platforms.

This is a newish change though, within the last couple of years.