My confidence is bitcoin seems fairly grounded and rational to me.
Despite the failure of both Mt Gox and Flexcoin, the bitcoin exchange rate right now is still $670 according to coinbase, which is what it was yesterday. It's as if the currency is more resilient than the sometimes flawed implementation of a few exchanges, and it doesn't seem as if slashdot skepticism is moving the exchange rate either.
The Flexcoin issue doesn't seem hard to fix on other exchanges. How hard would it be for another exchange to use a smaller hot wallet? Or to insure the maximum size of their hot wallet?
Sites like flexcoin and Mt Gox are some of the early pioneers of probably the biggest innovation in currency in the history of currency. You'd expect some issues.
Here are the stats on the US-only bank robberies in 2011:
The sum total was $38M. Did these robberies decimate the value of the US dollar? Of course not.
When the credit default swaps started melting down, that's because all the banks were trying to insure each other in a giant interconnected circle jerk. That illustrated a huge, late flaw in the US banking system, and it hurt the US dollar. When bitcoin exchanges start trying to insure each other well beyond their actual ability to, then it'll be time to worry.
In the meantime, this is looking a lot like natural selection against bad implementations, not against the currency's fundamentals.
Fill the limo floor to ceiling with balloons. It'll look more festive, be very hard to see who is inside or what they're doing, and they may even act as a kind of low-tech packing material in a car crash, which is a serious issue, as most limo passengers don't wear seat belts.
Enjoy that while it lasts. Soon enough, only AI's will be trusted to write good code. The age of the smelly, surly, bug-prone, human coder is coming to an end.
Agreed. A lot of people aren't aware of the financing model that Tesla came up with, either. It's a steep monthly note, but your recharges are free, and even if they weren't, the cost would be noise. It would be illuminating to see a true use case comparison between owning a Tesla and a gasoline car given the high price of fuel today.
Ever lived in a house with a built-in intercom? Find yourself using it? Don't feel bad. No one else does, either.
For long-term value, try to resist the urge to automate it today. Lasting value will come from routing high quality, shielded cables both for data and power to multiple outlets in every room as well as creating strong rooms and creating lots of easily accessible, strong mount points where you can install things you'd like to automate with whatever the latest and greatest tech is. They might be mounts for motors for pulleys for shades or mount points for light fixtures or for a robotic arm that changes your baby's diapers or a landing pad for flying bot that fetches you snacks from the kitchen. The thing is, tech is changing *so* ridiculously fast now, that no matter what you choose today, it's going to be not only obsolete in no time, but in all probability some kind of maintenance and even security liability later.
If you design those mount points in to look attractive instead of like nubs of unfinished 2x4, that's going to be the real art of making a house that a hacker can thrive in but that can improve continuously over time and that can be of value to someone in the market for a house 10-20 years later. Goes without saying, but removable wall panels are also a great way to make a house far more maintainable into the future.
They would rather embrace a fantasy and believe they can make it real by closing their eyes and clicking their heels.
Interestingly, strong belief has been scientifically shown to have profound effects on our psyche and even our biology. You can see why religion evolved. It confers impressive "mind-over-matter" advantages. Science, for all the things it does well, has never been too brilliant at helping us blindly believing things to be true, nor can it ever be as accessible to everyone as religions are, simply because it's so much more complex to comprehend. Science in its current form is probably a better fit for computers- deliberate, slow, logical, skeptical. Religion is a much better fit for the design of humans. What would be really interesting is a religion that elegantly incorporated science into its stories and belief system and scripture, particularly one that uses all the other successful global religions' growth technique of folding in other religions, so that they feel they have a place in the new one.
Also, writing, debugging, and maintaining GPU code is a lot less fun than CPU code. Much open source GPU code do you know of that is still in use after 5 years?
The interesting thing about this debate is that whoever figures out how to extract elements and useful molecules in a generalized way from any refuse first is going to literally and figuratively be sitting on a gold mine. Countries will jealously guard their garbage as a national resource, and exporting products overseas will make a lot less sense than it does today.
One of the reasons we didn't support the iPad 1 in my last two games was that Apple put an iPhone 4 GPU in it to drive 4X as many pixels as it was driving on the iPhone, and this fill rate strain made the iPad 1 super hard to get a decent frame rate on.
If you're doing anything media-rich, particularly if it involves any kind of screen-space post processing (like deferred rendering, glow, depth of field, or one of many others), then you're really going to feel the cost of that extra resolution in both frame rate and battery life.
As with most things, balance in design is what you want.
I'm sorry, but this is just wrong, and I'm sick of hearing these theories about why JavaScript must always be sloewr. There's nothing limiting to the potential back-end performance of a JavaScript VM just because of a lack of data types. If you want to get serious about execution speed, then you dynamically profile the domains and ranges of all your operations. You don't make assumptions about them. When you know what their potential ranges given the input domains, then you use as small a datatype as you can in order to get optimal performance (cache locality, memory bandwidth, as well as auto-vectorization opportunities and even table-lookups).
This is HARD WORK to do, but it is NOT impossible, NOR is it a limitation of languages lacking a rich set of numeric datatypes. In fact, once you get serious about domain/range analysis, you can potentially pull WAY AHEAD of statically compiled languages in speed, because they are stuck performing full 64-bit or 80-bit FP operations (and moving all that bloated data around) on numbers that often doesn't need even a fraction of that precision.
If they had no concern for human life, they would have killed the drivers instead of beating them up. And it is safe to assume that one or more of thieves was doing it because of peer pressure, which can be intense amoung criminals, where your buddy can suddenly turn judge and executioner if you say or do the wrong thing.
While we're on the subject, let's talk about what white collar criminals "deserve" for the crimes they do that can hurt millions instead of just a handful.
I'm hip-shooting, but it could be that as an LA resident, you're experiencing some prejudice. They go months in Seattle with nothing but gray skies and/or rain, and you have to remain productive. The lack of interest could be due to the perceived risk that you might not be able to hack the gloomy weather.
I'm in the same boat, btw. I live in Santa Monica, and I love the weather here. I would prefer to live amoungst Washingtonians if for no other reason than higher quality conversation, but I know I couldn't handle the Seattle weather for long.
What you should take from a list of specific requirements is that they don't know how to write a good help wanted ad. Contact em (a dev, not HR), be up front that you don't have what they're listing, but that you have experience in the skills behind the tools and that you learn quickly.
It's a common misconception that you need fertilization. If you plant the right crops together, they feed each other the nutrients and take care of nitrogen fixation. The catch is that with intermixed crops, it can become more difficult to harvest your crops with bulk thrashers, but robotics and image recognition can come to the rescue on this front.
Agreed. The assertion is totally ridiculous. Smells like slashdot is getting played by someone who wants to convince the world to buy underpowered GPUs.
It'll seem a little counter-intuitive, but I strongly recommend JavaScript in the Unity game engine for a lotta reasons.
The problem with most visual programming languages is that they don't transition well to written languages, which you start to pine for after getting sick of dragging the output of one module to the input of another for the 300th time. You want this just for laziness/productivity reasons, and it also happens to be a good way to get her motivated to learn English faster.
So here's my thinking: JavaScript and Unity are clearly going to stick around a while, so it's a skill that serve her a long time. Kids love playing games and just about all want to make games. It's a great way to motivate them to learn anything.
You can start with pre-made game templates (tons of stuff out there as well as cheap games w/ source on the asset store, and it's easy to make your own mini-games), and just let her futz around inside the scene editor, changing the numbers for the weapons, health, colours of things, etc. No programming required here. This is all done through easy-to-play-with inspectors which hide the ugly truth that you're changing the initialization numbers of the public members of classes in JavaScript.
This is going to feel fun for a while and is an easy way to start, because it's partly like cheating, and when you push numbers to ridiculous extents, it can even really change the nature of gameplay sometimes.
But there's going to come a point where she's sick of being limited to changing surface stuff, and she's going to want to change behaviours, so she's gonna need to look inside of that Badguy.js file attached to the bad guy that she put the pink hat on for "public float healthPoints;" to see what happens to the "Health Points" mentioned in the inspector for the bad guy class so she can come up with a special weapon that cuts the hit points in half, or that heals the baddie up slowly, or that makes the baddie pinker, or whatever she wants to do.
Lo and behold. She's coding.
Unity is made in Copenhagen, so I'm sure Danish docs are possible, but I don't know much about where they'd be. I think if you want to code, tho, you'd better get used to English. English won that war.
The problem with progress bars is that computer science hasn't stressed measuring the time and resource cost of different kinds of computation. We talk about the Big-O notation and discuss profiling as if it were a curiosity. This is contributing to making operating systems sloppy about what kind of resources they'll allocate to a given process to the point where the idea of a "real-time" operating system is considered novel and different instead of the norm.
If we learned a holistic time and resource cost to our code and built in self-profiling in from the start, we could have extremely accurate progress bars, assuming they reflected a deterministic process, which the vast majority are.
Slashdot Mirror
I imagine their data center power draws are starting to go up.
confidence in Bitcoin is gone.
My confidence is bitcoin seems fairly grounded and rational to me.
Despite the failure of both Mt Gox and Flexcoin, the bitcoin exchange rate right now is still $670 according to coinbase, which is what it was yesterday. It's as if the currency is more resilient than the sometimes flawed implementation of a few exchanges, and it doesn't seem as if slashdot skepticism is moving the exchange rate either.
The Flexcoin issue doesn't seem hard to fix on other exchanges. How hard would it be for another exchange to use a smaller hot wallet? Or to insure the maximum size of their hot wallet?
Sites like flexcoin and Mt Gox are some of the early pioneers of probably the biggest innovation in currency in the history of currency. You'd expect some issues.
Here are the stats on the US-only bank robberies in 2011:
http://www.fbi.gov/stats-servi...
The sum total was $38M. Did these robberies decimate the value of the US dollar? Of course not.
When the credit default swaps started melting down, that's because all the banks were trying to insure each other in a giant interconnected circle jerk. That illustrated a huge, late flaw in the US banking system, and it hurt the US dollar. When bitcoin exchanges start trying to insure each other well beyond their actual ability to, then it'll be time to worry.
In the meantime, this is looking a lot like natural selection against bad implementations, not against the currency's fundamentals.
Fill the limo floor to ceiling with balloons. It'll look more festive, be very hard to see who is inside or what they're doing, and they may even act as a kind of low-tech packing material in a car crash, which is a serious issue, as most limo passengers don't wear seat belts.
Enjoy that while it lasts. Soon enough, only AI's will be trusted to write good code. The age of the smelly, surly, bug-prone, human coder is coming to an end.
Agreed. A lot of people aren't aware of the financing model that Tesla came up with, either. It's a steep monthly note, but your recharges are free, and even if they weren't, the cost would be noise. It would be illuminating to see a true use case comparison between owning a Tesla and a gasoline car given the high price of fuel today.
Ever lived in a house with a built-in intercom? Find yourself using it? Don't feel bad. No one else does, either.
For long-term value, try to resist the urge to automate it today. Lasting value will come from routing high quality, shielded cables both for data and power to multiple outlets in every room as well as creating strong rooms and creating lots of easily accessible, strong mount points where you can install things you'd like to automate with whatever the latest and greatest tech is. They might be mounts for motors for pulleys for shades or mount points for light fixtures or for a robotic arm that changes your baby's diapers or a landing pad for flying bot that fetches you snacks from the kitchen. The thing is, tech is changing *so* ridiculously fast now, that no matter what you choose today, it's going to be not only obsolete in no time, but in all probability some kind of maintenance and even security liability later.
If you design those mount points in to look attractive instead of like nubs of unfinished 2x4, that's going to be the real art of making a house that a hacker can thrive in but that can improve continuously over time and that can be of value to someone in the market for a house 10-20 years later. Goes without saying, but removable wall panels are also a great way to make a house far more maintainable into the future.
Who is John Galt?
They would rather embrace a fantasy and believe they can make it real by closing their eyes and clicking their heels.
Interestingly, strong belief has been scientifically shown to have profound effects on our psyche and even our biology. You can see why religion evolved. It confers impressive "mind-over-matter" advantages. Science, for all the things it does well, has never been too brilliant at helping us blindly believing things to be true, nor can it ever be as accessible to everyone as religions are, simply because it's so much more complex to comprehend. Science in its current form is probably a better fit for computers- deliberate, slow, logical, skeptical. Religion is a much better fit for the design of humans. What would be really interesting is a religion that elegantly incorporated science into its stories and belief system and scripture, particularly one that uses all the other successful global religions' growth technique of folding in other religions, so that they feel they have a place in the new one.
If it's publicly viewable, it's archivable, which means someone will archive it, particularly if no one else is, so it's not erasable.
Nice catch, Fatphil!
Also, writing, debugging, and maintaining GPU code is a lot less fun than CPU code. Much open source GPU code do you know of that is still in use after 5 years?
The interesting thing about this debate is that whoever figures out how to extract elements and useful molecules in a generalized way from any refuse first is going to literally and figuratively be sitting on a gold mine. Countries will jealously guard their garbage as a national resource, and exporting products overseas will make a lot less sense than it does today.
One of the reasons we didn't support the iPad 1 in my last two games was that Apple put an iPhone 4 GPU in it to drive 4X as many pixels as it was driving on the iPhone, and this fill rate strain made the iPad 1 super hard to get a decent frame rate on.
If you're doing anything media-rich, particularly if it involves any kind of screen-space post processing (like deferred rendering, glow, depth of field, or one of many others), then you're really going to feel the cost of that extra resolution in both frame rate and battery life.
As with most things, balance in design is what you want.
I'm sorry, but this is just wrong, and I'm sick of hearing these theories about why JavaScript must always be sloewr. There's nothing limiting to the potential back-end performance of a JavaScript VM just because of a lack of data types. If you want to get serious about execution speed, then you dynamically profile the domains and ranges of all your operations. You don't make assumptions about them. When you know what their potential ranges given the input domains, then you use as small a datatype as you can in order to get optimal performance (cache locality, memory bandwidth, as well as auto-vectorization opportunities and even table-lookups).
This is HARD WORK to do, but it is NOT impossible, NOR is it a limitation of languages lacking a rich set of numeric datatypes. In fact, once you get serious about domain/range analysis, you can potentially pull WAY AHEAD of statically compiled languages in speed, because they are stuck performing full 64-bit or 80-bit FP operations (and moving all that bloated data around) on numbers that often doesn't need even a fraction of that precision.
Don't worry, CodeBuster. The geeks with good taste are also having and raising kids, and they're raising them right- on the command line in Linux.
If they had no concern for human life, they would have killed the drivers instead of beating them up. And it is safe to assume that one or more of thieves was doing it because of peer pressure, which can be intense amoung criminals, where your buddy can suddenly turn judge and executioner if you say or do the wrong thing.
While we're on the subject, let's talk about what white collar criminals "deserve" for the crimes they do that can hurt millions instead of just a handful.
I'm hip-shooting, but it could be that as an LA resident, you're experiencing some prejudice. They go months in Seattle with nothing but gray skies and/or rain, and you have to remain productive. The lack of interest could be due to the perceived risk that you might not be able to hack the gloomy weather.
I'm in the same boat, btw. I live in Santa Monica, and I love the weather here. I would prefer to live amoungst Washingtonians if for no other reason than higher quality conversation, but I know I couldn't handle the Seattle weather for long.
What you should take from a list of specific requirements is that they don't know how to write a good help wanted ad. Contact em (a dev, not HR), be up front that you don't have what they're listing, but that you have experience in the skills behind the tools and that you learn quickly.
What do you find to be the most promising technology for embedding electronics inside 3D prints?
While waiting for this tech to arrive, have you tried emulating electronics with mechanical equivalents?
Come on, there are only 11M car accidents a year, and less than 40k people die from them. We've got 315M people living in the US. Plenty of spares!
It's a common misconception that you need fertilization. If you plant the right crops together, they feed each other the nutrients and take care of nitrogen fixation. The catch is that with intermixed crops, it can become more difficult to harvest your crops with bulk thrashers, but robotics and image recognition can come to the rescue on this front.
Agreed. The assertion is totally ridiculous. Smells like slashdot is getting played by someone who wants to convince the world to buy underpowered GPUs.
That's why you want to save meals and sex for when you've been good.
It'll seem a little counter-intuitive, but I strongly recommend JavaScript in the Unity game engine for a lotta reasons.
The problem with most visual programming languages is that they don't transition well to written languages, which you start to pine for after getting sick of dragging the output of one module to the input of another for the 300th time. You want this just for laziness/productivity reasons, and it also happens to be a good way to get her motivated to learn English faster.
So here's my thinking: JavaScript and Unity are clearly going to stick around a while, so it's a skill that serve her a long time. Kids love playing games and just about all want to make games. It's a great way to motivate them to learn anything.
You can start with pre-made game templates (tons of stuff out there as well as cheap games w/ source on the asset store, and it's easy to make your own mini-games), and just let her futz around inside the scene editor, changing the numbers for the weapons, health, colours of things, etc. No programming required here. This is all done through easy-to-play-with inspectors which hide the ugly truth that you're changing the initialization numbers of the public members of classes in JavaScript.
This is going to feel fun for a while and is an easy way to start, because it's partly like cheating, and when you push numbers to ridiculous extents, it can even really change the nature of gameplay sometimes.
But there's going to come a point where she's sick of being limited to changing surface stuff, and she's going to want to change behaviours, so she's gonna need to look inside of that Badguy.js file attached to the bad guy that she put the pink hat on for "public float healthPoints;" to see what happens to the "Health Points" mentioned in the inspector for the bad guy class so she can come up with a special weapon that cuts the hit points in half, or that heals the baddie up slowly, or that makes the baddie pinker, or whatever she wants to do.
Lo and behold. She's coding.
Unity is made in Copenhagen, so I'm sure Danish docs are possible, but I don't know much about where they'd be. I think if you want to code, tho, you'd better get used to English. English won that war.
The one. The only. The original monitor:
] CALL -151
The problem with progress bars is that computer science hasn't stressed measuring the time and resource cost of different kinds of computation. We talk about the Big-O notation and discuss profiling as if it were a curiosity. This is contributing to making operating systems sloppy about what kind of resources they'll allocate to a given process to the point where the idea of a "real-time" operating system is considered novel and different instead of the norm.
If we learned a holistic time and resource cost to our code and built in self-profiling in from the start, we could have extremely accurate progress bars, assuming they reflected a deterministic process, which the vast majority are.