Comment Re:Um... No. Hijacking this thread for Jimmy Kimme (Score 2) 35
Um... No.
Um... No.
The data brokers likely know what color your underwear is, and that you didn't change it this morning.
Do they know at what rate it changes color if I keep it several days ?
OpenAI is still stealing everyone else's lunch.
Just as much as Google News is.
Books: The Bourne trilogy, which, contrary to the movies, were very entertaining.
Everyone is using OpenJDK these days, nobody in their right mind would pay for their licensing.
The free market works on it's own
The planet may disagree though.
A plumber can make art while plumbing. A truck driver can make art while driving. Yet that is not the first purpose of their jobs. Hence, in general, a truck driver is not an artist. Of course, nothing prevents a truck driver from being an artist.
Same for engineering (software here). Our job is to build / maintain systems. Not to create art. Now, we can create art in the process, of course, just like everyone else. But no, engineering is not art by any stretch of the imagination.
Art: the expression or application of human creative skill and imagination, typically in a visual form such as painting or sculpture, producing works to be appreciated primarily for their beauty or emotional power.
Engineering is an activity that has a practical goal: Build a plane, make a website, make this piece of code scale. Not activities primarily appreciated for their beauty or emotional power.
If your program will be up for days (think a server, a browser, etc...), the startup time can easily become negligible.
Well, each thread uses its own buffer, so there is no issue, is there ? They can then switch buffers when they feel the need to.
Engineering is inherently a creative job, so is researcher, and many others. That does not make it art.
Java is slow to start, because the JVM is a beast that takes its sweet time to get up to speed. After this hit, the type of code you are talking about will be about 5 to 10 % slower, which might be acceptable or not depending of your requirements and the value you put in all that Java provides and C does not.
The reason so few games are written in Java is that the GUI layer is not efficient to optimize your UI down to your graphic chipset *and* the fact that a full GC will stop the world fr a split second and you have no control over it. So, a game needs fluid interface which the GC doesn't allow and lightning fast graphics performance which java is not equipped for. The general CPU performance of Java is not at all an issue there.
Rust do not allow you to share a buffer between two threads for example. That might be one optimization that the C code does and the Rust implementation *cannot* do. It might not just be the ASM produced by the compiler.
That's one example of course.
"All my life I wanted to be someone; I guess I should have been more specific." -- Jane Wagner