Most places in the US require businesses to "make up" the delta between minimum wage and what the employee receives through wage+tips. Seattle just codified this more clearly by having a "minimum wage" and a separate (higher) "minimum compensation". So while wait staff have a minimum compensation of $15/hr, that number is inclusive of tips they receive. Their minimum wage (what the business has to pay regardless of tip) is lower at $12/hr.
People may have considered no longer tipping because of the publicity behind the new-to-them-but-not-actually-new concept of minimum compensation but it's effectively the same system at a higher number.
100% of phone calls to my mobile device are robo calls. I get around 5 per day and (because of this) I never answer the phone. I actually tried to uninstall the dialer app but it seems to be fairly well-integrated into Android.
The humans in my life call via voip(ish) apps (Messenger and Facetime mostly).
Part of my monthly cell service cost is ostensibly for the line. Which I don't use and would prefer not to have all.
"As with all of Epic’s internally developed assets, the Paragon assets are only licensed for use in Unreal Engine 4."
This is marketing for their game engine. They don't have to do it, sure. But SaaS companies don't have to provide free blogs, webinars and e-books either but we don't pretend they are benevolent for doing so.
Don't get me wrong. I think more art assets available in the game dev community is a good thing. I think more free stuff from one company (Epic in this case) will beget more free stuff from their competitors (Unity mainly). I'm just pointing out that this isn't free for the sake of being benevolent. It's free for the sake of capturing market share.
Benevolent: "(of an organization) serving a charitable rather than a profit-making purpose."
That's not how this word works. We can use another one.
I hasten to add, again, that I'm attributing nothing pejorative. I'm glad Epic have done this. It's great marketing that may be helpful to lots of people.
The issue is this action isn't benevolent. It's nice, but as said previously it's to promote their engine. So they will profit from it indirectly.
If on the other hand they would release the assets without strings attached (for use with any game engine / in any way) then I'd say this word would apply.
True. A dichotomy cannot explain for example tax deductible donations: they're obviously self advertising at much lower cost than a real PR campaign, still they benefit someone, so we probably should use a trichotomy like "I'm doing good even if it has a sustainable cost" - "I'm doing good only if it somehow benefits me as well" - "I'm not doing good because being evil brings even more profit than the above".
Which faces _stiff_ competition against the Unity engine. Epic is the incumbent in the space and the success of Unity in the last several years must be a huge concern for Epic.
Epic has always been a game engine developer first and foremost, so anything to claw back market share from Unity is going to be a calculated strategic move on their part.
I don't think it's quite that clear. Sure Epic has been in the game engine market longer, but it was only relatively recently that they entered the non-AAA market due to a major change in licensing. Unity was really the incumbent in that space at the time. In some ways Epic is the up and comer. You can also see that as Unity has had to react strongly to Epic's entry into the market.
I had a friend in college — let's call him Sam — with whom I paired on most CS projects. It was useful to find a partner who was as studious as yourself to avoid having to deal with anyone else's potential BS and end up doing all the work yourself. Sam seemed like a completely normal guy where normal is… we share some of the same interests.
Sam wasn't from money, worked hard on assignments, we shot pool and worked on projects together. I knew Sam was "into" poker but I didn't understand the extent. I was "into" lots of things too.
We're hanging out one day and Sam tells me the "funny story" that happened last week where his parents and girlfriend staged an intervention to demand that he stop playing online poker after he had gone on tilt and lost $200k in a single night.
I about lost my marbles.
He then goes on to explain that while he had agreed to quit playing online poker because he valued his relationships, he was of the opinion that an intervention was a bit much since he was still up over $600k and wasn't on tilt so much as trying out higher stakes tables in an effort to make money more quickly than on the low stakes tables he had already found success grinding.
Same. Especially at poker's hottest peak, I had a number of friends who ended up going really large on online gambling (and they didn't come from money, either- just had built up a bank roll over a few years). After awhile they found themselves experiencing these huge $xx,xxx swings on a daily and sometimes hourly basis. I think they intellectually understood what that meant, but once you got to that level you kind of have to put the idea of it being a lot of money aside to be able to properly gamble it (if there is a "proper" way to gamble it).
Anyway, one friend in particular told me he was making ~$200k a year, when we were around 22. Asked him about taxes and he said he had never paid a dime. So, uh, that could have been his greatest gamble right there.
It sounds like you're new to both React Native and the JavaScript ecosystem. I can imagine this being very frustrating for someone regardless of their general programming chops. I happen to be on a React Native project at work right now. Hopefully I can provide a viewpoint that is helpful and give direct answers to some of your questions.
One thing that would be helpful to understand that's missing from the OP, what are you building?
> However, seeing the differences between react and react native, this seems overstated.
I'm actually not sure which specific differences you're referring to. Perhaps you can clarify?
> It was recommended to use javascript and react/react native so I only needed to program once.
It's possible to use RN to build an application which runs on both Android and iOS from a single code base. This is possible with a few other environments but none are (IMO) quite as good at affording for a truly native look and feel including dropping down into native code when necessary.
Building a really great app is still a grind on execution and perfecting small details is a chore. The standards of quality in the mobile app world are high which leads to average users having higher standards than they might with desktop or web applications.
> What were the other benefits?
For people who enjoy working in JavaScript, the fact that you can write native applications using mostly JS is a benefit.
Some products benefit from being able to share code between a web product and a RN application is a big boost in productivity. I've personally saved hundreds of hours leveraging this. It's not a 1:1 swap but it's close enough to lower the mental burden compared to creating something from scratch.
> I thought there was already built components/libraries I could drop in for data management.
There are lots of data management libraries for React. Most can be used in a RN app. Maybe the community resources section of the React documentation will be helpful: https://reactjs.org/community/model-management.html
I can provide specific recommendations if you can describe specific needs. Like most ecosystems deciding which tool to use in which situation is a skill which builds up with experience.
Here is too much information, but this is how I spend my evenings now...
Goal is a finance tech app, although I probably just need a pretty front end, and I can do stuff manually in the background (like invest money, wire transfers, etc...).
I do have some database experience, writing to mysql. Was planning on doing that using LAMP, because I have experience already.
Features needed:
>write to database(should be easy with my previous experience)
>Usernames/passwords(I am actually clueless how to start doing this, I have Wordpress if needed)
>Accept payments(but again, I can probably do this through wordpress if its too time consuming).
Other specs, since its finance and people are going to be putting money into it, its gotta look and feel good. I'm willing to invest many months into building this to be perfect. However, progress feels slow since I'm learning the new javascript react-native syntax.
Any tutorials you recommend? Working through the facebook tutorial right now.
last trivia question- I was considering using Reflux, but I saw an article saying reflux is dying. I've heard facebook is especially brutal with changes.
> last trivia question- I was considering using Reflux, but I saw an article saying reflux is dying. I've heard facebook is especially brutal with changes.
Not dying, just shrinking usage area. The community feels that it got overused. Kinda like you don't buy an Oracle license to make a todo app. So there's some backlash in the blogs. Upcoming versions of React include better/expanded global state management (the context API). Some of what people use Redux for now will be better served by that API.
Redux also doesn't tie in with any specific database or backend. As other vertically integrated solutions take shape, that will also cut into Redux's usage. At facebook, this would be Relay, a GraphQL library. A lot of people are excited about using a query language to talk to the server. It makes versioning and supporting multiple generic apps/features much simpler. Writing specific web service APIs locks you in if you need to support old client versions, etc. You end up with fetchUserInfo(), fetchUserInfo2(), fetchUserInfo3(), etc to avoid breaking clients. Ugh.
I'm a Redux maintainer, and that post is utterly and completely wrong in every way.
What Dan Abramov showed at JSConf Iceland was a pair of demo apps that illustrated upcoming improvements in React related to async rendering and data cache handling. Those features have no bearing on whether or not you use Redux, and are certainly not "replacements" for Redux. The linked tweet from Kent C Dodds was a joke tweet in a joke discussion thread, and the author of that site has repeatedly shown that either they don't understand the React world, they are very bad at writing and researching, or that they're just flat-out trolling.
There's certainly been plenty of discussion lately about when it's appropriate to use Redux, and I'd agree that many people are told to use it blindly without understanding what the tradeoffs are. It's also true that the new React context API (available in the upcoming React 16.3 release) means you won't need to pull in Redux _just_ to avoid "prop-drilling" data all the way down the tree.
However, Redux is absolutely not deprecated and not being replaced, and the React team isn't in charge of Redux anyway. Dan Abramov and Andrew Clark, the co-creators, are both now part of the React team, and are no longer active maintainers - Tim Dorr and I are. We _do_ still talk a lot about what the future plans are for Redux, and in fact right now we're working on updating the React-Redux library so that it properly works with the "async rendering" capabilities once those are released (see discussion [0] and an early WIP PR I filed yesterday [1] ).
With that said, in many circles I frequent there seems to be growing consensus that Redux just isn’t that useful, and in many cases ends up being a tar pit of boilerplate code that slows down development. Any project complex enough to require Redux should have enough talent on hand to basically write their own version of Redux for their purposes. Redux is such a small library and not enough people seem to be looking under the hood to realize there’s nothing magical about it.
If this is a growing perception amongst the developer community, it’s only a matter of time before it begins to impact the Redux’s relevancy.
I'll agree with the "nothing magical" statement, but I disagree with most of the rest of that comment.
Certainly there's nothing "magical" about Redux. After all, the core `createStore` function can be written in about 25 lines if you leave out error handling, and the entire core lib in about 100 lines [0]. React-Redux does have a ton of optimization work internally, but conceptually it's pretty simple too - components subscribe to the store, call getState(), extract what they need, and re-render [1]. And that's the great thing: Redux is, as its tagline says, "a _predictable_ state container" - there _is no magic_ involved.
What a lot of people don't seem to realize is that the Redux core is a _starting point_. One of my favorite quotes is:
> "Redux is a platform for developers to build customized state management for their use-cases, while being able to reuse things like the graphical debugger or middleware"
We encourage Redux users to use whatever abstractions are appropriate for their own applications, including writing their own. In addition, Redux was designed from the ground up to be extensible [2]. As a result, the Redux ecosystem has exploded. My Redux addons catalog [3] lists somewhere around 2000 Redux-related libraries, utilities, and tools, ranging from action/reducer generation utils to side effects management addons to abstractions for fetching data from REST APIs.
I've seen dozens of "Redux, but.." knockoffs. Most of them wind up throwing away the key design decisions that make Redux special. In particular, the concepts of plain object actions and reducer functions are what truly enable time-travel debugging and easy serialization of state.
My current estimate is that somewhere between 50-60% of React apps currently use Redux. Redux has gained adoption in the Angular, Ember, and Vue communities as well, and inspired dozens of similar libraries, like NgRx, VueX, and more.
Sure, I expect that some of that "market share" will slip over time, especially with the release of the new React context API soon. But, I also feel safe in saying that Redux will be around for a long time.
This article puts a pretty hard spin on what actually happened: Dan Abramov did not announce a "replacement for Redux", nor is he developing a "Future Fetcher" library. The React team is working on a feature that defers state updates until an asynchronous operation is finished, but we don't know how it'll fit into existing state management solutions.
With respect to the last point: redux isn’t dying. I’d posit that most articles and blog posts written about front end technology are highly inaccurate marketing pieces designed to get clicks :)
> Goal is a finance tech app, although I probably just need a pretty front end…
Sounds like an interesting, ambitious project, I wish you the best :).
For building a finance app, you're completely right to build just a pretty front end. Since you can't trust the client, most everything of substance is going to be done on the backend.
> write to database
You want to send messages to a backend which are validated for sanity and safety then written to a database. What you're after is very likely a simple http client. Documentation is here: https://facebook.github.io/react-native/docs/network.html
> Usernames/passwords
You want an authentication screen that submits to a backend for validation. The backend creates a session which can be managed in a myriad of different ways. Making decisions about exactly how this works is context dependent. You can manage credentialing, tokens, authentication and authorization, someone else can manage it for you, you may oAuth with a platform that you're building on top of etc.
> Accept payments
If people are paying you for a product or service, Stripe. If people are transferring money to you for financial services, planning or management, they will expect to be able to send ACH/wire transfers without a fee associated. I don't have a foot in this world so I don't really know what direction to point.
> its gotta look and feel good
This can be done w/ RN but (obviously) RN isn't required. If you're more comfortable with the native language of the two platforms (Java & Objective-C or Swift) it may be a more productive use of your time to go that direction.
Unsolicited start-up advice: Don't go out of your way to learn new technology while building a company. There are plenty of "hard parts". Intentionally adding to the litany of hurdles to overcome is a very bad idea.
> Any tutorials you recommend?
Given your past experience, I recommend you work through a single simple tutorial (the Facebook one will do) then start trying to build your app. No reason to solve someone else's made up problems when building your own thing will naturally present plenty of problems.
> Reflux
If you mean "Reflux", I don't know what that is and I'm pretty deep in that world. Probably unnecessary.
If you mean "Redux", it's a very popular, extremely simple state management library. I recommend you try going without it and pick it up if you think it will help later on. Redux solves a specific set of problems that most small applications don't have.
>You can manage credentialing, tokens, authentication and authorization, someone else can manage it for you, you may oAuth with a platform that you're building on top of etc.
Is there a Stripe of passwords/credentials?
Or something I can google to understand how to get started?
If you’re on a LAMP stack, I assume you’ll use a PHP framework? If so, they will have libraries available that can handle auth for you. Laravel is the big php framework these days. Lots of libraries and tutorials available.
On the payment side of things, Stripe isn’t the only option available. The pro is that it has the fastest Onboarding workflow and a super slick api. The con is that you pay for it.
If you are margin conscious or your business revolves primarily around payments you can do better.
If that is the case for you, build with stripe through MVP stage but keep in mind you may want to swap out one day while building.
I’ve seen some niche businesses save 1% over stripe. That doesn’t apply to everyone but is frequently overlooked.
You're responding to points that the author hasn't made. Any time you're writing, you can absolutely not afford to explain to readers all of the things which you are _not_ talking about. You have to rely on a reader's ability to discern that there may well be other valid points besides the one(s) that you're writing about.
> but taking them as a chance to generalize about most boys or even a small percentage of boys seems incorrect.
This points was made in the article. The author points that that boys committing mass killing is extremely uncommon. That most are okay. That nearly all will turn out fine.
That doesn't seem to me to be the point.
> We should be concerned with school shooters, of course
That (it seems to me) is the author's point. That all of the mass killings are committed by men. And since we are concerned with school shootings, masculinity in the context of modernity is one topic worth discussing.
Yes, it's only one topic amongst many. This article isn't about those topics. It's about one of the many topics. We can discuss how the world is getting better all the time (a statement I agree with), in some other article.
> That all of the mass killings are committed by men.
Should that honestly surprise us? Most killings are done by men. This has been true since time immemorial, going back to the time when we first stepped out of Africa.
I didn't say that "many feel that" those qualities are no longer wanted or needed, I said that in modern 'western' civilisation they are explicitly disparaged.
And I wasn't saying that those qualities "used to define [males]", I was saying that they are inherent qualities of a male human, and that trying to redefine the social interpretation of masculinity is not going to change that.
I think the reason that I feel that the authors points is the same as yours but better made is that the author's doesn't lean so heavily on hyperbole.
> I said that in modern 'western' civilisation they are explicitly disparaged.
In parts, sure. In other parts. Not at all.
Anyone who feels that disparagement of traditionally (or genetically) masculine qualities is a universal in the west spends too much time in the wrong filter bubbles. Go watch some sports ball.
Please understand that I don't think it's a bad point either. I'm not disagreeing with the point. I'm saying your can have you point and make it more charitably, carefully and accurately.
Why not explicitly define strength, aggression and competitiveness as measurable quantities and provide reproduced studies proving males would be stronger in these qualities even without socialization in childhood, rather than leave people guessing?
Most places in the US require businesses to "make up" the delta between minimum wage and what the employee receives through wage+tips. Seattle just codified this more clearly by having a "minimum wage" and a separate (higher) "minimum compensation". So while wait staff have a minimum compensation of $15/hr, that number is inclusive of tips they receive. Their minimum wage (what the business has to pay regardless of tip) is lower at $12/hr.
People may have considered no longer tipping because of the publicity behind the new-to-them-but-not-actually-new concept of minimum compensation but it's effectively the same system at a higher number.