Without it, devs just throw the responsibly to operate over the wall and divorces them from the consequence of poor design.
I have no clue where you have been working (and hope never to work there), but in all the places I have worked, dev is *NEVER* divorced from the consequences. If there is a problem that isn't obviously hardware (failing disk, machine rebooting from kernel panics, router failing,...), dev, almost always in conjunction with ops works on the problem. Sometimes the problem will still be hardware (a failing drive in one system manifested as a DB slowdown in a different system), sometimes it will be in the app.
In the rare cases where enterprise services are paid for with a credit card, any and all verification for the $10k+/mo in charges is done when the contract is signed in person.
I can't speak to Google's requirements, but we signed up with AWS, and paid with a Corporate Credit Card (I think we were around $6K/month) quite happily, and only changed when we got bought, and the new overlords had their own AWS account we are now a part of. We never had to go to any Amazon site to sign anything.
Which is great for the private school. but that just means the problem children end up at the public school. If the private school can cherry pick the students, they can probably provide them with a better education, but that doesn't remove the need for ALL students to be educated, problem or otherwise.
there was a regional grocery store chain where I used to live whose prices were consistently about 40% off of all major competing grocery stores in the area.
I call bullshit. Grocery stores run at about a 1 to 3 percent profit margin. Some individual items might be priced wildly differently, and a discontinued store (one getting rid of merchandise other stores can't sell) might be able to do a larger discount, but 40% off of standard goods just ain't gonna happen.
It wasn't until some time later that the relational database was developed, with the idea that the database server would figure out the relations between data, rather than forcing the application to do that work.
That "some time later" was about 50 years ago. I think we can safely declare this "mature" technology that everyone can safely use...
And before you ask - we're running the 6th busiest Oracle database in Europe - according to Oracle themselves - running across 4*128 SSD drive arrays at a cost of millions.. and for the 3 or 4 features we need to justify the licenses instead or designing our way out of the same problem, at times I really wonder about the hassle, especially when our data is so important and locked up into such a bloated closed up mess.
You might think such things as a fun fantasy, but you would be insane to actually do it. When it (say) turns out your home grown solution corrupts records spanning odd page boundaries, you will be quite sad as you and the one other guy who has a clue how your "clever hack" functions gets to work 24hour days trying to debug the problem, determine the extent of the damage, and try and figure out a solution. It is times like that when having thousands of consultants, and a major corporation with teams of dedicated programmers ready to jump on your problem (for a price, certainly for a price) is the only sane option. If you are really as big as you say, your data is WAY to valuable.
I may not be fond of Oracle either as a corporation or as a product, but there are reasons it rules in the enterprise DB niche.
Why was C so lame? Because it had to run on PDP-11 machines, which were weaker than PCs. On a PC, at least you had 640Kb. On a PDP-11, you had 64Kb of data space and (on the later PDP-11 models) 64Kb of code space, for each program.
Your relative comparisons are a bit off. The Altair from 1975 (the first versions of C were finished around 1973) had a whopping 1KB of memory. The mini computers of the day ran rings around what PCs there were, both in raw power and in memory.
I subscribe to the journal Science. While I admit the actual research articles might as well be written in Linear B, the news articles, and the in-depth sections in front are written assuming the reader is intelligent and educated, but just not an expert in the particular field. It is such a joy to read articles that aren't aimed at the lowest common denominator!
I'm sure Nature, or other similar quality journals, would work as well (I choose Science, mostly because I found a subscription card for them).
We used to have variants of Pascal suitable for systems programming.
No. You might have used Pascal for systems programming, it was never suitable for it. C ate Pascal's lunch for really good reasons, and it has since drifted off into the irrelevancy it deserves. Google Kernighan's "Why Pascal is Not My Favorite Programming Language" as a start, the rest I leave as an exercise for the reader.
(I always thought profs were secretly bastards at heart.)
Nope, profs are people too, and just as likely to get caught up in the heat of the moment as anyone else. They might know more than you ever will about Shakespeare, or fluid dynamics, that doesn't make them infallible.
Come to think of it where does it say that he's allowed to live in that house? The mortgage/rental agreement is in your name, not his.
The rental agreements that I use have a section that describes the rights of minors to live in the space (and they are listed by name). If they are not minors, they are required to sign the lease (you are not allowed to have guest for longer than 2 weeks without permission, no matter their relationship to you).
Based on your UID number, you probably remember... but the keyboards at the time Rogue (and vi) came out didn't _have_ cursor keys.
You can't tell by my UID, but I was actually AT Berkeley when Rogue and vi came out. The ADM-3A terminal (which was by far the most common terminal there, and lots of other places) had a left arrow on the H, a down arrow on the J, a up arrow on the K and a right arrow on the L. Not cursor keys per-se, but a dang strong hint.
Re:BCC still existed?
on
The Death of BCC
·
· Score: 2, Interesting
BCC doesnt show other recipients
Not all mail systems handle BCC this way. The X.400 system (at least used to) take the odd approach of hiding the BCC recipients from the main recipients, but all the BCC recipients could see each other. Other mailers may do equally odd things (or have non-standard settings).
Re:Why only one database language?
on
SQL in a Nutshell
·
· Score: 5, Informative
It's mainly because SQL was the first (only? someone correct me) language to implement Codd's relational model, via the tuple calculus.
Hardly. Quel predates SQL, and was superior in almost every way. However, SQL had IBM behind it, and Quel just had UC Berkeley (guess who won that battle).
There's overwhelming evidence that early Greek epics were re-told using an enormous set of conventions
While I believe you, can you tell us what this overwhelming evidence is? I'm actually curious where we get evidence of social and commercial interaction that doesn't leave a physical by-product from 3,000 years ago.
Have we found instruction books? Fragments of private notes? Historians describing how storytellers attracted customers in their towns? Other things? How do we weigh what the evidence seems to say (say a book of instructions for young storytellers) versus reality (the books might have been ignored)?
Thanks,
Gators/Crocs are famous for having not changed much since the time of the dinosaurs.
Well, they haven't changed much on the outside. For all we know, they went from cold-blooded to warm-blooded then back to cold-blooded, with an odd couple of million years using kerosene for blood. None of that would show up in the fossil record.
vi(m) may use less memory, but that just doesn't matter anymore. If you want to customize it (non-trivially), you have to hack vim and recompile. So while emacs jokes are hilarious, it dates you to the early 80s. There is no reason to write tiny apps in assembly anymore. Big apps that can be extended are a much better approach.
Give it up, this is a religious war. Those of us who prefer vi(m) consider it a more focused editor. We neither need, nor want the extensibility crave. Those of you who prefer emacs consider the extensibility vital to your work, and can't imagine how anyone can live without it.
We have been debating this forever, and will continue to do so, as long as there are vi(m) and emacs users out there. There is no "right" answer, so just enjoy the jokes (they are normally harmless, and often good for at least a smile).
Without it, devs just throw the responsibly to operate over the wall and divorces them from the consequence of poor design.
I have no clue where you have been working (and hope never to work there), but in all the places I have worked, dev is *NEVER* divorced from the consequences. If there is a problem that isn't obviously hardware (failing disk, machine rebooting from kernel panics, router failing, ...), dev, almost always in conjunction with ops works on the problem. Sometimes the problem will still be hardware (a failing drive in one system manifested as a DB slowdown in a different system), sometimes it will be in the app.
In the rare cases where enterprise services are paid for with a credit card, any and all verification for the $10k+/mo in charges is done when the contract is signed in person.
I can't speak to Google's requirements, but we signed up with AWS, and paid with a Corporate Credit Card (I think we were around $6K/month) quite happily, and only changed when we got bought, and the new overlords had their own AWS account we are now a part of. We never had to go to any Amazon site to sign anything.
It has always been a crows sourced link repository.
Crow sourced. That does actually explain a lot...
problem children are expelled
Which is great for the private school. but that just means the problem children end up at the public school. If the private school can cherry pick the students, they can probably provide them with a better education, but that doesn't remove the need for ALL students to be educated, problem or otherwise.
Baseball is a nineteenth-century pastoral game. Football is a twentieth-century technological struggle.
Nice to see I'm not the only one who likes George Carlin!
Me, I keep having trouble with that damn Voight-Kampff test...
there was a regional grocery store chain where I used to live whose prices were consistently about 40% off of all major competing grocery stores in the area.
I call bullshit. Grocery stores run at about a 1 to 3 percent profit margin. Some individual items might be priced wildly differently, and a discontinued store (one getting rid of merchandise other stores can't sell) might be able to do a larger discount, but 40% off of standard goods just ain't gonna happen.
Oddly missing from the summary, the name of the infected App: "Instaquotes Quotes Cards for Instagram"
It wasn't until some time later that the relational database was developed, with the idea that the database server would figure out the relations between data, rather than forcing the application to do that work.
That "some time later" was about 50 years ago. I think we can safely declare this "mature" technology that everyone can safely use...
Could you expand on the Pascal limitations things?
Allow me to just link to a demi-god:
Why Pascal is Not My Favorite Programming Language by Brian W. Kernighan,
http://www.lysator.liu.se/c/bwk-on-pascal.html
Frack, funniest thing in MONTHS on slashdot, and I don't have any moderator points :(
And before you ask - we're running the 6th busiest Oracle database in Europe - according to Oracle themselves - running across 4*128 SSD drive arrays at a cost of millions.. and for the 3 or 4 features we need to justify the licenses instead or designing our way out of the same problem, at times I really wonder about the hassle, especially when our data is so important and locked up into such a bloated closed up mess.
You might think such things as a fun fantasy, but you would be insane to actually do it. When it (say) turns out your home grown solution corrupts records spanning odd page boundaries, you will be quite sad as you and the one other guy who has a clue how your "clever hack" functions gets to work 24hour days trying to debug the problem, determine the extent of the damage, and try and figure out a solution. It is times like that when having thousands of consultants, and a major corporation with teams of dedicated programmers ready to jump on your problem (for a price, certainly for a price) is the only sane option. If you are really as big as you say, your data is WAY to valuable.
I may not be fond of Oracle either as a corporation or as a product, but there are reasons it rules in the enterprise DB niche.
Why was C so lame? Because it had to run on PDP-11 machines, which were weaker than PCs. On a PC, at least you had 640Kb. On a PDP-11, you had 64Kb of data space and (on the later PDP-11 models) 64Kb of code space, for each program.
Your relative comparisons are a bit off. The Altair from 1975 (the first versions of C were finished around 1973) had a whopping 1KB of memory. The mini computers of the day ran rings around what PCs there were, both in raw power and in memory.
I'm sure Nature, or other similar quality journals, would work as well (I choose Science, mostly because I found a subscription card for them).
We used to have variants of Pascal suitable for systems programming.
No. You might have used Pascal for systems programming, it was never suitable for it. C ate Pascal's lunch for really good reasons, and it has since drifted off into the irrelevancy it deserves. Google Kernighan's "Why Pascal is Not My Favorite Programming Language" as a start, the rest I leave as an exercise for the reader.
I'm not sure what 80s system it's supposed to be emulating. .
Seems kinda TOPS/10 to me.
(I always thought profs were secretly bastards at heart.)
Nope, profs are people too, and just as likely to get caught up in the heat of the moment as anyone else. They might know more than you ever will about Shakespeare, or fluid dynamics, that doesn't make them infallible.
Come to think of it where does it say that he's allowed to live in that house? The mortgage/rental agreement is in your name, not his.
The rental agreements that I use have a section that describes the rights of minors to live in the space (and they are listed by name). If they are not minors, they are required to sign the lease (you are not allowed to have guest for longer than 2 weeks without permission, no matter their relationship to you).
Based on your UID number, you probably remember... but the keyboards at the time Rogue (and vi) came out didn't _have_ cursor keys.
You can't tell by my UID, but I was actually AT Berkeley when Rogue and vi came out. The ADM-3A terminal (which was by far the most common terminal there, and lots of other places) had a left arrow on the H, a down arrow on the J, a up arrow on the K and a right arrow on the L. Not cursor keys per-se, but a dang strong hint.
BCC doesnt show other recipients
Not all mail systems handle BCC this way. The X.400 system (at least used to) take the odd approach of hiding the BCC recipients from the main recipients, but all the BCC recipients could see each other. Other mailers may do equally odd things (or have non-standard settings).
Hardly. Quel predates SQL, and was superior in almost every way. However, SQL had IBM behind it, and Quel just had UC Berkeley (guess who won that battle).
While I believe you, can you tell us what this overwhelming evidence is? I'm actually curious where we get evidence of social and commercial interaction that doesn't leave a physical by-product from 3,000 years ago.
Have we found instruction books? Fragments of private notes? Historians describing how storytellers attracted customers in their towns? Other things? How do we weigh what the evidence seems to say (say a book of instructions for young storytellers) versus reality (the books might have been ignored)? Thanks,
Well, they haven't changed much on the outside. For all we know, they went from cold-blooded to warm-blooded then back to cold-blooded, with an odd couple of million years using kerosene for blood. None of that would show up in the fossil record.
Give it up, this is a religious war. Those of us who prefer vi(m) consider it a more focused editor. We neither need, nor want the extensibility crave. Those of you who prefer emacs consider the extensibility vital to your work, and can't imagine how anyone can live without it.
We have been debating this forever, and will continue to do so, as long as there are vi(m) and emacs users out there. There is no "right" answer, so just enjoy the jokes (they are normally harmless, and often good for at least a smile).