Depends on the coin. It's not all that crazy to think a mobile platform as an alternative to ads could pull in enough revenue from mining and selling alt coins to be a viable product.
Sure, but that systems level code can be written in whatever language you want, like C. Systems code needs an ABI, but it's rare to need anything like that in higher level langs like Swift. It's just not a priority for most languages because there usually higher level mechanisms built in to accomplish the same thing for 99% of the real world cases.
But if you have the source code, portability is as easy as recompling. You don't need an ABI for that. The other benefits of an ABI you mentioned are not compelling enough for many language developers. Swift needs it because it operates in a closed source world with Objective-C. It's common to need to interact with systems level code in C, but it's rare to have to interact that deeply with - say - a web server written in Python. So unless you are developing a systems language, an ABI is not high on the priority scale. Most likely the language already has various mechanisms to accomplish the same thing within the stack, and interop with other languages is usually already well supported by web services or IPC or some such thing.
Unless I'm missing something, it doesn't matter how random the PRNG is if the selection isn't influenced by the other relevant data. Everyone got their random number generated by the same shitty PRNG, so it's a fair and equitable system.
Amazon does not maintain inventory for these products. They don't have the infrastructure in place to take in a returned couch that was never manufactured, stored, or shipped by them in the first place.
ABIs are largely irrelevant with open source, so languages without large communities of developers working inside walled gardens don't prioritize that.
I did not mention complexity or central planning. You can simplify this to independent agents modelled with only a few rules and you come to to the same outcome. Any agent that acts as a communication go-between has more power over society than those that don't, because they are in control of what people know and what they believe.
All civilizations are hierarchical because it is necessary to organize people who do not know one another. Even in some fantasy scenario where everyone is equal, but some act as liaisons to organize society, those liaisons are de facto heads of state.
I blame the shitty/. UI. You go to reply and when you get to the reply screen you can no longer see the original comment, nor can you use the back button (which takes you to the top of page). It's exceedingly frustrating, and I know at times I end up making assumptions about what I thought I read by the time I'm done writing and proofreading my response.
A typical one. I never sign for my packages nor do I see the delivery driver. The fulfillment process has completed before I ever set eyes on my package.
If that daemon is is - say - a PHP server with access to your data, then the fact that the problem is "isolated" to the PHP instance is not very helpful.
Docker - as it is usually recommended for setup - is not a good fit for production for this reason. It'r possible to make Docker secure, but it's so much work it's usually easier to just not use Docker in production.
If you're doing validation to help the user, that might be fine. But if you're validating for correctness or assuming data has followed all your validation rules, then client-side validation is worthless.
I'm not in the industry and know nothing, but my guess is it's because it's simpler logistically during manufacturing to have an all-in-one that is provided by a single vendor.
Slashdot Mirror
God of the Gaps is God of Ignorance.
It totally does though. It might not be intentional, but laws are written by lawyers, not technologists.
Depends on the coin. It's not all that crazy to think a mobile platform as an alternative to ads could pull in enough revenue from mining and selling alt coins to be a viable product.
I for one am shocked that gene editing can lead to a disease caused by altered genes.
Sure, but that systems level code can be written in whatever language you want, like C. Systems code needs an ABI, but it's rare to need anything like that in higher level langs like Swift. It's just not a priority for most languages because there usually higher level mechanisms built in to accomplish the same thing for 99% of the real world cases.
But if you have the source code, portability is as easy as recompling. You don't need an ABI for that. The other benefits of an ABI you mentioned are not compelling enough for many language developers. Swift needs it because it operates in a closed source world with Objective-C. It's common to need to interact with systems level code in C, but it's rare to have to interact that deeply with - say - a web server written in Python. So unless you are developing a systems language, an ABI is not high on the priority scale. Most likely the language already has various mechanisms to accomplish the same thing within the stack, and interop with other languages is usually already well supported by web services or IPC or some such thing.
Unless I'm missing something, it doesn't matter how random the PRNG is if the selection isn't influenced by the other relevant data. Everyone got their random number generated by the same shitty PRNG, so it's a fair and equitable system.
Amazon does not maintain inventory for these products. They don't have the infrastructure in place to take in a returned couch that was never manufactured, stored, or shipped by them in the first place.
ABIs are largely irrelevant with open source, so languages without large communities of developers working inside walled gardens don't prioritize that.
Managing the money in and money out is like the most basic API call for a cryptocurrency. What kinds of APIs would even be useful without those?
Being your own bank is a bit like being your own armed defense. It's fine if you take the time to understand the role and get proper training.
Not the default. It wasn't a failure to configure proper security, it was a decision people made to intentionally turn off default security.
You mean writing apps on the blockchain doesn't make them magically secure? I am shocked!
I did not mention complexity or central planning. You can simplify this to independent agents modelled with only a few rules and you come to to the same outcome. Any agent that acts as a communication go-between has more power over society than those that don't, because they are in control of what people know and what they believe.
Cue no-true-leftist fallacy in 3... 2... 1...
All civilizations are hierarchical because it is necessary to organize people who do not know one another. Even in some fantasy scenario where everyone is equal, but some act as liaisons to organize society, those liaisons are de facto heads of state.
But how much of that revenue will be made up for in sales of the "Donald Glover as Lando Calrissian" action figure?
I blame the shitty /. UI. You go to reply and when you get to the reply screen you can no longer see the original comment, nor can you use the back button (which takes you to the top of page). It's exceedingly frustrating, and I know at times I end up making assumptions about what I thought I read by the time I'm done writing and proofreading my response.
Unfortunately, that will likely never happen. Centralized services are fundamentally more user friendly than distributed ones.
A typical one. I never sign for my packages nor do I see the delivery driver. The fulfillment process has completed before I ever set eyes on my package.
If that daemon is is - say - a PHP server with access to your data, then the fact that the problem is "isolated" to the PHP instance is not very helpful.
Docker - as it is usually recommended for setup - is not a good fit for production for this reason. It'r possible to make Docker secure, but it's so much work it's usually easier to just not use Docker in production.
Customers are not involved in fulfillment.
If you're doing validation to help the user, that might be fine. But if you're validating for correctness or assuming data has followed all your validation rules, then client-side validation is worthless.
One man's price gouge is another man's price discovery.
I'm not in the industry and know nothing, but my guess is it's because it's simpler logistically during manufacturing to have an all-in-one that is provided by a single vendor.