Your comment is so bizarre that I almost think you must have attached it to the wrong post.
I programmed in OCaml for many years.
Yes, there is no automatic type conversion in OCaml. I certainly never said there was. Some people see this as a feature (you know exactly what you're dealing with at all times), some as an issue (you have to write tedious conversions that some languages handle for you).
Yes, there are different arithmetic operators for different numeric types. It's a little bizarre when you're used to other languages, but once you get used to it it's not an issue.
Most of my code was compiled so I didn't experience issues with compiled vs interpreted.
It certainly had a few rough edges here and there, perhaps because the community was not as large as more mainstream languages. They probably would have been ironed out if the language had really taken off.
I haven't looked at it for a while, but it's basically Microsoft's version of OCaml which is an objected oriented ML variant, (and a very slick language with a long development history).
I'm not really seeing it catch on either, but OCaml's sweet spot was writing fast code that dealt with very complex data structures. It enforced static typing, but used type inference to figure out what the types of variables were. It has powerful operators for assembling and splitting up data structures that let you write very concise code that was checked at compile time for correctness.
It is somewhat similar in flavor to Haskell (although it's probably wrong to say they're going in Haskells direction.. more that they have common ancestors).
You understand that that number is flawed, right? He only figures in the average lives of products that Google has killed. It's kind of like looking at all the people who died of heart attacks, finding out they lived to an average of 48 years old, and then telling the general population that, on average, they're going to die of a heart attack when they're 48 years old.
But please, jump on the anti-google circle jerk. It seems to be the thing to do at the moment.
If you look at what he's saying, you'll see that the javascript only gets downloaded once for all the domains. For each domain you need an html page that just has a script link to the fixed js file (that your browser already has cached). So, think maybe 100 bytes per 5-10MB.
We've used it to develop a mission critical B-to-B site for a client, and it's been a pleasure. It's very well architected, and there are extensions out there for handling almost any need you might have (anything we've come up with, in any case).
I anticipate any future PHP work we do will use it.
Re:I am pleased to say...
on
Vim Turns 20
·
· Score: 1
emailed Bram on these issues and he was very responsive to my reports
When vim 6 was in testing I ran into a small problem with one of the release candidates. Something minor that probably only affected me and a small set of other users. I emailed bugs@vim.org, and in less than 24 hours I got a personal response from Bram who told me he had replicated it and thanked me for my example. It was fixed in the next candidate.
I would be pleased with that kind of responsiveness from a commercial software vender.
GUI? Dude, I can promise you that there was no GUI in Turbo Pascal back in 1986. Also, it was the most amazing development environment back then. A decent editor tied to a fast compiler that would run on computers with 4Mhz chips, 128k of memory, and a floppy drive. I wrote some cool *@#$ with turbo pascal back then.
That aside, I'm pretty sure nobody here is saying that they want to go back to coding in Turbo Pascal. It's more of a gee wiz fact.
"In the most common form of sweeping, funds in bank customers' retail checking accounts are shifted overnight into savings accounts exempt from reserve requirements and then returned to customers' checking accounts the next business day. "
Personally, I find the zero reserve banking system to be pretty worrisome. I can't help but think that much of the bank deregulation from that last 30 years has gotten us where we are now.
Yeah, that was my first thought. I'm pretty long in the tooth myself, but for the most part, if something has been forgotten, it's because it is no longer of use.
Sure things come back (the mobile app market is a good example), and this becomes a great opportunity for the older generation to pass on information to the younger. But I'm not going to miss the days where you had to figure out how to handle your data set when you couldn't use more than 64k of consecutive memory.
Slashdot Mirror
Your comment is so bizarre that I almost think you must have attached it to the wrong post.
I programmed in OCaml for many years.
Yes, there is no automatic type conversion in OCaml. I certainly never said there was. Some people see this as a feature (you know exactly what you're dealing with at all times), some as an issue (you have to write tedious conversions that some languages handle for you).
Yes, there are different arithmetic operators for different numeric types. It's a little bizarre when you're used to other languages, but once you get used to it it's not an issue.
Most of my code was compiled so I didn't experience issues with compiled vs interpreted.
It certainly had a few rough edges here and there, perhaps because the community was not as large as more mainstream languages. They probably would have been ironed out if the language had really taken off.
I haven't looked at it for a while, but it's basically Microsoft's version of OCaml which is an objected oriented ML variant, (and a very slick language with a long development history).
I'm not really seeing it catch on either, but OCaml's sweet spot was writing fast code that dealt with very complex data structures. It enforced static typing, but used type inference to figure out what the types of variables were. It has powerful operators for assembling and splitting up data structures that let you write very concise code that was checked at compile time for correctness.
It is somewhat similar in flavor to Haskell (although it's probably wrong to say they're going in Haskells direction.. more that they have common ancestors).
40% of their workforce? I guess the worst part of this is that there are still ~6,750 more jobs to lose...
Did you really just say they should release a non-touchscreen version of the iPod touch?
You understand that that number is flawed, right? He only figures in the average lives of products that Google has killed. It's kind of like looking at all the people who died of heart attacks, finding out they lived to an average of 48 years old, and then telling the general population that, on average, they're going to die of a heart attack when they're 48 years old.
But please, jump on the anti-google circle jerk. It seems to be the thing to do at the moment.
Actually I don't think headers on either side get compressed.. so I'm probably totally wrong on this.
Fair enough. But then you turn on gzip compression and it drops to 1/7th of that...
If you look at what he's saying, you'll see that the javascript only gets downloaded once for all the domains. For each domain you need an html page that just has a script link to the fixed js file (that your browser already has cached). So, think maybe 100 bytes per 5-10MB.
Linking to "Canada's Best Satirical Newspaper". Really sir, an article stating "Cucumbers Cause Genital Baldness" didn't trigger your skepticism?
It's been 14 years since I did any graphics programming, and I was thinking back, "Yeah, I remember this being an issue back then."
The world is unfair in so many ways. I suppose it's not surprising that people forget that we can strive to make it better.
Honestly, I went the other way on this one.
Samsung has just had their product ruled demonstrably inferior by a court of law. Not exactly a marketing message they want celebrate.
Unless you've invented a device to transmit people's thoughts and intentions, then their words are all we have to go by.
Yeah, I'm over 40, and my father was a software guy before me (still working for Adobe).
I came here to say this. Language matters.
You have color graphics? I'm still using my monochrome 80 column card...
Another vote for Yii.
We've used it to develop a mission critical B-to-B site for a client, and it's been a pleasure. It's very well architected, and there are extensions out there for handling almost any need you might have (anything we've come up with, in any case).
I anticipate any future PHP work we do will use it.
emailed Bram on these issues and he was very responsive to my reports
When vim 6 was in testing I ran into a small problem with one of the release candidates. Something minor that probably only affected me and a small set of other users. I emailed bugs@vim.org, and in less than 24 hours I got a personal response from Bram who told me he had replicated it and thanked me for my example. It was fixed in the next candidate.
I would be pleased with that kind of responsiveness from a commercial software vender.
GUI? Dude, I can promise you that there was no GUI in Turbo Pascal back in 1986. Also, it was the most amazing development environment back then. A decent editor tied to a fast compiler that would run on computers with 4Mhz chips, 128k of memory, and a floppy drive. I wrote some cool *@#$ with turbo pascal back then.
That aside, I'm pretty sure nobody here is saying that they want to go back to coding in Turbo Pascal. It's more of a gee wiz fact.
I was skeptical, but my skepticism was misplaced.
Here's a research article from the NY Fed back in 2002 about how banks even avoid the checking account reserve requirements by using "sweep accounts" overnight:
http://www.newyorkfed.org/research/epr/02v08n1/0205benn/0205benn.html
"In the most common form of sweeping, funds in bank customers' retail checking accounts are shifted overnight into savings accounts exempt from reserve requirements and then returned to customers' checking accounts the next business day. "
Personally, I find the zero reserve banking system to be pretty worrisome. I can't help but think that much of the bank deregulation from that last 30 years has gotten us where we are now.
The ray bounces!
The ray hits you!
You die...
Yeah, that was my first thought. I'm pretty long in the tooth myself, but for the most part, if something has been forgotten, it's because it is no longer of use.
Sure things come back (the mobile app market is a good example), and this becomes a great opportunity for the older generation to pass on information to the younger. But I'm not going to miss the days where you had to figure out how to handle your data set when you couldn't use more than 64k of consecutive memory.
You clearly didn't click on his link, where you would have been disabused of your notion.
I totally read your comment in the the voice of Cave Johnson, CEO of Aperture Science.
At the local PC bang playing starcraft/broodwar?