> The 4 months of “hell” were really not that bad looking back at it now. All of this taught me a great lesson in humility and resourcefulness. It also taught me to be kind and loving to your fellow man all the while making sure to “pay it forward”.
But it didn't teach them to save a year's living expenses so they'd never get into this situation again? I wonder what is protecting them from becoming homeless if they fall on hard time again -- probably nothing. With that said, this was a really engrossing read and should reinforce the idea that responsible spending is absolutely key to a comfortable life for those of us who perhaps don't appreciate our nest egg of savings quite as much as we should.
This app just facilitates short-sighted abuse of commercial infrastructure while opening clients up to a massive security vulnerability. Doesn't surprise me one bit that this comes from China. They have a culture of extreme self-interest with complete disregard of the implications against other people or even themselves long term.
While I haven't used Angular, I have watched a live demonstration of it and was not impressed. Yes it's very boilerplate heavy and reminds me of some of the clunkier Java frameworks.
I'll keep my suggestion short and simple. Look into ReactJs. If your coworkers are sharp they may be willing to look into it too. It's not just another crappy framework.
Bold, and beautiful!! Quick everyone, scrap all your existing frameworks and jump on the flavor of the week!
Seriously though, I think it's borderline negligent to contribute any kind of hype to new javascript frameworks considering they are spraying out into the ecosystem like a broken fire hydrant. New javascript frameworks should be met with extreme skepticism, if not indifference, if we want this industry to be anything more than a joke.
Front-end development considered harmful. Every moron wants to defecate out the next best frontend framework it's a joke at this point. Front end developers have made a mockery of the industry.
I don't think you understand how badly 10gen overmarketed Mongo as something that it isn't. I personally believe the people at 10gen deserve legal repercussions (I expect we'll see this in the coming years), even incarceration for the pure lies they spouted that cost companies so much. MongoDB is a trojan horse, a trap, completely incapable of serving any real-world need. If someone thinks MongoDB is working from them, they just don't realize yet how it's subtly broken.
> …we eliminate so-called “structured programming” constructs like “for” and “if”. Only function calls, variables, and constants are allowed. The result is that we end up with something that looks a lot more like assembly code; but instead of “GOTO” statements, we use callbacks…
Oh god please no.
Building a nontrivial app in node is already a nightmare.
Lenovo going down the drain. All they had to do was continue the Thinkpad legacy left by IBM. It's honestly breathtaking how badly they've fucked up. After the touch-based function keys, ruining the trackpoint buttons and now this. It's unbelievable.
This bears no resemblance to react whatsoever.
By taking out the render, getInitialState, componentWillMount and other lifecycle methods Riot.js completely misses the ideology behind react and becomes just another templating library. Waste of time, anyone reading this should stick with React.
Not to mention we've moved past code tags like "each={ item, i in items }".
This was really good but there were a few levels that left a bit to be desired. Some of them were basically "find a way to mash this code into these functions without exceeding the instruction cap" while others encouraged quite elegant programming. The last one of the final stage was probably the best example, I thought it was quite elegant.
Why would you want to use a database for this problem? The input data would take time to load into an ACID db and we're only interested in a single ternary value within that data. The output data is just a few lists of boolean values so it has no reason to be in a database either.
This is a textbook stream processing problem. Adding a database creates more complexity for literally no benefit assuming the requirements in the linked article were complete. I would be baffled to see a solution to this problem that was anything more than a stream processor, to say nothing of a database being involved.
Are you saying you're using a single MongoDB collection as a dumping ground for all your entities? I hope you're not building a real product that someone has to maintain.
What? When would it ever be OK to lose parts of an invoice. Mongo apologists baffle me sometimes. To anyone considering MongoDB, don't be fooled, you probably want to stick with an RDBMS.
MongoDB will always be a relevant example of false advertising and over-marketing (to the point of 10gen probably opening themselves to litigation) and how we all need to stop drinking the kool-aid.
There is LITERALLY no reason to use MongoDB today. If you're thinking of using MongoDB, for the love of god just try PostgreSQL.