Or you know, you could configure the ThinkPad you are buying to have a quadcore and a 3K screen.
The T440s is the "Ultrabook" form factor; it tops out at dual-core, and 1920x1080 screen size.
The T440p is the "performance" form factor, and has quad-core available, but it's thicker and heavier.
I just checked the Lenovo web site, and the T440s is discontinued. They are now on the T450s and T450p. The T450p does have a quad-core i7 option and a 3K screen option. It can also be equipped with 16 GB of RAM (vs. max 12 GB for a T440s).
I'm only recommending the ThinkPad I have. I would rather have my T440s than a MacBook Pro, but I'm not sure how well I would like a T450p (thicker and heavier; weight listed as "starting at 5.5 pounds"). Also, the top-spec T450p, if ordered directly from Lenovo, would cost more than a 15" quad-core MacBook Pro.
I think in modern science, the heavy computation is likely being done on servers rather than on laptops, so it would make more sense to go thin and light on a laptop. I'm happy with the T440s so I recommended it.
If she's spending her own money, it's hard to beat the value of a Thinkpad T440s. It's an "Ultrabook" so it's similar form factor to a MacBook Pro. Great screen, good battery life, good processor, and Linux works out of the box.
She will need to get a mini-DisplayPort to HDMI adapter, for giving presentations where there is an HDMI connection to use. The T440s has both mini-DisplayPort and VGA connectors built-in.
I have one running Linux Mint 17.1 64-bit MATE. I got the top-of-the-line one with the 1920x1080 display, which I recommend. I got mine from B&H Photo in New York; it was significantly cheaper than other web sites I checked.
I have mine set up on a docking station, which came with its own power supply. So its power supply stays in my laptop travel bag, ready to go. Just undock and you are good to go. This is one way in which this is actually better than a Mac.
The Mac will cost $700 extra, and come with a higher-resolution display, a quad-core processor, and more RAM. That may be a better deal for her if she plans to do a whole lot of work directly on the laptop, rather than using the laptop to access remote computers.
P.S. I recommend that she take a look at the IPython Notebook, if she hasn't already. Running SciPy under IPython will be great for her.
I'm not in a big hurry, and I want to see what DTS comes out with before I invest in an object-oriented sound system. Also I'm not in a hurry to bolt speakers to my ceiling and run the wires.
Now that you explained your points I don't think I disagree with you about any of the technical stuff.
I interpreted "nothing is mixed in Neural Surround" as "Neural Surround does not mix anything" which wasn't your intent. I agree that there isn't much content in Neural Surround; that press release was from 2006, and I don't know if that radio station is still doing the 5.1 broadcasts or not.
I'm a feature film sound designer and mixer, DTS is completely out of theatrical and television -- the original theater format is owned by a different company now
Correct. DTS the company split into two, and the theatre-related one changed its name to Datasat.
"optimized" for Neo:X
I think that "optimized for Neo:X" might also mean that an audio mix with height channels might have been run through a downmixer to get a suitable 7.1 mix that can be upmixed properly to 11.1. I don't know if Expendables 2 has helicopters or planes flying overhead, but if so, the people who bought height speakers might as well get some sound out of them.
"Object-oriented" audio encoding formats solve the problem in the best way: if there is a helicopter overhead, there will be an audio object tagged "overhead" and the mix can be adapted to whatever speakers the user has. If the user has height speakers, they get used. That's what I want for my living room anyway.
[DTS Neural Upmix is] marketed as a spatializing upmixer that can also decode Neural Surround (which is a third format not necessarily related to Neo:X).
No, there is no "Neural Surround" format as such. Neural Downmix uses phase encodings and the output is just an audio stream (can be analog, saved as a wave file, saved as DTS Master Audio, saved as MP3, etc.).
Look at this PDF. There are two columns: one shows different disk formats and how many bits per second each one needs; the other column has one thing in it, Neural Surround. This is because Neural Surround isn't a format as such.
See also this press release. A radio station was broadcasting in 5.1 using Neural Surround... broadcasting in ordinary stereo FM as well as HD radio. Anyone could listen in stereo, but those with Neural Upmix in their stereo receivers could hear 5.1 sound.
But this feature is sorta incidental, as literally nothing is mixed in Neural Surround.
I'm sorry but you are completely mistaken on this point. Let's look at the DTS web site again:
DTS Neural Surround DownMix technology reduces multichannel surround sound to a stereo mix that accurately represents the original intent of the content creator.
The DTS Neural Surround DownMix uses patented âoeActive Correctionâ technology. By analyzing the audio, the phase and intensity are rewritten, creating a pristine Lt/Rt stereo mix.
This process eliminates problems that traditionally occur in matrix surround downmix systems, such as comb filtering and spatial distortion. DTS Neural Surround DownMix creates a natural sounding stereo mix that is spatially true to the original multichannel localization.
Note the phrase "pristing Lt/Rt stereo mix" and the concerns about comb filtering in the output mix. There is mixing going on here.
DTS Neural Downmix produces a stereo output stream which may be saved in any format. You can feed the result to DTS Neural Upmix, even as an analog waveform, and it will upmix using the encoded signals. There is no disk format for "DTS Neural Surround" as such.
My understand is that the height channels are encoded sum-and-difference with the main L-R channels, and a special decoder reads reads additional channel data to subtract out the height channels from the mains.
I think it is possible that there is some additional metadata embedded in the DTS Master Audio bitstream, because old DTS decoders do understand metadata tags and will ignore them. But there is no bitstream change from plain DTS 7.1 to DTS 11.1, and you can play the 11.1 stream on an old DVD player and you will get 7.1 out. (Just like you could play Dolby Surround on a stereo and get stereo out, if you didn't have the Dolby Surround decoder to upmix from stereo to surround.)
If you are still convinced that DTS 11.1 has additional discrete channels, please find a reference and show me. If I'm wrong, I'm wrong, but I think the DTS web page I referenced in the previous post backs me up.
By "actual format" I mean its a communications channel where the sender and recipient agree on what goes into the channel and what is supposed to come out.
Then I would say that DTS 11.1 is an actual format exactly the way Dolby Surround was an actual format. Both rely on specific, agreed-upon phase encodings
There's a fundamental difference between an encoded mix and an upmixer. Dolby Surround is intended to be decoded from 2 tracks into LCRS, the filmmakers mixed the film in Dolby Stereo and were listening to the surrounds so they know what's in them. The phase encoding is part of the channel spec.
I'm with you so far.
An upmixer takes a stereo or 5.1 mix and applies effects to it to make it sound like it was mixed in a wider format, but there's nothing really being decoded, it's just synthesizing or guessing what should be in the additional channels using heuristics, all-pass filters, delays, crossover networks and other stuff that sounds cool or "provide a good experience" but, in fact, interfere with the filmmaker's intent.
The original Dolby surround and DTS Neural Upmix can both be applied to any stereo recording and some sort of upmix will occur, but both were designed to be used with a mix that was intended to be upmixed. DTS also sells DTS Neural Downmix which can take a 5.1 or 7.1 stream and output stereo with intentionally encoded signals that decode back to 5.1 or 7.1 sound.
When DTS Neural Upmix is working from a stereo signal that was made using DTS Neural Downmix, you get a really clean surround sound with no leakage. I used to listen to the multichannel recording of "Money" by Pink Floyd, and the cash register and coin sound effects very cleanly came from all the different directions like the original multichannel mix.
Again, you can't fit 8 kilos of flour into a 2-kilo sack, so 7.1 audio sent through downmix, then upmixed back to 7.1, can never perfectly reproduce the original multichannel recording. But I was impressed by just how well it did.
Despite the name "Neural Upmix", it is designed to work with phase-encoded signals intentionally mixed using Neural Downmix.
Neural Upmix is an upmixer, DTS Neo:X is an actual format that decodes an 11.1. Neo:X home receivers also employ upmixing, mainly because no films are mixed in 11.1 Neo:X, it's a surround audiophile format, and it needs to do an upmix in order to justify people spending money on it.
My understanding is that DTS 11.1 audio uses intentionally encoded signals for the height channels, but the on-disk format is DTS Master Audio 7.1 (no additional discrete channels).
Just as the original Dolby surround could be listened to in stereo if you didn't have surround speakers, the 11.1 mix can be listened to in 7.1 if you don't have height speakers; in both cases, the downmix process is supposed to not add anything objectionable.
I don't know what you mean by "DTS 11.1 is an actual format"... if you mean that it has 12 discrete channels, I believe you are mistaken on this point.
Here's how DTS describes the 11.1 system:
An important goal of the DTS multi-tiered plan is to enable content creators to produce 3D audio and provide it to consumers without changing the delivery chain. With the DTS Neo:X capability for near discrete Height/Wide output, studios can produce directional cues intended only for these speakers, with no audible leakage into other channels. Studios can also produce soundtracks optimized for DTS Neo:X that offer a compatible listening environment in âoestandardâ multi-channel playback configurations.
"without changing the delivery chain": no new audio format, disks play fine on older DTS decoders
"no audible leakage": there's no problem with leakage if you have discrete channels; if we are even talking about leakage, we are talking about an upmix.
I don't believe Imade any mistakes in my original post.
Actually in the audio world, "binaural" is used to specifically mean a recording intended for being played directly into the ears.
I was once present for a binaural recording session. The guy doing the recording had brought a fake human head, and the two microphones for the recoding were positioned in the two ears. The idea was to reproduce as fully as possible what you would have heard if you had been sitting in that spot in the room, with your head in that position.
You can listen to a binaural recording on speakers of course, but for the best experience you should use headphones.
For the absolute best experience, the recording should use a fake head that is exactly like your head. Not many people are ever going to experience that.
Audio can do funny things as it travels around your head. For the absolute best 3D experience with headphones, you want to measure what happens to audio around your head; this is called your "Head-Related Transfer Function" or "HRTF". Instead of recording the audio with a fake head shaped just like yours, companies can just record a good 5.1 or 7.1 recording, and then you can mix that down to a binaural stereo mix that is perfect for your head if you have your HRTF. According to the article the AES is standardizing a file format for HRTF data, so that the software you get will be more likely to be able to work with your HRTF data if you have it measured.
The ultimate in VR audio will be headphones with motion tracking, and real-time mixing that uses your HRTF and changes the mix as you turn your head. If something is supposed to be coming from your left, and you turn your head to the left, that sound should get louder; then if you turn your head away from it, it should get quieter. If this is done right it should be incredible. People have been working on this for years and I'm sure someone somewhere has done it right, but I haven't seen any commonly available products to do it yet.
But with VR goggles you should totally have VR audio like I described above. It would be really immersive.
3d audio = surround sound (5.1/7.1/8.1/etc)
Pretty much, 3D audio is intended to include speakers above the plane of the 5.1 or 7.1 speaker setup; the industry calls these "height speakers". DTS 11.1 audio, for example, has a standard 7.1 setup, and then 4 height speakers: two in the front and two in the back.
The current ultimate in 3D audio is a 22.2 setup, where the ceiling has a 3x3 array of speakers, there are speakers at mid height, and there are speakers at ground level. However, IMHO there is zero chance that 22.2 will catch on as an audio standard.
Before the 5.1 and 7.1 digital standards, there was Dolby Surround that was encoded within a stereo soundtrack. A simple audio mixer could "upmix" from stereo to surround. DTS Neural Upmix can make a very clean 7.1 from a stereo signal, and it works from an analog signal (it's not something tricky inside a digital encoded format). You can't get 8 kilograms of flour into a 2-kilo bag, and Neural Upmix 7.1 can't completely reproduce the same mix as you can play through 8 discrete channels, but it can provide a good experience.
DTS 11.1, as I understand it, uses technology similar to DTS Neural Upmix to encode the 4 "height" channels within the other 7.1 channels. Turning 7.1 into 11.1 should be a lot easier than turning 2.0 into 7.1 so it should provide a good experience.
I expect the industry to go to "object oriented" audio. This means that audio will have metadata tags saying what direction the audio is coming from, and then a real-time mixer upmixes from the digital format with the metadata tags to whatever mix you need (i.e. if you have 11.1 speakers you get an 11.1 mix, if you actually have 22.2 speakers you get that, if you have 7.1 you get that, etc.) I believe Dolby Atmos works this way, and I believe DTS
Despite my mentioning the Cree 4FLOW, I still recommend buying Cree's more-expensive but better-made bulbs. The 4FLOW costs less, but it has a much shorter warranty and isn't nearly as well made.
The 4FLOW would be perfect for a light inside a closet that's rarely turned on, but then if it's rarely turned on you might as well leave the incandescent bulb in there until it burns out.
I had a similar experience with fluorescents. I replaced most of the ordinary light fixtures in my home with special fixtures with a circular fluorescent bulb (not "compact fluorescent"). I liked the quality of the light and I figured I'd be saving electricity.
Then the fixtures started burning out. Sometimes it would just be the bulb, but usually it was the whole fixture. At first I replaced the fixture with another (at $20 per fixture), but eventually I decide it was stupid and I started replacing the fluorescent fixtures with ordinary fixtures that take standard bulbs. At the time I installed compact fluorescents. And of course the compact fluorescents, which would be easy to replace if they die, never die. (I don't care, I'm replacing them with LEDs anyway.)
As for avoiding burning your house down, I suggest you do as I do: buy Cree products. I get the top of the Cree line, the "TrueWhite" bulbs, but they have new "4FLOW" bulbs that cost less and run very cool.
The cheapest LED bulbs will be like the cheapest anything electronic: made at some random factory in China with possibly bad quality control and even possibly bad safety. Sounds like you had the bad luck to get a bad bulb. Sometimes it's worth it to pay a bit more for a name brand.
I don't know how much these cost where you live, but where I live I can get LED bulbs at Home Depot from $6 to $20 depending on quality and brightness. They have an expected lifetime of 20+ years, and I don't have to change the light in that time. To me, this is a no-brainer and I've been buying LEDs for my whole house.
In fairness, I know that the power company where I live is subsidizing the bulbs, and absent the subsidy they would cost more. But it seems likely that you might be able to buy subsidized bulbs where you live too.
Also, I just checked the EarthLED web site, and without asking me where I live, the site showed me a deal: $100 for a 20-pack of LED bulbs. I've never heard of the brand ("Euri") but surely you could pay $5 per bulb for something that will last so long?
I like the Cree TrueWhite bulbs and I pay extra for them. LED bulbs tend to be a bit too yellow, so Cree developed a "notch filter" that takes out some of the yellow from the light, correcting the color. But now the light is a bit dimmer since some was taken out; so Cree puts a few extra LED modules into the bulb. Result: same amount of light, better color, consumes a little more power but not too much more.
I have also replaced all the 48-inch fluorescent fixtures in my home with Cree Linear LS4 fixtures at 3500K color temperature. Wow, it's so much nicer light and completely silent. Totally worth it.
If you are using incandescent bulbs, and you replace your most-commonly-used ones with LED bulbs, you will save enough money on electricity to pay for the new bulbs within a reasonable time. If you already have compact fluorescent bulbs, and you don't mind their light, then LEDs aren't guaranteed to pay for themselves right away and it might make sense to keep waiting. Otherwise, go for it.
It's interesting the headphone jack is still there since bluetooth chips are so cheap, easy to use, and are smaller than the headphone jack itself. I guess the problem for wireless headphones is powering them requires too many batteries.
Current Bluetooth headsets require the audio stream to be compressed using lossy compression. If you want the best audio quality, you buy nice headphones and plug them into the analog jack.
According to a post on soundexpert.org, Bluetooth audio has 721 kbps bandwidth. That's bits, not bytes. Thus the requirement for lossy compression.
Unless Bluetooth becomes able to carry FLAC or Apple Lossless with at least 2 channels at CD quality, the headphone jack is still essential.
And as you noted, Bluetooth means battery hassles while wired headphones always work.
held up by a tangle of clean power foes, regulatory and financing woes, and Cape Cod homeowners afraid it'd ruin the view.
Who exactly are "clean power foes"?
This seems like using an epithet to delegitimize others.
I'm sure there are people who oppose this project for stupid reasons, like "it'd ruin the view". But I am equally sure that absolutely nobody opposes this project because it is too clean.
I suppose that if you looked and looked, you could find someone who is so certain that an ice age is coming that he wants all power generated by burning stuff. But even this imaginary guy isn't really a foe of clean power, he's just a fan of carbon dioxide.
I've read about phones where you program which number the phone calls, but I can't find any now. Maybe they are no longer sold.
But here's a phone that calls some sort of operator, who can then decide how to handle the situation. You need to pay a monthly fee for the operator but I think that's better for a 2-year-old than a phone that just dials 911.
IMHO, the sooner the world standardizes on Python 3.x, the better. It contains numerous small improvements, no one of which is invaluable, but together which add up to a better language.
As for print as a statement, I only miss that for interactive use, and you can assuage the issue by using ipython with the --autocall feature enabled. And I like the simple way you can now control how the output is formatted and where it goes, and you can re-bind the name print to completely hook the behavior of printing. Overall it's a win.
The big shocking change is that you are now required to be careful about character encodings on I/O because all strings are Unicode. My own name can be perfectly written with 7-bit ASCII, but there are many people in the world whose names require more than ASCII provides, and Python 3.x programs will work out of the box for those people. I wish everyone using a web framework to build a website would use Python 3.x and be international-ready from day 0.
As for Python 2.6.x, there are some things in Python 2.7.x that I definitely want. I find it odd that you called out 2.6 specifically.
P.S. I agree with you that Python was already pretty darn good even in 2.x.
Pascal might be underrated but it doesn't matter. There is no place for Pascal in the modern programming world.
When I went to college, Pascal was the standard teaching language. I have studied it pretty thoroughly and I understand it pretty well.
Pascal was designed as a teaching language. There are features in Pascal that are stripped-down, and I think it was just to make the teaching easier. In particular, why must all goto labels be integers rather than strings? I'd much rather write goto cleanup_after_fatal_error than goto 1000. It was a tiny bit simpler to write a Pascal compiler because of this limitation.
If you know C and really want to understand why Pascal didn't win over C, get a copy of Software Tools in Pascal. Look at all the places they had to work around limitations in Pascal, and consider how to write similar code in C. In all the cases, I realized that they simply wouldn't have had a problem in C.
C really is the king of the "third-generation languages". In its earliest form it had dangerously little type-checking, but in its modern form (where you use function prototypes so the compiler can check types) it has type checking similar to Pascal, with all the benefits that provides. And it has all the little things I appreciate, such as terminating a loop early using break. In Pascal, to terminate a loop early you needed to either clutter up the loop conditionals with an extra flag variable (early_exit or some such) or else you had to use goto to break out (with a numeric label target, of course).
"But wait," some of you are muttering. "I used to write Pascal programs and I remember using break..." No, you didn't used to write Pascal programs: you used to write Turbo Pascal programs. When Borland created Turbo Pascal they fixed all of the worst problems of Pascal, pretty much by just doing whatever C did first. I wrote a lot of Turbo Pascal and I liked it very much.
But this points out the biggest problem of Pascal: it was not well specified, and as a result it didn't work a lot of the time. Where a spec is weak, you tend to get different implementations doing different things, which is horrible for portability. The wonderful book Oh, Pascal! discusses the brokenness of the I/O in Standard Pascal, and the various ways that Pascal implementations work around the problem, and summarizes with Cooper's Law of Standards: "If it doesn't work, it doesn't stay standard."
For Pascal to have a niche, it should do something a lot better than C, for it is C that it needs to displace. But IMHO there really isn't anything it does very much better than C, and there are numerous areas where it's a non-starter unless it copies features from C.
Given the massive installed base of C, C isn't going anywhere, and that leaves no room for Pascal; Pascal does the same sort of things as C does, but not as well.
So when things are wrong a frequent reason to use such a command is used), it wastes my time to display something I didn't request and don't want to see.
When things are wrong, you don't want to see the recent log events to diagnose what went wrong?
It's a legit complaint if this display slows you down, but I'm amazed that you are so hostile to the idea. However, as a sysadmin I'm just a dilettante so I will defer to your expertise.
Citation needed? I seem to remember that X could also run as non-root before systemd.
0) Okay, I agree that I should have phrased that differently. Note that I didn't use a pejorative phrase; I didn't say something like "morons too stupid to understand the greatness of SystemD" or whatever. I really only meant to say "some people who strongly disapprove of SystemD do not want it involved in logging at all."
1) I hope you didn't intend to lump me in with "systemd people" because I'm not one. I am an interested observer looking in from the outside. To the extent that I care about Linux and its future, I care about SystemD; I've been trying to understand how good or bad it is.
But the vast majority of the criticism I have read of SystemD has been just opinion-based flaming. To read most of the posts on Slashdot, there must not be anything good about SystemD and the people who choose it must be deluded or fools or something. I wanted to push past that and understand why smart people might not reject SystemD.
for those of us that use 'sed' and 'grep'
I'm quite skilled with grep so I can query plain-text files just fine, but I'm not opposed to SystemD making a binary log with an index for its own purposes.
If you set up rsyslog or whatever, you will still get a plain-text log file, and you have the option to simply ignore SystemD's own log file.
Windows style 'Services' (your word)
No, don't lump me in as a "systemd person". And don't assume that I'm your enemy or something.
And don't ask "how are they forcing" again, that isn't helpful when I can't get just turn the package off and sysv init on.
My understanding is that SystemD makes binary logs for its own purposes, and that the binary features include indexes so it can very quickly answer queries like "what were the last ten things logged by Apache?"
However, SystemD permits continuing to run a time-tested conventional log daemon. The current recommended way to get network logging is to run rsyslog.
Some hard-core SystemD haters are still not happy, because the log events flow through SystemD on their way to the conventional log daemon.[1]
takes over vast chunks of functionality that it has no business touching
I'm not certain this really is the case. SystemD is a collection of services, and each one has a specific area of concern. The actual technical analyses I have read suggest that the basic design of SystemD is sound, and that it is doing things that people want to be done. For example, SystemD allows the graphics system (X.org) to run as a non-root user.
One criticism of SystemD that may have some validity: that the only documentation is whatever the source code contains this week. SystemD is being developed at a rapid pace and documentation may be suffering. This is one reason I am glad for projects like UselessD... they will force the SystemD interface to settle down a bit and be documented a bit better.
But I'll say it again: from what I have read (in technical analyses) the basic design of SystemD seems to be sound. The Debian technical committee that evaluated the situation concluded that SystemD was the best choice for Debian. (Then the politics blew up but that's another story.) Do you think that the Debian technical committee spent months evaluating SystemD and were just wrong about it? (That's not to say that SystemD is perfect. But something can be imperfect and still be the best choice for the future.)
makes it basically impossible to debug problems
I will not comment on this because I have no experience with SystemD yet. I have seen comments like this multiple times.
Perhaps, even if SystemD is the future, it should be adopted slowly and carefully in the present. Debian "jessie" has SystemD as optional which seems like a very good thing to me.
[1] I think that's probably an overreaction... if Red Hat can't get SystemD to reliably pass through log events, that would imply a level of brokenness that would preclude the widespread adoption that seems to be taking place.
remember when the speed would double and the cost would halve like clockwork? Those days are gone forever.
True. If you buy AMD processors, you aren't getting the fastest possible, but they will still be plenty fast enough. I built my wife's computer with an AMD FX-8350 and she's very happy with it (and I want one for myself).
And as I said, I would be happy to buy the tiny computer discussed in TFA. Sounds neat. (I'd also be happy to buy a tiny computer based on an ARM chip, but I'd rather have full Linux than just ChromeOS so I probably won't buy a "ChromeBox".)
My feelings towards big UPSes is that the battery only lasts a couple years, and costs a ton to replace.
Just make sure to buy a UPS that takes a standard battery. All my UPSes will accept a standard 12V 9ah battery (search for "UB1290") which you can get for $20 or less. I bought a six-pack from Amazon for $100 or so.
It pays to buy a decent UPS with decent status reporting. I have some old ones that I bought cheaper, and they don't report how loaded they are (they have a single "overloaded" light that lights and another single "battery problem" light). My better ones have a little bar graph for how loaded the UPS is, and another bar graph for how charged it is, plus various status lights.
My old UPSes can report status through a serial port, but my newer ones can report through USB. Again, do your homework: some UPSes use a wacky undocumented proprietary protocol, while others are just plug-and-work under Linux. (But I haven't spent any time messing with this yet.)
Also, when your UPS goes into battery fail, replace the battery right away. If you leave the battery too long, it can cook, swell up (from expanding gases I guess) and be difficult to remove from the UPS. <shifty_eyes>Not that I am speaking from experience..</shifty_eyes>
(Isn't it cute how the legal notice is embedded in an image file, so it's hard for search engines to find it?)
It really is true that Intel chips are better than AMD chips now. Intel has fixed the problems in their chips (the Pentium 4 had serious issues) and Intel is two generations ahead on semiconductor process technology.
Intel could be beating AMD fair and square, yet they still engage in the sleazy underhanded practice of making their compiler sabotage the competition.
Intel's remaining chip problems are self-inflicted: they want to maximize the dollars they extract from the customers, so they make a bunch of different chip versions, and different versions have features enabled or not. AMD is #2 and trying harder, so AMD chips always have all features enabled.
So I would be willing to buy one of these AMD-based mini PCs. It will be slower and/or consume more energy than an Intel version; but I just plain don't approve of Intel, and its performance will be adequate. I'm not going to be computing digits of pi on this thing.
P.S. The best thing I can say about Intel: they have cooperated well with the Linux kernel team, and Linux support is great for Intel chipsets including graphics accelerators.
But AMD is doing a pretty good job of cooperating with the Linux kernel guys, and I'd rather give AMD my money.
A few years ago, a relative bought a new laptop that came with Windows Vista. She asked me for help putting her QuickBooks onto it.
Her version of QuickBooks simply wouldn't run on Vista. So I went to the store to buy an upgrade. I carefully studied the feature lists on the boxes for the various versions, trying to figure out which one she needed. For $100 I got some version ("Express" or "Starter" or something like that). It had all the features she needed and was $100 cheaper than the next version.
It turned out that it was missing one key feature: it didn't support upgrading! It would have been fine for her if she had started out with it, but because she was upgrading from an old version, she had to get the $200 QuickBooks. That's right, her reward for being a long-time customer was to pay $200 instead of $100 for a version that would run on Vista. (And it really didn't say on the box that upgrading wasn't supported. I had to figure it out... when I couldn't find an "import" dialog in the menus, I searched their web site; and I found a knowledge base article that plainly spelled out that importing was a feature reserved to the $200 and above versions.)
If I ever start a home business, I'll run it on some open source system. No Intuit products for me, not ever.
Slashdot Mirror
Or you know, you could configure the ThinkPad you are buying to have a quadcore and a 3K screen.
The T440s is the "Ultrabook" form factor; it tops out at dual-core, and 1920x1080 screen size.
The T440p is the "performance" form factor, and has quad-core available, but it's thicker and heavier.
I just checked the Lenovo web site, and the T440s is discontinued. They are now on the T450s and T450p. The T450p does have a quad-core i7 option and a 3K screen option. It can also be equipped with 16 GB of RAM (vs. max 12 GB for a T440s).
I'm only recommending the ThinkPad I have. I would rather have my T440s than a MacBook Pro, but I'm not sure how well I would like a T450p (thicker and heavier; weight listed as "starting at 5.5 pounds"). Also, the top-spec T450p, if ordered directly from Lenovo, would cost more than a 15" quad-core MacBook Pro.
I think in modern science, the heavy computation is likely being done on servers rather than on laptops, so it would make more sense to go thin and light on a laptop. I'm happy with the T440s so I recommended it.
If she's spending her own money, it's hard to beat the value of a Thinkpad T440s. It's an "Ultrabook" so it's similar form factor to a MacBook Pro. Great screen, good battery life, good processor, and Linux works out of the box.
She will need to get a mini-DisplayPort to HDMI adapter, for giving presentations where there is an HDMI connection to use. The T440s has both mini-DisplayPort and VGA connectors built-in.
I have one running Linux Mint 17.1 64-bit MATE. I got the top-of-the-line one with the 1920x1080 display, which I recommend. I got mine from B&H Photo in New York; it was significantly cheaper than other web sites I checked.
http://www.bhphotovideo.com/c/product/1014801-REG/lenovo_20aq006hus_t440s_i7_4600u_8gb_256ssd_windows_7_windows_8.html
I have mine set up on a docking station, which came with its own power supply. So its power supply stays in my laptop travel bag, ready to go. Just undock and you are good to go. This is one way in which this is actually better than a Mac.
The Mac will cost $700 extra, and come with a higher-resolution display, a quad-core processor, and more RAM. That may be a better deal for her if she plans to do a whole lot of work directly on the laptop, rather than using the laptop to access remote computers.
P.S. I recommend that she take a look at the IPython Notebook, if she hasn't already. Running SciPy under IPython will be great for her.
http://nbviewer.ipython.org/gist/rpmuller/5920182
My favorite: XKCD-style plots in SciPy
http://nbviewer.ipython.org/url/jakevdp.github.com/downloads/notebooks/XKCD_plots.ipynb
Buy a Home Atmos rig
I'm not in a big hurry, and I want to see what DTS comes out with before I invest in an object-oriented sound system. Also I'm not in a hurry to bolt speakers to my ceiling and run the wires.
Now that you explained your points I don't think I disagree with you about any of the technical stuff.
I interpreted "nothing is mixed in Neural Surround" as "Neural Surround does not mix anything" which wasn't your intent. I agree that there isn't much content in Neural Surround; that press release was from 2006, and I don't know if that radio station is still doing the 5.1 broadcasts or not.
I'm a feature film sound designer and mixer, DTS is completely out of theatrical and television -- the original theater format is owned by a different company now
Correct. DTS the company split into two, and the theatre-related one changed its name to Datasat.
"optimized" for Neo:X
I think that "optimized for Neo:X" might also mean that an audio mix with height channels might have been run through a downmixer to get a suitable 7.1 mix that can be upmixed properly to 11.1. I don't know if Expendables 2 has helicopters or planes flying overhead, but if so, the people who bought height speakers might as well get some sound out of them.
"Object-oriented" audio encoding formats solve the problem in the best way: if there is a helicopter overhead, there will be an audio object tagged "overhead" and the mix can be adapted to whatever speakers the user has. If the user has height speakers, they get used. That's what I want for my living room anyway.
[DTS Neural Upmix is] marketed as a spatializing upmixer that can also decode Neural Surround (which is a third format not necessarily related to Neo:X).
No, there is no "Neural Surround" format as such. Neural Downmix uses phase encodings and the output is just an audio stream (can be analog, saved as a wave file, saved as DTS Master Audio, saved as MP3, etc.).
Look at this PDF. There are two columns: one shows different disk formats and how many bits per second each one needs; the other column has one thing in it, Neural Surround. This is because Neural Surround isn't a format as such.
http://www.dts.com/~/media/d5aad4e0d179439c8588ac3b61e37444/DTS_Broadcast_infosheet.pdf
See also this press release. A radio station was broadcasting in 5.1 using Neural Surround... broadcasting in ordinary stereo FM as well as HD radio. Anyone could listen in stereo, but those with Neural Upmix in their stereo receivers could hear 5.1 sound.
http://www.prnewswire.com/news-releases/wguc-fm-begins-51-broadcasting-with-neural-surroundtm-56267632.html
But this feature is sorta incidental, as literally nothing is mixed in Neural Surround.
I'm sorry but you are completely mistaken on this point. Let's look at the DTS web site again:
http://www.dts.com/professionals/sound-technologies/audio-processing/dts-neural-surround.aspx#downmix
Note the phrase "pristing Lt/Rt stereo mix" and the concerns about comb filtering in the output mix. There is mixing going on here.
DTS Neural Downmix produces a stereo output stream which may be saved in any format. You can feed the result to DTS Neural Upmix, even as an analog waveform, and it will upmix using the encoded signals. There is no disk format for "DTS Neural Surround" as such.
My understand is that the height channels are encoded sum-and-difference with the main L-R channels, and a special decoder reads reads additional channel data to subtract out the height channels from the mains.
I think it is possible that there is some additional metadata embedded in the DTS Master Audio bitstream, because old DTS decoders do understand metadata tags and will ignore them. But there is no bitstream change from plain DTS 7.1 to DTS 11.1, and you can play the 11.1 stream on an old DVD player and you will get 7.1 out. (Just like you could play Dolby Surround on a stereo and get stereo out, if you didn't have the Dolby Surround decoder to upmix from stereo to surround.)
If you are still convinced that DTS 11.1 has additional discrete channels, please find a reference and show me. If I'm wrong, I'm wrong, but I think the DTS web page I referenced in the previous post backs me up.
By "actual format" I mean its a communications channel where the sender and recipient agree on what goes into the channel and what is supposed to come out.
Then I would say that DTS 11.1 is an actual format exactly the way Dolby Surround was an actual format. Both rely on specific, agreed-upon phase encodings
There's a fundamental difference between an encoded mix and an upmixer. Dolby Surround is intended to be decoded from 2 tracks into LCRS, the filmmakers mixed the film in Dolby Stereo and were listening to the surrounds so they know what's in them. The phase encoding is part of the channel spec.
I'm with you so far.
An upmixer takes a stereo or 5.1 mix and applies effects to it to make it sound like it was mixed in a wider format, but there's nothing really being decoded, it's just synthesizing or guessing what should be in the additional channels using heuristics, all-pass filters, delays, crossover networks and other stuff that sounds cool or "provide a good experience" but, in fact, interfere with the filmmaker's intent.
The original Dolby surround and DTS Neural Upmix can both be applied to any stereo recording and some sort of upmix will occur, but both were designed to be used with a mix that was intended to be upmixed. DTS also sells DTS Neural Downmix which can take a 5.1 or 7.1 stream and output stereo with intentionally encoded signals that decode back to 5.1 or 7.1 sound.
When DTS Neural Upmix is working from a stereo signal that was made using DTS Neural Downmix, you get a really clean surround sound with no leakage. I used to listen to the multichannel recording of "Money" by Pink Floyd, and the cash register and coin sound effects very cleanly came from all the different directions like the original multichannel mix.
Again, you can't fit 8 kilos of flour into a 2-kilo sack, so 7.1 audio sent through downmix, then upmixed back to 7.1, can never perfectly reproduce the original multichannel recording. But I was impressed by just how well it did.
Despite the name "Neural Upmix", it is designed to work with phase-encoded signals intentionally mixed using Neural Downmix.
Neural Upmix is an upmixer, DTS Neo:X is an actual format that decodes an 11.1. Neo:X home receivers also employ upmixing, mainly because no films are mixed in 11.1 Neo:X, it's a surround audiophile format, and it needs to do an upmix in order to justify people spending money on it.
My understanding is that DTS 11.1 audio uses intentionally encoded signals for the height channels, but the on-disk format is DTS Master Audio 7.1 (no additional discrete channels).
Just as the original Dolby surround could be listened to in stereo if you didn't have surround speakers, the 11.1 mix can be listened to in 7.1 if you don't have height speakers; in both cases, the downmix process is supposed to not add anything objectionable.
I don't know what you mean by "DTS 11.1 is an actual format"... if you mean that it has 12 discrete channels, I believe you are mistaken on this point.
Here's how DTS describes the 11.1 system:
From the "How it works" tab on this page:
http://www.dts.com/professionals/sound-technologies/audio-processing/dts-3d-audio.aspx
"without changing the delivery chain": no new audio format, disks play fine on older DTS decoders
"no audible leakage": there's no problem with leakage if you have discrete channels; if we are even talking about leakage, we are talking about an upmix.
I don't believe Imade any mistakes in my original post.
binaural = stereo
Actually in the audio world, "binaural" is used to specifically mean a recording intended for being played directly into the ears.
I was once present for a binaural recording session. The guy doing the recording had brought a fake human head, and the two microphones for the recoding were positioned in the two ears. The idea was to reproduce as fully as possible what you would have heard if you had been sitting in that spot in the room, with your head in that position.
You can listen to a binaural recording on speakers of course, but for the best experience you should use headphones.
For the absolute best experience, the recording should use a fake head that is exactly like your head. Not many people are ever going to experience that.
http://en.wikipedia.org/wiki/Binaural_recording
Audio can do funny things as it travels around your head. For the absolute best 3D experience with headphones, you want to measure what happens to audio around your head; this is called your "Head-Related Transfer Function" or "HRTF". Instead of recording the audio with a fake head shaped just like yours, companies can just record a good 5.1 or 7.1 recording, and then you can mix that down to a binaural stereo mix that is perfect for your head if you have your HRTF. According to the article the AES is standardizing a file format for HRTF data, so that the software you get will be more likely to be able to work with your HRTF data if you have it measured.
The ultimate in VR audio will be headphones with motion tracking, and real-time mixing that uses your HRTF and changes the mix as you turn your head. If something is supposed to be coming from your left, and you turn your head to the left, that sound should get louder; then if you turn your head away from it, it should get quieter. If this is done right it should be incredible. People have been working on this for years and I'm sure someone somewhere has done it right, but I haven't seen any commonly available products to do it yet.
But with VR goggles you should totally have VR audio like I described above. It would be really immersive.
3d audio = surround sound (5.1/7.1/8.1/etc)
Pretty much, 3D audio is intended to include speakers above the plane of the 5.1 or 7.1 speaker setup; the industry calls these "height speakers". DTS 11.1 audio, for example, has a standard 7.1 setup, and then 4 height speakers: two in the front and two in the back.
The current ultimate in 3D audio is a 22.2 setup, where the ceiling has a 3x3 array of speakers, there are speakers at mid height, and there are speakers at ground level. However, IMHO there is zero chance that 22.2 will catch on as an audio standard.
Before the 5.1 and 7.1 digital standards, there was Dolby Surround that was encoded within a stereo soundtrack. A simple audio mixer could "upmix" from stereo to surround. DTS Neural Upmix can make a very clean 7.1 from a stereo signal, and it works from an analog signal (it's not something tricky inside a digital encoded format). You can't get 8 kilograms of flour into a 2-kilo bag, and Neural Upmix 7.1 can't completely reproduce the same mix as you can play through 8 discrete channels, but it can provide a good experience.
DTS 11.1, as I understand it, uses technology similar to DTS Neural Upmix to encode the 4 "height" channels within the other 7.1 channels. Turning 7.1 into 11.1 should be a lot easier than turning 2.0 into 7.1 so it should provide a good experience.
I expect the industry to go to "object oriented" audio. This means that audio will have metadata tags saying what direction the audio is coming from, and then a real-time mixer upmixes from the digital format with the metadata tags to whatever mix you need (i.e. if you have 11.1 speakers you get an 11.1 mix, if you actually have 22.2 speakers you get that, if you have 7.1 you get that, etc.) I believe Dolby Atmos works this way, and I believe DTS
Despite my mentioning the Cree 4FLOW, I still recommend buying Cree's more-expensive but better-made bulbs. The 4FLOW costs less, but it has a much shorter warranty and isn't nearly as well made.
The 4FLOW would be perfect for a light inside a closet that's rarely turned on, but then if it's rarely turned on you might as well leave the incandescent bulb in there until it burns out.
I had a similar experience with fluorescents. I replaced most of the ordinary light fixtures in my home with special fixtures with a circular fluorescent bulb (not "compact fluorescent"). I liked the quality of the light and I figured I'd be saving electricity.
Then the fixtures started burning out. Sometimes it would just be the bulb, but usually it was the whole fixture. At first I replaced the fixture with another (at $20 per fixture), but eventually I decide it was stupid and I started replacing the fluorescent fixtures with ordinary fixtures that take standard bulbs. At the time I installed compact fluorescents. And of course the compact fluorescents, which would be easy to replace if they die, never die. (I don't care, I'm replacing them with LEDs anyway.)
As for avoiding burning your house down, I suggest you do as I do: buy Cree products. I get the top of the Cree line, the "TrueWhite" bulbs, but they have new "4FLOW" bulbs that cost less and run very cool.
The cheapest LED bulbs will be like the cheapest anything electronic: made at some random factory in China with possibly bad quality control and even possibly bad safety. Sounds like you had the bad luck to get a bad bulb. Sometimes it's worth it to pay a bit more for a name brand.
waiting for a good price point
I don't know how much these cost where you live, but where I live I can get LED bulbs at Home Depot from $6 to $20 depending on quality and brightness. They have an expected lifetime of 20+ years, and I don't have to change the light in that time. To me, this is a no-brainer and I've been buying LEDs for my whole house.
In fairness, I know that the power company where I live is subsidizing the bulbs, and absent the subsidy they would cost more. But it seems likely that you might be able to buy subsidized bulbs where you live too.
Also, I just checked the EarthLED web site, and without asking me where I live, the site showed me a deal: $100 for a 20-pack of LED bulbs. I've never heard of the brand ("Euri") but surely you could pay $5 per bulb for something that will last so long?
I like the Cree TrueWhite bulbs and I pay extra for them. LED bulbs tend to be a bit too yellow, so Cree developed a "notch filter" that takes out some of the yellow from the light, correcting the color. But now the light is a bit dimmer since some was taken out; so Cree puts a few extra LED modules into the bulb. Result: same amount of light, better color, consumes a little more power but not too much more.
I have also replaced all the 48-inch fluorescent fixtures in my home with Cree Linear LS4 fixtures at 3500K color temperature. Wow, it's so much nicer light and completely silent. Totally worth it.
If you are using incandescent bulbs, and you replace your most-commonly-used ones with LED bulbs, you will save enough money on electricity to pay for the new bulbs within a reasonable time. If you already have compact fluorescent bulbs, and you don't mind their light, then LEDs aren't guaranteed to pay for themselves right away and it might make sense to keep waiting. Otherwise, go for it.
It's interesting the headphone jack is still there since bluetooth chips are so cheap, easy to use, and are smaller than the headphone jack itself. I guess the problem for wireless headphones is powering them requires too many batteries.
Current Bluetooth headsets require the audio stream to be compressed using lossy compression. If you want the best audio quality, you buy nice headphones and plug them into the analog jack.
According to a post on soundexpert.org, Bluetooth audio has 721 kbps bandwidth. That's bits, not bytes. Thus the requirement for lossy compression.
Unless Bluetooth becomes able to carry FLAC or Apple Lossless with at least 2 channels at CD quality, the headphone jack is still essential.
And as you noted, Bluetooth means battery hassles while wired headphones always work.
Don't forget:
Overdrawn at the Memory Bank
2.1 out of 10 on IMDB.
On the other hand, I rather liked the adaptation of The Lathe of Heaven.
From TFA:
Who exactly are "clean power foes"?
This seems like using an epithet to delegitimize others.
I'm sure there are people who oppose this project for stupid reasons, like "it'd ruin the view". But I am equally sure that absolutely nobody opposes this project because it is too clean.
I suppose that if you looked and looked, you could find someone who is so certain that an ice age is coming that he wants all power generated by burning stuff. But even this imaginary guy isn't really a foe of clean power, he's just a fan of carbon dioxide.
If you want a really awesome chemistry set, you can buy one:
http://hms-beagle.com/heirloom-chemistry-set/
This was a KickStarter project. He was trying to raise $30K and he raised almost five times that much.
https://www.kickstarter.com/projects/1742632993/heirloom-chemistry-set
If you can't afford the full set, contact the store; the web page says they can sell any subset of the kit.
Hmm, if I ever make it to Kansas City I will try to go check out the H.M.S. Beagle science store.
How about a one-button waterproof cell phone?
I've read about phones where you program which number the phone calls, but I can't find any now. Maybe they are no longer sold.
But here's a phone that calls some sort of operator, who can then decide how to handle the situation. You need to pay a monthly fee for the operator but I think that's better for a 2-year-old than a phone that just dials 911.
http://www.greatcall.com/products/greatcall-splash
If you could find a 1-button programmable phone, and program it to call you, that might be ideal.
IMHO, the sooner the world standardizes on Python 3.x, the better. It contains numerous small improvements, no one of which is invaluable, but together which add up to a better language.
As for print as a statement, I only miss that for interactive use, and you can assuage the issue by using ipython with the --autocall feature enabled. And I like the simple way you can now control how the output is formatted and where it goes, and you can re-bind the name print to completely hook the behavior of printing. Overall it's a win.
The big shocking change is that you are now required to be careful about character encodings on I/O because all strings are Unicode. My own name can be perfectly written with 7-bit ASCII, but there are many people in the world whose names require more than ASCII provides, and Python 3.x programs will work out of the box for those people. I wish everyone using a web framework to build a website would use Python 3.x and be international-ready from day 0.
As for Python 2.6.x, there are some things in Python 2.7.x that I definitely want. I find it odd that you called out 2.6 specifically.
P.S. I agree with you that Python was already pretty darn good even in 2.x.
Pascal might be underrated but it doesn't matter. There is no place for Pascal in the modern programming world.
When I went to college, Pascal was the standard teaching language. I have studied it pretty thoroughly and I understand it pretty well.
Pascal was designed as a teaching language. There are features in Pascal that are stripped-down, and I think it was just to make the teaching easier. In particular, why must all goto labels be integers rather than strings? I'd much rather write goto cleanup_after_fatal_error than goto 1000. It was a tiny bit simpler to write a Pascal compiler because of this limitation.
If you know C and really want to understand why Pascal didn't win over C, get a copy of Software Tools in Pascal. Look at all the places they had to work around limitations in Pascal, and consider how to write similar code in C. In all the cases, I realized that they simply wouldn't have had a problem in C.
Also, after writing the above book, Brian Kernaghan wrote an essay Why Pascal Is Not My Favorite Programming Language and if you have rose-colored glasses for Pascal I suggest you read it.
C really is the king of the "third-generation languages". In its earliest form it had dangerously little type-checking, but in its modern form (where you use function prototypes so the compiler can check types) it has type checking similar to Pascal, with all the benefits that provides. And it has all the little things I appreciate, such as terminating a loop early using break. In Pascal, to terminate a loop early you needed to either clutter up the loop conditionals with an extra flag variable (early_exit or some such) or else you had to use goto to break out (with a numeric label target, of course).
"But wait," some of you are muttering. "I used to write Pascal programs and I remember using break..." No, you didn't used to write Pascal programs: you used to write Turbo Pascal programs. When Borland created Turbo Pascal they fixed all of the worst problems of Pascal, pretty much by just doing whatever C did first. I wrote a lot of Turbo Pascal and I liked it very much.
But this points out the biggest problem of Pascal: it was not well specified, and as a result it didn't work a lot of the time. Where a spec is weak, you tend to get different implementations doing different things, which is horrible for portability. The wonderful book Oh, Pascal! discusses the brokenness of the I/O in Standard Pascal, and the various ways that Pascal implementations work around the problem, and summarizes with Cooper's Law of Standards: "If it doesn't work, it doesn't stay standard."
For Pascal to have a niche, it should do something a lot better than C, for it is C that it needs to displace. But IMHO there really isn't anything it does very much better than C, and there are numerous areas where it's a non-starter unless it copies features from C.
Given the massive installed base of C, C isn't going anywhere, and that leaves no room for Pascal; Pascal does the same sort of things as C does, but not as well.
So when things are wrong a frequent reason to use such a command is used), it wastes my time to display something I didn't request and don't want to see.
When things are wrong, you don't want to see the recent log events to diagnose what went wrong?
It's a legit complaint if this display slows you down, but I'm amazed that you are so hostile to the idea. However, as a sysadmin I'm just a dilettante so I will defer to your expertise.
Citation needed? I seem to remember that X could also run as non-root before systemd.
http://hansdegoede.livejournal.com/14268.html
The main problem with systemd is that it is beeing pushed onto and by the mayor distributions without fixing the problems first.
Makes sense to me. I'm glad that Debian did the work to leave SystemD as optional.
0) Okay, I agree that I should have phrased that differently. Note that I didn't use a pejorative phrase; I didn't say something like "morons too stupid to understand the greatness of SystemD" or whatever. I really only meant to say "some people who strongly disapprove of SystemD do not want it involved in logging at all."
1) I hope you didn't intend to lump me in with "systemd people" because I'm not one. I am an interested observer looking in from the outside. To the extent that I care about Linux and its future, I care about SystemD; I've been trying to understand how good or bad it is.
But the vast majority of the criticism I have read of SystemD has been just opinion-based flaming. To read most of the posts on Slashdot, there must not be anything good about SystemD and the people who choose it must be deluded or fools or something. I wanted to push past that and understand why smart people might not reject SystemD.
for those of us that use 'sed' and 'grep'
I'm quite skilled with grep so I can query plain-text files just fine, but I'm not opposed to SystemD making a binary log with an index for its own purposes.
If you set up rsyslog or whatever, you will still get a plain-text log file, and you have the option to simply ignore SystemD's own log file.
Windows style 'Services' (your word)
No, don't lump me in as a "systemd person". And don't assume that I'm your enemy or something.
And don't ask "how are they forcing" again, that isn't helpful when I can't get just turn the package off and sysv init on.
In Debian "jessie" you can do just that.
https://wiki.debian.org/systemd#Installing_without_systemd
systemd insists on binary logs
My understanding is that SystemD makes binary logs for its own purposes, and that the binary features include indexes so it can very quickly answer queries like "what were the last ten things logged by Apache?"
However, SystemD permits continuing to run a time-tested conventional log daemon. The current recommended way to get network logging is to run rsyslog.
Some hard-core SystemD haters are still not happy, because the log events flow through SystemD on their way to the conventional log daemon.[1]
takes over vast chunks of functionality that it has no business touching
I'm not certain this really is the case. SystemD is a collection of services, and each one has a specific area of concern. The actual technical analyses I have read suggest that the basic design of SystemD is sound, and that it is doing things that people want to be done. For example, SystemD allows the graphics system (X.org) to run as a non-root user.
One criticism of SystemD that may have some validity: that the only documentation is whatever the source code contains this week. SystemD is being developed at a rapid pace and documentation may be suffering. This is one reason I am glad for projects like UselessD... they will force the SystemD interface to settle down a bit and be documented a bit better.
But I'll say it again: from what I have read (in technical analyses) the basic design of SystemD seems to be sound. The Debian technical committee that evaluated the situation concluded that SystemD was the best choice for Debian. (Then the politics blew up but that's another story.) Do you think that the Debian technical committee spent months evaluating SystemD and were just wrong about it? (That's not to say that SystemD is perfect. But something can be imperfect and still be the best choice for the future.)
makes it basically impossible to debug problems
I will not comment on this because I have no experience with SystemD yet. I have seen comments like this multiple times.
Perhaps, even if SystemD is the future, it should be adopted slowly and carefully in the present. Debian "jessie" has SystemD as optional which seems like a very good thing to me.
[1] I think that's probably an overreaction... if Red Hat can't get SystemD to reliably pass through log events, that would imply a level of brokenness that would preclude the widespread adoption that seems to be taking place.
Huh, I didn't think that was a troll when I wrote it. But it has been modded as Troll twice now.
Well, I really do prefer to give my money to AMD and I really would buy the fanless mini-PC in TFA.
remember when the speed would double and the cost would halve like clockwork? Those days are gone forever.
True. If you buy AMD processors, you aren't getting the fastest possible, but they will still be plenty fast enough. I built my wife's computer with an AMD FX-8350 and she's very happy with it (and I want one for myself).
And as I said, I would be happy to buy the tiny computer discussed in TFA. Sounds neat. (I'd also be happy to buy a tiny computer based on an ARM chip, but I'd rather have full Linux than just ChromeOS so I probably won't buy a "ChromeBox".)
My feelings towards big UPSes is that the battery only lasts a couple years, and costs a ton to replace.
Just make sure to buy a UPS that takes a standard battery. All my UPSes will accept a standard 12V 9ah battery (search for "UB1290") which you can get for $20 or less. I bought a six-pack from Amazon for $100 or so.
It pays to buy a decent UPS with decent status reporting. I have some old ones that I bought cheaper, and they don't report how loaded they are (they have a single "overloaded" light that lights and another single "battery problem" light). My better ones have a little bar graph for how loaded the UPS is, and another bar graph for how charged it is, plus various status lights.
My old UPSes can report status through a serial port, but my newer ones can report through USB. Again, do your homework: some UPSes use a wacky undocumented proprietary protocol, while others are just plug-and-work under Linux. (But I haven't spent any time messing with this yet.)
Also, when your UPS goes into battery fail, replace the battery right away. If you leave the battery too long, it can cook, swell up (from expanding gases I guess) and be difficult to remove from the UPS. <shifty_eyes>Not that I am speaking from experience..</shifty_eyes>
I wonder, though, if the benchmarks were made using code compiled with an Intel compiler.
http://yro.slashdot.org/story/05/07/12/1320202/amd-alleges-intel-compilers-create-slower-amd-code
Oh, but surely by now they have stopped doing it? Nope:
https://software.intel.com/en-us/articles/optimization-notice
(Isn't it cute how the legal notice is embedded in an image file, so it's hard for search engines to find it?)
It really is true that Intel chips are better than AMD chips now. Intel has fixed the problems in their chips (the Pentium 4 had serious issues) and Intel is two generations ahead on semiconductor process technology.
Intel could be beating AMD fair and square, yet they still engage in the sleazy underhanded practice of making their compiler sabotage the competition.
Intel's remaining chip problems are self-inflicted: they want to maximize the dollars they extract from the customers, so they make a bunch of different chip versions, and different versions have features enabled or not. AMD is #2 and trying harder, so AMD chips always have all features enabled.
So I would be willing to buy one of these AMD-based mini PCs. It will be slower and/or consume more energy than an Intel version; but I just plain don't approve of Intel, and its performance will be adequate. I'm not going to be computing digits of pi on this thing.
P.S. The best thing I can say about Intel: they have cooperated well with the Linux kernel team, and Linux support is great for Intel chipsets including graphics accelerators.
But AMD is doing a pretty good job of cooperating with the Linux kernel guys, and I'd rather give AMD my money.
A few years ago, a relative bought a new laptop that came with Windows Vista. She asked me for help putting her QuickBooks onto it.
Her version of QuickBooks simply wouldn't run on Vista. So I went to the store to buy an upgrade. I carefully studied the feature lists on the boxes for the various versions, trying to figure out which one she needed. For $100 I got some version ("Express" or "Starter" or something like that). It had all the features she needed and was $100 cheaper than the next version.
It turned out that it was missing one key feature: it didn't support upgrading! It would have been fine for her if she had started out with it, but because she was upgrading from an old version, she had to get the $200 QuickBooks. That's right, her reward for being a long-time customer was to pay $200 instead of $100 for a version that would run on Vista. (And it really didn't say on the box that upgrading wasn't supported. I had to figure it out... when I couldn't find an "import" dialog in the menus, I searched their web site; and I found a knowledge base article that plainly spelled out that importing was a feature reserved to the $200 and above versions.)
If I ever start a home business, I'll run it on some open source system. No Intuit products for me, not ever.