ingas
It was absolutely the same in Soviet Union.
I still remember formula from my childhood: 3 empty bottles (10 kopeks each) + 3 kopeks = 1 full bottle of lemonade (33 kopeks).
I think it was a good thing, less glass garbage at least.
> You usually return them at shops that sell them, even if you haven't bought them at this exact shop.
It seems that such things needs some central regulation, they did not survive in pure capitalism
More frequently as a joke but sometimes you start thinking: "what if?"
Looking on Latin America it's always ends with something violent.
On the other side: in Asia it's usually transforms into something not that bad, e.g. South Korea.
It served up to 70K of subscribers, call center with 30-40 employees, payment systems integration, everything.
Next was 8 socket Intel server. We were never able to saturate it's CPUs - 300 Mhz (or was it 400 ?) bus was a stopper. It served 350-400K of subscribers.
And next: we changed architecture and used 2 servers with 2 socket Intel CPUs again but that was time when Ghz frequencies appeared on market. We dreamed about 4xAMD server. We came to ~1 mln of active subscribers.
Nowadays: every phone has more power than it was those servers. Typical react application consumes more resources than billing system. Gigabyte here, gigabyte there - nobody counts them.
/grumpy oldster mode
Wernher von Braun considered this a problem. He (and his team) once was frustrated when instruments came in yards and pounds.
I can believe that maybe geographic mile will be used in future but all those local standards cleary not belongs to space future.
But "Sgt. Pepper" - I think the only motivation is to try squeeze a little bit more money from fans.
My hope is that sometime in future we will get a remix of Metallica "Justice for All" with bass on it.
But Hetfield already stated that they don't plan to do that:
> "And why would you change that? Why would you change history? Why would you all of a sudden put bass on it? There is bass on it, but why would you remix an album? You can remaster it, yes, but why would you remix something and make it different? It'd be like… I don't know. Not that I'm comparing us to the Mona Lisa, but it's, like, 'Uh, can we make her smile a little better?!' You know?! Why?"
That's quite sad but that's creator's decision.
OMG. What will be next? Apple vendored flash cards?
It's when I see articles about space exploration with miles and pounds - it feels wrong.
In Soviet Union considerable part was in cooperation. And more in Stalin era then later.
Citing Russian wikipedia:
> By the end of the 1950s, there were more than 114 thousand workshops and other industrial enterprises in its system, where 1.8 million people worked. They produced 5.9 % of the gross industrial output, for example, up to 40 % of all furniture, up to 70 % of all metal utensils, more than a third of upper knitwear, almost all children's toys. The system of commercial cooperation included 100 design bureaus, 22 experimental laboratories and two research institutes.
China is capitalism all the way now.
IDK about North Korea but they don't seems like a "communist country" for me.
> If we are going to be pedantic
The whole article was about going to be pedantic over dictionary definitions.
"Now, one major concern in academia is rigor. Academics like to get deep into a topic, examine the nuances, and bring clarity."
I suppose it's hard to argue against that words in "technical debt" were chosen poorly: it's not debt and it's not technical.
Maybe better definition is needed.
"Mathematician's Apology" by G.H.Hardy. IDK why exactly this book (essay?) influenced me. I'm not a mathematician but I certainly found something that touches me.
"ANSI Common Lisp" by Paul Graham. I did not became a lisper because of that but it helped me to came out of my cave. I considered myself an experienced programmer but that was something about "other" programming. I remember the feeling that I had a secret magical weapon in my hands.
"Programming Erlang" by Joe Armstrong. This book is not about Erlang mainly but about ideas and conceptions behind Erlang. Actor model, messaging, "let it fail", "happy path" - all that influenced me a lot.
"Data Warehouse Toolkit: The Definitive Guide to Dimensional Modelling" by Ralph Kimball and Margy Ross. The book about how to make data clean, inambigious and easy to understand.
I think that you idealizing ancient Rome.
Ice was a delicacy.
"Dishes for geographically distant ingredients"?
No meat, no fruits, no milk products.
So it's only cereals could be imported from long distances.
Differences must be same as differences between Thai/Vietnamese/Japanese sorts.
You just leave salted fish to ferment under sun and then collect liquid. Add other ingredients you like but they are not essential.
CORBA - I did not even finish reading "Introduction to CORBA". A book of 500+ pages.
Starting from some point (Pentium Pro I suppose?) even x86 CPUs became RISC internally CISC externally.
From the list: " psilocybin, psilocyn, dimethyltryptamine (DMT) , ibogaine, mescaline, lysergic acid diethylamide (LSD) , ketamine, and 3,4-methylenedioxymethamphetamine (MDMA)" - I think only MDMA is abusable.
I conclude that it will be incompatible with hasura Allow-list (or lead to explosion of Allow-list for all possible combinations which is impossible in practice)
So it could look nice but makes unusable in case you rely on Allow-list for security.
It could be good for prototyping.
"Machine learning" here is crucial I suppose. Sklearn, keras are big beasts.
Would you install something like django/flask site than I don't think you would had any problems.
GraphQL is not that different from REST.
We are using hasura (which is written in Haskel), I'm interested in dgraph.io (which is golang).
I had terrible experience writing graphql-service in typescript. I finished it but I did not liked it's strange behaviour and bloated docker image size. I rewrote it in 2 days with graphql-go/go and then it became OK: predictable behaviour and ~16Mb docker image. I'm thinking about rewriting another service too.
On client side I used: - python client `gql` - .NET `graphql-dotnet` - Apollo client - graphqurl - js client from hasura team
The worst impressions are from Apollo. Starting from their documentation. IDK why they explain everything starting from UI.
I wrote comment to him:
It's only natural that you're trying to find solutions for problems you encountered in past.
But exploring new technology this way leads to absolutely natural mistakes. You're are worring about wrong things.
Dependency management This problem is not (and never was) in such terrible scale as in javascript.
You can forget about this problem while you learn go. I suppose that dep will be released offically when you will really need this.
Asynchronicity I did the same mistake as you: I thought that channels and messages are similar to Actor pattern in Erlang, Akka.
Don't try to think about promises, futures and other abstraction when you programming in go.
In fact, you need learn synchronicity now, golang already asynchronous in its nature.
That's a point from ... long past.
Dollar, yen, euro, bitcoin(!) have no direct relation to resources.
So, I agree with your opponent that economic growth is not limited in principle.
Gyrojet rifle was the ultimate weapon in Jagged Alliance 2 (my favorite game in college times).
I always thought that it was pure sci-fi element in game until somebody on forum posted information about this guns.
I think you're overestimating weirdness of 日本語. For native Russian speaker, Japanese is slightly weirder than English. The only rule: be prepared that every rule could be broken.
WCF and EF - "oh noes". My eyes are bleeding with just one look at this.
Microsoft can make something simple and brilliant as TPL, but on other side we have such overengineered behemots as WCF and EF.
WCF, WindowsForms, EntityFramework are proprietary. But nobody in sane mind will use them.