Looks good to me, except what happens if your TODO item ID already exists in your DB? If your IDs aren't unique they really aren't IDs, and the retrieval/remove behavior is not going to be what you expect I suspect.

You probably need some logic to handle duplicate items, although w/o knowing your exact use case and how To Dos get into your DB, it's hard for me to say what that logic should be.

For whatever reason express split off the json body parser a while back, so you have to explicitly add it. There are also some config options you might want to set. Here's what we use:

I don't think you need the second unless you have some weird link pointing to index.html.

More shocking it's been a full 2 years since a 0 day in Java was publicly disclosed...I mean "discovered".

Lol applets

The id I'm using is auto generated by mongo so I think its fine?

Items are all (now) being referred to by the id I'm throwing into the data-todo-id there i.e. the DELETE is sending its ajax request to that url. Still seems "wrong" to me but I understand what other people are saying.

Its more like.. why do I even need a json body parser at all? It blew me away that inside of a app.post's req object there's no direct reference to what was sent in the body! req.body does nothing without that bodyParser nonsense. Oh well.

This is a long shot but is anyone using or has done research on using Violin Memory for their data storage needs? I'm interested to know if you belive they have any advantages vs competitors such as Pure Storage. Be it price or technology. Also any insight you can share on the flash data storage sector as a whole would be appreciated.

Youre using es6 string interpolation which is an improvement over adding a bunch of strings but its still not in fashion I'm afraid. I wouldn't want to be seen wearing anything less than handlebars and still the jade people will look down on your taste.

You should probably be setting the status code for your post/delete routes, I think mongo can take another function as the error callback where you can send the 404.

hehe

Yeah the problem here is you can have identical To Dos which are viewed as the same thing to the user, but separate identities by the DB. I would think when a user enters a TODO - your code should check for one of the same text that already exists and warn them.



I think there were some potential security issues with body-parser, so they wanted to separate it out from express so users only use it when they definitely need it.

You probably should consider it.

All your concerns in that snippet seem tangled together. You have your backend server definition, the composing of the pages in pieces, and even the composing of a html <ul> list all together.

Also, you link to js files and mentioned ajax stuff, so I assume you have a SPA app of some sort. So, other than SEO concerns, you should consider not composing your html serverside at all, and using a js framework like react or mithril. That's a separate issue, though. Assuming you are doing server side html rendering, you should at least do it with proper templates rather than manual string concatenation.

yeah I misspoke, obviously templating engines such as handlebars & even underscores are great and I use them all the time, I meant html templating "languages" such as jade which seems a bit excessive.

and yeah its a 50 line app learning tool for express and mongo so didn't bother with that stuff anyways. ES6 string template literals are actually pretty cool.

Another classic example of Android ****edupdness. One of our devs just spent 3 hours trying to create a workaround because the Samsung 10" tablet (which like 43 people own in the world) was getting portrait and landscape mixed up.

I finally figured out that because the button is on the long side, rather than short side - the device reports landscape as window.orientation = 0. When you rotate it to portrait then window.orientation changes to 90 or -90. Whereas every other device we have in our test pantheon (about a dozen) have buttons on the bottom, and therefore portrait is window.orientation = 0, not landscape. Whole front end framework needs to be refactored 2 hours before we're supposed to be done testing.

So fun.

You might be able to style the select element but pretty sure you cannot style the options element

I'm about to start on redoing our front end. I've used Jade quite a lot on my own. I suggested that we should use it but my team leader was less than enthusiastic about it. I need a really convincing argument that no sane man can say no to. Can you help me?

Broken HTML breaks hard and fast instead of weird edge case where you find out an orphaned </div> tag is causing layout issues.

Cuts the # of lines of a template roughly in half.

Due to the indentation = opening and closing tag - you get a lot more built in HTML validation than other templating engines.

Indentation for blocks vs. <tag></tag> is much easier to read once you get use to it.

To me the best argument I can think of - I've never known anyone who tried it, got used to it, and still hated it and wanted to go back - whereas I know dozens of people who can't stand to look at HTML tags now.

I fall into the category of used it for a while, got used to it, disliked it and never touched it again.

It's been around 4 years since I used node/jade heavily but I remember the issue that annoyed me the most with jade. It was wanting to do this:

I forgot the exact implementation with jade but I remember having to pipe the period on a new line due to how jade processes elements. It was so alien looking, an online converter shows:

I remember addressing this with the author of jade and he was like in those cases just use the raw html element in jade, but I think mixing both together is even uglier.

Anyone got a recommendation for cheap cloud static file hosting? Need it for our arcade, if a game gets a ton of hits we need to be serving the game files from the cloud as our 1gbps connection wont cut it.

Is there a better recent website overhaul than Bloomberg and even more so BloombergView? Seriously, the sites just absolutely crush in pretty much everything I could use to critique a site.

How long do you think it lasts with Bloomberg in charge?

Bloomberg looks much better on mobile than it does on full screen.

I love the Apple Watch article. I'll give you an estimate. There are 7 million people in the SF Bay area, so if you have the expectation of every man, woman and child in SV buying one and add that to the weighted probability of everyone else in America buying one, you end up with 7 million units sold.

Really? On desktop, the front page left scroller, which scrolls faster than the main page (I'm guessing to fit in more content? Or maybe someone trying to be cool?) is distracting and captures my visual focus, so that I'm noticing that instead of the headlines in the main section.

Not crazy about the typography.

The tiled article layout is nice but I don't like the needless animation rollovers that show some kind of article tag I can't figure out in red.

Top nav on homepage seems too thick and cluttered -- I count 5 distinct sections, 3 dropdown menus, 9 or 10 clickable items, and an embedded live news feed, and that's ignoring the stock ticker below the main nav, which has its own nav.

When you click on the main dropdown under "Bloomberg Business" that brings up the full site menu, you cannot click again to close it. It brings up a full page modal, and you have to move your mouse to the far right of the page and click the X to close it.

I could go on... All that said, compared to other major news sites it fares pretty well, but it seems strange to hold it up as some paragon of amazing web design and usability.

"Apple is Failing" is still a safe story I guess.

I believe the Apple Watch' potential lies in what developers can come up with.

So far, I personally haven't found a use case to want one. So I can relate with that point of view.

When the iPad came out, there were similar opinions. But the main difference to the watch (so far) is that people came up with tons of use cases in very short order and that was prior to release. Even to the point where the device itself without specific apps could be of use in some way. I'm missing that with the watch.

Having said all that, it seems to sell like hot cakes. Might be fanboism this time around, but only time will tell.

Except that's not what the article is at all...

For those who didn't read it, it is actually a total Apple fanboi article, dripping in awe of Apple's incredible marketing strategy. The fact that no sales numbers have been released shrouds the company in mystery and intrigue, and teasing us with sales numbers produces more hype, and yes, it is quite possible that more people have bought the Apple Watch in the first few months than people who bought the iPhone and iPad... combined!

Maybe it is perception, but I haven't seen a single watch to date.

Hmm, that's not the article I read, perhaps we came into it from different starting points.

if the primary functionality of an app is creating user profiles and filtering/aggregating average user stats for these profiles... is the best option by far to use a relational db? or are mongodb queries good enough for say ~1000-10,000 users? computing the #s once a day in a background job would be fine.