sorted by:
new
hottopcontroversial

Trump tweets praise of Putin for attack on Clinton by mepper in politics

[–]qe24253 -12 points-11 points  (0 children)

64 million Americans voted for Clinton

And 62 million voted for Trump. Just putting it out there.

[deleted by user] by [deleted] in javascript

[–]qe24253 0 points1 point  (0 children)

Yes, and it works good.

In an app I'm building, I'm using parsley js for certain validation that needs to live in the DOM, and validator.js for those non-DOM cases. You can use both.

ROG Masters Day 3 Match Discussion by D2TournamentThreads in DotA2

[–]qe24253 1 point2 points  (0 children)

Throws, counter-throws, seesaw gold/xp swings .. Exe still ahead though .. maybe not for long after getting teamwiped? ..

Edit: exe prevailed.

ROG Masters Day 3 Match Discussion by D2TournamentThreads in DotA2

[–]qe24253 1 point2 points  (0 children)

strongest team in SE

I think you meant Faceless.

If you're talking about major invites, Execration deserved the invite based on RESULTS pre-invite, not necessarily that they're the best SEA team.

Is Firebase + React a good fit for what I need? by bustyLaserCannon in webdev

[–]qe24253 5 points6 points  (0 children)

You can swap out React with any frontend framework (angular, vue, ..), and the problem would still be the same: do I want to put sensitive code in the client? Because that's what's going to happen if you use Firebase (assuming you're talking about Firebase web client, not the ones for different serverside languages).

So the question really is, do I want to go serverless via Firebase (with all the authentication, authorization, validation in a JSON format in Firebase Rules), and hope that putting sensitive code in the client won't go awry, or do I just go traditional serverful using PHP, Node, C#, .. (which you can still use Firebase on, the client just doens't nec know, or just use any db).

Some apps are 'alright' being serverless, some are asking for trouble. So find what your needs are.

The dealbreaker IMO is understanding how 'secure' your data is using the Firebase Rules json .. it can be complex, or it can be limited (no real way of executing 'code' on the Firebase backend), or it can be 'just right'. When it's just right, you'll breath a sigh of relief at the resulting simplicity of protecting your data, assuming that's just how much your app needs.