I think what he's getting at is that "Features" are not, by themselves, vulnerabilities. For a feature to become a vulnerability requires context. To a certain degree, you have to frame the conversation a bit. If you frame the conversation "I want to be protected", you can spend days/weeks/lifetimes spinning around in circles. "I want to protect myself against terrorists" is a lot different than "I want to protect myself from dishonest employees", which is a lot different from "I want to protect myself from a foreign invasion force". A road is not something you need to consider for all of these scenarios.
The real trick lies in tying the micro and macro views together so that nothing slips through the cracks.
IE9 and FF4 aren't really full-release yet, so I can see why someone might include those in their compatibility list. Likelihood of new compat. issues before release is slim, but I probably wouldn't pre-release browsers as a matter of habit.
I, for one, am glad I live in a world where the practical dominates my day-to-day, but the fantastical is occasionally made reality.
Get your head out of your bank acocunt balance, and enjoy the dream... Especially since you're not writing the checks, and the dream looks like a fun one.
This site is useless in it's current state. I wanted to compare the performance of different netbooks... Searching doesn't get me the results I want. Browsing by computer type is useless. I can find two different netbooks, but if I can't get them on the same page together, then I can't ask the site to compare their results.
You could always line it with material similar to microwave food heating sleeves / some kind of foil. That may make a significant impact.
As for heat: Paper burns at what... 451? I don't think we have a huge problem here. Most PCs will self-preserve shutdown waaaaaay before that. The only time you have a potential problem is for a bad build/short causing a component to go up in flames, taking the rest of the box/case.
One of the things the article mentions is using more/smaller cells to reduce power needs of cell phones (by having the broadcast location closer). So, if you have a multitude of smaller broadcast stations, they could be positioned closer to the people that need them... Less towers / more bulding-mounted cubes. For example: The chimney on my neighbor's house gets good LOS to my neighborhood.
The real killer here, is that ticket volume is down, so uppermost management sees a cost savings. They don't always see that the company staff are being less efficient because they're "making do".
Though, the inverse can be true too. If the system is incredibly easy to use/effective, then you aand your team are stuck applying band-aids over every tiny papercut, which can be a costly waste of resources.
Agreed. This is a case of someone creating the world they want to live in. I hope he gets an opportunity to create his own successful business, or at least get a managerial position.
Mr. Kim didn't last the night he set out. Mr. Finley lasted 9 weeks.
It's all about gambles and risk (so there will always be examples where the other worked), but I'd much rather put my money on something that will help me live 60x longer.
Agreed and understood buuut: Sony is known for boosting claims way above hyprobole or boasting, and have gotten a reputation for something more akin to outright lies. Do not give them the benefit of the doubt. I reserve judgement until I see one one running a game real-time (not video).
However, the words "Based on the classic arcade game Pac-Man", pretty much classify the whole project as a derivitive work... Which, combined with the name ("Super Pac", where "SuperPacman" is a copyrighted name), is probably reason for the copyright holders to send out a C&D. I mean, I'm no big fan of the corporate machine, but I can see their rationale on this one.
Someone doesn't run over grandpa because he isn't visible enough, they run over grandpa because they ~aren't looking~ (small children may be another story, below the FOV when backing up). If someone isn't looking, this device isn't miraculously going to turn them into a good driver.
Even if you could realize all the proposed lives saved, 292 deaths is less than 1% of automotive fatalities in a year (Source: http://en.wikipedia.org/wiki/List_of_motor_vehicle_deaths_in_U.S._by_year). Of course, automakers aren't going to fight this too much, since everyone has to play ball/raise prices, and having the in-dash monitor is an immediate point for feature up-sells such as GPS.
The killer, of course, is that one of these parties actually produces the goods, and the other merely provides a convenient marketplace for those goods. If it were a cage match, I know who I'd bet my money on.
You forgot one major value point to a few folks: One license works for both PC and Mac versions. If I ever wanted to switch (Or just play one of my games while visiting a friend who uses a Mac), I can do so without loosing my entire game catalog. This is often not the case with discs.
I cannot buy games without evil DRM. I cannot resell PC games where I live. Therefore, to me, Steam is ~no more evil~ than the rest of the industry. The fact that they simplify and streamline my purchase process, as well as allow me to re-acquire any game I've ever bought at any time, and allow cross-platform gaming... They're just as evil as the rest of the industry, but they provide much better customer service.
Uh... Who said I didn't have keyboard shortcuts? I don't have an exhaustive highly-configurable shortcut engine, and keyboard shortcuts are inappropriate for some tasks in the application ("Create a one-to-many containment relationship between entity a and entity b" isn't terribly shortcut friendly), I got the core functionality covered.
VS, EMACS and VI are also keyboard-centric development environments. I'm developing a language-agnostic modeling tool with an interface more akin to Visio or NClass, which are notoriously mouse-centric/slow.
Shortcuts in ProtoModel are more like shortcuts in Photoshop: Yes, they exist, and they do speed things up, but there is a practical barrier to how they can be used. The console gets around that via a faster-than-mouse means for skilled typists (as almost all programmers are).
You know, I was going to do a somewhat similar project... With a baseball cap. Put the IR source BEHIND the WII remote, and get a baseball cap or similar with a small IR reflective dot on it (front and back, for those who still want to look like Fred Durst). Blammo, no batteries around your neck. The only issue would be other IR reflective surfaces you might be wearing.
Actually, the GP's comment about going to a restaurant is a really good one.... Or a cullinary school. If you go out and find someone (or a couple of someones), instead of having them come to you, you're much more likely to get a less biased opinion.
And hey... If you watched the whole video, you'd discover: They do have ways of navigating the space via keyboard.
I'm more a.NET guy these days, but I'd love to try this. Even if the whole thing isn't a slam-dunk, I think there are valuable and useful concepts here that can be useful elsewhere.
From what I see this appears to be more useful for code editing versus code authoring...
When you're maintaining 10,000 lines of code, you're usually focused on a few dozen lines of code, usually broken into a couple of places... Finding that 50 lines of code, and navigating between the places you care about, can be a significant portion of the task. This appears to have a much superior means of finding those lines of code I care about, and maintaining the context between them to edit faster.
As for code authoring? That could be a real headache (literally)
Execpt the vast, vast, vast majority of data that's sent isn't random at all. In fact, it's extremely not-random. If you open a file in a hex editor (even a binary instead of ascii file), there are patterns, there is text, there are markers to show you what you have. Heck, in many files, the first 4-8 bytes of the file will tell you exactly what kind of file it is. While it's not a super-easy problem, it's easier than you're making it out to be.
How about "Birds were dinosaurs. Period."? There's this little thing called evolution... What my ancestors were may not be what I am now. Where you draw the distinguishing line is non-trivial.
Slashdot Mirror
I think what he's getting at is that "Features" are not, by themselves, vulnerabilities. For a feature to become a vulnerability requires context. To a certain degree, you have to frame the conversation a bit. If you frame the conversation "I want to be protected", you can spend days/weeks/lifetimes spinning around in circles. "I want to protect myself against terrorists" is a lot different than "I want to protect myself from dishonest employees", which is a lot different from "I want to protect myself from a foreign invasion force". A road is not something you need to consider for all of these scenarios.
The real trick lies in tying the micro and macro views together so that nothing slips through the cracks.
IE9 and FF4 aren't really full-release yet, so I can see why someone might include those in their compatibility list. Likelihood of new compat. issues before release is slim, but I probably wouldn't pre-release browsers as a matter of habit.
I, for one, am glad I live in a world where the practical dominates my day-to-day, but the fantastical is occasionally made reality.
Get your head out of your bank acocunt balance, and enjoy the dream... Especially since you're not writing the checks, and the dream looks like a fun one.
This site is useless in it's current state. I wanted to compare the performance of different netbooks... Searching doesn't get me the results I want. Browsing by computer type is useless. I can find two different netbooks, but if I can't get them on the same page together, then I can't ask the site to compare their results.
Needs major refinement. Major. Refinement.
You could always line it with material similar to microwave food heating sleeves / some kind of foil. That may make a significant impact.
As for heat: Paper burns at what... 451? I don't think we have a huge problem here. Most PCs will self-preserve shutdown waaaaaay before that. The only time you have a potential problem is for a bad build/short causing a component to go up in flames, taking the rest of the box/case.
Well, maybe, maybe not.
One of the things the article mentions is using more/smaller cells to reduce power needs of cell phones (by having the broadcast location closer). So, if you have a multitude of smaller broadcast stations, they could be positioned closer to the people that need them... Less towers / more bulding-mounted cubes. For example: The chimney on my neighbor's house gets good LOS to my neighborhood.
The real killer here, is that ticket volume is down, so uppermost management sees a cost savings. They don't always see that the company staff are being less efficient because they're "making do".
Though, the inverse can be true too. If the system is incredibly easy to use/effective, then you aand your team are stuck applying band-aids over every tiny papercut, which can be a costly waste of resources.
Agreed. This is a case of someone creating the world they want to live in. I hope he gets an opportunity to create his own successful business, or at least get a managerial position.
Mr. Kim didn't last the night he set out. Mr. Finley lasted 9 weeks.
It's all about gambles and risk (so there will always be examples where the other worked), but I'd much rather put my money on something that will help me live 60x longer.
No, more broadly, and more important:
If you're lost/stranded, never leave the protection of your car.
Please Remember What's First!
PRWF
Protection
Rescue
Water
Food
Importance is in order. Do not give up protection without a extremely high chance of rescue.
Agreed and understood buuut: Sony is known for boosting claims way above hyprobole or boasting, and have gotten a reputation for something more akin to outright lies. Do not give them the benefit of the doubt. I reserve judgement until I see one one running a game real-time (not video).
~D
You forgot us former WoW players, who are cautiously curious, but still keeping our distance.
~D
However, the words "Based on the classic arcade game Pac-Man", pretty much classify the whole project as a derivitive work... Which, combined with the name ("Super Pac", where "SuperPacman" is a copyrighted name), is probably reason for the copyright holders to send out a C&D. I mean, I'm no big fan of the corporate machine, but I can see their rationale on this one.
~D
Someone doesn't run over grandpa because he isn't visible enough, they run over grandpa because they ~aren't looking~ (small children may be another story, below the FOV when backing up). If someone isn't looking, this device isn't miraculously going to turn them into a good driver.
Even if you could realize all the proposed lives saved, 292 deaths is less than 1% of automotive fatalities in a year (Source: http://en.wikipedia.org/wiki/List_of_motor_vehicle_deaths_in_U.S._by_year). Of course, automakers aren't going to fight this too much, since everyone has to play ball/raise prices, and having the in-dash monitor is an immediate point for feature up-sells such as GPS.
The killer, of course, is that one of these parties actually produces the goods, and the other merely provides a convenient marketplace for those goods. If it were a cage match, I know who I'd bet my money on.
You forgot one major value point to a few folks: One license works for both PC and Mac versions. If I ever wanted to switch (Or just play one of my games while visiting a friend who uses a Mac), I can do so without loosing my entire game catalog. This is often not the case with discs.
I cannot buy games without evil DRM. I cannot resell PC games where I live. Therefore, to me, Steam is ~no more evil~ than the rest of the industry. The fact that they simplify and streamline my purchase process, as well as allow me to re-acquire any game I've ever bought at any time, and allow cross-platform gaming... They're just as evil as the rest of the industry, but they provide much better customer service.
~D
Uh... Who said I didn't have keyboard shortcuts? I don't have an exhaustive highly-configurable shortcut engine, and keyboard shortcuts are inappropriate for some tasks in the application ("Create a one-to-many containment relationship between entity a and entity b" isn't terribly shortcut friendly), I got the core functionality covered.
VS, EMACS and VI are also keyboard-centric development environments. I'm developing a language-agnostic modeling tool with an interface more akin to Visio or NClass, which are notoriously mouse-centric/slow.
Shortcuts in ProtoModel are more like shortcuts in Photoshop: Yes, they exist, and they do speed things up, but there is a practical barrier to how they can be used. The console gets around that via a faster-than-mouse means for skilled typists (as almost all programmers are).
~D
Interestingly enough, that is the EXACT philosophy I took when I added a command console to a software modeling tool I'm writing.
Turns out, I'm WAY faster at modeling stuff this way then by pointing & clicking all day.
~D
You know, I was going to do a somewhat similar project... With a baseball cap. Put the IR source BEHIND the WII remote, and get a baseball cap or similar with a small IR reflective dot on it (front and back, for those who still want to look like Fred Durst). Blammo, no batteries around your neck. The only issue would be other IR reflective surfaces you might be wearing.
Actually, the GP's comment about going to a restaurant is a really good one.... Or a cullinary school. If you go out and find someone (or a couple of someones), instead of having them come to you, you're much more likely to get a less biased opinion.
~D
And hey... If you watched the whole video, you'd discover: They do have ways of navigating the space via keyboard.
I'm more a .NET guy these days, but I'd love to try this. Even if the whole thing isn't a slam-dunk, I think there are valuable and useful concepts here that can be useful elsewhere.
~D
From what I see this appears to be more useful for code editing versus code authoring...
When you're maintaining 10,000 lines of code, you're usually focused on a few dozen lines of code, usually broken into a couple of places... Finding that 50 lines of code, and navigating between the places you care about, can be a significant portion of the task. This appears to have a much superior means of finding those lines of code I care about, and maintaining the context between them to edit faster.
As for code authoring? That could be a real headache (literally)
~D
Execpt the vast, vast, vast majority of data that's sent isn't random at all. In fact, it's extremely not-random. If you open a file in a hex editor (even a binary instead of ascii file), there are patterns, there is text, there are markers to show you what you have. Heck, in many files, the first 4-8 bytes of the file will tell you exactly what kind of file it is. While it's not a super-easy problem, it's easier than you're making it out to be.
~D
How about "Birds were dinosaurs. Period."? There's this little thing called evolution... What my ancestors were may not be what I am now. Where you draw the distinguishing line is non-trivial.
~D