Most published numbers aren’t actually using the tensor cores. We’re using dlib (which is in c++) and gives us more direct control, but surely Tensorflow will eventually do this too.
Exactly. I doubt most of the ChromeApps that exist today were made for ChromeOS. They were made because it was an easy and straight forward way of making a webapp on the desktop. Now, as OP mentions, everyone is moving to Electron and NWJS, neither of which works directly on ChromeOS.
The only upside I can see is that CrOS is soon going to support running Android Apps which may save it, but even then... Maybe they'll figure out a way to run Electron/NWJS apps on ChromeOS?
OP isn't calling out how it hurts CrOS, they're describing how it's the place that Chrome Apps are still available, and thus could have that functionality copied out of CrOS and rejiggered to (continue to) work in Linux.
I wish more web services provided opensource versions (Service-as-a-Software). Large orgs would still pay for service contracts even if they self host, and just having the option makes everyone more likely to invest on top of your service.
This is a very good point. Even if you don't want to self-host and you'd rather use a service, having the software available as open source so you can self-host if you so choose, makes it more rational to use the service, because it makes it harder for you to be screwed the way OP's startup was.
Chat at "indie scale" is fairly easy. 10-20k concurrent users fit into one or two machines with off the shelf software (ejabberd) with minimal expertise. 1k-2k concurrent users could easily be done in almost any stack.
If you're doing more than 20k concurrent users, odds are you can afford to hire someone to scale up or build out a team to do it, or find a 3rd party service and pay them to host your chat.
The author works for mozilla, and firefox is a common theme on his blog. I think it's for regular readers of his blog to understand the practical impact (readers he assumes care more than average about firefox).
Found this after Joël tweeted the quote "The dilemma every artist confronts, again and again, is when to stick with familair tools and materials, and when to reach out and embrace those that offer new possibilities." So true.
If there's one thing I've learn from reading about Systems Theory / reading Russell Ackoff, it's that every field, every practice, every art is far more similar than they are different.
"This method takes a foo object, applies HTML encoding, and returns an array of the original and the clean code." could be a 3-line unit test that's just as clear to read, but has the side effect of actually being true instead of maybe being true!
I would consider that comment just as bad as the ones in my examples, but maybe not quite as obviously so.
The main benefit of comments that you seem to be missing is that they are in the right context. Unit tests, while useful and required, make for boring reading and are not right where you need them. If I need to open up a separate file and scroll through tons of other tests to find the unit test "docs" on a function, you've lost me already.
Of course a better comment could be written. I was using a short and concise comment to illustrate how you can gain a huge amount of understanding in a single line versus parsing a long function definition. Other comments here make suggestions for writing good comments.
Do we need significant software changes to take advantage of the new power? Are the TFLOPs somehow not directly comparable?