1,867 karma · joined March 12, 2013
> Forthcoming...
I feel like introducing something without documentation is a little premature. Or maybe its use is abundantly clear to those who've used Aurelia.
Also, the post isn't about bloat anyway; it's about FOIC vs FOUC and lazily loading fonts. Complaining that the page is "bloated" at 500kb (Edit: Fine, 1.2MB, whatever) is a shitty nitpick.
Yarn installs packages, much like Gem, NuGet, whatever. Pretty standard.
React is a frontend framework. Not surprising that you'd use one. I suppose you could opt to write a giant pile of vanilla JavaScript instead (I'm assuming you're not using this kit for a simple webpage, which would be silly. We're building a web app, right?)
I'd dare to compare Gulp + Webpack + Babel to your "compiler" in a way. I'm a little lost at why we're using both Webpack and Gulp though. Babel is a necessary evil to ensure we're "cross-platform" in a manner of speaking. These are probably your most "unnecessarily complicated" tools.
ESLint and Flow check your code for obvious mistakes. Reminds me of IntelliSense and compiler warnings. Again, pretty standard stuff.
Mocha is a test runner and Chai is an "assertion library". Chai isn't a big deal: expect(foo).to.equal('bar'); Simple stuff.
Feel free to scoff at Redux and Immutable if you'd like. Probably unnecessary.
Am I the only one that likes this ecosystem? I feel like it follows the Unix philosophy of "Make each program do one thing well". You need almost all these tools in other environments -- they're just typically chosen for you in advanced.
Are you sure you've seen them all? Even the Linux ones? :) Try Xming (an X server for Windows). You can run just about any terminal emulator you want. I find Terminator to be quite nice.
I've found that "edge cases that rarely happen" are typically 90% of my major headaches.
Maybe take a look at the last paragraph:
> To sum up – I’m not trying to say that Windows is not so good for the software development. For example, the Visual Studio will be probably hard to beat for many years amongst many other great tools. My point is that if you’re not tied up to some specific technology which is not cross platform (which usually means for the Windows users only), you might want to give a try to some other environment. It’s always a good thing to try out something new, hone skills and broaden your horizons.
Combine that with a need (for whatever reason) to run .NET & IIS and it can definitely make sense to start running some Nano containers.
This is super annoying when dealing with JavaScript, especially in a Node.js environment. Often times I'll see an answer using jQuery, and maybe somewhere buried in the comments someone will say "In ES6 you'll be able to `code`". I'm not sure what the solution to that problem is, but it's frustrating.
That's not correct. The S3 bucket name is always prefixed. The format is: bucketname.region.amazonaws.com.
https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosti...
To clarify, you're going to have to add a DNS record either way. Doesn't matter what you call your bucket. And no, you don't need to put CloudFlare in front of it for this.
I've seen people write their own XML parsing libraries, try to handle dates + timezones on their own, and write REST API helpers for products that already had official packages. In each of these cases, even a brief look at some docs and a wild-ass-guess would've been more productive. It's super frustrating to watch.
But that doesn't make it any more feasible, possible, or even safe. We're talking about special needs that will be difficult or impossible for a non-targeted service to adequately meet. It would be better for a different service to specialize in this, as our theoretical service is likely woefully ill-equipped to handle the vetting of caregivers for the developmentally disabled (among other problems outside the original problem domain). I'd even be tempted to argue that attempting to address these problems simply for the sake of soothing guilt and/or avoiding lawsuits would be immoral itself.
Whether or not there should be legislation to cover issues like this is another discussion. (Maybe there should be! If AirBnB manages to kill off hotels in a few spots it would make for some very interesting discussion.) But I don't think this theoretical babysitting app is a good candidate to be targeted by such legislation, and I think it's a little silly to damn this example... There's other help and services out there specifically for the developmentally disabled, and nobody expects every babysitter or daycare to be able to handle the developmentally disabled either. Calm down.
(Even more interesting is that I'm getting downvoted... has the hype pendulum swung that far?)
"we have taken the entire messy and complex world of telephony..."
Twilio _chose_ and solved a problem that sucked. If your product doesn't solve a tough problem, it will be almost impossible to get the same "wow" factor that Twilio does.
Maybe the answer is that less obvious applications will simply be at a disadvantage right out of the gate.
That's scary. I'm supposed to police my employers actions? To some extent I can understand, but that puts a lot of IT people in awkward positions. Do Dropbox employees need to worry that infringing content is being taken down fast enough, lest the face prosecution?
I didn't follow Megaupload too closely, so I hope I'm blowing this out of proportion...
> Have migrations (except they're going to be some scary ad hoc nodejs script that loop through your document store and modify fields on the fly).
I literally just spent the better part of tonight AND yesterday evening dealing with one of these scripts. I had pulled down the production table to locally test the script (gross), but when I later ran it in the production environment, we'd somehow had an array sneak in to what was an object field. The whole thing just felt like a mess.
I'm not sure this is inherently bad or good. I don't like it personally, but I do see the reasoning. Self-driving cars probably shouldn't be hackable, and the first attempts need to be airtight as possible (what with the media jumping at every chance to spread FUD). But it concerns me that the days of opening the hood to hack away at your pickup truck might someday, largely, go away... That's not good for anyone.