It's not evil type coercion, at least in my opinion, and that of others I know (Matz for example). When everything that isn't specifically false/nil evals to true it makes a lot of business logic strategies a lot simpler to code. It might suck for lower level progs, dunno b/c I'm not one.
Ruby works like this also - if the var has gook in it, it's true. If it's deref'ed it's false.
Yeah seriously. My phone I think is faster than my laptop (t43). OTOH, I got a work laptop recently (Toshiba) which is ostensibly modern but is a total POS and has the same JS UI lag as my trusty t43.
Which seems great - and is exactly the same solution that Ruby, Python, Perl and everyone is working on. Same game, different instrument.. What am I missing?
Wow - yours is the first post that actually makes a good point. Mod parent up!
Moving JS out of the browser just means it loses all the competitive advantages is could possibly have. Moving it out of the browser means that it will suck for writing multi-OS client applications in the same way Ruby (or pick your scripted language) does.
I already notice the javascript cycle churn on my local workstation when browsing (ahem slashdot and gmail). Dumping more cycles on my client isn't a good idea unless someone finds a way to keep the utilization from lagging UI and other noticeable items..
Huh? This sounds like a bizarre argument of "don't make things too simple or people will get confused." Getting confused about whether something is running on the front-end or the back-end is a problem I think a lot of web programmers would like to have (including me). Using separate languages simply to indicate where the code is running doesn't sound like the right solution to the problem.
I think you're referring JScript, which was Microsoft's look-alike to Javascript. It's been a while but I seem to recall that there were substantial differences in the languages, down in the weeds, which made porting some applications back and forth a pain.
I've been using it too. It has some great features. My experience is that it's a little buggy. For example, it doesn't always catch new folders that have been created, so I've found myself unable to remotely access a file b/c the new folder was not caught by the service (and so none of the files were backed up). Second complaint is that restorations are slow-ish sometimes (10 min for a 300k file). Sometimes the restorations are fast and I can't tell if it's the specific file (due to fragmentation in the cloud or something) is slow or if it's their server utilization. Finally I can't ever get the folder sync to work - it always errors out with a weird message.
Do you have any of these problems?
Overall I like the product but I think it has to mature.. Your input would be great!
I've been using spideroak, and I have one complaint which is restorations are sometimes fairly slow (10 minutes to pull down a 300k file). Sometimes it's fast-ish (30 sec) , so I guess it's where the file is in their cloud.
We ran across a classic one of these. A application we developed in 1992 stopped working in 1994 for some unknown reason. After a few days of heinous debugging to build a test case, we come across a line of code headed with this comment:/* this will not work - jr */
We fix that line so it will work, and all have a good laugh later. At the time it was pretty frustrating as I recall. I'm still good friends with JR by the way.
And while "he" is getting called at three in morning 2 years later to fix a crazy bug that has stopped all business, due to a new use-case being introduced that mysteriously breaks that function, "you" is now coding on a new project, using sound development techniques (including understanding how code works while "you" writes it), making the company new money.
Yeah really - mod parent up. This is largely an issue of contract not copyright. The Apple EULA says "thou shalt not do X" Pystar did "X" and the court said that they had to stop it. Pystar raised some copyright issues but the big shut down is because the EULA is enforceable in court. Am I following along?
I think the judge ruled that Psystar violated the EULA contract. So I'm not sure the issue of copyright plays in this regard. There might have been rulings about Pystar's use of copyrighted materials also, but the big deal is that the EULA defines some things you can't do and the judge ruled that this shrinkwrap contract applied to Psytar.
IANAL, but I think if Apple has gone so far as to fund Psytar and stage this whole litigation, if it ever came out they could be liable on a number of fronts. Wasting the court's time might be one, but a lawyer in the right field could probably find some more serious offenses for such shenanigans.
Doesn't zsh work pretty much the same on Windows these day? Cygwin or other variants? I'm not arguing with your point, just looking for the significant differences between casual use of Unix command line on various OS's. I realize Mac is going to have deeper support for Unix make/build stuff than Windows, but I don't think that was your point? Just curious really..
Wouldn't a several km mag field require a lot of power? Much more than can be derived from the limited # of sq meters of solar panels available for a satellite?
Are you seriously arguing that it's possible to drive a #2 pencil through 100mm of armored steel? If so, please produce some evidence of this ever having been done. I'll be interested even if the pencil comes out the other end dulled.
Your second point about 36k km/s seems wrong to me b/c the relative velocity of the net and the objects will be much, much lower than this. Am I missing something?
Just wanted to point out that for the first time in the history of slashdot, you correctly spelled "losing" and "loose" in the same sentence. The content of your point is good too!
Slashdot Mirror
Don't forget the tinfoil hat - electric company satellites are a threat too!
It's not evil type coercion, at least in my opinion, and that of others I know (Matz for example). When everything that isn't specifically false/nil evals to true it makes a lot of business logic strategies a lot simpler to code. It might suck for lower level progs, dunno b/c I'm not one.
Ruby works like this also - if the var has gook in it, it's true. If it's deref'ed it's false.
Yeah seriously. My phone I think is faster than my laptop (t43). OTOH, I got a work laptop recently (Toshiba) which is ostensibly modern but is a total POS and has the same JS UI lag as my trusty t43.
Which seems great - and is exactly the same solution that Ruby, Python, Perl and everyone is working on. Same game, different instrument.. What am I missing?
First to market is hard to overturn in the web world, so I think you'll be waiting for a long time for CL+.
Are you trolling? I use all those features and I know many people who use at least one or two of them, and like them.
Wow - yours is the first post that actually makes a good point. Mod parent up!
Moving JS out of the browser just means it loses all the competitive advantages is could possibly have. Moving it out of the browser means that it will suck for writing multi-OS client applications in the same way Ruby (or pick your scripted language) does.
I already notice the javascript cycle churn on my local workstation when browsing (ahem slashdot and gmail). Dumping more cycles on my client isn't a good idea unless someone finds a way to keep the utilization from lagging UI and other noticeable items..
Huh? This sounds like a bizarre argument of "don't make things too simple or people will get confused." Getting confused about whether something is running on the front-end or the back-end is a problem I think a lot of web programmers would like to have (including me). Using separate languages simply to indicate where the code is running doesn't sound like the right solution to the problem.
I can't tell if you're complaining or praising? In my experience this is a feature and is a real bonus for programmers.
I think you're referring JScript, which was Microsoft's look-alike to Javascript. It's been a while but I seem to recall that there were substantial differences in the languages, down in the weeds, which made porting some applications back and forth a pain.
I've been using it too. It has some great features. My experience is that it's a little buggy. For example, it doesn't always catch new folders that have been created, so I've found myself unable to remotely access a file b/c the new folder was not caught by the service (and so none of the files were backed up). Second complaint is that restorations are slow-ish sometimes (10 min for a 300k file). Sometimes the restorations are fast and I can't tell if it's the specific file (due to fragmentation in the cloud or something) is slow or if it's their server utilization. Finally I can't ever get the folder sync to work - it always errors out with a weird message.
Do you have any of these problems?
Overall I like the product but I think it has to mature.. Your input would be great!
I've been using spideroak, and I have one complaint which is restorations are sometimes fairly slow (10 minutes to pull down a 300k file). Sometimes it's fast-ish (30 sec) , so I guess it's where the file is in their cloud.
How is restoration time on Dropbox?
We ran across a classic one of these. A application we developed in 1992 stopped working in 1994 for some unknown reason. After a few days of heinous debugging to build a test case, we come across a line of code headed with this comment: /* this will not work - jr */
We fix that line so it will work, and all have a good laugh later. At the time it was pretty frustrating as I recall. I'm still good friends with JR by the way.
And while "he" is getting called at three in morning 2 years later to fix a crazy bug that has stopped all business, due to a new use-case being introduced that mysteriously breaks that function, "you" is now coding on a new project, using sound development techniques (including understanding how code works while "you" writes it), making the company new money.
Oh great. Another movie ending spoiled.
Yeah really - mod parent up. This is largely an issue of contract not copyright. The Apple EULA says "thou shalt not do X" Pystar did "X" and the court said that they had to stop it. Pystar raised some copyright issues but the big shut down is because the EULA is enforceable in court. Am I following along?
I think the judge ruled that Psystar violated the EULA contract. So I'm not sure the issue of copyright plays in this regard. There might have been rulings about Pystar's use of copyrighted materials also, but the big deal is that the EULA defines some things you can't do and the judge ruled that this shrinkwrap contract applied to Psytar.
IANAL, but I think if Apple has gone so far as to fund Psytar and stage this whole litigation, if it ever came out they could be liable on a number of fronts. Wasting the court's time might be one, but a lawyer in the right field could probably find some more serious offenses for such shenanigans.
Doesn't zsh work pretty much the same on Windows these day? Cygwin or other variants? I'm not arguing with your point, just looking for the significant differences between casual use of Unix command line on various OS's. I realize Mac is going to have deeper support for Unix make/build stuff than Windows, but I don't think that was your point? Just curious really..
SCO comes to mind, and CP's comment about "useful idiots" plays well in this context too.
Wouldn't a several km mag field require a lot of power? Much more than can be derived from the limited # of sq meters of solar panels available for a satellite?
Good point. Probably should be km/h?
Are you seriously arguing that it's possible to drive a #2 pencil through 100mm of armored steel? If so, please produce some evidence of this ever having been done. I'll be interested even if the pencil comes out the other end dulled.
Your second point about 36k km/s seems wrong to me b/c the relative velocity of the net and the objects will be much, much lower than this. Am I missing something?
Just wanted to point out that for the first time in the history of slashdot, you correctly spelled "losing" and "loose" in the same sentence. The content of your point is good too!