Comment You just opened a blackhole (Score 4, Funny) 77
Things posted to the internet aren't always true...
Since you posted this on internet, maybe it's not true, which would mean that it's true, which would mean that it's not! *tilt*
Things posted to the internet aren't always true...
Since you posted this on internet, maybe it's not true, which would mean that it's true, which would mean that it's not! *tilt*
you are a lying troll
Of course. Anyone who disagree with your flawed logic is a troll. I'm not sure where the "lying" part came from, but the important thing is that you can walk away from this discussion wrapped in the comfortable fabric of self-righteousness, so if that can help, feel free to call me a liar, a nazi, a racist or anything else.
At the end of the day you are just another dinosaur trying to pretend that everything has been invented decades ago and as such there is no need to make an effort to understand "new" things. Now why don't you go grab something to drink in the icebox and watch a show on that disguised radio they call a tv.
The other day I found out that it's impossible to use yum on a Red Hat machine with an expired RHN subscription. It proved quite unpleasant to work my way around it, as wget was not installed.
Of course you should have a valid subscription, otherwise you won't get security updates. It happens every now and then that I run into people that run five year old RHEL installations which they have never updated because they either are too cheap to pay for it or have never heard about CentOS.
The point is not about how someone should use or not use RHN subscriptions, or whether they should have gone with CentOS if they didn't plan to renew a subscription. Your advice on those topics is not needed here and is probably not needed anywhere you typically provide it.
The issue is that when you install Red Hat, yum becomes dependent on the repos that are behind Red Hat's paywall. Of course you can reconfigure yum - provided that you have an easy way to do it (try without wget or make or even unzip).
systemd is something that could make the same lock-in approach work on daemons and who knows what else.
It's people using "cloud" for just about anything that creates confusion. That cloud gaming you describe is closer to "gaming as a service" rather than it is to cloud computing.
A SaaS offering, like your gaming example, may or may not be based on cloud computing; but that distinction is not something the end user can see.
Cloud computing is pay-per-use and elastic, just like electricity. Cloud gaming is neither - you pay for a service, it's SaaS; maybe you can have in-game purchase, but from a resource perspective you don't pay more or less based on what you do, and you can't get things like burstable performance.
Time-sharing on a mainframe can be pay-per-use, it depends on the service provider, but it's not elastic, you can't get more resources on demand. And from an architecture perspective, it's not cloud computing because it's not distributed and resource allocation is not automated.
When you say that dumb terminals and mainframe computers in the 50s were cloud computing, not only are you wrong, you are also insulting the incredible work that took place at Amazon and other companies to make computing a convenient commodity. Next time you sit in your sofa to watch a movie on Netflix remember that this type of service at that price would have never been possible with a mainframe architecture. Your Netflix subscription is SaaS - but Netflix's infrastructure is running on Amazon EC2 and that's pure cloud computing.
Cadence software
I don't understand why some people choose a career path that exposes them to such things. It's like that guy I know who is a Tivoli Backup expert. Or that other guy who spends his days working on Oracle Forms.
Life is too short for that!
The other day I found out that it's impossible to use yum on a Red Hat machine with an expired RHN subscription. It proved quite unpleasant to work my way around it, as wget was not installed.
Pretty soon we'll need a valid subscription to start daemons, something made possible by "improvements" like systemd.
This subscription model is becoming quite the rage (Microsoft, Adobe, Red Hat, etc) and this is leading real fast to absurd situations like in the novel from Philip K. Dick (Ubik) where the guy has to pay a few dimes each time he wants to use the door of his apartment.
I have 20+ year old network diagrams with a "cloud" that represents the server farm in a client-server environment. "The cloud" has been around ever since Visio shipped with a cloud graphic
You are rewriting history. The cloud symbol was not used back then to represent servers, it was used to represent a network location (usually internet).
I won't spend forever trying to prove an obvious point but see this example:
In every discussion about cloud computing there's always the same technology adoption laggard that has to come up with the same tired "it's client-server it has existed for 50 years" argument. It's exhausting.
Eventually, we'll probably have massive swarms of small, cheap, robotic drones that can swarm the oceans and search for them with active methods (not caring if they get detected themselves). That will probably signal the end of practical, stealthy submarines.
Until someone removes the salt from the ocean it will be difficult to remote-control submarine drones. Training dolphins or creating a new breed of soldiers that can breath, eat and drink underwater is probably less ambitious.
"cloud computing" is a new buzzword for an old concept
I'm guessing that you refer to dumb terminals and mainframes, but it's not the same concept at all - it's actually almost the opposite. In a cloud scenario, quite often the client has more computing power than the average server used by the cloud provider. It's the sheer number of commodity servers and the high level of automation that makes the cloud what it is.
I'm sure he learned his lesson.
Damn thing sat there, then autoplayed right over a KMFDM song I had playing... took me nearly a minute before I realized the voiceover wasn't part of the song...
The exact opposite happens to me all the time with my Kitaro playlist (there's also an Air Sculpture song in there to mix things up).
Did you read the report before talking about short-sighted comments?
It's buying 2+ tickets that aren't worth the money,
Unless you buy 2 tickets with the same numbers. Which could make sense because if someone else has the same numbers you will get 2/3 instead of 1/2. Even better: buy 99 tickets with the same numbers. Just the face of that other dude who ends up winning 1% of the jackpot would be well worth the $198 investment.
Real Programmers don't eat quiche. They eat Twinkies and Szechwan food.
