OS/X is OS/X. The Audio API, to use your example, is the best there is and in widespread commercial use. There is a reason they did their own Audio API. The one In Linux and BSD sucks. Completely.
As for Graphics, OS/X was always based on a PostScript/PDF rendering pipeline for reasons that it widely used in Desktop Publishing. OS/X is OS/X, not BSD. It works very well for the tasks it was designed for. FreeBSD works well for the tasks it was designed for. There is quite a bit of overlap, sure, but they are not the same
>..the transport agency then emailed the entire database in messages to marketers that subscribe to it.
This sentence makes no sense. What did the marketers subscribe to? The top secret database??!! This must have been quite a large database, I doubt that you can attach and mail it. Who mailed what to whom?
The whole article reads like something Google translate did on a day when the server was drunk or half asleep.
Yes but if you do use the syn version of readFile all the Nodies freak out. And there are NO syn version of thing like accessing mongodb, which, incidentally I needed today (for initializing my program with settings, in case you ask).
Javascript's continuation passing style is total crap. The problem is that is pretty hard to modularize programs because you can't fit pieces of program together properly. It was a really, really bad design decision. And don't get my started on promises. No, they are not the answer to all the world's problems, at least not at the scale they are used in Node to fix all the problem with continuation callbacks.
The laser would typically be used to target incoming anti shipping missiles or ICBMs in boost phase. If you think a hypersonic missile or an ICBM is going to shoogle like a mad bastard in a few Milliseconds I have a bridge to sell you. Cheap.
Are you kidding? Ok, serious question: is PL/I still being used somewhere? I remember the thing from back in the late 80s but never bothered to learn it. I met the wife of a colleague in 95 and she claimed to be working it, which surprised me a bit, even then.
That is something all of the Apple haters tend to forget. Apple is a hardware company. The make money from slick expensive hardware, not from user data. Their software is very cheap for what it does, actually, unlike Microsoft.
They do NOT sell user data like Google or Facebook because it is not part of their business model. Which is the main reason I use my iPhone even though I like my Windows Phone more.
Strangely, this puts Apple at a disadvantage in the big neurocomputing AI thing that seems to be coming on like a Tsunami: Google has a hell of a lot more data to trains their networks since they have all the data about searches , scans peoples emails and are not ashamed about it.
If AI is the future Apple better start watching their backs.
No, he's right. I have an Android, a iPhone and a WinPhone lying around. I like the WinPhone, and am looking around for a cheap Lumia. It is really a nice phone.
> That's not a problem anymore since javascript promises.
You must be kidding me. Have you actually ever used promises?
The problem with promises is that a very deeply fundamental construct is broken in Javascript. The ides of "First do X and then do Y. Eveyr other programming language (except Haskell) does this by writing the X and then Y on another line next to it, or separated with a semicolon.
This makes good sense since you can, well, read the code from top to bottom just like a real book. Callbacks totally breaks this fundamental thing, and now promises is supposed to fix it. Problems aplenty:
a) Promises need to wrap the "things that comes after X". This is pretty bizarre, and adds a hell of a lot of overhead just so the computer can go on with its task. Both CPU and mental on the programmer side b) There are multiple promise implementations, many libraries, that you might want to use, do NOT use promises (the node filesystem lib for one!) which means some of your code wirkt with them and some do not. I know ES6 is supposed to rectify this but it is still half baked and browsers do not run it necessitating a whole build chain to get Javascript to properly do things one after the other with a sane syntax.
If JS really, really wants to use callbacks to sequence things it should be a syntactical construct with no more complexity than a semicolon, like in any other language. It is too basic a thing to be left to multiple independent half-compatible complex libraries.
Does implementing your own invented functional language in 10K+ of Prolog count? Even when it was in 1989 and the language is a pre-Haskell lazy pure language?
Call me a simple farmboy if you like but I prefer the real things ng, not a string of promises. Miss node always promises me a lot, but Ruby? She gives me the goods straight away!
"Illegal Alien Hunter" is probably no going to go down well on that card.
This. And in order to render HTML one library happens to be an entire browser. This is the case for Electron apps
I am still sad that I can't get a 160 wide Hercules Graphics Card that can drive my 24 Inch monitor in monochrome :(
OS/X is OS/X. The Audio API, to use your example, is the best there is and in widespread commercial use. There is a reason they did their own Audio API. The one In Linux and BSD sucks. Completely.
As for Graphics, OS/X was always based on a PostScript/PDF rendering pipeline for reasons that it widely used in Desktop Publishing. OS/X is OS/X, not BSD. It works very well for the tasks it was designed for. FreeBSD works well for the tasks it was designed for. There is quite a bit of overlap, sure, but they are not the same
Since when is ThreadRipper on the market? Where did you buy one?
> ..the transport agency then emailed the entire database in messages to marketers that subscribe to it.
This sentence makes no sense. What did the marketers subscribe to? The top secret database??!! This must have been quite a large database, I doubt that you can attach and mail it. Who mailed what to whom?
The whole article reads like something Google translate did on a day when the server was drunk or half asleep.
Since when is docker written in Python? It is written in Go as far as I know.
Ansible is written in Python.
That is true. I work for a niche industry. We sell one device every two years.
Yes but if you do use the syn version of readFile all the Nodies freak out. And there are NO syn version of thing like accessing mongodb, which, incidentally I needed today (for initializing my program with settings, in case you ask).
Javascript's continuation passing style is total crap. The problem is that is pretty hard to modularize programs because you can't fit pieces of program together properly. It was a really, really bad design decision. And don't get my started on promises. No, they are not the answer to all the world's problems, at least not at the scale they are used in Node to fix all the problem with continuation callbacks.
With a tube iPhine XLR sockets is probably better
The laser would typically be used to target incoming anti shipping missiles or ICBMs in boost phase. If you think a hypersonic missile or an ICBM is going to shoogle like a mad bastard in a few Milliseconds I have a bridge to sell you. Cheap.
> disclosure: I personally always liked PL/I
Are you kidding?
Ok, serious question: is PL/I still being used somewhere?
I remember the thing from back in the late 80s but never bothered to learn it. I met the wife of a colleague in 95 and she claimed to be working it, which surprised me a bit, even then.
Maybe you have weird kids but playing with my children beats the hell out of the nagging b1tch3s at work!
I will take a shorter commute BECAUSE i have kids any day
Who, me?
Agreed, although the Bluetooth sucks
That is something all of the Apple haters tend to forget. Apple is a hardware company. The make money from slick expensive hardware, not from user data.
Their software is very cheap for what it does, actually, unlike Microsoft.
They do NOT sell user data like Google or Facebook because it is not part of their business model. Which is the main reason I use my iPhone even though I like my Windows Phone more.
Strangely, this puts Apple at a disadvantage in the big neurocomputing AI thing that seems to be coming on like a Tsunami: Google has a hell of a lot more data to trains their networks since they have all the data about searches , scans peoples emails and are not ashamed about it.
If AI is the future Apple better start watching their backs.
No, he's right. I have an Android, a iPhone and a WinPhone lying around. I like the WinPhone, and am looking around for a cheap Lumia. It is really a nice phone.
So that would be another 200 bucks then
Top and Bottom honey
So that guy in the desert who got another message 600 years or so later, he is just talking crap then?
> That's not a problem anymore since javascript promises.
You must be kidding me. Have you actually ever used promises?
The problem with promises is that a very deeply fundamental construct is broken in Javascript. The ides of "First do X and then do Y. Eveyr other programming language (except Haskell) does this by writing the X and then Y on another line next to it, or separated with a semicolon.
This makes good sense since you can, well, read the code from top to bottom just like a real book. Callbacks totally breaks this fundamental thing, and now promises is supposed to fix it. Problems aplenty:
a) Promises need to wrap the "things that comes after X". This is pretty bizarre, and adds a hell of a lot of overhead just so the computer can go on with its task. Both CPU and mental on the programmer side
b) There are multiple promise implementations, many libraries, that you might want to use, do NOT use promises (the node filesystem lib for one!) which means some of your code wirkt with them and some do not. I know ES6 is supposed to rectify this but it is still half baked and browsers do not run it necessitating a whole build chain to get Javascript to properly do things one after the other with a sane syntax.
If JS really, really wants to use callbacks to sequence things it should be a syntactical construct with no more complexity than a semicolon, like in any other language. It is too basic a thing to be left to multiple independent half-compatible complex libraries.
Does implementing your own invented functional language in 10K+ of Prolog count? Even when it was in 1989 and the language is a pre-Haskell lazy pure language?
Bingo.
Call me a simple farmboy if you like but I prefer the real things ng, not a string of promises. Miss node always promises me a lot, but Ruby? She gives me the goods straight away!
RoRs main attraction is not the Web layer. It is ActiveRecord, the dblayer.
Maybe so but we still have all the money and that compensates for therest.