people don't want an intelligent dryer and an intelligent toaster
We need to try to solve the FTL problem.
r.e. FTL research: you raise some good points.
But nobody (except maybe a Comi-Con panel) is going to get behind funding FTL research.
Our species also has some baby steps to work on first: in no particular order... orbital solar power, fusion, space elevators, mars colonies, asteroid mining. *shrug* Let's solve those things first because they will (eventually) set the stage for interstellar work, including FTL research.
As for basic physics research, I would say China is showing some interest in basic research and advancing the state of the art; with any luck that will motivate some other governments to not be left behind. India also seems hungry to establish itself as a prestigious space power; they're doing some cool things - I hope they are successful.
Likewise I'm optimistic about the progress SpaceX has made; I hope they're wildly successful because it will open new doors for humans.
All very cool stuff; some days I think it would be more fun to work with atoms instead of bits. I suppose there a lots of people doing both these days
Because if not... if this is really large company, you may be perceived as a "precious little snowflake that also complains a lot."
And if this is a really large company, they're going to be able to coast along on the status quo for LONGGG time and I don't know why anybody would listen or care about a whiny snowflake.
So... can you (OP) elaborate the "real" part of "real innovation" ?
What amazing market opportunities are the current group missing?
What kinds of obvious fraud detection is slipping through their collective fingers?
What tremendous potential for increasing shareholder value is being left on the table?
Look, I'm not saying this incredibly large organization of yours could never benefit from some innovation, but realize this: you're going to be pushing against the inertia of entrenched culture and "we've always done it this way", which makes those "Stop Plate Tectonics" bumper stickers seem like an easy task by comparison.
I'll close with an alternative possibility: "I don't much like SAS. Nor do I like the people who have built a functioning SAS-ecosystem that handles this company's Multi-Billion euro statistical needs 'well enough'... it just doesn't encourage real innovation ('real' being code for 'fun'), instead I have to spend my time reading through thousands of pages of documentation and requirements specs and I have to troubleshoot this existing install base... Boy, I wish we had an opportunity to do real innovation here..."
1) offer strength-to-weight savings (vs. solid slab cement walls)
2) use less material for a given surface area (yeah, this follows #1),
and 3) allow some extra insulation if warranted by the destination environment.
Also it would probably allow different configurations depending on how tall one wanted to stack (thicker lower-flow pieces; thinner upper-floor pieces). And the other point about embedding services cabling & plumbing stands; I could see them using standard interconnects to splice things together as they get assembled. *shrug* Maybe all that is common place today with prefab walls; don't know ianapfba (pre-fab building architect).
My first thought was "Big deal, another kind of prefab building" but the design + deposit is pretty interesting. This gets into some of the same things for machining I've read about where casting and/or subtractive (cnc milling) runs into limitations; additive manufacturing can create nested structure that were just not possible before. *shrug* It is cool to see people doing neat things with cement++.
And maybe - at some point - it would be cost effective for larger & taller structures to print segments on-site (and possibly at elevation for multi-story units). I don't know that they need to print in-situ; having useful-sized freshly printed & cured components (think just-in-time lego-blocks for the construction crew) could still be useful.
(One downside: I wonder about the "quick-set" additives and how nice (or not-so-nice) it would be to breath anything that off-gassed after it was all put together.)
* Time travel, +/- 5000 years, with return feature
* Teleportation, up to 50km distance
* Time dilation ("bullet time"), minimum 60 seconds subjective to 1 second external observer.
* 3D copier (3D scanner + 3D printer; synthesize feedstock from atmospheric carbon)
* Flight (up to 30 minutes, max load 200kg, max speed 50km/hr)
* Force shield (deflect rain + bullets), 60 minute runtime
* Transforms into giant Battle Robot
* Underwater breathing support + waterproof (rated to 300 m)
* 2d projector (4m diagonal w/1200 lumens @ 20m)
* Holographic projector that plays "Help me, Obi Wan Kenobi..."; monochrome image ok
* Sleep gas feature
* Dog-walking feature
The larger Unicode becomes, the more fragmented the implementations will be.
Maybe instead of fragmented, you mean there won't be font sets that can't render all of unicode's characters?
*shrug* Even if that were a problem, the underlying data is intact and undamaged and will be viewable once a suitable font library is obtained.
The more fragmented it is, the more errors and incompatibilities will compound. It will get less and less useful, and more and more bulky, and will eventually be as useful as Flash. (well, it may not be that bad, but still, Flash was all things to all people, and almost universally installed, until it wasn't.
Can you give me an example of an incompatibility? I'm not saying there are none, just that I don't know of anything and that, in general, I've been very pleased with Unicode's stability - compared to other encodings - for doing data exchange.
One of the scripting things I look for is portability. While Java itself is pretty awful for rapid development (at least for me Java is painfully verbose), if you want to piggyback on Java's virtual machines you can go a long way with Groovy, Clojure, and maybe Python (here's an interesting review of JVM languages). It turns out for my day job there is always a JVM in the environments I need to work in, so I look for easier languages to work with in that regard.
My current personal favorite is Clojure; great leverage, you get a lot of bang for your buck for a line of clojure vs. a line of Java or C.
r.e. self serving: sure, but it also serves others (like myself) by being educational. I hope Keen IO makes a ton of money and goes on to create more cool things.
...but you really needed a bold "disclaimer" in both the summary and article for me to think this is anything but a self-serving post to advertise something that will profit your wife and, by obvious extension, you.
So it seems appropriate that this story showed up near thorium-the-wonder-fuel-that-wasnt article trashing thorium (though the comments there are actually pretty informative).
So... I'll just leave this here: https://www.ted.com/talks/kirk_sorensen_thorium_an_alternative_nuclear_fuel.
*shrug* Our species may evolve some long term planning capability; or it may not.
Then again, the we don't need 100% of humans to be capable of long term planning... just enough to make a difference. Which may not need to be much at all, given that most will be distracted by famine or disease or economic collapse or reality tv. Maybe it only needs to be 0.1% that consider the long term and are worried enough to act. (Maybe, at the risk of being too obvious, we can make a difference.)
crgrace: r.e. micoprocessor simulator, that is a smashing idea... it sounds very cool.
orignal poster (an anonyous reader): Let's assume you're doing this for fun - as a hobby.
car analogy: I read that you don't need to know how an engine works to drive a car, but a good racers will know something about engines.
So... if you want to really learn programming, learn some assembler - doesn't have to be a lot, but every little bit you do learn will help you. Simpler chips are probably better to get started with than jumping into contemporary laptop CPU's. Maybe Arduino? Sounds like you an get plenty of online help with that (example: http://stackoverflow.com/questions/14464713/arduino-assembler-programming-nothing-happens), and they have a 8-bit processor that should make a fine research project for you.
Then learn a compiled language, probably some straight up C.
Once you understand how a cpu works you'll have a deeper appreciation of what CPython's virtual machine is doing, or what 'just in time compilation' is doing for PyPy.
othoh, if just coding Python is fun then have fun. Nothing wrong with that; you don't have to learn assembly... but if you can wrap your brain around assembly, it will certainly raise your game.
Fine slashdot fare, if I ever saw it.
It would be better to say, "the fall of Rome was caused by the introduction of Slashdot. Polling shows that..."