Certainly! A comparison of performance with specialized tools for large point clouds would be very interesting (like cloudcompare and potree).
14,003 karma · joined February 11, 2016
just another C hackerCertainly! A comparison of performance with specialized tools for large point clouds would be very interesting (like cloudcompare and potree).
> These days, having a GPU is practically a prerequisite to doing science, and visualization is no exception.
It becomes really funny when they go on to this, as if it was a big deal:
> Depicted below is an example of plotting 3 million points
Anybody who has ever used C or fortran knows that a modern CPU can easily churn through "3 million points" at more than 30 frames per second, using just one thread. It's not a particularly impressive feat, three million points is the size of a mid-resolution picture, and you can zoom-in and out those trivially in real-time using a CPU (and you could do that 20 years ago, as well). Maybe the stated slowness of fastplotlib comes from the unholy mix of rust and python?
Now, besides this rant, I think that fastplotlib is fantastic and, as an (unwilling) user of Python for data science, it's a godsend. It's just that the hype of that website sits wrong in me. All the demos show things that could be done much easier and just as fast when I was a teenager. The big feat, and a really big one at that, is that you can access this sort of performance from python. I love it, in a way, because it makes my life easier now; but it feels like a self-inflicted problem was solved in a very roundabout way.
Well, actually, it was the OP who said, literally, that "the most interesting thing about Fish (...) will be that it is now written in Rust"
There you said it! But, if you cannot control the software, then it's not your hardware.
It doesn't, and that's OK; not a big deal.
JSON has no support for standard floating-point numbers, and that's a bigger problem for me. I can easily change my keys to make them sane, but I cannot change the numbers!
But for that case you don't need json. A dockerfile-like text file with lines of the form
STRING other stuff
is trivial to parse in any language and without requiring any library. And it's actually human-editable.Using json for such trivial stuff is like using a linear algebra library to compute b/a (the quotient of two numbers) by calling linalg.solve([[a]],[b]). Of course it will work. Of course it is more general. But it feels silly.
JSON is just a modern flavor of XML, and in a few years we'll likely mock both of them as if they were the same silly thing. They are functionally equivalent: not human-writable, cumbersome, crufty, with unclear semantics, with unclear semantic usage, and all around ugly.
EDIT: playing with it, it's a bit sad that large numbers do not work at all (in any language); and that not all common forms of a word are shown. For example, I tried to see how "ninety six" is said in french in France, Belgium and Switzerland, but it does not work.
My point is that when you say:
> Gimps are considered inappropriate to even talk about in school and business settings
This refers solely to the tiny percent of the world where people are native english speakers. Elsewhere, it already means the image processing software, if anything at all.
Why?
Honestly, why?
As a non-native English speaker (like the vast majority of people in this planet), the word "gimp" to me means "the free software image processing program". If I search google, duckduckgo, bing, whatever, the entire first page of results refers to that very program. Digging deeper, I start to find some references to the Pulp Fiction movie, where a minor character is named like that. I remember that character, but in my language it was called by a different name. Is that all?
Is there any other meaning to this word? If so, it must be so obscure as to be completely irrelevant.
Please, take into account that most English speakers are not native speakers, and many words will have a different meaning to us. English as a lingua franca may be comfortable to native speakers, but it also means that it's no longer yours.
The name of the program does not seem to be a serious issue for its adoption. Now, if you want to talk about its user interface... I don't think it does, either (but I may be open to discussion). I have taught my kids to do simple image processing tasks in gimp: copy-pasting parts of an image into another, removing some stuff, blurring, simple layer operations, etc. Anyhow, they got it in a few minutes. Important to say: they are not at all tech-savvy (to my dismay! but this is another story). If they use adobe or krita they will surely find it slightly confusing at the beginning, but no big deal either. Just like a regular person moving from photoshop to gimp.
NAME
echo - echo arguments
SYNOPSIS
echo [ arg ... ]
DESCRIPTION
Echo writes its arguments in order as a line on the standard
output file. It is mainly useful for producing diagnostics
in command files.Never heard of echo? What do you expect this to do?
echo --helpCOPY: select text with the mouse
PASTE: middle click
don't people use that? No need for the keyboard at all! It works across all programs since forever (except inside jupyter notebooks on firefox, for some weird reason).
If I had to single out a unique feature that makes linux worthwhile (as compared to windows or macos) it would be that one! Way ahead of anything else.
The writing style is reminiscent to this famous text (not written in jest, you have to understand that most of these statements depend on a context that is for you to provide):
"Property is theft." -- P.J. Proudhon
"Property is liberty." -- P.J. Proudhon
"Property is impossible." -- P.J. Proudhon
"Consistency is the hobgoblin of small minds." -- R.W. Emerson
Why not? I love to peek at .tex file comments, and secretively hope that somebody somewhere is reading mine...
you can easily add variables to your rpn calculator. For example ">x" pops the top of the stack into the variable x, and "<x" pushes the value of x to the stack.
You can also interpret parentheses as whitespace to enable users to group parts of the computation (but this may become confusing when they write nonsensical parentheses).
Wow. It's amazing to see the beast laid out so clearly before me.
As someone who grew with the mantra "a program is a piece of text", my jaw dropped when I read this post and realized that it was not written in jest. Of course the mantra is still deeply entrenched in my mind, it's too late to remove it now; but I feel as if the world is crumbling around me. What other sacred beliefs will fall? Why doesn't everybody realize that the text file is one of the finest inventions of the third millennium?
Maybe it's just another period in the eternal cycle of fashion trends... programs as free-form text files were an exhilarating liberation from the crufty, fixed-form structures of older languages. Now, we are not only going back to write our code starting at column 4 (like in punched cards), but we still want to add even more structure to it! Maybe in forty years we will go back to free-form text and cherish it again.
Reading the sentence "programs are not text" was the first time I felt old in my life.
Sounds good, doesn't it? This means that efforts to produce a fully static distribution would imply a sweeping wave of fixes across a wide range of packages and build systems!
There's still a long way to go. The elephant in the room, prudently sidestepped by the hyperbola community, is the removal of dynamic linking. Now that would be a great, but difficult, brave choice. Most of the other removals (except the removal of dbus, which is mind-boggingly awesome) are fairly isolated stuff.
Fortunately, they are steadily taking steps in the right direction!