It's a quiet evening in my office at the respected media empire of "Fair and biased, inc". My editor and I are discussing ideas for a great story. "You know", says the respected journalist of 96 years, "I'm hearing a lot about Bitcoin these days, it's some new currency or whatnot. Why don't you see if you can interview the creator, Satoshi Nakamoto?"
That's complete claptrap. Yes, very recent (last 5-10 years) widget toolkits have started to force use of features that result in bitmaps being sent across the network, but that's hardly a reason to throw out X. And it's essentially a lie to pretend it means, somehow, that X11 doesn't have network transparency.
I find it pretty bad, to be honest, that the same devs who are protesting that X11's network transparency isn't what it could be are:
1. The devs that did this in the first place, refusing to advance the protocol to include the features that GTK3 et al required.
2. Apparently think the solution is getting rid of network transparency altogether.
I'm staggered, to be honest, by the whole thing. I appreciate old code is sometimes awkward to support, but the solution isn't a wholesale replacement of the project. Mozilla's developers may have made many mistakes in their decision to throw out the Netscape code that delayed the release of a great browser for many years, but they were NEVER, NEVER so stupid as to say "Well, we looked at the Netscape source code, and we think the solution is to get rid of HTML. It's too kludgy! I mean, just look at it, it's impossible to add features to it cleanly!"
If we were talking about a rewrite of X.org, nee XFree86.org, nee X86, that'd be one thing. It's probably necessary by now although I'd still say they need to seriously think in terms of refactoring the project. But throwing out the entire protocol because they refused to add the features necessary to make the protocol efficient? Fuck that.
It's hard to see why anyone with an interest in Linux would want us to move away from X11 to an unstable untried display system that will be missing features by design, simply because some X11 developers feel that the core X.org server has a lot of cruft in it.
Wayland will look elegant to those programmers until the day they start adding the missing features. It'll be far more crufty and inefficient than X.org long before it ends up being feature complete. That's how programming works.
Once you have "an ecosystem of roads" as you suggest which is maintained by road fees and requires public access so you can get to all places you want to go, you have just reimplemented government owned public infrastructure under a different name
Nonsense. In the libertarian utopia, the network of roads is a monopoly owned by someone else with no accountability or democratic input. Hooray!
I believe all Galaxy devices are capable of connecting to 2G towers. So assuming the message can be transmitted via 2GSM, the sophisticated hacker (I assume) would need to spoof such a tower at a time when the targetted phone would need to avoid 3G for some reason (say, lack of signal or too poor a signal)
In Japan, MtGox is not liable because bitcoins aren't money
Couldn't one say the same about most any fiat currency
No. One couldn't. You see, a fiat currency, that is, a currency by fiat, is money by law. In fact, "currency by fiat" and "money by law" consist of a sequence "X by Y" where X is represented by synonyms of the same concept ("money", "currency") and Y is represented by synonyms of the same concept ("fiat", "law")
Let me understand this correctly. You found Comcast's DNS isn't perfect and doesn't resolve some names. It does not appear to be malicious in any way, as the two domains you find affected are a foreign furniture store, and your friend's brand new website. It's fairly obviously a bug.
So: you call Comcast Tech support, demand to talk to the Boss of Comcast, and then write a 10,000 word article (I didn't count) about it on Slashdot where you know 90% of the readers will take "Websites inaccessible on Comcast" as meaning "OUT OF CONTROL MEGACORP MONOPOLIST COMCAST IS CENSORING WEBSITES!!!"
This makes sense to you? This is what you do? Really? Really?
Just curious, but that time you got a duff cable modem and had to send it back, did you write a 60,000 article on how Comcast has banned you from the Internet, and did you demand to speak to the PRESIDENT OF THE INTERNET? When it rained that one time and you attempted to tune in the cable TV, only to find many of your channels were inaccessible, did you write a 75,000 word article on how COMCAST IS DROPPING CHANNELS and did you call tech support demanding to talk to THE LORD HIGH RULER OF TV?
I think I've found an article where the discussion would be likely improved for once if the Betoddlers spammed it with anti-Beta comments.
Then they become the person that a sexist guy cites as his "female friend" that backs up his sexist theories that get perpetuated to the next generation.
Which is, if you think about it, is rather evil.
I think the bar for being "evil" seems to have been lowered quite remarkably in that case. It used to involve, at the very least, cruelty and malice. Now, apparently, it's posting some terms and conditions about the use of your services when those services are pretty much optional and when the terms and conditions are more about protecting consumers from brand confusion ("Oh, I'll just buy this Google Play tablet. (One hour later, at home, after cash spent) Wait, it doesn't run half my apps because it's actually just a "compatible" Android-like operating system rather than the real deal?") than they are about Google making money.
Points to note:
- Android is still FOSS
- Google Play is optional. Sure, Google are doing everything they can to encourage you to use it and encourage developers to build stuff on it, but it's not necessary
- Google does not sell Google Mobile Services. And the chump-change it makes in terms of compatibility testing barely pays for the services it covers.
- While Google makes some money from the various stores they sell, between bandwidth costs, transaction processing, etc, nobody out there believes it's a significant source of revenue.
- Finally, until GMS, people were screaming at Google about "Fragmentation". Even today, Android bashers still insist on posting highly misleading pie-charts showing how many different versions of Android are still in use vs iOS.
We can scream at Google when they insist that versions of Android bundled with GMS must no longer allow users to install apps via third parties. Until then, faced with a choice between "Google are doing this because they want control of teh users", and "Google are doing this because they want manufacturers to stop fucking up", we'll go with the former.
Nah, PHP still is used for those things. It shouldn't. The fucking language should DIE. But it's still there. It spreads like a virus, people get exposed to it because they're forced to hack their Wordpress distribution, and the next thing you know they're thinking it's "pretty cool".
Visual Basic was never this bad.
I think the person the questioner was talking to was a tad out of touch. And we see that regularly on Slashdot with people absolutely convinced that $TECHNOLOGY is never used because they don't see it used in their circle of technology acquaintances.
The four most commonly used platforms right now are LAMP with PHP (not Perl, not Python, Goddamnedfuckingawful PHP), JEE,
LAMP is generally used for a lot of new projects that end up phenomenally successful but start as essentially hacks where someone wanted something and didn't know much about coding, but knew enough PHP to put something together that did what they needed.
Objective C on iOS and Java on Android are, obviously, the two major mobile platforms. And C++ is used on Windows because it's what was, until recently, the only standard Windows platform and a large number of Windows developers are still wary of
Even outside of the golden seven, we have languages like C that still serve a critical purpose in some domains such as kernel level systems software. And what remains is mostly a set of platforms that aren't "legacy", just not as popular. Python, Perl, node.js, Coldfusion (another platform I'd wish would die already, even more than PHP), Ruby, and others.
Legacy? I guess nobody's doing new COBOL development to the best of my knowledge, or new Fortran. Some would dearly like Adobe Flash to be legacy, but until a viable cross-platform DRM scheme gets added to HTML5, I don't see it going away.
Congratulations. You're the fourth (fifth, if we count hypothetical Nakamoto) person (maybe more, if we assume the moderators currently modding me back down also share the same misconception) who seems to have no understanding of how the Internet works and what the effect is has on privacy.
You are correct that logging, by itself, makes no difference. But logging is one of the key components of Bitcoin that destroys the ability to be genuinely anonymous on it. For more details, I suggest you read the response I made to the second of your sibling posts. But essentially, to re-iterate, the more you use a wallet, the more information "leaks" about you because the logging exists, is public, and will, from time to time, involve you making transactions with people who know you. Without the use of an extremely trustworthy Bitcoin laundering service, it will be the case that ultimately any well connected retailer or employer can find out what you've been spending your money on.
Comparing it to posting AC on Slashdot is inane and absurd. Indeed, even posting under a pseudonym on Slashdot, as I do, grants me more privacy than my attempting to use Bitcoin to buy both Samizdat and food.