Rygu

I use `delete object[key]` all the time to unset a property. I do think in the JS world the use of `new` is inconsistent, but avoiding the keyword does not rid of that fact. Your new-less libraries may be consistent with each other, but not the rest of the JS world that do it their own way. (http://xkcd.com/927/)

This seems like a problem the language should solve incrementally. Especially with ES6 classes and modules!

Loving the calendar+tasks hybrid view. It even resizes as you interact with either so you can fully make use of the available the screen estate. One can say it's "Touch-Responsive Design".

Last week I pushed my own isomorphic React starterkit to GitHub, where it was trending:

- https://github.com/RickWong/react-isomorphic-starterkit

The starterkit's focused on the build tools and overall ease-of-use. You can get started in less than 5 minutes. The included example showcases how the server & client work together elegantly to produce the page. The goal of the starterkit is to enhance productivity so there's one single cli command to watch and rebuild both the server with auto-reloads, and client with hot (instant) code updates. Everything happens automatically on-save.

Check it out, it just works. I'm looking for feedback.

According to you, it's even more racist then. Because, what about the asian students that come from poverty? Why is the adjustment (still can't believe they do this) based on ethnicity and not on the parents income or bank account?

Also, make backups regularly.

You gotta be a little insane in a particularly good way.

Learning is important. Part of being a developer is that you must keep learning new techniques and facts that help you accomplish your goals or your clients goals. So I'm not saying we don't need to deal with internationalization, localization, and globalization. When the time comes, deal with it. I'm just saying there's no shame in being a developer with little or no expertise in those subjects. Many commenters here don't seem to acknowledge the many amazing technical things that developers generally do know about.

Thanks for taking the time to respond in words.

Developers can't know everything there is to know in the world. Developers aren't suppose to know specific stuff like this. Some parts of modern society are easy to digitalize, other (often historical) parts aren't. I think it's up to entrepeneurs to find ways to solve these problems, and create a better world by doing that. Don't blame/shame developers for stuff like this. It's not even remotely fair.

When you're training developers remember that you're not training demigods.

If you simply need to test a website on a simulated slow connection, then Chrome Devtools. For all other purposes, this looks great!

PHP minor releases are bug and security fixes. But as long as the latest minor release fixed a vulnerability, in 99% of the cases, you can assume that all previous versions contain that vulnerability. (I know, I know, regressions do happen)

If few people hate programming in Javascript then explain this to me:

https://github.com/jashkenas/coffeescript/wiki/list-of-langu...

Perhaps legacy software is becoming the problem. In any system there's bound to be a dependency or any kind of use of a legacy piece of software with known bugs/exploits. Hackers identify these weakest links/weak spots and use these 0-days as entry points to breach the system further. As more systems are developed, it takes so much more time to track these weak spots, let alone maintain them.

So I think you're right. It's a miracle that the Internet even works. At all.

It already implements count() and the corresponding interface so it's possible to write count($collection) as if you're writing $collection->count(). It's a valid question why this type of object needs two methods for checking the same property.

No worries. That's why we have 2 Christmas days.

At the moment now it's default orange again. Xmas theme turned off?

Vrolijk Kerstfeest!

* HTML Imports

* Object.observe

* Promises

* HTML Templates

Sorry but IE8 support. Nuff said.

Fun side-project, kudos. Also for humans: https://imageoptim.com/

Well if "Pebble" is a platform and iOS is a platform, my bet is that Apple already won this.

Just heard about Shyp yesterday. Seems like it's the same idea but selling the concept of regular people helping each other for a more personal service (like Uber, Lyft). I kind of like that approach. http://www.shyp.com/heroes

This is why it's increasingly important to not only test your code, but also develop useful vulnerability scanners. I know, it sounds impossible to write a complete vulnerability scanner, but many companies would pay for such a thing.

Existing solutions are either lacking or way too difficult to operate.

Create a 5th div that exactly overlays the focussed element, and give the overlay an inset box-shadow. (You may need to pass through mouse events programmatically.)

The truth. Take web development. If you're willing to look objectively at the state of HTML5 and the lack of feature support for browsers (that stick around), then yes we've established many good specs and communities, however for the enduser comparing it to Flash back in the days, nothing different. At least Flash development was easy.

goes back to building JS and CSS files with his frontend build system, and testing in IE8

Ok, I thought it was an Apple product because of the (apple.com)

I wonder where the investment money ("millions") went. Knowing that, probably means knowing the truth.

I imagine the tags "government" and "open source". And if the answer to the question is "nowhere", then another topic is spawned.

Hilariously effective education. It's also a great display of the Cantonese' history, culture, and (wise) humor. Wonderful!

Seems that he was able to execute the "uptime" terminal command via that URL, and the output was served as page content. Now imagine what other dangerous terminal commands he could run.

This doesn't come as news to me. Every website can be shown via WK/UIWebViews as a "mobile app". Each javascript therefore is "hot code" being pushed. But I don't think Apple ever disallowed that, on the contrary it was the only way to develop for iPhone 1.

BitAuth is an overly complex system that's seriously standing in the way of mass developer adoption.

http://blog.bitpay.com/2014/07/01/bitauth-for-decentralized-...