Forgot your password?
typodupeerror

Comment: Re:Touch Server (Score 1) 681

If you have access, look at it over the last 6-7 years, it is brutal. Make sure you get installed rather than sales, MS keeps commissioning reports that somehow manage to not count Google, Facebook, Baidu, Tencent etc etc's servers. Not sure why though. :)

I can name a few possible scenarios, and I'll let you decide:

  • Ballmer had a notoriously short fuse and the company would rather pay for what he wanted to hear, not what they needed to hear.
  • Gartner, Forrester, et al were a bit intimidated by the piles of bodies in the C-level offices with gunshot wounds in them, and they liked the money.
  • Microsoft-commissioned reports aren't intended for market research, but rather publicity and their own marketing purposes. They don't publicize the ones they commission for actual research, because it's not pretty (especially since Windows 8/Server 2012).

Comment: Re:term limits don't matter (Score 2) 247

by baldass_newbie (#47204497) Attached to: Mayday Anti-PAC On Its Second Round of Funding

Bingo. If there are millions of dollars in subsidies at stake or a multi-million dollar firm, paying a bunch of lawyers to take a bunch of lawyer-politicians to dinner and on vacations.

Force Congress to work securely from their respective state houses (make the lobbyists travel if they want to influence) and simplify the tax code (a recommendation of the President's Simpson-Bowles commission which only the GOP has embraced) and you'll go a long way to limit influence.

Comment: Re:Fsck x86 (Score 1) 230

BTW x86 32-bit doesn't run on x86_64 either. The software and chips have emulation routines that allow it to happen. The same as happens with A64 that allows old A32 and T32 instructions to still run on the same chip.

Disregarding built-in microcode that converts CISC instructions into simpler RISC-like operations, this statement is not accurate. All x86-64 processors have the same native 32-bit registers and instructions that the original 386 had (some may be deprecated, but IIRC there is 100% compatibility). No hardware emulation is being done.

You may be confusing the virtual memory translation scheme (Wow64) that Windows uses to run 32-bit processes in Windows x64. Yes, there is some slight overhead, but it isn't considered to be emulation.

Comment: Re:What about PHP on the JVM? (Score 5, Funny) 213

by baldass_newbie (#47106481) Attached to: PHP Next Generation

"Yes, that's just what the world needs: the rigorous code quality of PHP combined with the high performance and lightweight Java Virtual Machine."

Fortunately, I had already swallowed my coffee so the keyboard was safe.
However, your point is valid. Just because you can theoretically run something on something doesn't mean it's a good idea.
Anyway, I need to get back to writing a JVM in VBA. This is going to be the tits.

Comment: Re:It's not a privacy policy (Score 2) 221

Moreover what about Terms of Use for the other content? I have not read the LG ToU, but it could be something as simple as 'hey we need to pass this information on and we will store it on your TV for you so you can use Netflix, iPlayer, etc. but we won't receive or store anything.'

Without a copy of the agreement, it's hard to tell how nefarious this is.

Comment: Re:Coded language? (Score 3, Insightful) 475

by Cornelius the Great (#47008929) Attached to: Comcast Predicts Usage Cap Within 5 Years

A free market presumes competition, and it presumes regulation against perverse incentives. Neither are the case here... That strongly implies that they have no leg to stand on when they argue 'free markets' to bypass regulations being imposed on their networks.

I think you're restating what parent wrote (only in more detail):

Make the market free so there is someplace else to go

I believe we're all in agreement that cable companies clamoring for "free market" are hypocrites, as there has never really been a free market for communication service providers, and it's amusing (yet sad, since it's often effective) to see the rent seekers that cry "free market" and "deregulation" only when it benefits them. Govt-subsidized and sanctioned monopolies and duopolies aren't capitalism, and neither is the collusion that results when the barrier to entry is so large due to these monopolies.

If they really want a "free market" and "deregulation", then they shouldn't be opposed to more open (unlicensed) spectrum, rather than allowing the FCC to auction frequency blocks off to the highest bidder. They also shouldn't ask for public handouts to "build rural infrastructure" and then completely renege on their contractual obligations through legal loopholes and shell games.

Comment: Re:Using C++11 and STL in Embedded (Score 1) 435

by Cornelius the Great (#46880495) Attached to: C++ and the STL 12 Years Later: What Do You Think Now?

Personally, I don't like auto_ptr and would avoid the smart pointers. They are really cool in trivial applications but it is as easy to screw up mem management with auto_ptr as it is with naked pointers in more complicated situations (IMO YMMV).

I was with you until this. Having worked on large C++ with and without smart pointers and seeing the differences between the memory leaks firsthand has made me a believer in using smart pointers.

There are shortcomings of the commonly taught RAII approach when handling raw pointers, mostly having to do with ambiguity of pointer ownership. Maybe not the auto_ptr itself (which has now been made deprecated in favor of unique_ptr due to having stricter move/copy semantics), but the smart pointers in Boost and C++11 are very strict about who owns the data in question. There are other things smart pointers can fix (such as automatic cleanups/refcount decrements with stack unwinding, which addresses leaks caused by unexpected thrown exceptions).

Hell, simply having a ref-counted pointer that handles its own cleanup is a great way to ease developers who only have previous experience with garbage-collected languages into C++ development without introducing a ton of memory leaks or dangling pointers everywhere- not an ideal solution, but this crutch has saved us from many potential horrors introduced by senior developers who have only used C# or Java previously (yes, this is quite common today).

You can measure a programmer's perspective by noting his attitude on the continuing viability of FORTRAN. -- Alan Perlis

Working...