sciolistse

TSLint has this: https://palantir.github.io/tslint/rules/strict-boolean-expre...

It doesn't play well with the vscode tslint extension for some reason (doesn't show up at all) so you need to run tslint manually to see the errors.. but it's better than nothing.

AmEx has theirs on the front, but I don't know if that says anything about it defeating the purpose or not.

Having it on the back prevents getting both cc number and cvv off single picture.. so I guess that's something.

You used to be able to decompile Terraria into perfectly readable code, since its c# and they didnt use an obfuscator. The code base was atrocious, but it is impressive that they got something working, and pretty fun, together as quickly as they did.

These days there are a fair amount of production Unity games out that you can extract full sources for.. Can make for a fun read sometimes.

Unfortunately even VisualNES experiences some inaccuracies compared to real hardware. I've only personally found an issue caused by it in one game (Who Framed Roger Rabbit,) and the effect isn't noticeable if you're not looking for it. But it is there.

I was pretty wary of the new mbp because of the initial negative posts.. but figured I may as well give it a shot, so I've also had mine since a few weeks after they came out.

In my own opinion all the negative attention was correct. It's not at all unusable, but it's been strictly worse than the previous generation.

The lack of tactile feedback on the touchbar makes me have to look at the keyboard to use it which is a step back. It also doesn't attempt to verify that i'm actually trying to press a button which makes them easier to accidentally press than a real button.

The keyboard is okay, but the buttons occasionally stick and require finagling to fix, typing is marginally slower and less friendly on my wrists than the previous gen.

I preferred using actual right click on my trackpad and on the newer version that's entirely impractical and I have not seen any benefit to the size increase.

None of my issues are dealbreakers and I'm sure most people find the new version to be fantastic.

While I agree that React (with ReactDOM) is heavier than it probably should be, a production build is around 140k minified, 45k min+gzipped.

I personally find React applications to be fairly easy to navigate compared to other JS projects, but my use of it has primarily been porting applications from Angular, Knockout or Asp.net Webforms to React.. and I find it a lot easier to work with than those personally. Haven't tried Vue though.

macieksarnowicz is shadowbanned for whatever reason, but he answered:

Thank you for your feedback. We indeed offer a whole server (database cluster) and you can create multiple databases in it and have full control of the resources allocated to that cluster.

The admin user provisioned for the server is not a full superuser, but it is close to that. We are trying to find the right set of permissions to provide to our customers without jeopardizing our ability to manage this server for you. Please submit your feedback here: https://feedback.azure.com/forums/597976-azure-database-for-... if you see a problem with the permissions.

Discords the voice chat works great and is super easy.. But without search there's just no way it could replace Slack for us.

We share model validation, internationalisation functions / string parsing and formatting values (language strings, datetime formats, currencies, etc), access rules, configuration settings, views and constants at least.. I've also had a few situations where we've moved client side code to the server, and not having to rewrite from scratch is nice.

None of these are huge issues to solve with a separate language on the server. But for our projects it's been a time saver.

Any bank can join.. if they meet the requirements.

https://www.bankgirot.se/en/about-bankgirot/participant-requ...

There are plenty of legal regulations to wade through to join, but it's not impossible and the requirements are publicly available.

They never specify what he asked them, so it's hard to know.. He might have asked if they use a syringe to access the blood in the vial, which they wouldn't since you can just remove the rubber stopper and have complete (undetectable) access.

Hard to find good pictures, but you can see here: http://i.imgur.com/mhdkpui.jpg some vacutainers (newer, but they work the same) that have been filled, complete with puncture holes. That's just how you fill them.

It's a lot more compelling that the evidence box has been tampered with, in my opinion. You can find a few phlebotomists confirming this in the makingamurderer subreddit, if you look around.

The package being tampered with was problematic, but the hole is made when the container is filled with blood not when removing the blood. If you're removing blood, you just take the lid off.

It's been "the same javascript everywhere" mostly due to the ECMAScript group kinda stalling for the past 15 years. The stabilisation created through that has been useful, but the plan is to transition the spec onto a one-year update cycle.

That means that going forward we'll likely have more feature mismatch between engines, making backward compatibility compilers pretty important.

I'm not entirely sure if that's good or not.

You can also add ".patch" at the end of a github commit url, which will show the users email address. For example:

https://github.com/TinyCC/TinyCC/commit/c52d79605a3c895a16e1...

the font isn't animated, but font awesome's css file uses css transitions to rotate the icon element.

I'm not sure that's accurate.. I've been using Browserify for some time, and write code like that pretty much all over (require('../lib/api'), require('./api'), etc.) without having file duplication issues in the bundled output. Do you have an example that exhibits the problem?

Also, if you're requiring large files that you know won't need processing by browserify (like react), you can use the 'noparse' option to prevent the performance hit during bundling. (Of course a cdn is potentially a better option.)

I know right? I've been working on one for the past year or so, have a few customers on my lil platform.. But I've had to stuff it in between projects, so progress has been slow.

that's twice as long as it has to be.. not that it matters.

In generator code you'd use try/catch to handle failure instead.

    try {
      var user = yield Users.get(1234);
      return user.name;
    } catch(ex) {
      // do whatever
    }

rather than..

    return Users.get(1234).then(
      function (u) { return u.name; },
      function (ex) { /* do whatever */ }
    );

Unfortunately, the .Net Framework source is available under a 'reference license'.. You are allowed to look at the source, but not modify or redistribute it. Mono specifically has to be very careful about these problems, so if you have ever looked at Microsoft's 'shared source' code you are not eligible to contribute to Mono.

That's the way it works now. In earlier versions any added columns would still be retrieved, shifting all the other column values to the right.. So all the data would wind up having the wrong column names.

Web archive has it at Jan 2003, so it seems to be awfully close.

Sounds reasonable. Could be better timing now as well, what with server-side javascript having become popular. Good luck with the library!

I've made a lazy linq-like library for javascript in the past..

The problem i had was that the native array methods are rather fast while function calls (for moveNext) are quite slow, so i couldn't get a whole lot of speed out of it.

Newer javascript engines might be sufficient to offset that though.

If you're using local files directly, // will resolve to file://, and not work as you'd expect. It'll work if you use a local web server instead, of course.

Those are actually a part of a "future reserved keywords" list from an older version of the ecmascript spec.. Safari v1 used to disallow the use of a few of them, but they never actually wound up getting used, and in more recent versions have been removed.

You can see them here: http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/...

Search for "Future Reserved Words"

Gah, you're right.. I only saw the larger function.

Seems to have caused using an array to specify easing in jQuery.animate to break. Was a bit surprising.

I've been working with B2B e-Commerce for about a decade, and it's a pretty sorry field to be sure. Past few years it's come to where I don't really want to recommend anyone any longer, since I know the chances of a good release coming out of it are near zero.

There are probably a fair amount of people here who work with less sexy things, that just don't really talk about it since integration with enterprise resource planners isn't as much fun to hear about as a 12-minute reddit clone getting millions in funding. I know I rarely post.

you might want to escape those text messages.