Re: Good to keep a sense of humour
Of course, the extra memory needed for the code to do it that way will mean out of memory is reached sooner.
42402 publicly visible posts • joined 16 Jun 2014
The main issue of "Pascal" was it was not portable across platforms.
UCSD p-System was in that, like Java, it defined a virtual processor and compiled to that processor's "machine" code, the virtual processor being implemented on a number of different platforms. The original Apple Pascal was UCSD with a 6502 implementation of the p-machine.
Kylix was badly received because it didn't work well. The IDE was Delphi on a customised version of WIne with a cross-compiler. I had code that compiled under Delphi but threw a spurious compilation error under Kylix. The real problem was that it got left behind. It was released, IIRC, towards the end of the version 2 kernel era and didn't get updated for version 4 when a lot of the underlying libraries changed. Nothing to do with Linux "purity", Borland let it die.
"I always think a OO language is just the non OO one where the object reference (self, this) has crawled under the procedure name and advertised (->) itself to the left of the now rechristened method"
In order to do that the language also needs to provide for the definition of methods accompanying data structures. That's the feature that makes it an OO language.
Code can be written in an OO style in any language that provides some form of data structure, much as a Basic style program can be written in an other language; it's just that adding OO features to the language makes it easier. (Writing an OO program that is, not a Basic one!)
I've used both but my initial step was Pascal to C. I found them to be the pessimal* distance from each other for learning one from the other in that they do similar things in quite different ways. It's a very long time since I used C. Come to think of it, it's a long time since I've used Pascal either except for a few toy applications for my own use but as they've been GUI applications for Linux they were written with Lazarus.
* I thought I'd made it up but it really is a word.
"Almost completely and utterly wrong, but interesting."
An admirable illustration of the "all you have is a hammer" principle in taking an inappropriate use of OO as a counter example of the whole in favour of sequential data processing and pipelines.
As a counter example I'd offer my little Object Pascal file card program with different card types for text, tabular and image data, an absolute natural for OO in presentation. For storage, however, I had two options, a database (underlain by a set approach) such as SQLite or text which involved sequential processing.
Or my crossword assistant. It would be unreasonable to expect SWMBO to construct a grep command so it gets encapsulated in OP with the output displayed in a TMemo object.
Successful application development requires thinking in whatever mode is appropriate - OO, sets (OO fundamentalists freak out at the idea of an RDMBS), sequential or anything else that springs to mind.
Pragmatism is the true approach.
"A few minutes later and, if they hadn't noticed the smell of gas, they would probably have reached in and turned the lights on, then possibly boom."
The closest call of that nature was the lab cleaner who arrived one morning to find a jet of flame issuing from a wall mounted gas tap. What we decided must have happened:
Research student failed to completely turn off a bunsen when he left for the night. The flame struck back, i.e. moved back to become a small flame the jet inside the air-hole at the base. This heated the base until eventually it melted the rubber tube where it joined the base. The flame then moved back to the hole in the tube. For the rest of the night it progressively melted the end of the tube until there was no tube left and the flame, still small, was now burning at the tab. This heated the body of the tap. The tap was wall-mounted with the outlet pointed down at 45° with the operating lever sticking up at 45°. The heat expanded the body allowing the weight of the lever to fall into the fully open position which must just have happened before the cleaner arrived. She turned it off with the handle of her mop, no damage done other than coating the inside of the room with soot.
Reading the Wikipedia article suggests Hansson is part owner. It refers to him as a partner in Basecamp which looks like a stale entry from the time before the company changed its name back to 37Signals. When you own the company, or a large part of it, it makes decision making a lot quicker although it helps if you know what you're doing.
"Ironically, shortly after the migration was complete, he got a call from a VMware account manager who introduced themselves as his new point of contact - unaware that Johnston had already planned to end Golding's relationship with the Broadcom business unit."
Ironically? In Johnston's place "happily" might have been the least of it. It would have been a call I'd really have enjoyed. Draw it out nicely. Explain what I'd need from VMware. Reject each of his offerings with lengthy explanations. And even if he did come up with some offer, drop the bombshell that he was too late. Finally explain how easy it was to complete the transfer.
Life doesn't present too many opportunities like that.
"Google just cut it all off. They just pushed a model update that's cut off its willingness to talk about any of this kind of work despite it having an explicit settings panel to enable this and a warning system to allow it. And now it's affecting other users whose apps relied on it, and now it won't even chat [about] mental health support."
How many times do we have to say this? It's somebody else's computer that you don't control.
"Sudo is a command-line utility on Unix-like systems that allows authorized users to run commands with elevated privileges, typically as root" without the safeguard of an additional password. It fails Saltzer and Schroeder's separation of privilege criterion: https://en.wikipedia.org/wiki/Saltzer_and_Schroeder's_design_principles
"Unfortunately StackOverflow, SuperUser and StackEchange (all owned by the same company) now require you to enable cookies and JavaScript to view their webpage as of two days ago."
I have a second browser set up to forget all cookies etc. on exit. Happily click the "accept" button thinking "and much good may it do you".
From the linked report:
The Department of Transportation will announce a plan Thursday to transform the air traffic control system, remodeling an outdated system that contributed to days of delays at Newark, Duffy, the transportation secretary, told Fox News on Monday.
...
Duffy has since pledged to implement a new, “state-of-the-art” system at air traffic control facilities across the country that would be the “envy of the world” – but said it might take three to four years.
“We are going to radically transform the way air traffic control looks,” Duffy told Fox News’ Laura Ingraham.
President Donald Trump has “bought into the plan,” he said
In normal times that might be good news. Now it might be a case of the most terrifying words in the English languge being "I'm from the government and I'm here to help."
Suffering those systems as a result of a 90 second glitch (and note that they wouldn't have known it was going to be "only" 90 seconds) was probably the result of already being at the limit due to accumulated stress. They have my sympathy and, from me, no suggestion at all that they "weren't cut out for the job".
To some extent it's the stock market's fault. They can't be satisfied with a nice little earner, they demand growth. The nice little earner for S/W ought to be get the product complete, shake out the bugs. Don't faff with it to add more so the cost of development can be cut to minimal maintenance and just take the licence fees from new H/W.
But, no. The user base has to be forced to fork out more and more. If that doesn't happen the share price falls below its original unwarranted level and bonuses, tied to further unreasonable growth, are missed and the sharks move in.