But what's really interesting to me is the camera. I'm really interested in seeing that put through its paces.

Who do you think MAKES those M.2 SSDs in Apples? Hint: Samsung

As bad as Mozilla? It's at version 42, Mozilla is at 37. Who do you think started this cadence in the first place?

I have a Nexus 5, with Lollipop 5.1 on it. No boot loop issues. Coworkers with Nexus 5 aren't reporting this, either. /shrug/

They do that in cartoons for kids. That's how they learn, since they don't have a full grasp of the kanji characters until around high school. Without knowing a good chuck of Kanji, it's very difficult to tell where one word stops and another starts. It's not how adults typically read, though.

As far as news sites, I'm not good enough to read those in Japanese yet, but the ones I've seen only have spaces after punctuation, like commas or at the end of sentences, not between words.

FYI: My native language is English, and I have studied Spanish, French, and am currently studying Japanese.

As already mentioned, no irregular verbs

No verb conjugation

Japanese has the concept of particles, which is brilliant, and can solve a great many problems that are present in most natural languages

The problems with Japanese (being a natural language, it has problems like any other) could be solved by more extensive use of particles. Verb conjugation particles could be added; counters could be replaced by a counter particle, etc. Verb particles could also let you put the verb anywhere in the sentence you want, making for a very flexible language. Particles for various levels of politeness could make that very easy for those societies where that is a thing.

re: sounds

I would evaluate the major languages of the world and see if there is a sizable enough set of sounds they have in common that would be sufficient for the new language. One of the problems learners of second languages have is their new language often has sounds that simply do not exist in their native language. If you don't start learning your new language before puberty, the chances of you being able to make native-level sounds in your target language (when those sounds don't exist in your native language) become very unlikely. Some people are able to, but most are not, especially if they don't have the opportunity to immerse themselves in that language every day, which will never happen in a new constructed language.

re: writing

I'm learning Japanese, and the no spaces between words is VERY difficult to adapt to. I would recommend against no spaces. :)

Logographs like Chinese characters (which are also used in Japanese) are VERY efficient for a native language (and I can read those far faster than the Japanese words which do not use them), but learning them is a total pain in the ass, and takes far longer than I would think a good idea for a secondary, universal language. For this reason, I would use an alphabet system that is already in widespread use, and well-understood by more people than any other - the Latin character set used by English and the Romanesque/Romance languages. I would avoid the use of diacritical marks, if possible, due to being harder to type.

My reading of the results is that while no backdoors were found, there were some vulnerabilities found, which are being addressed in the forked projects. That's about as good as could be expected, really, since all software has bugs.

Many such scripts are running from compromised boxes. Instead try to run some notification to the owner of said box (assuming you can trace it) that their system is compromised. Or notify upstream provider. Something useful, rather than wasting time (which would also likely waste bandwidth - which hurts everyone).

Keep in mind that if proper scaling ever gets implemented, there is still a long way to go for displays to equal the quality of text compared to paper. I saw noticeable improvements in text quality from laser printers all the way up to 1200dpi, and people back in the day were saying we'd never need anything more dense than 300dpi, then it was 600dpi, etc. If we can get displays to 1200dpi, and especially with near-zero reflectivity, then I'll say we've gone far enough - but we're nowhere near that yet.

But we need GOOD scaling. I've read that Windows 10 will have proper scaling. We'll see.

Weird. I've been watching HTML5 videos in >720p resolution for some time now. What OS are you using? I'm using it on Windows. You enabled MSE via the about:config page, yes?

I enabled MSE in Firefox in the previous version, and the HTML5 YT videos seemed to work fine except 1080/60p videos, which stuttered a lot. As of v37, that seems to have also been fixed. YMMV, but it's A-OK for me.

It may not be on by default, and it may be 'incomplete', but I turned that on in Firefox some time ago and can view HTML5 YT videos in resolutions greater than 720p. It's certainly good enough for now (though I don't know why it's not on by default).

The nuts and bolts of computer architecture isn't in the scope of computer science. Sure, you might want to know a little about how things work from an abstract level, but let's be clear; Computer science and electrical engineering are two different disciplines.

There's also a big gap between traditional electrical engineering and computer science - computer engineering really is its own thing.

The standard EE curriculum covers a lot of topics: E&M, circuit analysis and design, signal analysis and information theory, wireless communication, VLSI and VHDL, linear electronics, control systems, FPGAs / MOSFETs / ASICs, etc. The most computer architecture that EE covers is the basics of digital logic, and *maybe* a selection of other topics, like memory addressing and a basic instruction set, but it's really just an introduction.

Computer engineering is where the rubber meets the road, so to speak. Consider all of the specialized things that a computer engineer studies: processor design, instruction sets, memory / storage / caching, buses / pipelines / wire protocols, networking, parallel processing, power management (especially conservation), GPUs, firmware and device drivers, multithreading and stack analysis, security systems...

My point is simply that a typical EE barely scratches the surface of CE, and a typical CE has only a modest overlap with both EE and CS.

It's frustrating that so many people don't appreciate just how deep and rich and technically challenging these areas are. It's oddly stylish to diss CS and CE as of a lesser scientific caliber than traditional sciences - to look at a computer as a commodity, a basic web browser wired to a basic keyboard. Very disappointing in general, and it's culturally perpetuated by offhanded comments like Nye's.

Even if they were at our level of technology, if they have starships, then they have nuclear weapons. They don't have to invade, they can simple drop rocks or nukes on us to accomplish the same thing, and there wouldn't be anything we could do about it...

Yeah, nukes aren't even necessary. A lump of any kind of matter, parked at the top of Earth's gravity well and possessing sufficient bulk / shape / cohesiveness to deliver a sizable mass to the surface, will be devastating. If you can multiply that by, I dunno, several thousand - you have a fairly low-tech and cost-effective means of civilization annihilation.

This whole "gravity" thing is really a bummer. If mankind can ever conquer its internal existential threats - global war, nuclear proliferation, climate change, and the cultural-dumbness bomb called "the Kardashians" - then our own gravity well becomes our largest existential vulnerability.