That's pretty scary to be honest, especially given the range. A sniper squad could very effective with quick extraction available.
I wonder if the system supports a remote spotter (fire in general direction, bullet waits to find it's tracking laser at the remote point, the bullet would have to be able to handle dramatically different angles, and know where the spotter is I would think), someone closer in could more easily track movement or switch targets on the fly.
It's cool though, that's for sure. They don't mention it, but I wonder what the specs on the optics are.
If Dart performance is better than Javascript on supported browsers then some will adopt it (surpassing JS performance should be pretty easy in my opinion, Google Maps suffers badly from JS lag and I would not expect that from Google).
If a converter allows other browsers to be supported, then hell yes!
Adoption will probably be mostly for new projects, I'm not sure how it would work with an existing JS heavy code base (I guess not well).
I openly admit that I'm not a web UI developer. JS is one of the reasons. And it's not about learning syntax, it's about the things JS will allow, it is a different beast at its core from my experience. For the record, I'm a C# developer most of the time.
The soul of an individual is composed of the direct and indirect memories people have of one, while living and after death.
Most people's souls last two to three generations, and then we are just geat-great-grand-father Jason with no stories (I don't even know the names of my family that far back), forgotten other than by name, if lucky.
Some people's souls live forever, those enshrined in history, such as Abraham Lincoln.
That's how I see things.
I'm around to have fun and provide for my family. And after a while I won't be. I really enjoy camping and playing guitar (mostly for myself, which is fine). So I bring my kids camping a lot and play guitar with/for them a lot (my 4 year old daughter requests Follow You Into the Dark, which I love to play). This is the purpose of life.
I'm not perfect, no one is, but keeping things simple (seek for happiness for you and those around you, the happiness of those around you should be a focus with significant others and children).
Anyway, the kids are in bed and the guitar is calling. Shameless self promotion, here's a cool video/song of my sunrise drive home on Father's Day this year (I asked for and received a day of solitary camping, it was fantastic): https://www.youtube.com/watch?...
Back in 1991 in Illinois I had to take a driving class in high school if I wanted my license at 16 (I was already an accomplished driver thanks to farming, it was nice having an old 50's pickup I could drive in the cow field anytime). Otherwise you had to wait until you were 18. You had to meet time requirements for classes, simulator (it was stupid, but provided hazard training), and behind the wheel. There were very few dropouts through junior year, a lot of people dropped out right after passing driving class...
The requirements and license restrictions are even more strict now.
As you do, I always pay attention and adjust speed to conditions (in the fast lane I won't pass other cars at more than 5-10mph than they are moving).
Driving is dangerous, but most people don't realize that.
Another approach rather than in-place same-tech modernization is the Strangler Pattern, coined by Martin Fowler.
This involves building a new application (or applications, utilities can be important) "around the edges" of the existing one, rewriting functionality aspects into a new system; chipping away at the old system (give the users a better solution for some things and they will not mind working with two systems).
The key word in the summary is "legacy". This indicates that there is a large code base that the current developers are not too familiar with (deep knowledge, staff turnover causes this). This causes an organization to fear change due to the related complexity of changes and potential regression bugs. I'm going to guess that there aren't large, mature suites of unit and regression tests.
So I believe you have: 1. Complex code base without a lot of deep developer knowledge of the innards. 2. Fear to change things too much due to complexity and the possibility of introducing bugs. 3. Do not have effective, wide coverage testing implemented.
But, you also have good knowledge of Perl and the architectural elements that compose the system (server software, external libraries, etc.). That knowledge is very valuable and shouldn't be dismissed just for the sake of changing the base language of a system. And you have a working system. How many person years of development have been put into it? Are you willing to spend that much time on the replacement (do you think a replacement could be built in less time, and if so, why?)?
As well, rewriting large admin systems is very risky. I've personally seen two such efforts fail, a 100% failure rate from my personal experience (both had budgets over $5 million, one was over $40 million). Here's an article on this topic: http://hbr.org/2011/09/why-you...
Consider keeping the existing system, but embarking on a long term (years) modernization/re-design/improvement effort to make the system more modern (ie. easier to work with). Focus on small, non-breaking changes that can go out with regular enhancement promotions (the modernization effort should be able to stop at any point, with any improvements to the system staying in place - this allows for tight budget control and financial risk mitigation). Hire a good application DBA to perform analysis and recommend changes to the data model. Hire a good software architect or bring in architectural consultants that can bring a different perspective to the understanding of the application, its goals, and how it could be improved.
I RTFA and the company, SkyTran, is based in California, USA. In fact, the CEO is a former Navy Seal (he also has a lot of international experience, but none previously involving Israel, from what is listed).
Here's more info regarding the link that NormalVisual provided.
Spidey is an Android app that tracks the cell towers available at a location and can supposedly notify you when new towers show up (or at least identify them by comparing against prior scans).
I've been trying to use it, but I can't get it to pick up more than one tower at a time, in downtown St. Louis (I would expect several towers to be visible).
I loved those bible sized tomes, reading about all of the computers I couldn't afford because I was a poor college student. It was all about the advertising, and it was fantastic.
I'd mod you up if I had points. Elon Musk is a true visionary of our times. I hope he continues to have success with his current endeavors, and even more with future projects.
I can't think of anyone who is changing the world in constructive ways like he is.
One word, use tax havens in the Caribbean. Who doesn't do that?
If a company says that what you do is public, there is no recourse. As long as what they are sharing is clearly stated (how it's used, I'm not so sure). If a company says blatantly that certain information is public, then it can be so.
For a while I worked for an US based international insurance company, with several years on an underwriting project (medical record images and data). The project didn't involve business in the US, there was already a system for that. We kept UK data in our UK servers. European data was stored in Canada (latency is a bitch). The Asian/Australian data was in Australia, Malaysia, and Hong Kong. South African and Indian data were in South Africa.
One day the Indian office was told that keeping the personal records (medical info) in South Africa wasn't good enough for Indian records. Data privacy. We had to move personal data to the UK.
The distributed service design I put together allowed us to move personally identifying data to the UK (database moves), and a simple endpoint update to the client configuration was all that was needed on the code side. The latency increase was substantial (> 1 second per request for personal info) but the regulatory requirements were met.
International data can be complicated, but if it is made clear that things are public the situation is much more simple.
Everyone is playing by the same rules. We may not like the rules, but they define how the game is played. At this time it is up to a company to identify patents they may be infringing.and avoid infringement or seek to license as required.
And if litigation starts, I'm sure the initiating party has to disclose the patents in question (probably along with a non-disclosure agreement).
Apple and Amazon play the same way, as do many companies.
Slashdot Mirror
This is why I have a dash cam. Aside from evidence it can capture some very cool road trips.
That's pretty scary to be honest, especially given the range. A sniper squad could very effective with quick extraction available.
I wonder if the system supports a remote spotter (fire in general direction, bullet waits to find it's tracking laser at the remote point, the bullet would have to be able to handle dramatically different angles, and know where the spotter is I would think), someone closer in could more easily track movement or switch targets on the fly.
It's cool though, that's for sure. They don't mention it, but I wonder what the specs on the optics are.
If Dart performance is better than Javascript on supported browsers then some will adopt it (surpassing JS performance should be pretty easy in my opinion, Google Maps suffers badly from JS lag and I would not expect that from Google).
If a converter allows other browsers to be supported, then hell yes!
Adoption will probably be mostly for new projects, I'm not sure how it would work with an existing JS heavy code base (I guess not well).
I openly admit that I'm not a web UI developer. JS is one of the reasons. And it's not about learning syntax, it's about the things JS will allow, it is a different beast at its core from my experience. For the record, I'm a C# developer most of the time.
VB6 and all versions of the Office scripting language (VB6..., I'd much rather use C#) had this option. In the early 1990s.
I hugely prefer static typing.
And don't get me started on function redefinition in Javascript. It's more than a debugging nightmare, it is a debugging apocalypse.
How about this?
The soul of an individual is composed of the direct and indirect memories people have of one, while living and after death.
Most people's souls last two to three generations, and then we are just geat-great-grand-father Jason with no stories (I don't even know the names of my family that far back), forgotten other than by name, if lucky.
Some people's souls live forever, those enshrined in history, such as Abraham Lincoln.
That's how I see things.
I'm around to have fun and provide for my family. And after a while I won't be. I really enjoy camping and playing guitar (mostly for myself, which is fine). So I bring my kids camping a lot and play guitar with/for them a lot (my 4 year old daughter requests Follow You Into the Dark, which I love to play). This is the purpose of life.
I'm not perfect, no one is, but keeping things simple (seek for happiness for you and those around you, the happiness of those around you should be a focus with significant others and children).
Anyway, the kids are in bed and the guitar is calling. Shameless self promotion, here's a cool video/song of my sunrise drive home on Father's Day this year (I asked for and received a day of solitary camping, it was fantastic):
https://www.youtube.com/watch?...
How are they powering this muscle?
I'm actually thinking about doing this in the kids room (the wife even thinks it is an interesting idea).
Magnetic paint? Where the hell have I been while paint technology have been moving forward so fast???
I've always considered Idiocracy a documentary. Now I just want a Kleenex style T-Shirt dispenser.
I didn't realize they made whiteboard paint. That sounds cool.
Thanks.
Back in 1991 in Illinois I had to take a driving class in high school if I wanted my license at 16 (I was already an accomplished driver thanks to farming, it was nice having an old 50's pickup I could drive in the cow field anytime). Otherwise you had to wait until you were 18. You had to meet time requirements for classes, simulator (it was stupid, but provided hazard training), and behind the wheel. There were very few dropouts through junior year, a lot of people dropped out right after passing driving class...
The requirements and license restrictions are even more strict now.
As you do, I always pay attention and adjust speed to conditions (in the fast lane I won't pass other cars at more than 5-10mph than they are moving).
Driving is dangerous, but most people don't realize that.
Another approach rather than in-place same-tech modernization is the Strangler Pattern, coined by Martin Fowler.
This involves building a new application (or applications, utilities can be important) "around the edges" of the existing one, rewriting functionality aspects into a new system; chipping away at the old system (give the users a better solution for some things and they will not mind working with two systems).
Here's Mr. Fowler's original article about such:
http://martinfowler.com/bliki/...
The key word in the summary is "legacy". This indicates that there is a large code base that the current developers are not too familiar with (deep knowledge, staff turnover causes this). This causes an organization to fear change due to the related complexity of changes and potential regression bugs. I'm going to guess that there aren't large, mature suites of unit and regression tests.
So I believe you have:
1. Complex code base without a lot of deep developer knowledge of the innards.
2. Fear to change things too much due to complexity and the possibility of introducing bugs.
3. Do not have effective, wide coverage testing implemented.
But, you also have good knowledge of Perl and the architectural elements that compose the system (server software, external libraries, etc.). That knowledge is very valuable and shouldn't be dismissed just for the sake of changing the base language of a system. And you have a working system. How many person years of development have been put into it? Are you willing to spend that much time on the replacement (do you think a replacement could be built in less time, and if so, why?)?
As well, rewriting large admin systems is very risky. I've personally seen two such efforts fail, a 100% failure rate from my personal experience (both had budgets over $5 million, one was over $40 million). Here's an article on this topic:
http://hbr.org/2011/09/why-you...
Consider keeping the existing system, but embarking on a long term (years) modernization/re-design/improvement effort to make the system more modern (ie. easier to work with). Focus on small, non-breaking changes that can go out with regular enhancement promotions (the modernization effort should be able to stop at any point, with any improvements to the system staying in place - this allows for tight budget control and financial risk mitigation). Hire a good application DBA to perform analysis and recommend changes to the data model. Hire a good software architect or bring in architectural consultants that can bring a different perspective to the understanding of the application, its goals, and how it could be improved.
Here's an article on approaching IT projects in a "Small and Simple" manner:
http://w.objectwatch.com/white...
The summary mentions that funding is at $4.5 million and Seth will match $1 million above $4 million.
The project is at $4.66 million now with 41 hours left. Seth is going to be in for $1 million.
I like his shows, but he is showing some true character lately. Good guy all around.
Wish I had mod points, although I'd have to decide between Funny and Insightful, it is both.
Slashdot was mentioned prominently in the comments for the project once it hit the front page.
I followed the posts that day (Tuesday?) and comments were much more lively than before that point.
I RTFA and the company, SkyTran, is based in California, USA. In fact, the CEO is a former Navy Seal (he also has a lot of international experience, but none previously involving Israel, from what is listed).
They do have an attorney in Israel.
http://skytran.us/skytran-team...
This doesn't explain why Tel Aviv was chosen as the first build out.
A very apt question in this case.
And the next question, Who Prosecutes the Watchers?
Here's more info regarding the link that NormalVisual provided.
Spidey is an Android app that tracks the cell towers available at a location and can supposedly notify you when new towers show up (or at least identify them by comparing against prior scans).
I've been trying to use it, but I can't get it to pick up more than one tower at a time, in downtown St. Louis (I would expect several towers to be visible).
Here's a presentation about the application:
https://docs.google.com/presen...
Here's the download link for the app:
https://rink.hockeyapp.net/app...
Hear, hear! I'm 40 and just entering the most interesting part of my career (architecture and rapid prototyping).
Relevant to the article, I'm also a guy.
I loved those bible sized tomes, reading about all of the computers I couldn't afford because I was a poor college student. It was all about the advertising, and it was fantastic.
You are correct about 18 cents all at once never happening.
But the summary says it's 12 cents over 2 years.
I'd mod you up if I had points. Elon Musk is a true visionary of our times. I hope he continues to have success with his current endeavors, and even more with future projects.
I can't think of anyone who is changing the world in constructive ways like he is.
One word, use tax havens in the Caribbean. Who doesn't do that?
If a company says that what you do is public, there is no recourse. As long as what they are sharing is clearly stated (how it's used, I'm not so sure). If a company says blatantly that certain information is public, then it can be so.
For a while I worked for an US based international insurance company, with several years on an underwriting project (medical record images and data). The project didn't involve business in the US, there was already a system for that. We kept UK data in our UK servers. European data was stored in Canada (latency is a bitch). The Asian/Australian data was in Australia, Malaysia, and Hong Kong. South African and Indian data were in South Africa.
One day the Indian office was told that keeping the personal records (medical info) in South Africa wasn't good enough for Indian records. Data privacy. We had to move personal data to the UK.
The distributed service design I put together allowed us to move personally identifying data to the UK (database moves), and a simple endpoint update to the client configuration was all that was needed on the code side. The latency increase was substantial (> 1 second per request for personal info) but the regulatory requirements were met.
International data can be complicated, but if it is made clear that things are public the situation is much more simple.
Everyone is playing by the same rules. We may not like the rules, but they define how the game is played. At this time it is up to a company to identify patents they may be infringing.and avoid infringement or seek to license as required.
And if litigation starts, I'm sure the initiating party has to disclose the patents in question (probably along with a non-disclosure agreement).
Apple and Amazon play the same way, as do many companies.
Can you estimate how many hours you have spent playing Donkey Kong? Is it still fun to play?