Half the "old generation" didn't know half the time if they are redirected to a phony site by a phishing email. Anyway, that assumes you're going somewhere worth scamming. Email, online bank, ebay sure... but in the last 15+ years I haven't seen a single phishing attempt for my slashdot account info. And stuff that you just read, what's to phish? And that's why the important stuff is moving towards two-factor authentication so just stealing your password isn't enough.

It's the same generation

I wasn't talking about branching at (full) speed, just how effectively you can insert/extract trains from the loop though I suppose low speed exit/merge tubes could be built. Say you have stations 1-5 connecting two major cities with suburbs at 2-4, could you effectively have a schedule like:

1-5 express
1-5 express
1-5 express
1-5 express
1-4, same time 4-5
1-3, same time 3-5 (and maybe 3-4 local following)
1-2, same time 2-5 (and maybe 2-3 local following)
(pause long enough for train to get out of way at station #2
1-5 express
etc.

Then it would be a real boon to the people living at #2-4, because I think the "every 30 seconds" is to get volume up, I don't think it's very significant if you have to wait 5-10 minutes for your route to come into rotation.

What I'm interested in about the hyperloop is that unlike airplanes, high speed rail and traditional tube is that in the concept you'll have 6-8 passengers/capsule and 3 capsules/train = 18-24 passengers/train, which hopefully means you can have many more dedicated routes and/or a mix of long-hop/short-hop routes using the same infrastructure that'll serve the whole 3000 miles and not just the endpoints.

Around here the train is used for a lot of regional travel instead of bus, shorter than airplane and every time there's talk of building out high speed rail the problem is that it'll actually serve the regions worse since you don't have time to stop, so effectively you're just building a grounded airline. It's a lot easier to find 20 passengers going somewhere at the same time than 400-800 so that could be a major game changer if the technology works out.

As such it's not the brightness, it's the color temperature. The spectrum of light ranges in color temperature from 1850K at sunrise/sunset to 6500K on an overcast day to 15000K under a clear blue sky. The eyes adjust to this, if you look at someone using a cell phone at night it'll probably seem to have an eerie blue glow as it has daylight color temperature. So with "nightvision" the dress looks blue/black, with "dayvision" it looks white/gold.

The people trying to read the RGB values to determine the "truth" forget that the color space assumes you have a D65 white point. Basically your LCD screen is trying to show you correct colors for overcast daylight. If you stare at the red sunrise/sunset or the blue sky for a while and then look at the LCD screen, your color perception will be off. Apparently this picture is in just the right sweet spot to confuse a lot of people.

I live in a city in a "coastal region" and what's generally recognized as the city center is 10m above sea level with most areas trending upwards, 2 meters would affect <5% of the city. So there's coastal cities and there's "flat as a pancake cities that are 1 meter above sea level", you can take a look for yourself here. Note that the links in the top bar is showing you pretty much the worst case locations, zoom out and you can see the whole world. Take for example New York at 2m, the bulk of the city is intact. Even at +60m(!) you'll still have Manhatten and Staten Island peaking up above sea level.

I would worry about climate change and resource conflicts as a consequence, but the loss of land as such? Most people would do just fine relocating <1 km further inland. We're on all the beaches because we want beachfront property, maybe that's a bad idea in a 100 year perspective but feel free to buy the second row 50 meters back and 2 meters further up. Of course there's a few tropical islands where that's not an option, but they're <0,01% of the world population.

Dying old beats dying young I guess, but dying sucks overall. The only ones "ready to die" are those where age or illness has already sucked the life out of them. I'm not going to chase the singularity or cryogenics or any other mumbo-jumbo promising eternal life, but heck I hope I'll be like this when I'm 89.

Living in Norway + artificial light + student life with no real commitments I found that my natural cycle is more like 24/12 = 36 hour days than 24. In fact, without alarm clocks I'd have a helluva time staying on the same page as everyone else. The problem is that that sooner or later that clashes with real life and you must get up in the "middle of the night" for a family dinner or you get up in the "morning" and start drinking at a party which messes you up. On Mars making it another 40 mins would be the least of my worries.

Sounds like you've never seen what passes for production code in the bowels of a major corporation. Look at the questions on experts-exchange or stackoverflow. You can safely assume most of them are for paid work. After that, you shouldn't have self esteem issues anymore.

Nothing is better than your own code. But given the choice between my predecessor's hairy ball of custom code and a hairy ball of clue between documented frameworks, I'm not so sure anymore. Because the other side to being generic is "will probably continue to function in a sane fashion if I tweak it a little" while one-off code tends to make a lot of assumptions that may have been true when it was written but falls apart in surprising ways when you try to change it. Unless your predecessor actually made clean, documented code but I know with myself that if you're in a hurry that won't happen. I had to walk a colleague through some systems we use once a year to update various coding schemes and such and to be honest it's an ugly mess. But we do it once a year and we're busy fixing the stuff we use often, so....

I have no idea what you're talking about.

That's not it, CRLF was a feature. How do you make strike-through text on a type-wheel printer? It automatically advances to the next position and it only has a fixed number of characters, you don't double it with strikethrough-a in addition to regular a. So you send a CR - carriage return - to return to first position, space your way over to the text to be striked out and make a ------- over it before you CRLF to the next line. And you have no idea how old knowing that makes me feel.

Unfortunately most of the projects I've been on are of the "We want to replace old system A and make a new system B that also has features X, Y, Z" variety. What they want from the new system is usually okay, it's somewhat documented already, you've identified some stakeholders, you can show them prototypes, you can ask for clarifications and their testing validates the feature. Developing new code for genuinely new features is actually quite easy and fun.

The old system on the other hand is more like software archaeology, nobody really seems to have the specs - or maybe a spec 1.0 from 10 years ago that's got nothing to do with reality - and if you're replacing it it's probably because it's crap, uncommented code in an arcane language with poor frameworks and third party components. So you dig and keep digging and try to implement something similar without knowing what's a feature and what's a bug, who'll come yelling if you break something or features nobody told you about and you weren't aware anyone was using disappear.

I had a bit of an epiphany today at work when i finally found out how structure a major piece of the redo I'm working on and I've so far spent ~2 months digging through that code. From a similar job I was doing in another area I thought maybe 2-3 months total, now I'm guessing it'll be 6-12 because of all the rework I have to make and every apparently simple thing has exceptions and special cases. It's wasn't my bad estimation, it's that the conditions are entirely different. Like comparing travel speed for a walk in the park to chopping your way through a dense jungle.

Good managers get my best guess.
Bad managers get my worst case.
Horrible managers get my resignation.

Tag: WORKS4ME

Except for cost. That's what powered the Android drive, it wasn't the technical superiority. There's probably more people gaming on phones and tablets than any other platform when you count Angry Birds, Candy Crush and such. Chromebooks running on Linux also seem to sell reasonably well for the same reason. If Valve can get a a range of steamboxes out there to sell to everything from a $99 box to sell freemium + $1-5 games to a $999 gaming rig to people who don't really care about having a desktop anymore with their tablet/convertible covering those needs there's probably a market for gaming boxes.

It does of course assume that you commit enough to get it off the ground. Nobody wanted to code for Android either before it got popular. And if Valve is backing off now that the Microsoft Store doesn't seem that big a threat after all, it might take many years. But Linux is well propped up by servers, supercomputers, embedded, cell phones, tables, chromebooks... it's not going away. Particularly not in the direction we're going with more cloud, less local it's certainly not going to get worse.

The driving force behind Mesa is Intel, they're certainly not going away. Pretty soon they'll hit the big OpenGL 4.0 and it seems almost all the prerequisities for 4.1 and 4.2 are done once they get over that hurdle. And they certainly want to keep their OpenGL ES current if they want to play in the x86 smartphone/tablet market. AMD also apparently like their open source driver for embedded/custom projects, less legal hurdles for customers who want full control. So maybe they don't win, but I don't see how they could lose much terrain either.

Built one almost like it, but with a 35W Core i7 4765T. It's not exactly a cheap machine though, for a HTPC it's way overkill. You can get a lot cheaper to play 1080p BluRays and probably won't be enough when 4K BluRay arrives, 3840x2160x60fps 10-bit HEVC decoding will need new, dedicated chips.