The devs with the bugs aren't my devs. I wouldn't have told them to use.Net.
I have no reason to distrust the devs with the bugs. I also have no reason to implicitly trust that.Net does not have bugs. Therefore their testimony that it's a.Net bug is valid.
I'd be an idiot and a sucker to believe you when you have no first-hand knowledge of the problems encountered.
Fox News was founded by Reagan apparatchiks. It's owned by Rupert Murdoch. It donated money to the RNC.
I wouldn't even know where to go to get the employee records needed to make the counts you imply someone's made.
As for "comments I have seen online", I used the word "astroturfing" in my OP. And I don't know how you get an impression about a propaganda organization by not watching it.
I made a simple claim about.Net not working on Windows so expecting it to work on Android is a stretch. When asked for details I gave two cases (thus preemptively proving you can't count) with all the necessary details. Based on the discussion here my posts are factual and your entire premise for claiming otherwise is a leap of faith.
Apparently it worked in some situations, but not in all. My system was nothing special, so it should have worked in my situation. Yes, they aren't bright. They chose to use.Net's FTP libraries, which apparently have a bug in them.
That article has a rundown on the pedigree of the LSE's code.
I've done real-time on Windows platforms (well, pseudo-real-time; but I worked around the jitter and built robustness into the receiving end in case Windows did something unusual) and it's not impossible even at those speeds. From the sound of it, the people who implemented that system had it all balled up; typical of inexperienced people doing real-time without proper supervision. There's no indication there that.Net was the culprit, and that article's author is just being silly claiming that "linux" is the solution. The solution is proper coding and using a real-time OS, which most versions of linux aren't.
I can't use a certain app to store file on an FTP server. The app's devs blame.Net. I believe them, as I can use FTP through a terminal to store files to that site.
I can't use another app that has embedded Google maps unless I manually turn off all the security in Internet Explorer first; now, this one may be a dev issue, if there's a way for.Net to use IE libraries with settings of its own instead of the settings for the browser, but so far they say there's no way for them to do that.
You're prepared to tell me there are no bugs in the most recent version of.Net? None? Zero? Nil?
It's software. It has bugs. In this case, bugs that pop up in critical places and can't be hammered into place without avoiding.Net for that feature entirely.
A number of applications that rely on.Net that don't work properly. There's nothing you can do to fix them except wait for Microsoft to fix the behavior of.Net.
Hmm. Somehow I got that they were doing that in their film, but it appears all they've done is make the film polarizing and omitted one of the LCD layers.
Which means that M isn't an active display, it's a canned demo set into the film.
Slashdot Mirror
Staples is being sued by Paul Allen for his invention, "Not Being Office Max."
In fact, we all need to tread carefully around that one, unless we actually are Office Max.
It's the sound the low-end notebook market made the first time they heard it was coming.
The devs with the bugs aren't my devs. I wouldn't have told them to use .Net.
I have no reason to distrust the devs with the bugs. I also have no reason to implicitly trust that .Net does not have bugs. Therefore their testimony that it's a .Net bug is valid.
I'd be an idiot and a sucker to believe you when you have no first-hand knowledge of the problems encountered.
Fox News was founded by Reagan apparatchiks. It's owned by Rupert Murdoch. It donated money to the RNC.
I wouldn't even know where to go to get the employee records needed to make the counts you imply someone's made.
As for "comments I have seen online", I used the word "astroturfing" in my OP. And I don't know how you get an impression about a propaganda organization by not watching it.
You need to look up astroturf. Those outlets are reporting the facts. If anything, they're failing to properly deal with the facts about Fox News.
We overhauled democracy in the late-19th/early-20th century. Before then, your state legislature appointed your Senators and Congressmen.
But the real problem is that plural voting results in a need to bifurcate the electorate. Approval voting would make things much less choppy.
Considering that both US parties will sell you down the river,
This is an utter myth, promulgated by the US party that actually will sell you down the river.
I made a simple claim about .Net not working on Windows so expecting it to work on Android is a stretch. When asked for details I gave two cases (thus preemptively proving you can't count) with all the necessary details. Based on the discussion here my posts are factual and your entire premise for claiming otherwise is a leap of faith.
Or they isoltated the problem to .Net and couldn't do anything about it.
Apparently it worked in some situations, but not in all. My system was nothing special, so it should have worked in my situation. Yes, they aren't bright. They chose to use .Net's FTP libraries, which apparently have a bug in them.
I patented patenting.
I also patented suing.
You're in deep kim-che, friend.
Yeah, that's it. I must have made it all up.
http://blogs.computerworld.com/london_stock_exchange_to_abandon_failed_windows_platform
That article has a rundown on the pedigree of the LSE's code.
I've done real-time on Windows platforms (well, pseudo-real-time; but I worked around the jitter and built robustness into the receiving end in case Windows did something unusual) and it's not impossible even at those speeds. From the sound of it, the people who implemented that system had it all balled up; typical of inexperienced people doing real-time without proper supervision. There's no indication there that .Net was the culprit, and that article's author is just being silly claiming that "linux" is the solution. The solution is proper coding and using a real-time OS, which most versions of linux aren't.
I'm prepared to ignore your changing the subject from .Net's bugs to other people's bugs.
Absolute FUD. It works fine on Windows
In that subset of things you've used it for, maybe. Other people have run into its bugs. Your presumption that they haven't is called "ignorance".
Well, first, I'm not Anti-MS. I'm not even Anti-.Net. I'm anti-unstable code and anti-blinkered fealty.
Maybe you should stop being a fanboi and realize their shit do stink, just like everyone else's.
Or you could stop hitting reload and read the rest of the thread.
No, you broke it. The apps are broken because .Net is broken. The devs would fix it but they can't do anything about broken parts of .Net.
Because some random app doesn't work right and the developers of the app isolated the problem to a .Net component, it's .Net's fault.
Because you make presumptions like you did you're an idiot.
Take better care of your car.
I can't use a certain app to store file on an FTP server. The app's devs blame .Net. I believe them, as I can use FTP through a terminal to store files to that site.
I can't use another app that has embedded Google maps unless I manually turn off all the security in Internet Explorer first; now, this one may be a dev issue, if there's a way for .Net to use IE libraries with settings of its own instead of the settings for the browser, but so far they say there's no way for them to do that.
You're prepared to tell me there are no bugs in the most recent version of .Net? None? Zero? Nil?
It's software. It has bugs. In this case, bugs that pop up in critical places and can't be hammered into place without avoiding .Net for that feature entirely.
.Net has bugs. My devs shouldn't have to reimplement portions of .Net to do what .Net says it's supposed to do.
A number of applications that rely on .Net that don't work properly. There's nothing you can do to fix them except wait for Microsoft to fix the behavior of .Net.
Hmm. Somehow I got that they were doing that in their film, but it appears all they've done is make the film polarizing and omitted one of the LCD layers.
Which means that M isn't an active display, it's a canned demo set into the film.
Oh well. Maybe next week.
.Net doesn't work on Windows operating systems. Why expect it to work on Android?