As a developer who has written drivers for DSP and other low level stuff, I can say with great certainty that this is definitely an iOS bug. The problem did not occur at all before the 11.4.0 update. As soon as that update dropped it happens without fail for the past 5 weeks. It's not background apps. I can close all apps, charge to 100%, unplug when I go to bed and in the morning it's 20%. Something is getting stuck in a loop or maybe some chip is getting bad commands. The phone gets physically warm so something is running free.
No doubt everyone that always used their iPhone a lot is going to jump in an say "me too" when their problem is that they're just using their phone a lot. So naturally that has created enough doubt to muddy the diagnosis. And Apple has not acknowledge the bug so there are a lot of responses regarding how to turn things off to improve battery. But, again, that is NOT the problem. The problem is something is running uncontrolled.
There are many theories as to the cause. Many have to do with something related to WiFi. The only pattern that I have seen is that if I shutdown and restart, the problem goes away for a while. But as soon as I use the phone for whatever reason, it comes back. It might take 6 hours. It might take a day. But eventually it always comes back and then it's stuck draining battery unless I reboot.
Note that iOS 11.4.1 was just released yesterday. But the release notes say nothing about battery anything so it remains to be seen if they have fixed it. It is discouraging that they have not acknowledged it. It makes you wonder if they're actually having trouble reproducing it. But that would almost unbelievable since they could just install 11.3 and compare. Of course we can't do that because 11.3 isn't signed anymore so it cannot be installed. Obviously it's not a trivial CPU loop or they would have spotted it quick. Running the CPU in debugging mode probably suppresses it or again they would have spotted it quick.
I'm starting to have doubts about Apple. Steve Jobs was a prick but maybe that's precisely why he was so successful.
If they don't fix the battery drain problem (which AFAIK they have not actually acknowledged as a "problem" and it absolutely most definitely is) I will be dumping iPhone for sure. Bring on Android.
Agreed. AI used to mean a computer that could "think". At least that's what people have been lead to believe. Over the years the term "AI" has been hijacked by companies who are clearly taking advantage of the misconception with advertisements for systems that talk to people about finding viruses and "healing" networks and other such nonsense. These programs are not "thinking" like a person and I don't believe they ever will simply because they do not have human experiences. They are simply sophisticated algorithms for specific problems.
Sounds like they need to further develop their hypothesis, conduct trials to collect data, establish a control group, analyze the data and present their findings for peer review to determine precisely how much Science should be permitted at the EPA.
Many robo calls are using arbitrary numbers now. They can do that if they have a particular type of service. I know this for sure because I have received calls from myself!
Then again, I guess it wasn't my smart phone that really initiated the call.
You are gullible beyond belief. You said, "see campaign stump speeches for more information"? You must be joking. Trump is a narcissistic reality TV show personality who is a master at manipulating public opinion. You have taken the bait hook-line-and-sinker my friend. Trump is going to try to start a war by scaring people so that they rally around him to do something (war). Just watch. They are going to start to build up rhetoric about threats from NK or Iran or wherever and use the whole thing to scare people into being his followers. How ironic it is that Kim Jong Un does precisely the same thing.
I have used Linux as my primary desktop since ~1997. As a software developer it is a power platform. The shell is critical. However, as a conventional desktop it is just not competitive with Windows. And OSX isn't either. Both Linux and OSX are below 4% market share. Vertical integration is very weak. Windows has an identity management system that allows transparent filesharing, advanced group based access control, sophisticated business applications. Getting stuff like that to work on Linux is too difficult or simply not possible. So software venders focus on the Windows platform. And rightly so. I just tried and application that recently released a Beta for Linux and it was a total fail. I occasionally dabble in engineering related stuff and I have to have a Windows machine for all of the various programs for cad, PCB design, simulation. Yeah, programs like that exist for Linux but they're just not good. And I know people agree with me that the GNOME desktop has actually regressed. It used to be much more usable. But they dumbed it down for reasons that where not entirely clear. My guess would be that when new developers come along, they have a tendency to want to re-write everything from scratch. I'm not diametrically opposed to this strategy but you better come up with something that was at least as good as what you're dumping. And that didn't happen. There are other integration related issues as well. For example, for as long as I can recall there has always been a fight between X and the desktop over who should remember the positions of windows. X says applications should save that information and recall it when re-launching an app. Desktop people think it should be handled by lower level facilities. Now, whenever logout and back in, all of my terminal windows have to be re-launced and repositioned (I run 6-8 terms on 4-5 workspaces). That is something that actually used to work somewhat in GNOME. It worked in WindowMaker IIRC. The Linux desktop has been dumbed way down to the point where it's not nearly as useful as it used to be. At least not for people doing more than surfing the web and email. Might as well just get a Chomebook for that.
The reason people don't respect the W3C specs is because they don't meet application requirements. HTTP and HTML were designed to serve static documents. The W3C thought the web was going to be like a giant encyclopedia composed of book like content with chapters, paragraphs, static images and so on. The statelessness of HTTP causes all sorts of problems that have resulted in hacks like cookies. Consider that HTTP does not specify any way to even authenticate a client. There's no way to do a proper complete stand-alone authentication. So we have to process plaintext passwords on the server over HTTPS. If HTTP had a proper authentication mech, major hacks like those we hear about on the news would be significantly reduced. The whole tool-chain stinks. Nobody understands CSS. The DOM is buggy and generally not that useful. JavaScript is mess. It's all way more complicated than it needs to be. The only upside is that it's so bad, it's an inevitablility that someone will come up with a completetly different "browser" with it's own tool-chain or possibly a browser plugin that just completely replaces the whole W3C toolchain. I hope anyway.
Theoretical computer scientists might be intelligent but in my experience they make bad programmers. Computer science professors are almost always really bad programmers. Good programmers are more artist than scientist. And you can't automate art.
Also, I don't know what automation is being referenced because I never met an IDE I didn't hate. And as far as build tools go, the whole automake, autoconf, libtool tool-chain is a bad joke. I wish that stuff were automated. But right now it all seems to be very manual to me.
Last I checked a RedHat subscription was not priced for the non-corporate user.
And I have tried those "long term support" distros more than once (although not RH) and my experience was that a) nobody actually uses them so the support isn't that great (you can't find a lot of answers in forums, blogs and such) and bugs take a long time to get fixed and more likely b) they only support new hardware for a little while so they don't really work unless you buy a laptop at the same time the distro was released. As soon as the kernel is remotely dated, you can't get wireless or suspend or whatever to work properly because there's some new chip the kernel doesn't understand.
I don't think I've ever installed RHEL or CentOS with X Windows. Frankly it annoys me that there are no desktop distros that are maintained for longer than a year or two. Are we really expected to reinstall Linux on a workstation ever year? That scares me because it makes me think the people who are using Linux are just screwing around and not doing real work. Anyone doing real work doesn't have time to reinstall Linux every year.
Seriously. I think the media coverage of these events inspires these guys. They have to stop reciting every little detail over and over. These shooters are not just raging against something, they want to become infamous. And CNN is making these guys infamous. The media should just report some basic facts and then change the topic. Don't show video, don't show pics, don't play 911 calls and most important stop leading witnesses through each moment of the crime. The shooter's fantasy is people reciting the horror over and over on prime time TV. Please stop!
Note that the article is referring to NTLMv1 which uses 56 bit DES and, as illustrated by the article, that is easily broken. However, the article conveniently fails to mention that as of Vista and Windows 2008, default security policy requires NTLMv2 which uses 128 bit RC4. That is a totally different crypto scheme. Despite the fact that the protocol for exchanging authentication tokens (NTLMSSP) has been around since early Windows NT days, it doesn't matter - cryptographically 128 bit RC4 is fairly secure. At least the difference between 128 bit RC4 and the 256 bit AES used by Kerberos is not the weak link (and as of today Windows domains still default to allowing 128 bit AES to be negotiated anyway).
Also, note that NTLM authentication is absolutely not obsolete. Kerberos clients require access to domain controllers. Kerberos is very sensitive about the name a client uses to authenticate with a service and it is very sensitive about DNS. It requires a lot of manipulation of principal names and key files. Time must be synchronized on all three machines involved in a Kerberos authentication. Stale tickets may need to be purged. If any of these things are not right, it can be non-trivial to track down the problem. NTLM does not have any of these issues. NTLM is much more robust than Kerberos. It's just less efficient and it lacks features like delegation. A "pass through Kerberos" mechanism is being developed to replace NTLM that would resolve some of these issues (the main one being that clients would not be required to access domain controllers), but I suspect it will still be quite a while before it actually does and it's not clear that it will solve all of the aforementioned issues anyway.
The article on this are horribly inadequate. First, any helicopter is "Marine One" as soon as the president steps on board. So what helicopter is it? Is it the 30 year old Sikorskys that we're used to seeing or is it the new Lockheed Martin VH-71?
Files or "persistent objects", it doesn't make any difference since things are ultimately serialized to streams. In fact, the whole thing sounds pretty clumsy to me.
I've been using Linux on my laptops for almost 10 years. I've used RH, Fedora, then CentOS for a long time, Ubuntu very briefly and now I'm well into Fedora 9. So there's my street cred - ok.
I'm sorry to say that running Linux on a laptop has some serious problems, always has, and I suspect, always will. It's nothing that a seasoned Linux power user can't fix but for the average person it's not something you want to mess with. There are almost always problems with video, wireless, sound and suspend/resume. Meaning they just don't work and require serious tweaking or sound dies after suspend/resume or if you're unlucky need a kernel module which means it will break again on the next kernel update. Etc, etc, etc... This has been going on forever. It's gotten a little better over the years (e.g. no more XF86Config "modelines" thank you) but until there is a paradigm shift in how the kernel developers interface with hardware vendors I have a feeling we're going to go on having problems with Linux on laptops.
Linux is for servers. And it kick's ass on servers. Solaris is dying (or at least it's dying like FreeBSD is dying). Their edge used to be large hardware support but that has become less and less important as people start to accept the idea of lots of little cheap $5000 servers instead of a few really big multi-million $ servers. Windows is not a good choice for a server if you don't need Windows libraries. If you're just running web apps, some Java, a DB, etc Windows is a liability with all that code you're not using.
Of course there's always someone who claims they have never had a problem with Linux on their laptop. Any then five minutes later the can't get on the WiFi network because NetworkManager is lost. And pretend it's nothing...
make it available, so not every friggin windows machine has to do unencrypted passwords across the network to access SAMBA shares
This is completely WRONG.
Samba fully supports NTLM and NTLMv2 which Windows will initiate without any configuration. And if the Samba machine is a domain member, Windows clients will also do Kerberos.
A few years back Samba required that you run some goofy commands to setup the password database. As a result, some users would simply punt and turn off encrypted passwords. I think that might be what you're thinking of.
No one should every be sending domain passwords over the network in plain text. However, last I checked, Windows clients actually do have a security policy setting that instructs the client to use plain text authentication. But you should never use that in a domain environment. It's for home users who just want to drop the pants on security for maximum compatibility with legacy systems (e.g. Windows 3.x).
The summary reads "coded by Bob Jacobsen that Katzer used in...". But did Katzer actually use the JMRI source code? If he did not actually copy and paste or fragments of code or entire files I fail to see why there would be a violation of the license agreement.
This time they really really really really really really found water. Just like the last time they really really really found water. But that one time they found water they really didn't. But this time they really almost definitely did.
Languange compatibility was never the main problem - it was class libraries. Java has a mountain of class libraries.
Unfortunately most of them are complete bloat (e.g. Swing, NIO, logging...). Each package is like a treatise on OOP and design patterns. When are people going to learn that OOP is just one tool of many?
But Java the *language* is great. I wish that someone would create a non-bloat version of the Java class libraries. Do an analysis of important use cases, redesigned the class libraries to be much less "fluffy" and then post some metrics to show how much better it performs.
I have a mantra that I follow that has served me well over the years. It's somewhat abstract but it goes something like this: Model the concept of what your software is doing and not the physical world or procedures. If you model a concept correctly, the result will be equally useful 10 years from now because a concept, in the most abstract sense of the word, does not change over time. Modeling a concept as it pertains to software ultimately means designing an API.
[I can hear people sarcastically saying "So what you're saying is that if you do it right it will be right - whatever dude."]
Let's say you do an analysis of a task that your software is supposed to perform and you identify parts X, Y and Z. Most people are compelled to simply write some code that does X and then some more that does Y and then a bit that does Z. But I would stop and ask myself "What is X, what's it's relationship to Y and do I really need Z at all?".
If you philosophize over the task enough you should begin to identify patterns. Those patters outline the concepts involved in the task. Those patterns and concepts dictate the API.
The purpose of all of this is of course normalization. As you develop a tool-chest of modules and libraries that implement each concept the end result is highly normalized code. The chances of running into a problem that transcends the codebase is greatly decreased and the flexibility of the codebase is greatly increased. If you do encounter a problem it is more likely to be isolated and therefore easily replaced. That is what makes good software.
The original Dune movie had the potential to be great. But it was just too much packed into one movie. It's impossible to follow the first time around and needed a lot of narration.
They should have made Dune into a trio: Part I - The boy trains in "wierd" ways and travels to the other planet where in the last sceene he sees a big worm. Part II his family is betrayed, his father is killed and they flee to the rebels in the dunes. Part III he leads the rebels to victory, gets laid and saves the universe.
If the new flick is everything in one movie, then you know it's duned to failure.
it would mean that Microsoft is pretty much scrapping it's entire codebase for Windows and replacing it with a Unix or Unix-like architecture. Says who? The NT kernel was designed to be able to project different "personalities", much in the same way that Mac OS X does. The POSIX system necessary has been available in Windows for just shy of forever in an effort to win government contracts and companies that require POSIX as a checkbox on their requisition forms. No. The POSIX subsystem is for trivial little commandline utilities. It doesn't even have sockets. It's basically worthless. Personally I think they did it just so that they could claim POSIX compatibility, split hairs and trick people into thinking Windows was compatible with UNIX.
Just as bad was the Kerberos debacle where Microsoft extended Kerberos for Windows such that Unix machines could subscribe to a Windows domain, but a Windows machine could not subscribe to a Unix domain. I called a rep on it in one of their presentations on Win2K, and he assured me that I was mistaken. Yes, you were mistaken. Windows client accounts can be hosted by MIT and Heimdal KDCs. The KDCs just don't generate a PAC (which was not a "debacle" or even controvesial since an MIT or Heimdal KDC does not have the necessary group information to put into the PAC). The "debacle" you speak of was probably when MS claimed that the PAC information was a "trade secret". MIT sued them over it but MS quickly recinded the claim and published documentation about the PAC (which has since been used in Samba 4 incedentally). MIT and MS get along just fine. It's only people who actually believe what they read on Slashdot that think otherwise.
The OP is right. A GNU compatible system on Windows is a diffcult project. There are syscalls that are almost impossible to emulate efficiently on Windows. For one, the Windows' process model is fundamentally different which makes implementing something like fork(2) a problem.
Slashdot Mirror
As a developer who has written drivers for DSP and other low level stuff, I can say with great certainty that this is definitely an iOS bug. The problem did not occur at all before the 11.4.0 update. As soon as that update dropped it happens without fail for the past 5 weeks. It's not background apps. I can close all apps, charge to 100%, unplug when I go to bed and in the morning it's 20%. Something is getting stuck in a loop or maybe some chip is getting bad commands. The phone gets physically warm so something is running free.
No doubt everyone that always used their iPhone a lot is going to jump in an say "me too" when their problem is that they're just using their phone a lot. So naturally that has created enough doubt to muddy the diagnosis. And Apple has not acknowledge the bug so there are a lot of responses regarding how to turn things off to improve battery. But, again, that is NOT the problem. The problem is something is running uncontrolled.
There are many theories as to the cause. Many have to do with something related to WiFi. The only pattern that I have seen is that if I shutdown and restart, the problem goes away for a while. But as soon as I use the phone for whatever reason, it comes back. It might take 6 hours. It might take a day. But eventually it always comes back and then it's stuck draining battery unless I reboot.
Note that iOS 11.4.1 was just released yesterday. But the release notes say nothing about battery anything so it remains to be seen if they have fixed it. It is discouraging that they have not acknowledged it. It makes you wonder if they're actually having trouble reproducing it. But that would almost unbelievable since they could just install 11.3 and compare. Of course we can't do that because 11.3 isn't signed anymore so it cannot be installed. Obviously it's not a trivial CPU loop or they would have spotted it quick. Running the CPU in debugging mode probably suppresses it or again they would have spotted it quick.
I'm starting to have doubts about Apple. Steve Jobs was a prick but maybe that's precisely why he was so successful.
I want to know this too please.
If they don't fix the battery drain problem (which AFAIK they have not actually acknowledged as a "problem" and it absolutely most definitely is) I will be dumping iPhone for sure. Bring on Android.
Agreed. AI used to mean a computer that could "think". At least that's what people have been lead to believe. Over the years the term "AI" has been hijacked by companies who are clearly taking advantage of the misconception with advertisements for systems that talk to people about finding viruses and "healing" networks and other such nonsense. These programs are not "thinking" like a person and I don't believe they ever will simply because they do not have human experiences. They are simply sophisticated algorithms for specific problems.
Sounds like they need to further develop their hypothesis, conduct trials to collect data, establish a control group, analyze the data and present their findings for peer review to determine precisely how much Science should be permitted at the EPA.
Many robo calls are using arbitrary numbers now. They can do that if they have a particular type of service. I know this for sure because I have received calls from myself!
Then again, I guess it wasn't my smart phone that really initiated the call.
You are gullible beyond belief. You said, "see campaign stump speeches for more information"? You must be joking. Trump is a narcissistic reality TV show personality who is a master at manipulating public opinion. You have taken the bait hook-line-and-sinker my friend. Trump is going to try to start a war by scaring people so that they rally around him to do something (war). Just watch. They are going to start to build up rhetoric about threats from NK or Iran or wherever and use the whole thing to scare people into being his followers. How ironic it is that Kim Jong Un does precisely the same thing.
I have used Linux as my primary desktop since ~1997. As a software developer it is a power platform. The shell is critical. However, as a conventional desktop it is just not competitive with Windows. And OSX isn't either. Both Linux and OSX are below 4% market share. Vertical integration is very weak. Windows has an identity management system that allows transparent filesharing, advanced group based access control, sophisticated business applications. Getting stuff like that to work on Linux is too difficult or simply not possible. So software venders focus on the Windows platform. And rightly so. I just tried and application that recently released a Beta for Linux and it was a total fail. I occasionally dabble in engineering related stuff and I have to have a Windows machine for all of the various programs for cad, PCB design, simulation. Yeah, programs like that exist for Linux but they're just not good. And I know people agree with me that the GNOME desktop has actually regressed. It used to be much more usable. But they dumbed it down for reasons that where not entirely clear. My guess would be that when new developers come along, they have a tendency to want to re-write everything from scratch. I'm not diametrically opposed to this strategy but you better come up with something that was at least as good as what you're dumping. And that didn't happen. There are other integration related issues as well. For example, for as long as I can recall there has always been a fight between X and the desktop over who should remember the positions of windows. X says applications should save that information and recall it when re-launching an app. Desktop people think it should be handled by lower level facilities. Now, whenever logout and back in, all of my terminal windows have to be re-launced and repositioned (I run 6-8 terms on 4-5 workspaces). That is something that actually used to work somewhat in GNOME. It worked in WindowMaker IIRC. The Linux desktop has been dumbed way down to the point where it's not nearly as useful as it used to be. At least not for people doing more than surfing the web and email. Might as well just get a Chomebook for that.
The reason people don't respect the W3C specs is because they don't meet application requirements. HTTP and HTML were designed to serve static documents. The W3C thought the web was going to be like a giant encyclopedia composed of book like content with chapters, paragraphs, static images and so on. The statelessness of HTTP causes all sorts of problems that have resulted in hacks like cookies. Consider that HTTP does not specify any way to even authenticate a client. There's no way to do a proper complete stand-alone authentication. So we have to process plaintext passwords on the server over HTTPS. If HTTP had a proper authentication mech, major hacks like those we hear about on the news would be significantly reduced. The whole tool-chain stinks. Nobody understands CSS. The DOM is buggy and generally not that useful. JavaScript is mess. It's all way more complicated than it needs to be. The only upside is that it's so bad, it's an inevitablility that someone will come up with a completetly different "browser" with it's own tool-chain or possibly a browser plugin that just completely replaces the whole W3C toolchain. I hope anyway.
Theoretical computer scientists might be intelligent but in my experience they make bad programmers. Computer science professors are almost always really bad programmers. Good programmers are more artist than scientist. And you can't automate art.
Also, I don't know what automation is being referenced because I never met an IDE I didn't hate. And as far as build tools go, the whole automake, autoconf, libtool tool-chain is a bad joke. I wish that stuff were automated. But right now it all seems to be very manual to me.
Last I checked a RedHat subscription was not priced for the non-corporate user.
And I have tried those "long term support" distros more than once (although not RH) and my experience was that a) nobody actually uses them so the support isn't that great (you can't find a lot of answers in forums, blogs and such) and bugs take a long time to get fixed and more likely b) they only support new hardware for a little while so they don't really work unless you buy a laptop at the same time the distro was released. As soon as the kernel is remotely dated, you can't get wireless or suspend or whatever to work properly because there's some new chip the kernel doesn't understand.
I don't think I've ever installed RHEL or CentOS with X Windows. Frankly it annoys me that there are no desktop distros that are maintained for longer than a year or two. Are we really expected to reinstall Linux on a workstation ever year? That scares me because it makes me think the people who are using Linux are just screwing around and not doing real work. Anyone doing real work doesn't have time to reinstall Linux every year.
Seriously. I think the media coverage of these events inspires these guys. They have to stop reciting every little detail over and over. These shooters are not just raging against something, they want to become infamous. And CNN is making these guys infamous. The media should just report some basic facts and then change the topic. Don't show video, don't show pics, don't play 911 calls and most important stop leading witnesses through each moment of the crime. The shooter's fantasy is people reciting the horror over and over on prime time TV. Please stop!
Note that the article is referring to NTLMv1 which uses 56 bit DES and, as illustrated by the article, that is easily broken. However, the article conveniently fails to mention that as of Vista and Windows 2008, default security policy requires NTLMv2 which uses 128 bit RC4. That is a totally different crypto scheme. Despite the fact that the protocol for exchanging authentication tokens (NTLMSSP) has been around since early Windows NT days, it doesn't matter - cryptographically 128 bit RC4 is fairly secure. At least the difference between 128 bit RC4 and the 256 bit AES used by Kerberos is not the weak link (and as of today Windows domains still default to allowing 128 bit AES to be negotiated anyway).
Also, note that NTLM authentication is absolutely not obsolete. Kerberos clients require access to domain controllers. Kerberos is very sensitive about the name a client uses to authenticate with a service and it is very sensitive about DNS. It requires a lot of manipulation of principal names and key files. Time must be synchronized on all three machines involved in a Kerberos authentication. Stale tickets may need to be purged. If any of these things are not right, it can be non-trivial to track down the problem. NTLM does not have any of these issues. NTLM is much more robust than Kerberos. It's just less efficient and it lacks features like delegation. A "pass through Kerberos" mechanism is being developed to replace NTLM that would resolve some of these issues (the main one being that clients would not be required to access domain controllers), but I suspect it will still be quite a while before it actually does and it's not clear that it will solve all of the aforementioned issues anyway.
The article on this are horribly inadequate. First, any helicopter is "Marine One" as soon as the president steps on board. So what helicopter is it? Is it the 30 year old Sikorskys that we're used to seeing or is it the new Lockheed Martin VH-71?
I bet they type faster than Data from Star Trek TNG.
Files or "persistent objects", it doesn't make any difference since things are ultimately serialized to streams. In fact, the whole thing sounds pretty clumsy to me.
I've been using Linux on my laptops for almost 10 years. I've used RH, Fedora, then CentOS for a long time, Ubuntu very briefly and now I'm well into Fedora 9. So there's my street cred - ok.
I'm sorry to say that running Linux on a laptop has some serious problems, always has, and I suspect, always will. It's nothing that a seasoned Linux power user can't fix but for the average person it's not something you want to mess with. There are almost always problems with video, wireless, sound and suspend/resume. Meaning they just don't work and require serious tweaking or sound dies after suspend/resume or if you're unlucky need a kernel module which means it will break again on the next kernel update. Etc, etc, etc... This has been going on forever. It's gotten a little better over the years (e.g. no more XF86Config "modelines" thank you) but until there is a paradigm shift in how the kernel developers interface with hardware vendors I have a feeling we're going to go on having problems with Linux on laptops.
Linux is for servers. And it kick's ass on servers. Solaris is dying (or at least it's dying like FreeBSD is dying). Their edge used to be large hardware support but that has become less and less important as people start to accept the idea of lots of little cheap $5000 servers instead of a few really big multi-million $ servers. Windows is not a good choice for a server if you don't need Windows libraries. If you're just running web apps, some Java, a DB, etc Windows is a liability with all that code you're not using.
Of course there's always someone who claims they have never had a problem with Linux on their laptop. Any then five minutes later the can't get on the WiFi network because NetworkManager is lost. And pretend it's nothing ...
make it available, so not every friggin windows machine has to do unencrypted passwords across the network to access SAMBA shares
This is completely WRONG.
Samba fully supports NTLM and NTLMv2 which Windows will initiate without any configuration. And if the Samba machine is a domain member, Windows clients will also do Kerberos.
A few years back Samba required that you run some goofy commands to setup the password database. As a result, some users would simply punt and turn off encrypted passwords. I think that might be what you're thinking of.
No one should every be sending domain passwords over the network in plain text. However, last I checked, Windows clients actually do have a security policy setting that instructs the client to use plain text authentication. But you should never use that in a domain environment. It's for home users who just want to drop the pants on security for maximum compatibility with legacy systems (e.g. Windows 3.x).
The summary reads "coded by Bob Jacobsen that Katzer used in ...". But did Katzer actually use the JMRI source code? If he did not actually copy and paste or fragments of code or entire files I fail to see why there would be a violation of the license agreement.
This time they really really really really really really found water. Just like the last time they really really really found water. But that one time they found water they really didn't. But this time they really almost definitely did.
Languange compatibility was never the main problem - it was class libraries. Java has a mountain of class libraries.
...). Each package is like a treatise on OOP and design patterns. When are people going to learn that OOP is just one tool of many?
Unfortunately most of them are complete bloat (e.g. Swing, NIO, logging
But Java the *language* is great. I wish that someone would create a non-bloat version of the Java class libraries. Do an analysis of important use cases, redesigned the class libraries to be much less "fluffy" and then post some metrics to show how much better it performs.
I have a mantra that I follow that has served me well over the years. It's somewhat abstract but it goes something like this: Model the concept of what your software is doing and not the physical world or procedures. If you model a concept correctly, the result will be equally useful 10 years from now because a concept, in the most abstract sense of the word, does not change over time. Modeling a concept as it pertains to software ultimately means designing an API.
[I can hear people sarcastically saying "So what you're saying is that if you do it right it will be right - whatever dude."]
Let's say you do an analysis of a task that your software is supposed to perform and you identify parts X, Y and Z. Most people are compelled to simply write some code that does X and then some more that does Y and then a bit that does Z. But I would stop and ask myself "What is X, what's it's relationship to Y and do I really need Z at all?".
If you philosophize over the task enough you should begin to identify patterns. Those patters outline the concepts involved in the task. Those patterns and concepts dictate the API.
The purpose of all of this is of course normalization. As you develop a tool-chest of modules and libraries that implement each concept the end result is highly normalized code. The chances of running into a problem that transcends the codebase is greatly decreased and the flexibility of the codebase is greatly increased. If you do encounter a problem it is more likely to be isolated and therefore easily replaced. That is what makes good software.
The original Dune movie had the potential to be great. But it was just too much packed into one movie. It's impossible to follow the first time around and needed a lot of narration.
They should have made Dune into a trio: Part I - The boy trains in "wierd" ways and travels to the other planet where in the last sceene he sees a big worm. Part II his family is betrayed, his father is killed and they flee to the rebels in the dunes. Part III he leads the rebels to victory, gets laid and saves the universe.
If the new flick is everything in one movie, then you know it's duned to failure.
Mike
The OP is right. A GNU compatible system on Windows is a diffcult project. There are syscalls that are almost impossible to emulate efficiently on Windows. For one, the Windows' process model is fundamentally different which makes implementing something like fork(2) a problem.