Sorry for bringing logic to a shit-flinging party, can't help myself.
Unfortunately, you didn't. You have to look at absolute numbers, and not percentages, because the subsidies have a multiplicative effect. They not only change the profitability of milk, but they encourage overproduction (because the subsidies are based on production), which drives down prices.
You'd expect if the tariffs were completely out-of-line that nobody in Canada would import dairy form the US, and yet in 2016 alone we imported more than $631 million in dairy from the US. For a population smaller than that of California.
Again -- talk to your own government first. I'd be more than happy to see both of our countries (and the EU, which has the largest dairy subsidies in the world) drop dairy tariffs -- but the unfair subsidies have to come down first. It's the subsidies that have caused the tariffs, not the other way around. Canada is hardly in some power position where we can drop our tariffs and hope for some form of "general goodwill" that the US will stop unfair subsidies and attempts at dumping. The Canadian Government has been clear in the past that if the subsidies go away, we won't need the tariffs anymore.
(like a 270% tariff on dairy going into Canada, a very real and chilling fact about which I had no idea previously).
Then I suppose you also don't know that the US provides over $22 billion a year in direct subsidies to US dairy producers, accounting for over 40% of all dairy profits?
That's right -- American taxpayers are paying for >40% of all dairy production in the US. That has lead to a significant oversupply of milk and cheese products which the US can't sell domestically, so they want to be able to dump it on other countries well below market value (again -- it's government subsidized).
Technically they have a simulator. When you build your Xcode project, it is actually compiled twice: once for the target iOS device, and once for Intel x86_64. When you run your code in the simulator, it's running native Intel code, and not emulating the iPhone/iPad processor as in a full emulation environment.
It's worth being aware of the subtle differences. You can get huge performance increases in your code in the simulated environment, as you effectively have full access to the x86 CPU's processing capabilities. For this reason on-device testing is still very important.
As such, the CN Tower, Skydome (yeah, I still refuse to call it the "Rogers Centre"), the Air Canada Centre, Lakeshore Blvd, the Gardiner Expressway, The Metro Toronto Convention Centre, Union Station, and all those condos on Queens Quay are built on landfill.
(Interesting note -- the Harbour Commission building used to be right on the lakeshore. It's now about half a kilometre inland).
Unix was founded on the ideas of lots os simple command line tools that do one job well and don't depend on system idiosyncracies.
People who say this don't have a particularly deep set of UNIX experiences.
Off the top of my head, I've worked with Linux (on PC, PowerPC, Itanium, S390, and mipsel), *BSD, MacOS, HPUX, AIX, IRIX, XENIX, DYNIX, SunOS, Solaris, and QNX. Most of these various flavours of UNIX have completely different network configuration tooling. Sometimes they are simple tools that don't depend on system idiosyncrasies, sometimes not. Often "ifconfig" and "netstat" aren't present, or if they are, are simply wrappers around other utilities (often provided only to provide better compatibility with shell scripts targeting Linux).
ifconfig and netstat are noteven defined in POSIX.1-2017. Neither is/proc -- not all UNIX systems support procfs (although certainly many do).
Lastly, the tools discussed here in iproute2 originally made their way to Linux in 1999. They aren't new. And they are simple command line tools that do one job and do it well. They simply have more features, and provide better access to lower-level networking entities in Linux.
The history if UNIX has been a mishmash of all sorts of network (and other) configuration tools. Pretending otherwise is simply ignoring UNIX history by people who think Linux is UNIX.
The "Golden Age of Capitalism", post WWII until the mid-1970s, was the result of massive wealth redistribution, e.g. tax payer funded public infrastructure building that created millions of jobs, rapid expansion and subsidy of further and higher education, and progressive taxation, whereby the the richest paid the highest rates of taxes in order to fund govt. infrastructure projects, education, etc., starting from after the Great Depression, which itself was caused by massive wealth inequality. In other words, the USA enjoyed a brief period of unprecedented economic prosperity because it adopted a form of socialist policies known as Keynesianism.
I won't argue that these all played a part; but you're missing a massive truth from this time in history.
Of all the industrialized nations at the end of WWII, only the US and Canada escaped unscathed. The industrial capacity of the other main industrial powers -- particularly England, Germany, France, Italy, and Japan -- were beyond decimated. Factories throughout Europe and Japan were widely destroyed by the end of the war.
And while Canada's industrial capacity increased during the war years, with its significantly larger population and wealth the United States really remained as the only nation with significant industrial output for several decades. It took a roughly generation for Germany and Japan to get back to pre-war output levels. Korea and China weren't heavily industrialized before the war, but built capacity and eventually because industrial powers as well.
The point being, America enjoyed a good decade or two being the only significant industrial power on the planet. The USSR challenged the US in some areas certainly, but they weren't a significant international supplier of manufactured goods (outside of weapons). It took other countries decades to build the sort of capacity needed to challenge the Americans.
But today Asia is heavily industrialized, as is Europe. Japan overtook the US in certain areas back in the 70's and 80's (areas such as cameras and consumer electronics); Japan, Korea, and up-and-coming China are generally considered to have overtaken US automotive manufacturer in small to mid-sized vehicle categories as well (while German, Italian, French, and British manufacturers have put their marks on the high end).
The US had an advantage for an entire generation due to industrial capacity in much of the rest of the world being pounded into rubble. That is no longer the case. Where once the US had no competition, today they do.
Again, not to discount anything you've said -- wealth redistribution built a lot of very important infrastructure for the US. But you have to keep in mind that, during those times, the US didn't really have to compete with much of anybody. They got to win by default for decades. But that's not the world of today, and unless WWIII breaks out (and leaves North America primarily untouched), there isn't any way to turn back the clock to a time when the US had all the infrastructure, and everyone else was rebuilding nearly from scratch.
Seems to be a huge failure in the design of the system.
SMS is a bit of a nasty kludge. The messages themselves exist inside call setup packets that your phone needs to send and receive anyway. It wasn't originally intended for the sending of text messages -- it was merely a packet that needed to be sent and received, but where most of the packet data was empty, and so someone had the bright idea of putting message data in there.
This presents a number of problems. It's not exactly efficient. There is no guarantee of timeliness or message order. You can't message people geographically. And as the number of messages to transmit on a single cell increases, so do lost packets.
At the same time, SMS is store-and-forward; like e-mail if your phone isn't available to receive a transmitted message, the message will be stored and then transmitted once your phone is reconnected to the network. This again affects the timeliness of receiving messages -- if you're cell is offline or out of range, you might get alerts long after they have lost relevance. This would could cause confusion.
SMS was a great way for cell providers to extract more value out of packets of data they had to send and receive anyway, but otherwise SMS is a really crappy protocol. You don't want to base your emergency messaging for the general population of a large geographic area on SMS. You'd break the SMS network.
Notepad is a small simple text editor that exists because occasionally you might need to edit some text files (typically for config files or something). These will be in a Windows friendly text format. It doesn't pretend to do anything remotely sophisticated.
That's great if you're the one running the editor and doing the editing.
What's not so great is when you give a co-worker a bash script, and they open it in Notepad, and then complain to you about all the extra spacing -- forcing you to waste a ton of breath explaining why it's not a problem with the text file, but an issue with their editor.
I once had to send a developer at my employer a SQL script intended to be run on Linux, and they did just this. It was unbelievable how long it took me to finally convince them that Notepad was the issue. And it wasn't just the double-spacing; they early had a fit because the file showed up as "ANSI" encoding in Notepad, whereas the spec said the file had to be UTF-8. So not only did I have to convince them (with lots of references) that Notepad was rendering CR/LF as two lines whereas UNIX systems treat them as a single line ending pair, but then I ALSO had to waste a lot of time convincing them that not only is there no such encoding standard as "ANSI" (a very long-standing bug in Notepad Microsoft has never got around to fixing), but that ASCII and UTF-8 are identical for values between 0x00 and 0x7F (which every byte in the document were within).
It was extremely annoying, because even with lots of links to references as to why they shouldn't be using Notepad for UNIX text files in the first place (and why you can't trust its encoding field), in the end I couldn't convince them. Our DBA eventually had to tell them the file was just fine as-is. And sadly, this wasn't the first person I've had this problem with.
As such, as a non-Windows user I'm rather happy for this change. I can't believe how many developers I run into who have no notion of line termination or the actual details of encoding standards, and who simply trust whatever Notepad tell them. Hopefully it will save me some aggravation in the future.
By "Mac OS", they mean versions of Apple's operating system prior to version 10.0.0
By "macOS", they mean all versions since (and including) 10.0.0.
(Apple renamed Mac OS X to just "macOS" a year or two ago, to better align with "iOS", "tvOS", and "watchOS" naming, as well as to move away from marketing the OS as "version 10", which they had already done for over 15 years).
To confuse matters somewhat, early versions of macOS (OS X) could run Mac OS software that used the old-style CR-only line terminator, so the line demarcating the change isn't exactly clean.
If the tech industry was serious about IOT - tens or hundreds of millions of home devices that are internet connected - they should have gotten together, pooled a few Billion dollars of R&D money, and researched ways to make unauthorized access to these IOT products fucking-difficult-to-near-impossible.
This has been done. But it doesn't stop some fly-by-night overseas hardware manufacturer from churning out quick and dirty hardware that does the job, but which does the quickest and dirtiest job on the software front that they can get away with.
But for a counter-example, look at the work Apple has done with HomeKit. The entire setup is required to be encrypted back to front, and has to undergo an Apple certification program. The end result is pretty much bulletproof -- but the certification requirements that make the system so secure has meant few companies (and certainly none of the cheap-and-dirty ones) have released certified hardware.
That's hardly the fault of IoT as a concept. As with anything else, there will be expensive, better secured, better quality versions, and cheaper, crappier, less secure, low quality versions.
I suspect that Apple will be cloud-nudging and cloud-pushing for things like printing, music playing, and sharing so lack of Bonjour and Airplay is a feature (to them) not a bug.
They can't get rid of Bonjour. It underpins so much of Apple's cloud strategy in the first place. Wide Area Bonjour and Back to My Mac are already Cloud powered, and Wide Area Bonjour needs Bonjour Sleep Proxy if it's going to be able to deal with devices that can go into low power (sleep) mode. When it comes to Bonjour, it's as if you made the statement that Apple doesn't need to support TCP/IP anymore because "Cloud". Even with the cloud, you still want/need Service Discovery.
As for Airplay, considering Apple is getting close to introducing Airplay 2, I doubt it's going anywhere. It's still the only way to push video from an Apple device to an Apple TV, so it won't be going anywhere soon.
(I should note that you can get Bonjour Sleep Proxy service from an Apple TV if your router doesn't supply it, so again -- it's probably not going anywhere).
Sure there are good routers out there -- but do they have all of the protocol support the Apple routers have?
I mean, it if doesn't have Bonjour Sleep Proxy or Wide Area Bonjour (and yes, I use both), regular Bonjour advertisements (for services provided by the router itself), and doesn't have Airplay support, then I'm _losing functionality_. A small speed bump doesn't make up for that.
Besides which, Amplifi's IPv6 support is anemic compared to Apple's. According to their own docs they only support DHCPv6 and 6to4. It doesn't appear to support setting up a manual tunnel to something like tunnelbroker.net. I can only assume it supports ICMPv6 RA's (it would seem to be pretty dumb if it didn't), but that doesn't seem to be an option in their configuration.
So "blows out of the water" seems a rather overblown statement right now. I agree however that it would be awesome if Apple teamed up with Amplifi to get these technologies into their routers as a suitable replacement to Apple's APs (the code for all of them is Open Source, so there are no reasons why it can't be done).
They were fantastic. My AirPort Extreme I think I bought new in 2003 still works.
I have one as well, and it also still works. I haven't used it in over a decade, as it capped out at 802.11a/g and I relaxed it with the 802.11n version (and later the 802.11ac version) when they became available.
Some other cool features that people may have forgotten about -- as the Airport Express was designed for travel, it supported up to five "profiles" you could pre-load into it for connecting to different networks. So you could have one profile for home, and one for use in different hotels (for example). This was awesome at a time when many hotels didn't have their own WiFi networks, but who provided Ethernet for business travellers. You could just plug it in, set it to the correct profile, and have your own secure WPA encrypted WiFi network.
I have five Airport routers, and still actively use three of them (an ac Time Capsule, an n Extreme, and an n Express). I don't expect I'll need to replace them for at least 10 years.
This is really too bad, because the Airport line were fantastic routers, and had a pile of functionality that you can't easily get in any other package.
Back int he mid 2000s, the "flying saucer" routers were designed with institutional use in mind, supporting up to 50 simultaneous connections. They were one of the first home routers that provided IPv6 functionality, both native and tunnelled, right out of the box. They support the Bonjour Sleep Proxy service (I'm not aware of any other router that does), permitting Bonjour services for devices that switch to a low-power mode, along with wide-area Bonjour that can automatically register hosts and their services with a suitable DNS (akin to dynamic DNS, but with services as well). The Expresses have excellent Airplay support, accepting streaming Apple Lossless audio and outputting via either standard analog or digital optical. And the Time Capsules have out-of-the-box support for TimeMachine backups.
They are also very easy to mesh together, and have had it for fifteen years now. The configuration tool will even dynamically generate a connection diagram for all your Airport devices, showing how they interconnect (and whether connections are wired or wireless).
All in all, great routers for the money. I know of no other routers that provide all of these features in one box. Hopefully Apple will partner with someone so we don't lose Bonjour Sleep Proxy and wide-area Bonjour support in particular. And at least my existing installations will continue to work for many years yet. Still a bit of a sad day -- Apple used to be ahead of the curve, but let the market slip past them.
I have to agree with the GP that $10/mo is too high. And it has nothing to do with being cheap.
I'm not a heavy music listener. When I leave my door, I don't generally bother taking my earphones with me. In the car I listen to news and information. I'm married with a young daughter who is still into Wheels on the Bus. I'm lucky if I have the opportunity to just sit and listen to music for an hour or two a week. Combine that with having racked up a pretty good collection of legally purchased music over the years, and $10/mo really isn't that great of a deal.
If they had a $4/mo plan I'd pull the trigger. And $10/mo might seem like a great deal if I was spending 4 - 6 hours a day listening to music, but I don't. As it is, I have an Amazon Prime membership and can access their streaming library -- which while not as comprehensive as Spotify does give me significant value as it comes with free 2-day shipping and Prime Video, all for less per month than what Spotify charges.
It costs too much for what it is, and for how much value I'd be able to extract for it. That may be different for you, but not everyone is you.
Yeah -- I noticed that too. The funny thing is that I was just this past week assigned a brand-new MacBook Pro at work (running 10.13.4), and one of the first things I did was go to the App Store, find my Purchased items list, and download a bunch of items I have on my other Macs, one of which was TextWrangler. And it worked just fine (with the exception of the command line utilities, the installer for which seemed to stop working once Apple put added protections into the system directories. Which doesn't bother me, as I have bash aliases setup to do the same thing anyway).
I suspect Apple will drop that in 10.14, and will recommend VLC as an alternative. Either way, free app, free replacement, no great loss.
I suspect you're right -- Apple hasn't shipped a Mac with an optical drive for several years at least. And I doubt all that many people have unencrypted DVD backups stored on their machines for local playback.
That one is kind of embarrassing and sad; I suspect it involves 32-bit-only user-space driver code written by tablet vendors, but I'm not certain.
I suspect it's another little-used item that has simply been neglected due to low use.
Games are the big exception. Steam itself, however, is an embarrassment, and 64-bit support is probably just the tip of the iceberg. I wonder if they ever got around to fixing the dozens of bugs that prevented running the Mac version on a case-sensitive volume. Either way, I think it's safe to say that this announcement will light a fire under a company that IMO otherwise wouldn't bother fixing anything nonfatal....
We can only hope. My concern however is that even though they might eventually get around to making Steam 64-bit, will they go back and update some of their classic games for 64-bit as well? I'll admit I'm not a heavy Steam user, but it is the best way to get my occasional Portal 2 fix.
McAfee Endpoint Security
Wow. There are serious security implications involved in running 32-bit code. You've really gotta question any security-related app that still hasn't been compiled to support ASLR. That said, again, I wouldn't really call that an app.
Why not? It isn't just a backend service; it has a full GUI interface. And it isn't as if it's some out-of-date piece of software; the latest definitions for it are dated today. I can' help but feel we're getting into "No True Scotsmen" territory here...
Hmm. They have a 64-bit iOS client, which means most of their code base should literally be a simple recompile to run on 64-bit. What the heck, Cisco? Either way, again, I don't see them abandoning the Mac platform, so you can probably assume that they'll update it soon enough.
I've heard they had a 64-bit client very briefly released, but they had to pull it due to bugs/technical issues. So I suspect it's coming.
The point being, one can't say that 32 bit software on macOS is "really, really rare". As a fraction of the total software currently available for macOS it's probably pretty small, but some of the worst offenders are those that either a) still ship with the OS itself, or b) perform common vital functions that are used by a large number of users (anti-virus, VPN). I'm sure many of these will shake themselves out sooner rather than later (especially with Apple now warning users running these packages), but that wasn't really the point of my post.
Correcting myself slightly -- I only just discovered that TextWrangler has been replaced with the nearly identical BBEdit, which is 64-bit. So scratch that one off the list (or upgrade if like me you haven't done so already).
32-bit Intel apps are really, really rare on OS X.
I'd be careful with those qualifies if I were you.
Some significant software packages on macOS 10.13.4 are only available in 32-bit versions, including some of the software that ships with macOS. These include:
* Apple's DVD Player
* Apple's InkServer input method
* Steam
* McAfee Endpoint Security
* Cisco Anyconnect VPN Client for Mac
* TextWrangler (a popular text editor)
As such, I wouldn't say that 32-bit Intel apps are "really, really rare". Unless you've removed them manually, you have the DVD player and InkServer installed on your Mac. If you use a corporate Mac, you probably require McAfee Endpoint Security and/or Cisco Anyconnect. Hopefully these developers get with the programme and release 64-bit updates in the near future.
It can be. macOS includes Apple's Hypervisor.framework, atop which tools (such as xhyve) can be used to run Linux inside macOS.
This is how Docker for Mac works; it runs the Linux kernel inside Apple's Hypervisor.framework, allowing you to run Linux containers. If you have XQuartz installed, with a bit of fiddling you can run Linux GUI apps inside Docker containers on the macOS desktop.
Slashdot Mirror
Sorry for bringing logic to a shit-flinging party, can't help myself.
Unfortunately, you didn't. You have to look at absolute numbers, and not percentages, because the subsidies have a multiplicative effect. They not only change the profitability of milk, but they encourage overproduction (because the subsidies are based on production), which drives down prices.
Indeed, according to government numbers, the US has a 5-1 price edge against Canada in dairy pricing due to subsidies. That should call for a 500% subsidy to fully correct for, and yet we only charge a 270% tariff.
You'd expect if the tariffs were completely out-of-line that nobody in Canada would import dairy form the US, and yet in 2016 alone we imported more than $631 million in dairy from the US. For a population smaller than that of California.
Again -- talk to your own government first. I'd be more than happy to see both of our countries (and the EU, which has the largest dairy subsidies in the world) drop dairy tariffs -- but the unfair subsidies have to come down first. It's the subsidies that have caused the tariffs, not the other way around. Canada is hardly in some power position where we can drop our tariffs and hope for some form of "general goodwill" that the US will stop unfair subsidies and attempts at dumping. The Canadian Government has been clear in the past that if the subsidies go away, we won't need the tariffs anymore.
Yaz
(like a 270% tariff on dairy going into Canada, a very real and chilling fact about which I had no idea previously).
Then I suppose you also don't know that the US provides over $22 billion a year in direct subsidies to US dairy producers, accounting for over 40% of all dairy profits?
That's right -- American taxpayers are paying for >40% of all dairy production in the US. That has lead to a significant oversupply of milk and cheese products which the US can't sell domestically, so they want to be able to dump it on other countries well below market value (again -- it's government subsidized).
That is why Canada has a tariff on US dairy products. Canada doesn't subsidize its dairy industry at all. The tariffs came into effect because the US insists on subsidizing its dairy industry with more US tax dollars than the entire Canadian dairy industry is worth.
And you know what? Even with all that, Canada imports more dairy from the US than it exports (see above link).
Want to get rid of the tariffs? Get rid of your own market distorting subsidies first, then we can talk.
Yaz
They have an emulator in XCode.
Technically they have a simulator. When you build your Xcode project, it is actually compiled twice: once for the target iOS device, and once for Intel x86_64. When you run your code in the simulator, it's running native Intel code, and not emulating the iPhone/iPad processor as in a full emulation environment.
It's worth being aware of the subtle differences. You can get huge performance increases in your code in the simulated environment, as you effectively have full access to the x86 CPU's processing capabilities. For this reason on-device testing is still very important.
Yaz
Being on landfill, I'm guessing that foundations for highrise buildings would be difficult/expensive.
Everything south of Front street is landfill. When Front Street was laid down in 1796 (!), it was right along the shoreline of Lake Ontario.
As such, the CN Tower, Skydome (yeah, I still refuse to call it the "Rogers Centre"), the Air Canada Centre, Lakeshore Blvd, the Gardiner Expressway, The Metro Toronto Convention Centre, Union Station, and all those condos on Queens Quay are built on landfill.
(Interesting note -- the Harbour Commission building used to be right on the lakeshore. It's now about half a kilometre inland).
Yaz
Unix was founded on the ideas of lots os simple command line tools that do one job well and don't depend on system idiosyncracies.
People who say this don't have a particularly deep set of UNIX experiences.
Off the top of my head, I've worked with Linux (on PC, PowerPC, Itanium, S390, and mipsel), *BSD, MacOS, HPUX, AIX, IRIX, XENIX, DYNIX, SunOS, Solaris, and QNX. Most of these various flavours of UNIX have completely different network configuration tooling. Sometimes they are simple tools that don't depend on system idiosyncrasies, sometimes not. Often "ifconfig" and "netstat" aren't present, or if they are, are simply wrappers around other utilities (often provided only to provide better compatibility with shell scripts targeting Linux).
ifconfig and netstat are not even defined in POSIX.1-2017. Neither is /proc -- not all UNIX systems support procfs (although certainly many do).
Lastly, the tools discussed here in iproute2 originally made their way to Linux in 1999. They aren't new. And they are simple command line tools that do one job and do it well. They simply have more features, and provide better access to lower-level networking entities in Linux.
The history if UNIX has been a mishmash of all sorts of network (and other) configuration tools. Pretending otherwise is simply ignoring UNIX history by people who think Linux is UNIX.
Yaz
The "Golden Age of Capitalism", post WWII until the mid-1970s, was the result of massive wealth redistribution, e.g. tax payer funded public infrastructure building that created millions of jobs, rapid expansion and subsidy of further and higher education, and progressive taxation, whereby the the richest paid the highest rates of taxes in order to fund govt. infrastructure projects, education, etc., starting from after the Great Depression, which itself was caused by massive wealth inequality. In other words, the USA enjoyed a brief period of unprecedented economic prosperity because it adopted a form of socialist policies known as Keynesianism.
I won't argue that these all played a part; but you're missing a massive truth from this time in history.
Of all the industrialized nations at the end of WWII, only the US and Canada escaped unscathed. The industrial capacity of the other main industrial powers -- particularly England, Germany, France, Italy, and Japan -- were beyond decimated. Factories throughout Europe and Japan were widely destroyed by the end of the war.
And while Canada's industrial capacity increased during the war years, with its significantly larger population and wealth the United States really remained as the only nation with significant industrial output for several decades. It took a roughly generation for Germany and Japan to get back to pre-war output levels. Korea and China weren't heavily industrialized before the war, but built capacity and eventually because industrial powers as well.
The point being, America enjoyed a good decade or two being the only significant industrial power on the planet. The USSR challenged the US in some areas certainly, but they weren't a significant international supplier of manufactured goods (outside of weapons). It took other countries decades to build the sort of capacity needed to challenge the Americans.
But today Asia is heavily industrialized, as is Europe. Japan overtook the US in certain areas back in the 70's and 80's (areas such as cameras and consumer electronics); Japan, Korea, and up-and-coming China are generally considered to have overtaken US automotive manufacturer in small to mid-sized vehicle categories as well (while German, Italian, French, and British manufacturers have put their marks on the high end).
The US had an advantage for an entire generation due to industrial capacity in much of the rest of the world being pounded into rubble. That is no longer the case. Where once the US had no competition, today they do.
Again, not to discount anything you've said -- wealth redistribution built a lot of very important infrastructure for the US. But you have to keep in mind that, during those times, the US didn't really have to compete with much of anybody. They got to win by default for decades. But that's not the world of today, and unless WWIII breaks out (and leaves North America primarily untouched), there isn't any way to turn back the clock to a time when the US had all the infrastructure, and everyone else was rebuilding nearly from scratch.
Yaz
Seems to be a huge failure in the design of the system.
SMS is a bit of a nasty kludge. The messages themselves exist inside call setup packets that your phone needs to send and receive anyway. It wasn't originally intended for the sending of text messages -- it was merely a packet that needed to be sent and received, but where most of the packet data was empty, and so someone had the bright idea of putting message data in there.
This presents a number of problems. It's not exactly efficient. There is no guarantee of timeliness or message order. You can't message people geographically. And as the number of messages to transmit on a single cell increases, so do lost packets.
At the same time, SMS is store-and-forward; like e-mail if your phone isn't available to receive a transmitted message, the message will be stored and then transmitted once your phone is reconnected to the network. This again affects the timeliness of receiving messages -- if you're cell is offline or out of range, you might get alerts long after they have lost relevance. This would could cause confusion.
SMS was a great way for cell providers to extract more value out of packets of data they had to send and receive anyway, but otherwise SMS is a really crappy protocol. You don't want to base your emergency messaging for the general population of a large geographic area on SMS. You'd break the SMS network.
Yaz
Notepad is a small simple text editor that exists because occasionally you might need to edit some text files (typically for config files or something). These will be in a Windows friendly text format. It doesn't pretend to do anything remotely sophisticated.
That's great if you're the one running the editor and doing the editing.
What's not so great is when you give a co-worker a bash script, and they open it in Notepad, and then complain to you about all the extra spacing -- forcing you to waste a ton of breath explaining why it's not a problem with the text file, but an issue with their editor.
I once had to send a developer at my employer a SQL script intended to be run on Linux, and they did just this. It was unbelievable how long it took me to finally convince them that Notepad was the issue. And it wasn't just the double-spacing; they early had a fit because the file showed up as "ANSI" encoding in Notepad, whereas the spec said the file had to be UTF-8. So not only did I have to convince them (with lots of references) that Notepad was rendering CR/LF as two lines whereas UNIX systems treat them as a single line ending pair, but then I ALSO had to waste a lot of time convincing them that not only is there no such encoding standard as "ANSI" (a very long-standing bug in Notepad Microsoft has never got around to fixing), but that ASCII and UTF-8 are identical for values between 0x00 and 0x7F (which every byte in the document were within).
It was extremely annoying, because even with lots of links to references as to why they shouldn't be using Notepad for UNIX text files in the first place (and why you can't trust its encoding field), in the end I couldn't convince them. Our DBA eventually had to tell them the file was just fine as-is. And sadly, this wasn't the first person I've had this problem with.
As such, as a non-Windows user I'm rather happy for this change. I can't believe how many developers I run into who have no notion of line termination or the actual details of encoding standards, and who simply trust whatever Notepad tell them. Hopefully it will save me some aggravation in the future.
Yaz
By "Mac OS", they mean versions of Apple's operating system prior to version 10.0.0
By "macOS", they mean all versions since (and including) 10.0.0.
(Apple renamed Mac OS X to just "macOS" a year or two ago, to better align with "iOS", "tvOS", and "watchOS" naming, as well as to move away from marketing the OS as "version 10", which they had already done for over 15 years).
To confuse matters somewhat, early versions of macOS (OS X) could run Mac OS software that used the old-style CR-only line terminator, so the line demarcating the change isn't exactly clean.
Yaz
If the tech industry was serious about IOT - tens or hundreds of millions of home devices that are internet connected - they should have gotten together, pooled a few Billion dollars of R&D money, and researched ways to make unauthorized access to these IOT products fucking-difficult-to-near-impossible.
This has been done. But it doesn't stop some fly-by-night overseas hardware manufacturer from churning out quick and dirty hardware that does the job, but which does the quickest and dirtiest job on the software front that they can get away with.
But for a counter-example, look at the work Apple has done with HomeKit. The entire setup is required to be encrypted back to front, and has to undergo an Apple certification program. The end result is pretty much bulletproof -- but the certification requirements that make the system so secure has meant few companies (and certainly none of the cheap-and-dirty ones) have released certified hardware.
That's hardly the fault of IoT as a concept. As with anything else, there will be expensive, better secured, better quality versions, and cheaper, crappier, less secure, low quality versions.
Yaz
List of international .gov two-level domain equivalents
That's more than a handful.
Yaz
Isn't this why there are top level .gov sites?
No. .gov is reserved for US Government agencies only. They are not available to other countries.
Most other countries use a second-level domain against their country level domain for Government specific sites, like Canada's .gc.ca domain.
Yaz
I suspect that Apple will be cloud-nudging and cloud-pushing for things like printing, music playing, and sharing so lack of Bonjour and Airplay is a feature (to them) not a bug.
They can't get rid of Bonjour. It underpins so much of Apple's cloud strategy in the first place. Wide Area Bonjour and Back to My Mac are already Cloud powered, and Wide Area Bonjour needs Bonjour Sleep Proxy if it's going to be able to deal with devices that can go into low power (sleep) mode. When it comes to Bonjour, it's as if you made the statement that Apple doesn't need to support TCP/IP anymore because "Cloud". Even with the cloud, you still want/need Service Discovery.
As for Airplay, considering Apple is getting close to introducing Airplay 2, I doubt it's going anywhere. It's still the only way to push video from an Apple device to an Apple TV, so it won't be going anywhere soon.
(I should note that you can get Bonjour Sleep Proxy service from an Apple TV if your router doesn't supply it, so again -- it's probably not going anywhere).
Yaz
Sure there are good routers out there -- but do they have all of the protocol support the Apple routers have?
I mean, it if doesn't have Bonjour Sleep Proxy or Wide Area Bonjour (and yes, I use both), regular Bonjour advertisements (for services provided by the router itself), and doesn't have Airplay support, then I'm _losing functionality_. A small speed bump doesn't make up for that.
Besides which, Amplifi's IPv6 support is anemic compared to Apple's. According to their own docs they only support DHCPv6 and 6to4. It doesn't appear to support setting up a manual tunnel to something like tunnelbroker.net. I can only assume it supports ICMPv6 RA's (it would seem to be pretty dumb if it didn't), but that doesn't seem to be an option in their configuration.
So "blows out of the water" seems a rather overblown statement right now. I agree however that it would be awesome if Apple teamed up with Amplifi to get these technologies into their routers as a suitable replacement to Apple's APs (the code for all of them is Open Source, so there are no reasons why it can't be done).
Yaz
They were fantastic. My AirPort Extreme I think I bought new in 2003 still works.
I have one as well, and it also still works. I haven't used it in over a decade, as it capped out at 802.11a/g and I relaxed it with the 802.11n version (and later the 802.11ac version) when they became available.
Some other cool features that people may have forgotten about -- as the Airport Express was designed for travel, it supported up to five "profiles" you could pre-load into it for connecting to different networks. So you could have one profile for home, and one for use in different hotels (for example). This was awesome at a time when many hotels didn't have their own WiFi networks, but who provided Ethernet for business travellers. You could just plug it in, set it to the correct profile, and have your own secure WPA encrypted WiFi network.
I have five Airport routers, and still actively use three of them (an ac Time Capsule, an n Extreme, and an n Express). I don't expect I'll need to replace them for at least 10 years.
Yaz
This is really too bad, because the Airport line were fantastic routers, and had a pile of functionality that you can't easily get in any other package.
Back int he mid 2000s, the "flying saucer" routers were designed with institutional use in mind, supporting up to 50 simultaneous connections. They were one of the first home routers that provided IPv6 functionality, both native and tunnelled, right out of the box. They support the Bonjour Sleep Proxy service (I'm not aware of any other router that does), permitting Bonjour services for devices that switch to a low-power mode, along with wide-area Bonjour that can automatically register hosts and their services with a suitable DNS (akin to dynamic DNS, but with services as well). The Expresses have excellent Airplay support, accepting streaming Apple Lossless audio and outputting via either standard analog or digital optical. And the Time Capsules have out-of-the-box support for TimeMachine backups.
They are also very easy to mesh together, and have had it for fifteen years now. The configuration tool will even dynamically generate a connection diagram for all your Airport devices, showing how they interconnect (and whether connections are wired or wireless).
All in all, great routers for the money. I know of no other routers that provide all of these features in one box. Hopefully Apple will partner with someone so we don't lose Bonjour Sleep Proxy and wide-area Bonjour support in particular. And at least my existing installations will continue to work for many years yet. Still a bit of a sad day -- Apple used to be ahead of the curve, but let the market slip past them.
Yaz
I have to agree with the GP that $10/mo is too high. And it has nothing to do with being cheap.
I'm not a heavy music listener. When I leave my door, I don't generally bother taking my earphones with me. In the car I listen to news and information. I'm married with a young daughter who is still into Wheels on the Bus. I'm lucky if I have the opportunity to just sit and listen to music for an hour or two a week. Combine that with having racked up a pretty good collection of legally purchased music over the years, and $10/mo really isn't that great of a deal.
If they had a $4/mo plan I'd pull the trigger. And $10/mo might seem like a great deal if I was spending 4 - 6 hours a day listening to music, but I don't. As it is, I have an Amazon Prime membership and can access their streaming library -- which while not as comprehensive as Spotify does give me significant value as it comes with free 2-day shipping and Prime Video, all for less per month than what Spotify charges.
It costs too much for what it is, and for how much value I'd be able to extract for it. That may be different for you, but not everyone is you.
Yaz
You're welcome.
Yaz
Yeah -- I noticed that too. The funny thing is that I was just this past week assigned a brand-new MacBook Pro at work (running 10.13.4), and one of the first things I did was go to the App Store, find my Purchased items list, and download a bunch of items I have on my other Macs, one of which was TextWrangler. And it worked just fine (with the exception of the command line utilities, the installer for which seemed to stop working once Apple put added protections into the system directories. Which doesn't bother me, as I have bash aliases setup to do the same thing anyway).
Yaz
I suspect Apple will drop that in 10.14, and will recommend VLC as an alternative. Either way, free app, free replacement, no great loss.
I suspect you're right -- Apple hasn't shipped a Mac with an optical drive for several years at least. And I doubt all that many people have unencrypted DVD backups stored on their machines for local playback.
That one is kind of embarrassing and sad; I suspect it involves 32-bit-only user-space driver code written by tablet vendors, but I'm not certain.
I suspect it's another little-used item that has simply been neglected due to low use.
Games are the big exception. Steam itself, however, is an embarrassment, and 64-bit support is probably just the tip of the iceberg. I wonder if they ever got around to fixing the dozens of bugs that prevented running the Mac version on a case-sensitive volume. Either way, I think it's safe to say that this announcement will light a fire under a company that IMO otherwise wouldn't bother fixing anything nonfatal....
We can only hope. My concern however is that even though they might eventually get around to making Steam 64-bit, will they go back and update some of their classic games for 64-bit as well? I'll admit I'm not a heavy Steam user, but it is the best way to get my occasional Portal 2 fix.
McAfee Endpoint Security
Wow. There are serious security implications involved in running 32-bit code. You've really gotta question any security-related app that still hasn't been compiled to support ASLR. That said, again, I wouldn't really call that an app.
Why not? It isn't just a backend service; it has a full GUI interface. And it isn't as if it's some out-of-date piece of software; the latest definitions for it are dated today. I can' help but feel we're getting into "No True Scotsmen" territory here...
Hmm. They have a 64-bit iOS client, which means most of their code base should literally be a simple recompile to run on 64-bit. What the heck, Cisco? Either way, again, I don't see them abandoning the Mac platform, so you can probably assume that they'll update it soon enough.
I've heard they had a 64-bit client very briefly released, but they had to pull it due to bugs/technical issues. So I suspect it's coming.
The point being, one can't say that 32 bit software on macOS is "really, really rare". As a fraction of the total software currently available for macOS it's probably pretty small, but some of the worst offenders are those that either a) still ship with the OS itself, or b) perform common vital functions that are used by a large number of users (anti-virus, VPN). I'm sure many of these will shake themselves out sooner rather than later (especially with Apple now warning users running these packages), but that wasn't really the point of my post.
p>Yaz
And TextWrangler won't run in the current version of OS X, much less the next one.
Actually, I've been running it without any problems on 10.13.4 up until today.
Yaz
Correcting myself slightly -- I only just discovered that TextWrangler has been replaced with the nearly identical BBEdit, which is 64-bit. So scratch that one off the list (or upgrade if like me you haven't done so already).
Yaz
32-bit Intel apps are really, really rare on OS X.
I'd be careful with those qualifies if I were you.
Some significant software packages on macOS 10.13.4 are only available in 32-bit versions, including some of the software that ships with macOS. These include:
As such, I wouldn't say that 32-bit Intel apps are "really, really rare". Unless you've removed them manually, you have the DVD player and InkServer installed on your Mac. If you use a corporate Mac, you probably require McAfee Endpoint Security and/or Cisco Anyconnect. Hopefully these developers get with the programme and release 64-bit updates in the near future.
Yaz
I wonder if I can run Linux inside Windows using parallels?
I'm not sure why you'd want to, but I certainly see no reason why you couldn't do this.
Yaz
MacOS is not used to run Linux on a Mac.
It can be. macOS includes Apple's Hypervisor.framework, atop which tools (such as xhyve) can be used to run Linux inside macOS.
This is how Docker for Mac works; it runs the Linux kernel inside Apple's Hypervisor.framework, allowing you to run Linux containers. If you have XQuartz installed, with a bit of fiddling you can run Linux GUI apps inside Docker containers on the macOS desktop.
Yaz