I wonder what these people think of the blood that comes in a package of meat? What about the gonads of plants that people like to eat (such as an apple)?
As she continued to ignore me my explanations grew longer and more detailed, until finally she interrupted me with "What's inertia?"
After you explained the concept, did she at least understand the idea but not the term, or was even the concept of inertia something that was a revelation?
I *think* that fpc Pascal can not properly handle utf8 strings
Only because of purists that insist a six byte character is counted as one character.
A lack of documentation is an issue, but that is simply because it is an open source project. About par for the course on most open source projects, from my experience too. Delphi has some amazing documentation, but then again they can pay for that documentation to be developed.
People gave up on Pascal and moved to C++ back then for a reason.
It wasn't really for a good reason other than simply the choice of the software development shop, as well as the cost of compilers where C compilers were widely used as assignments in Computer Science graduate courses... thus frequently offered for free. Arguably a C compiler is also easier to write than a good Pascal compiler, so it frequently is the first compiler available for a given instruction set or computer architecture.
That doesn't mean it is necessarily inferior or for that matter better than C++ for high level application development. It does explain why you see fewer people developing in Object Pascal vs. C++.
For instance, "++i" is a more immediately recognizable idiom than "i
In Object Pascal, it is:
Inc(i)
A couple extra letters to write, but trivial and works just fine and clearly understandable. It even returns a value (if needed).
Wow, I hope you're not suggesting 22 div 3 vs. 22/3 is more intuitive to a novice for what it does compared to 22/3 and 22/3.0!
A properly designed compiler (like Turbo Pascal and later Delphi) makes no distinction nor software penalty for using either convention. This is nit picking at such a minor detail, although as a software developer I like to emphasize that I am using an integer division as opposed to floating point, thus deliberately use the div operator when appropriate. For a novice, it shouldn't make any difference at all.... particularly for the kinds of applications developed by a typical novice that would have any sort of confusion over this issue (or some C++ developer tasked to do some Object Pascal debugging).
From a maintainability standpoint when you need to have code written by an experienced software developer familiar with Pascal and its various (current) compilers as opposed to an experienced software developer familiar with C++... when you hand those software packages over to another developer to continue development by somebody having to start cold on that software and fix bugs, make extension, or overhaul that code... I dare say that the software written in Object Pascal can be developed sooner than a comparable application in C++. My direct experience has been in about half of the time or less than a comparable C++ program.
That is my standard for readability. The only reason you might notice some developers who have a hard time with Pascal readability is mainly due to the fact that the developer is simply unfamiliar with Pascal syntax due to a lack of development in that language for a prolonged period of time. Handing Object Pascal code to somebody else already familiar with the language clearly has a huge advantage.
Just because it is different doesn't mean it is worse. It might mean that you would need to personally take some extra time to learn another programming language. Besides, for a Pascal programmer, curly braces are for comments and stand out very well for that purpose.
I only hope that formats like these drive production of more UHD displays, bringing their price down. I don't want to watch UHD movies. I want cheap, high-res monitors for my computers.
Of course, I didn't follow his reasoning one bit:
Using 10-bit color may end up limiting chroma sub-sampling to 4:2:0.
The two details are completely orthogonal to each other!
In any case, 4:2:0 at UHD gives you as much color information as 4:4:4 at HD. You'd have a very hard time noticing the chroma subsampling....
My favorite things to laugh at were:
Well, among everything else in there. It seems that SkyMall has moved on from these favorites. But, they were reliable point-and-laugh items when I was flying regularly a few years ago.
Isn't that a common pattern, though? Spin off the few profit centers that are actually profitable, and then fold the rest of the business?
Or a mouse without a few wires & dongles and shit coming out of it.
While it is a cool hack, without wireless screen I'm not sure it is worth while.
Yes. And the problem is that VB is MS only. It is a vendor lock in.
It soon won't be, though. But I reckon waiting for this stuff to show up would be kind of a setback for a four-year college degree.
I learned programming in Microsoft BASIC, assembly language and a touch of Pascal, prior to reaching college. I don't use any of those languages now. (Ok, I still program in assembly language, but for different processors.)
As long as it's actual programming, with variables, data structures, and code to manipulate those things, then great! I don't really care if it's VB, Python, TCL, Lua, Perl, C++14, Delphi, Haskell, LISP, Erlang...
The real point is to open up the computer as a programmable device, and to get kids seeing the computer as something they can extend themselves with their own creativity. For that to happen, you want to choose a language that students can pick up quickly enough to see interesting results early on. You don't want their first meaningful program to come in the last weeks of a year-long class.
8 Catfish = 1 Octo-puss