As long as everyone keeps doing it in their own way, Linux will never supplant Windows.
Let's think about cars for a minute. If you move from a Honda to a Chevy, will you be able to drive it? Or would you have to learn a new interface before starting the engine?
Every time this comes up, I have to point to Eric Raymond's Luxury of Ignorance article. It's the perfect example of why Linux will never take over the desktop. And it was written 12 years ago. We still haven't learned.
Right. But to bring this back to the original line of thought, would you expect Joe User to be able to do this? Do you want Joe User poking around with kernel compiling?
The problem is that the people who are developing the code don't understand how stupid Jow User can be. But here's the thing, Joe User is right.
Do you drive a car? Could you change the oil? Change a tire? Change a headlight? Change the brake pads?
Should you have to know how in order to drive a car?
Then why the fuck do we keep expecting Joe User to understand how to update the kernel and rebuild the necessary drivers?
But that's the problem with almost every language. It's the old saying, "If the only tool you have is a hammer, every problem looks like a nail."
Perl programmers extended Perl to be able to do stuff that it was not suited to doing.
The same thing is happening now with JavaScript and Python.
My personal problems with Perl are the hieroglyphics and the "default variable". There is an implied target variable that I don't ever actually see? Fuck that.
Users don't want to know what's going on under the hood as long as it's simple and works. Linux UX development still hasn't caught up to Apple and MS on the "Stupidly Simple" interfaces. And likely never will.
Read it again. One of the female astronauts thought she could use the large suit but after her first space walk decided the medium fit better. She is the one who is not going on the next one.
It's only the newer models of the 737 MAX. The 737 was introduced in 1967 but the 737 MAX came in 2016.
And even then, the older models apparently had an automatic override that would kick in if the pilot held the yoke back. The newer models require the pilot to manually shut off that sensor.
All three experts pointed out that the key could not be used on the BlackBerry Enterprise Server phones which are typically used by corporations and governments.
The BlackBerry Internet Service (BIS) ran through BB's own server so they had to have the keys. The BES keys were never held by BB.
Okay. Now think of the average home user. Do you *really* think Joe Average will know how to find that option? Will he understand what the option means? Does he even know what "caching" is?
This type of question always rustles my jimmies simply because the experts know what it means and how it works but the average user is clueless. And wants to remain so. We all need to remember Eric Raymond's other essay on the "Luxury of Ignorance". It's still very applicable today.
In other words, this is a (at least) two part answer):
To home users - and Managers - Yes, you always need to eject the drive before removing the USB.
To be - sort of - fair. Windows ME was supposed to be a consumer version of the NT Kernel where Windows 2000 was the business version based on the same kernel.
At some point, Microsoft dropped the NT Kernel and went back to the 95/98 kernel with some of the tools from Windows 2000 due to time constraints. The rush decision and tight timeline did not work well.
Until the vendors can roll out LTE with voice over LTE (VoLTE) to cover the same area as UMTS, everyone will still be paying Qualcomm royalties. Qualcomm has the CDMA technology (which is used in WCDMA as the baseband for UMTS) all wrapped up in patents.
There is also an issue with routing VOIP calls (VoLTE is basically a VOIP call) to emergency services along with the trouble of allowing a phone without a SIM to access enough of the network to make the emergency call over VoLTE.
They keyboard is so integrated - and the spacebar so fragile - that they have to replace the entire top of the MacBook. After the warranty expires, that's a $700.00 repair.
So a piece of dust under the spacebar can lead to a $700.00 repair bill. Nice.
That's not entirely true. There are algorithms to handle machine learning but most of them require a trial-and-error approach. Computers can burn through thousands of choices and outcomes and pick the most effective.
The downside to this type of learning in medicine is that you have to kill thousands of people before you get the "best" treatment.
Read the summary. The issue with Swift is that the libraries are not locked down yet. Each app has to static link - or include the libraries as part of the installation - as it can't rely on the different versions being compatible.
It's in Variety. You expect an entertainment magazine to understand and report on the technical details? They'd get them wrong anyway.
From the sounds of it, the hacker group was simply port scanning and got lucky in finding that Windows 7 box that had a hole. Once on that machine, they had complete access to the internal network.
Coding, itself, is not fun. Seeing the results? That's the fun. It's like construction work. Swinging a hammer is not fun. Seeing the building come together and knowing you had a hand in it is fun.
The fun part about software is that we can quickly and easily - relatively speaking - change one thing and see what happens.
...writes code, gives it to you, and says, "here, debug this."
Call me odd, but I enjoy that role. Probably why I was in integration for 5 years....
Slashdot Mirror
As long as everyone keeps doing it in their own way, Linux will never supplant Windows.
Let's think about cars for a minute. If you move from a Honda to a Chevy, will you be able to drive it? Or would you have to learn a new interface before starting the engine?
Every time this comes up, I have to point to Eric Raymond's Luxury of Ignorance article. It's the perfect example of why Linux will never take over the desktop. And it was written 12 years ago. We still haven't learned.
Right. But to bring this back to the original line of thought, would you expect Joe User to be able to do this? Do you want Joe User poking around with kernel compiling?
The problem is that the people who are developing the code don't understand how stupid Jow User can be. But here's the thing, Joe User is right.
Do you drive a car? Could you change the oil? Change a tire? Change a headlight? Change the brake pads?
Should you have to know how in order to drive a car?
Then why the fuck do we keep expecting Joe User to understand how to update the kernel and rebuild the necessary drivers?
Nobody wants to admit they still use it. It's sliding into COBOL territory...
But that's the problem with almost every language. It's the old saying, "If the only tool you have is a hammer, every problem looks like a nail."
Perl programmers extended Perl to be able to do stuff that it was not suited to doing.
The same thing is happening now with JavaScript and Python.
My personal problems with Perl are the hieroglyphics and the "default variable". There is an implied target variable that I don't ever actually see? Fuck that.
Ummm....don't look at OpenStack then. It's all Python.
Admittedly, it's all "infrastructure automation" interfacing with hypervisors and storage arrays. But it is a large project.
This is something that Eric Raymond put out in 2006 and it's just as relevant today.
http://www.catb.org/~esr/writi...
Users don't want to know what's going on under the hood as long as it's simple and works. Linux UX development still hasn't caught up to Apple and MS on the "Stupidly Simple" interfaces. And likely never will.
Read it again. One of the female astronauts thought she could use the large suit but after her first space walk decided the medium fit better. She is the one who is not going on the next one.
It's only the newer models of the 737 MAX. The 737 was introduced in 1967 but the 737 MAX came in 2016.
And even then, the older models apparently had an automatic override that would kick in if the pilot held the yoke back. The newer models require the pilot to manually shut off that sensor.
From TFA:
All three experts pointed out that the key could not be used on the BlackBerry Enterprise Server phones which are typically used by corporations and governments.
The BlackBerry Internet Service (BIS) ran through BB's own server so they had to have the keys. The BES keys were never held by BB.
It was one of the selling points for enterprise customers. The BlackBerry Enterprise Server (BES) maintained the keys and was owned by the customer.
Okay. Now think of the average home user. Do you *really* think Joe Average will know how to find that option? Will he understand what the option means? Does he even know what "caching" is?
This type of question always rustles my jimmies simply because the experts know what it means and how it works but the average user is clueless. And wants to remain so. We all need to remember Eric Raymond's other essay on the "Luxury of Ignorance". It's still very applicable today.
In other words, this is a (at least) two part answer):
To home users - and Managers - Yes, you always need to eject the drive before removing the USB.
To IT professionals, you already know the answer.
Not exactly. They are complaining about people using their compiled and packaged binary without paying the licensing fee.
Note that this is not in violation of even the GPL as distribution costs can be charged.
To be - sort of - fair. Windows ME was supposed to be a consumer version of the NT Kernel where Windows 2000 was the business version based on the same kernel.
At some point, Microsoft dropped the NT Kernel and went back to the 95/98 kernel with some of the tools from Windows 2000 due to time constraints. The rush decision and tight timeline did not work well.
Until the vendors can roll out LTE with voice over LTE (VoLTE) to cover the same area as UMTS, everyone will still be paying Qualcomm royalties. Qualcomm has the CDMA technology (which is used in WCDMA as the baseband for UMTS) all wrapped up in patents.
There is also an issue with routing VOIP calls (VoLTE is basically a VOIP call) to emergency services along with the trouble of allowing a phone without a SIM to access enough of the network to make the emergency call over VoLTE.
Just to nitpick, GSM was 2G and TDMA only. UMTS was 3G and wideband CDMA (WCDMA).
Admittedly, beyond layer 2, the packet format was pretty much identical (why reinvent the wheel?), they were two "separate" standards.
Also, at some point UMTS HSPA was CDMA inside of TDMA inside of WCDMA. I think it became the poster child for over-engineering.
It's ended well every other time, right?
From reading TFA.
They keyboard is so integrated - and the spacebar so fragile - that they have to replace the entire top of the MacBook. After the warranty expires, that's a $700.00 repair.
So a piece of dust under the spacebar can lead to a $700.00 repair bill. Nice.
That's not entirely true. There are algorithms to handle machine learning but most of them require a trial-and-error approach. Computers can burn through thousands of choices and outcomes and pick the most effective.
The downside to this type of learning in medicine is that you have to kill thousands of people before you get the "best" treatment.
Read the summary. The issue with Swift is that the libraries are not locked down yet. Each app has to static link - or include the libraries as part of the installation - as it can't rely on the different versions being compatible.
Office macros are one of the most notorious attack vectors...
It's in Variety. You expect an entertainment magazine to understand and report on the technical details? They'd get them wrong anyway.
From the sounds of it, the hacker group was simply port scanning and got lucky in finding that Windows 7 box that had a hole. Once on that machine, they had complete access to the internal network.
...and have orgasms,...
Well, not quite. But for those trying to get pregnant there are apps that will tell you the best time to copulate.
Congratulations, you've successfully re-invented Perl
Not quite. More like "Made a readable version of Perl." There's a reason Perl tends to be disqualified from any "obfuscated code" contests.
Python seem to be the current popular "glue code" language.
See OpenStack for a perfect example. It's just "glue code" around various virtualization packages.
Freedom of speech does not mean freedom from consequences
Um, yes, that's exactly what it means. That is, in fact, the definition.
No. It means that you are free from governmental consequences. Private entities are still free to tell you to fuck off.
Coding, itself, is not fun. Seeing the results? That's the fun. It's like construction work. Swinging a hammer is not fun. Seeing the building come together and knowing you had a hand in it is fun.
The fun part about software is that we can quickly and easily - relatively speaking - change one thing and see what happens.
...writes code, gives it to you, and says, "here, debug this."
Call me odd, but I enjoy that role. Probably why I was in integration for 5 years....