You run these workloads in your on-premises datacenters, hosted at service providers, and in public clouds. [...] Several hundred thousand Linux and UNIX servers in production usage today are managed by System Center
Loving GNU/Linux on servers != loving GNU/Linux on laptops and home desktop PCs. Microsoft attempts to make up for it:
And if you look more broadly, Microsoft offers key productivity software such as Office365, Skype, and RDP clients on Linux-based and BSD-based client operating systems such as iOS, Android, and Mac OS X.
Of these three, a port of Skype with a largely outdated feature set is available for GNU/Linux. For the others, Microsoft falls back on "Linux-based" Android with Google Play, which isn't GNU/Linux and isn't intended to work on traditional desktop or laptop PCs. Android prior to 7.0 "Nougat" doesn't even have window tiling as a standard feature, instead forcing applications to run in the full screen. Enjoy your four-function calculator filling your 10-inch tablet.
In fact, Windows Signature Edition offers the end-user even more control by giving them an OS free of vendor crapware.
If you intend to run GNU/Linux on a PC, and a competing manufacturer doesn't offer a comparable PC that ships with GNU/Linux, then Windows is "vendor crapware".
And that's why the heavy government regulation of email is why I can send an email from my account to anyone, no matter what mail-provider he or she is using?
You can send an email. But even if your server correctly uses DKIM and SPF, your server's outgoing mail will likely just end up in the recipient's junk mail folder unless you lease an increasingly scarce static IPv4 address and qualify and pay for an EV certificate to give your mail server "instant reputation".
Correction: iMessage/FaceTime is available on two platforms: iOS and macOS. It's not like WhatsApp, which is unavailable to computer-only users by design.
You can't replace a driver and their car working locally with one working in Bangalore.
You might be surprised. Many aircraft are flown by wire, and surgeons have performed remote surgery through an Internet connection. Likewise, if it turns out that engineers cannot make a completely autonomous taxi safe enough for city driving, having someone in Bangalore take the digital wheel might end up being enough.
I thought the company known for domain name front running was Network Solutions. Or is there an article about front running by GoDaddy as well? And has it been a problem since mid-2008 when the tasting fee was introduced?
Install most linux distros and run 'python'. Odds are overwhelming that it will be python 2.
But at least on UNIX and Linux, you don't have the problem where the part of the filename after the last period determines which interpreter is used. Instead, you have the executable bit, which causes the OS to read the first line of the file to find the interpreter:
#!/usr/bin/env python3
This means use the env program and have it search the PATH for an interpreter called python3.
One reason Python 3.0 through 3.2 didn't gain popularity so fast is that on Windows,.py was still associated to Python 2. It took until 3.3 for the Python team to add the PEP 397 launcher, which looks at the first line to determine which interpreter to use UNIX-style. This way side-by-side installations of Python 2 and 3 work as expected.
I completely messed up the terminology in my parent post. I'll try to use standard RLL terminology here.
Commodore 1541 used an (0,2) RLL code that expands each 4 bits to 5 bits. This is similar to IBM GCR, but the code mappings differ.
The earliest model of Apple Disk II (13 sector, DOS 3.2) used a different (0,1) RLL code that expands 5 bits to 8. This allowed 3.25 KiB on each of 35 tracks, or 113.75 KiB per disk side. A later revision of Disk II (16 sector, DOS 3.3/ProDOS) kept the 8-bit words but improved detection of longer gaps between flux transitions, allowing a (0, 2) RLL code that expands 6 bits to 8. This allowed 4 KiB on each of 35 tracks, or 140 KiB per disk side.
IBM floppy drives and Mitsumi Quick Disk used MFM (Modified Frequency Modulation). This is a form of (1, 3) RLL that requires at least one bit of non-transition per transition, expanding 1 bit to 2 but allowing the overall bitrate to be doubled. This resulted in 4.5 KiB per track.
Compact Disc uses EFM, a (2,10) RLL that expands 8 bits to 14 with three linking bits between words. DVD uses the same expansion but with only two linking bits.
With FTTH, it only costs.50 cents per GB to provide bandwidth
Plus maintenance of the outside fiber, including rolling a truck if needed. Plus depreciation of the fiber modem (or whatever they call the device that takes the fiber line and turns it into 1000BASE-T signals at the wall).
get together with friends to play some old-fashioned board games.
I think people don't try this as often as you wish because many people find Internet cheaper than airfare and/or cab fare to travel to where their friends live.
Has Apple solved the problem of wireless interference?
Not perfectly solved, but spread spectrum and multiple-access schemes have made the problem less noticeable. An actual solution would involve beamforming to make the transmission and reception more strongly directional.
Is there really that much exclusive media that's only available in iTunes?
They did. For a long time, the album Sehnsucht by Rammstein wasn't available on Google Play or Amazon Music, only iTunes. And even now, there are plenty of iOS-exclusive games that haven't been ported to Android, such as Tiny Wings.
being an Apple developer I can't just switch to some laptop running Linux.
In theory, you could try coding your Mac apps for GNUstep, a free clone of most of Cocoa. (Cocoa is derived from the reference implementation of OpenStep, and GNUstep is a reimplementation of OpenStep.) Then solve incompatibilities with macOS on a separate desktop Mac (Mac mini or iMac) at home or at the office. The bonus is that you get Linux/Mac cross-compatibility for a large percentage of your application's functionality.
No. Many of the apps were developed on previous versions, like Windows 7, and would automatically be x86 only.
How would they "automatically be x86 only" even if recompiled? Did they contain substantial code written in assembly language or something? Or are you assuming that all developers of desktop apps for Windows 7 would have refused to recompile their apps for RT, particularly developers of apps distributed under a free software license?
Vendors who didn't compile for RT just missed a small part of the Surface market
How large was the Surface RT market compared to the Surface Pro market? My claim is that the Surface RT market remained "small" precisely because Microsoft refused to let developers recompile desktop apps for RT.
I don't think being able to sell them through the store would be likely to convince any developers to go to the trouble of reworking and recompiling for Arm
I disagree. There are plenty of Android NDK apps that have both ARM and Atom (x86) versions. And do you already forget the transition of macOS from 68K to PowerPC to Intel?
Those traditional desktop applications are all x86 assemblies. Can't run them on an ARM operating system
True, but not because of the ISA difference. Many developers of Windows desktop applications were willing to recompile them for ARM, just as Mac apps had been recompiled for PowerPC and then for Intel. Microsoft wouldn't let them, and it enforced this through a policy of not allowing any code to execute on the device unless signed by Microsoft, as if it were a g**d*** Xbox.
Given time I'm sure some linux developer will resolve that issue. Other than that, just don't buy it.
But given time, Lenovo will probably switch to some other weird hardware with no Linux drivers, and the cycle starts anew.
From the article you linked:
Loving GNU/Linux on servers != loving GNU/Linux on laptops and home desktop PCs. Microsoft attempts to make up for it:
Of these three, a port of Skype with a largely outdated feature set is available for GNU/Linux. For the others, Microsoft falls back on "Linux-based" Android with Google Play, which isn't GNU/Linux and isn't intended to work on traditional desktop or laptop PCs. Android prior to 7.0 "Nougat" doesn't even have window tiling as a standard feature, instead forcing applications to run in the full screen. Enjoy your four-function calculator filling your 10-inch tablet.
In fact, Windows Signature Edition offers the end-user even more control by giving them an OS free of vendor crapware.
If you intend to run GNU/Linux on a PC, and a competing manufacturer doesn't offer a comparable PC that ships with GNU/Linux, then Windows is "vendor crapware".
And that's why the heavy government regulation of email is why I can send an email from my account to anyone, no matter what mail-provider he or she is using?
You can send an email. But even if your server correctly uses DKIM and SPF, your server's outgoing mail will likely just end up in the recipient's junk mail folder unless you lease an increasingly scarce static IPv4 address and qualify and pay for an EV certificate to give your mail server "instant reputation".
Correction: iMessage/FaceTime is available on two platforms: iOS and macOS. It's not like WhatsApp, which is unavailable to computer-only users by design.
I appear to have failed to get across that a mixture of AI and remote control from Bangalore could be required.
You can't replace a driver and their car working locally with one working in Bangalore.
You might be surprised. Many aircraft are flown by wire, and surgeons have performed remote surgery through an Internet connection. Likewise, if it turns out that engineers cannot make a completely autonomous taxi safe enough for city driving, having someone in Bangalore take the digital wheel might end up being enough.
I thought the company known for domain name front running was Network Solutions. Or is there an article about front running by GoDaddy as well? And has it been a problem since mid-2008 when the tasting fee was introduced?
If you have an "ERP style website", it's probably a web application.
Install most linux distros and run 'python'. Odds are overwhelming that it will be python 2.
But at least on UNIX and Linux, you don't have the problem where the part of the filename after the last period determines which interpreter is used. Instead, you have the executable bit, which causes the OS to read the first line of the file to find the interpreter:
This means use the env program and have it search the PATH for an interpreter called python3.
One reason Python 3.0 through 3.2 didn't gain popularity so fast is that on Windows, .py was still associated to Python 2. It took until 3.3 for the Python team to add the PEP 397 launcher, which looks at the first line to determine which interpreter to use UNIX-style. This way side-by-side installations of Python 2 and 3 work as expected.
Emacs has had a text editor for a while. It's called Viper Mode.
I completely messed up the terminology in my parent post. I'll try to use standard RLL terminology here.
Commodore 1541 used an (0,2) RLL code that expands each 4 bits to 5 bits. This is similar to IBM GCR, but the code mappings differ.
The earliest model of Apple Disk II (13 sector, DOS 3.2) used a different (0,1) RLL code that expands 5 bits to 8. This allowed 3.25 KiB on each of 35 tracks, or 113.75 KiB per disk side. A later revision of Disk II (16 sector, DOS 3.3/ProDOS) kept the 8-bit words but improved detection of longer gaps between flux transitions, allowing a (0, 2) RLL code that expands 6 bits to 8. This allowed 4 KiB on each of 35 tracks, or 140 KiB per disk side.
IBM floppy drives and Mitsumi Quick Disk used MFM (Modified Frequency Modulation). This is a form of (1, 3) RLL that requires at least one bit of non-transition per transition, expanding 1 bit to 2 but allowing the overall bitrate to be doubled. This resulted in 4.5 KiB per track.
Compact Disc uses EFM, a (2,10) RLL that expands 8 bits to 14 with three linking bits between words. DVD uses the same expansion but with only two linking bits.
Commodore used 5:4 GCR. Apple used a different 6:2 GCR.
With FTTH, it only costs .50 cents per GB to provide bandwidth
Plus maintenance of the outside fiber, including rolling a truck if needed. Plus depreciation of the fiber modem (or whatever they call the device that takes the fiber line and turns it into 1000BASE-T signals at the wall).
get together with friends to play some old-fashioned board games.
I think people don't try this as often as you wish because many people find Internet cheaper than airfare and/or cab fare to travel to where their friends live.
Your sarcastic suggestion actually exists, in the form of an Apple Watch as a limited-function display for your iPhone.
Has Apple solved the problem of wireless interference?
Not perfectly solved, but spread spectrum and multiple-access schemes have made the problem less noticeable. An actual solution would involve beamforming to make the transmission and reception more strongly directional.
Is there really that much exclusive media that's only available in iTunes?
They did. For a long time, the album Sehnsucht by Rammstein wasn't available on Google Play or Amazon Music, only iTunes. And even now, there are plenty of iOS-exclusive games that haven't been ported to Android, such as Tiny Wings.
being an Apple developer I can't just switch to some laptop running Linux.
In theory, you could try coding your Mac apps for GNUstep, a free clone of most of Cocoa. (Cocoa is derived from the reference implementation of OpenStep, and GNUstep is a reimplementation of OpenStep.) Then solve incompatibilities with macOS on a separate desktop Mac (Mac mini or iMac) at home or at the office. The bonus is that you get Linux/Mac cross-compatibility for a large percentage of your application's functionality.
every crappy PA comes with BT
BT? We came to drop bombs, calling every man to arms.
No. Many of the apps were developed on previous versions, like Windows 7, and would automatically be x86 only.
How would they "automatically be x86 only" even if recompiled? Did they contain substantial code written in assembly language or something? Or are you assuming that all developers of desktop apps for Windows 7 would have refused to recompile their apps for RT, particularly developers of apps distributed under a free software license?
Vendors who didn't compile for RT just missed a small part of the Surface market
How large was the Surface RT market compared to the Surface Pro market? My claim is that the Surface RT market remained "small" precisely because Microsoft refused to let developers recompile desktop apps for RT.
I tried to mention tools like yours, but even including your initials in my comment caused it to trip Slashdot's lameness filter.
I don't think being able to sell them through the store would be likely to convince any developers to go to the trouble of reworking and recompiling for Arm
I disagree. There are plenty of Android NDK apps that have both ARM and Atom (x86) versions. And do you already forget the transition of macOS from 68K to PowerPC to Intel?
Adobe bought Cool Edit Pro, renamed it Audition, and put it behind a $240/year Creative Cloud subscription (source).
Those traditional desktop applications are all x86 assemblies. Can't run them on an ARM operating system
True, but not because of the ISA difference. Many developers of Windows desktop applications were willing to recompile them for ARM, just as Mac apps had been recompiled for PowerPC and then for Intel. Microsoft wouldn't let them, and it enforced this through a policy of not allowing any code to execute on the device unless signed by Microsoft, as if it were a g**d*** Xbox.