1. What is so awesome about adding two numbers in the shell?
2. In any case, bash can do it too -- try echo $((15+7)).
Bash only does integer arithmetic, and grownups generally need floating point math. I usually have a Python or Julia shell open for a variety of reasons, including the "desk calculator" aspect, which BTW might include things like sin/cos, log etc.
I develop in python, java, and objective-c... you know what I hate more then python? Putting parenthesis around every single conditional statement. Once you work in python for awhile and go back, you start to notice how many brackets there are in the other languages.
You'll also notice how other languages need a semicolon after each line, whereas Python (and Julia, Fortran etc.) understands line breaks. I guess early programming environments had a good reason for cramming multiple statements on one line, but now that we can use line breaks for readability, it might as well be a part of the syntax.
Learning Linux is like learning to drive a stick shift.
That's a nice comparison, because here in Finland everyone who learns to drive, does so with stick shift and clutch. Automatic transmissions are only used by disabled people. This is obviously why Linux comes from Finland and Windows comes from the USA.
I first read that as "Wine", and a good exploit should be portable in that way. Although I guess technically that would count as a mere operating environment.
We still don't have OLED at reasonable sizes, with reasonable life expectancy and reasonable prices sadly. I'm just praying my 65" Plasma lasts me at least another 4 or 5 years. I'm hoping to see 85" or larger, OLED 4k displays under $2500 US by then.
Also, who wants "OLED" when every screen on the market is now called "LED" for their backlight only...
"Earth is the 3rd planet from the Sun." Perfectly fine.
"The Earth is the 3rd planet from the Sun." Also fine.
"Mars is the 4th planet from the Sun." No problem.
"The Mars is the 4th planet from the Sun." Wrong.
"The Mars is the 4th planet from Sun." Double wrong.
What. The. Hell.
The difference is that "earth" is both the dirt beneath your feet and a specific planet in space, so you need different phrases to tell the two meanings apart. There's no such issue with Mars, which has always been a proper noun.
This is basically how I understood it, though technically RF counts as an input. The combination with "no speakers" was relevant here, because the tuner will also output audio in some form. I've yet to see a TV with a tuner but without speakers; if you're already bundling a display with your tuner, then you'll probably have speakers for a similar reason. (Does "just inputs" mean no outputs? In that case, how are you going to get the sound out of the tuner without speakers?;)
As others have pointed out, tuners will break and evolve, but a good display will last over generations of different content technologies. The only caveat can be with display input standards, but there aren't that many proper digital ones to choose from. My current workstation monitor is from 2004, and at the time there were lots of displays with analog only inputs, despite being digital flat panels. In fact, I didn't have any computers with digital display outputs at the time, but I made sure the monitor had at least DVI.
Also, consider simple proofs by induction. Besides the actual induction, you need to show that a trivial case works, which is usually plain arithmetic that could be done on a computer. More complicated proofs may require multiple brute-force cases before the actual math can be done. For example, I recall a proof of Bertrand's postulate which first needs individual cases for n < 2000.
It's a bit like physics where you need some concrete system of measurements, a real-world grounding for your abstract work to make sense. If you're doing math with actual numbers, you generally need some numbers to begin with.
Bitcoin was only launched in 2009, so it's a little young for a currency. If you want to wait for a century before using it like old-world money, be my guest. In the meantime, I'll be enjoying all the technical and societal benefits of a truly distributed payment system.
Curly braces? Pffft. Those are to passe. You need to close things with an 'end'.
Fortran uses the 'end' convention, and it was the first high-level programming language. As a more recent language for scientific computing, Julia has adopted this, and I personally prefer it to both braces and Python's syntactical indentation.
Basically, I want to minimize the amount of punctuation (aka line noise) I see. Line breaks are a simple way of getting rid of semicolons (unless you really need to write one-liners that aren't). For blocks you need something else, and Python's way is too fragile between different programmers/editors.
GPUs are increasingly being used for general purpose computation and rendering, not just playing games. For these purposes more computing power is always welcome, in the same way as faster CPUs and more/faster RAM and storage. For example, would you rather process this data set in 1 day or 2?
The display part won't benefit from indefinite improvements, as the human eye has its limits. But for everything behind the display, there's always more computing to be done.
These days, one tends to think that by "model", they mean a woman on a magazine's cover. However, those type of models do not necessarily have a detailed understanding of nuclear physics. Usually. Sadly.
Are you suggesting that the parton model has nothing to do with a model called Parton?
This. My first Linux laptop had 32 MB soldered on board, and a single SODIMM slot for a maximum of 128 MB extra, so I ended up with 160 MB. I thought that was such a huge amount I wouldn't need any swap...
The soldered-on trend is still alive in chromebooks, netbooks etc. but in many cases there aren't any extra slots. If there are, the sizes are more similar, in ratios like 1:1 or 2:1, so you won't see these weird totals any more.
For offline GPU rendering you might as well look at OpenCL right now, perhaps with a python wrapper (pyOpenCL) or some such so that it's easier to handle, as OpenCL can be a bit of a handful if you don't have much experience with GPU/shader programming or numerical linear algebra. I've read that the Processing language has (some) OpenCL support, that may be up your alley?
Ah, I've also considered both OpenCL and Processing. The latter looks interesting for education/workshop purposes, but too much of a monolithic framework to my tastes -- I have enough programming/math/physics background to hate any kind of handholding, and these days I mostly code in Julia. I did have a brief stint contributing to an OpenCL project a while ago, and I'll probably have to return to it at some point.
Slashdot Mirror
It wants its newfangled CPU architecture back.
1. What is so awesome about adding two numbers in the shell? 2. In any case, bash can do it too -- try echo $((15+7)).
Bash only does integer arithmetic, and grownups generally need floating point math. I usually have a Python or Julia shell open for a variety of reasons, including the "desk calculator" aspect, which BTW might include things like sin/cos, log etc.
I develop in python, java, and objective-c... you know what I hate more then python? Putting parenthesis around every single conditional statement. Once you work in python for awhile and go back, you start to notice how many brackets there are in the other languages.
You'll also notice how other languages need a semicolon after each line, whereas Python (and Julia, Fortran etc.) understands line breaks. I guess early programming environments had a good reason for cramming multiple statements on one line, but now that we can use line breaks for readability, it might as well be a part of the syntax.
Monitors lack TV tuners. So I myself would say No.
Then that would be an incredibly awful TV!
It has no speakers, and inputs only. So, OK, RF goes in, it displays pictures, but you're stuck watching silent films forever.
Displaying pictures is a kind of output. An input-only TV would not be terribly useful as a TV.
Learning Linux is like learning to drive a stick shift.
That's a nice comparison, because here in Finland everyone who learns to drive, does so with stick shift and clutch. Automatic transmissions are only used by disabled people. This is obviously why Linux comes from Finland and Windows comes from the USA.
The real question is, will it work on WinME
I first read that as "Wine", and a good exploit should be portable in that way. Although I guess technically that would count as a mere operating environment.
We still don't have OLED at reasonable sizes, with reasonable life expectancy and reasonable prices sadly. I'm just praying my 65" Plasma lasts me at least another 4 or 5 years. I'm hoping to see 85" or larger, OLED 4k displays under $2500 US by then.
Also, who wants "OLED" when every screen on the market is now called "LED" for their backlight only...
"Earth is the 3rd planet from the Sun." Perfectly fine. "The Earth is the 3rd planet from the Sun." Also fine. "Mars is the 4th planet from the Sun." No problem. "The Mars is the 4th planet from the Sun." Wrong. "The Mars is the 4th planet from Sun." Double wrong.
What. The. Hell.
The difference is that "earth" is both the dirt beneath your feet and a specific planet in space, so you need different phrases to tell the two meanings apart. There's no such issue with Mars, which has always been a proper noun.
"Just inputs" rules out a built-in TV tuner.
This is basically how I understood it, though technically RF counts as an input. The combination with "no speakers" was relevant here, because the tuner will also output audio in some form. I've yet to see a TV with a tuner but without speakers; if you're already bundling a display with your tuner, then you'll probably have speakers for a similar reason. (Does "just inputs" mean no outputs? In that case, how are you going to get the sound out of the tuner without speakers? ;)
As others have pointed out, tuners will break and evolve, but a good display will last over generations of different content technologies. The only caveat can be with display input standards, but there aren't that many proper digital ones to choose from. My current workstation monitor is from 2004, and at the time there were lots of displays with analog only inputs, despite being digital flat panels. In fact, I didn't have any computers with digital display outputs at the time, but I made sure the monitor had at least DVI.
I really just want a dumb TV. No android, no apps, no speakers just inputs.
So... a monitor?
...in bases of two, four or eight.
If every country joined NATO, there would be peace on Earth forever and ever.
Also, consider simple proofs by induction. Besides the actual induction, you need to show that a trivial case works, which is usually plain arithmetic that could be done on a computer. More complicated proofs may require multiple brute-force cases before the actual math can be done. For example, I recall a proof of Bertrand's postulate which first needs individual cases for n < 2000.
It's a bit like physics where you need some concrete system of measurements, a real-world grounding for your abstract work to make sense. If you're doing math with actual numbers, you generally need some numbers to begin with.
Bitcoin was only launched in 2009, so it's a little young for a currency. If you want to wait for a century before using it like old-world money, be my guest. In the meantime, I'll be enjoying all the technical and societal benefits of a truly distributed payment system.
Estonian President Toomas Hendrik talked
In other news, Barack Hussein is the way Slashdot editors refer to their president.
Curly braces? Pffft. Those are to passe. You need to close things with an 'end'.
Fortran uses the 'end' convention, and it was the first high-level programming language. As a more recent language for scientific computing, Julia has adopted this, and I personally prefer it to both braces and Python's syntactical indentation.
Basically, I want to minimize the amount of punctuation (aka line noise) I see. Line breaks are a simple way of getting rid of semicolons (unless you really need to write one-liners that aren't). For blocks you need something else, and Python's way is too fragile between different programmers/editors.
Shirley, you're joking. FPGAs took over GPUs for Bitcoin mining in 2011, and later ASICs.
Or in the style of von Neumann, use transitions between 0 and 1 as they will come equally often. Map 01 to 0 and 10 to 1, for example.
GPUs are increasingly being used for general purpose computation and rendering, not just playing games. For these purposes more computing power is always welcome, in the same way as faster CPUs and more/faster RAM and storage. For example, would you rather process this data set in 1 day or 2?
The display part won't benefit from indefinite improvements, as the human eye has its limits. But for everything behind the display, there's always more computing to be done.
No, /real/ hackers use butterflies after coding them up first.
These days, one tends to think that by "model", they mean a woman on a magazine's cover. However, those type of models do not necessarily have a detailed understanding of nuclear physics. Usually. Sadly.
Are you suggesting that the parton model has nothing to do with a model called Parton?
This. My first Linux laptop had 32 MB soldered on board, and a single SODIMM slot for a maximum of 128 MB extra, so I ended up with 160 MB. I thought that was such a huge amount I wouldn't need any swap...
The soldered-on trend is still alive in chromebooks, netbooks etc. but in many cases there aren't any extra slots. If there are, the sizes are more similar, in ratios like 1:1 or 2:1, so you won't see these weird totals any more.
Also, nobody wants a keyboard in a device they use for text messages.
IMHO, this is perfectly on topic. Fructose is fine when eating whole fruits, because they are digested more slowly due to fiber and all that.
For offline GPU rendering you might as well look at OpenCL right now, perhaps with a python wrapper (pyOpenCL) or some such so that it's easier to handle, as OpenCL can be a bit of a handful if you don't have much experience with GPU/shader programming or numerical linear algebra. I've read that the Processing language has (some) OpenCL support, that may be up your alley?
Ah, I've also considered both OpenCL and Processing. The latter looks interesting for education/workshop purposes, but too much of a monolithic framework to my tastes -- I have enough programming/math/physics background to hate any kind of handholding, and these days I mostly code in Julia. I did have a brief stint contributing to an OpenCL project a while ago, and I'll probably have to return to it at some point.