Yes, because the moment we decide "we don't need any more OSes" is the moment we decide that "innovation" is done and nothing new is to be had unless it comes from Google, Microsoft, or Apple. And that's a bad, bad state to be in.
Consenting adults will absolutely be allowed to, once 23andMe complies with the regulations we have empowered the FDA to impose upon corporations acting in a medial scope.
This isn't an impingement on your rights to control you, it's a regulatory burden imposed upon a corporation to defend the validity of its product.
The Founding Fathers never imagined or desired a federal government that regulates every aspect of our lives and runs 25% of the economy.
They were men of the late-18th century, there is a great deal they could never have imagined. That said, the current state of things has been 200+ years in the making- and it began almost immediately after the country was founded.
They certainly did not imagine or want anything like the FDA, DEA, or other such institutions.
To put the FDA in the same ranks as the DEA is ridiculous. The FDA came into existence because corporations and quacks were pushing shit out that was tainted, dangerous, and exploited people's ignorance and penchant for magical thinking. The DEA exists because prudish people beset by an "us vs. them" atmosphere are easily manipulated.
With luck, times will change and the DEA will go away. The FDA needs maintenance, but will remain because it serves a useful purpose.
The federal government is supposed to defend the nation and make sure that nobody interferes with free trade between the states, that's all.
Maybe in a naive, simplistic view of government. Frankly I rather like not having to deal with corporations on the basis of caveat emptor.
What the FDA is really afraid of is that people with a positive test demand costly follow-up tests, costs that would be quite inconvenient for Medicare/Medicaid and (now) the new Obamacare programs.
Actually what they're really afraid of is the return of the ancient aliens that society was built upon. And there's equal evidence for both our conclusions.
So long as the addon interface remains as powerful as it is, you can have any browser you want. Running FF28 with Australis now, and it's not far from FF27. I'm sure more changes could be done.
Why does an open-source project need to spend thirty million dollars promoting a "brand" most people are already fully aware of?
That's a very, very generous assumption. I would argue that IE and Safari have far more brand awareness than Firefox. What Firefox does have is a very loyal user base that promote it.
Firefox already has a healthy enough market share; there's no NEED for it to have more.
You make the assumption that the expenses aren't necessary to merely tread water and trade 1-2% with Chrome annually.
If it truly costs $150M/year to work on the "products" Mozilla produces, that's absurdly inefficient.
Because R&D is free, right? Or, rather, do you consider R&D to be pointless and not something Mozilla should do?
You know as well as I do that there is no way they would get enough donations. If they switched to that it's a virtual guarantee that Mozilla would be gone within a year.
What the fuck is Mozilla doing promoting a surfing competition?
Branding.
Why the fuck is Mozilla making an OS and trying to sell cell phones?
For the same reason they make Firefox - diversity and promotion of standards. They don't sell cellphones though.
nobody was clamoring for the moron-ization of Firefox's controls
Moron-ization? Between all the addons I've never had a more complex and capable browser. Perhaps you are annoyed at the defaults?
Want to only keep the last 7 days of history? Too fuckin' bad!
So purge it regularly? It's the second entry in the History menu. Of course, there are always addons that let you do just what you want.
Gee, who has an interest in that? Advertisers like GOOGLE
Paranoid accusation made, now prove that Google has access to it. Go on, do it.
About the only thing I see Mozilla doing well these days is pissing people off with every application update
And in my experience, people look aggressively for things to be pissed off about. Mozilla can do no right to many on Slashdot, so I can only assume they all use Chrome, IE, and Safari.
I didn't say that Qt wouldn't have a Mir backend, I said they likely wouldn't accept it upstream. Fucking learn to read, drinkypoo. They're developing all of the Mir backends and will likely be stuck doing out-of-tree maintenance or all of it.
Right, and I suspect that Qt won't either. Thus the increased burden on Canonical to keep all of it going, and why I don't believe it's likely that Mir could be used as a point for lock-in.
They'd have to find a way to lock the toolkits to Mir, which is unlikely. Both GTK and Qt already have Wayland backends, which mean that anything using them should be able to function on Wayland or Mir seamlessly- assuming Mir doesn't require application-level awareness to operate. Hell anything using X11 as its graphical backend should still function.
Linux fully supports TRIM and failure to enable it will not damage the device in any way. What will happen is the device will slow down and spend more time freeing blocks as-needed if the drive is increasingly full.
Of course, if your SSD is your boot drive and you have/home elsewhere, chances are you aren't going to suffer and current drives are significantly faster than older ones (and at their worst, still significantly faster than rotating media.)
The "everything in the kernel project" model means that every fix to every driver is dependent upon the upstream maintainers taking the changes. That's a maintenance nightmare.
Linus was in his early 20s and in college when he created the first version of the kernel.
It it does underscore how those opportunities to create haven't been extended to future 15 year olds in the same manner.
Actually, those opportunities exist for every kid with access to a PC.
If you want to talk about not extending opportunities, talk about devices like iPads that are displacing general purpose PCs. That is how you actively deny such opportunities.
The last two companies I've worked for flat out refuse to hire junior staff and train them.
Fire your management. It's the only way. That said, kernel developers are a distinctly different sort from the average "systems administrator." I did that in the late-90s, early 2000s as a summer job and quickly learned that it wasn't what I wanted to do.
The "everything in the kernel project" model means that every fix to every driver is dependent upon the upstream maintainers taking the changes. That's a maintenance nightmare.
How so? Getting drivers upstream isn't hard unless you're doing something really, really bonkers and or have to duplicate code for some reason. Spreading drivers to the winds would only make it harder to keep them up to date with the kernel, let alone finding them when you need them. Out of tree drivers are a huge pain to manage, something every Android vendor has to deal with because virtually none of the drivers for their support chips go upstream (nothing like a rotten, out of date sound driver.)
Nowadays it is extremely difficult to compile your own custom kernel without tripping into a cluster fuck dependency hell ( usually through no fault of your own / ie i know what i am doing )
If you end up there then I doubt the "I know what I am doing" bit. If you're building your own kernel, the best ways to do it are either make oldconfig if you have a known good one or make modconfig if you're using a pre-built kernel and want to use only what's loaded. I'm not sure how you end up in "dependency hell" when building the kernel because it will autocorrect missing dependencies.
poster above made good points with regard to nonsensical feature dependencies in make menuconfig
I once embarked on a quest to see what it took to discard the entire cryptographic subsystem. Long story short: good luck. I was surprised at how many different hashing and crypto algorithms were required to make use of common hardware and filesystems and network protocols. Are all of these interdependencies really necessary?
Rather than just asking if they are necessary, the better question to ask is what are they using the cryptographic subsystem for? For example, BTRFS does checksumming and offers compression. EXT4 uses CRC32 as well. And that use isn't arbitrary, they use it to protect data integrity and, in the case of BTRFS, maximize use of disk space. The TCP/IP stack offers encryption. These requirements aren't arbitrary, they pull it in to accomplish a specific goal and avoid duplicating code.
ARM is still a disaster.
And it will continue to be so long as every ARM device is its own unique thing. There might be forward progress with AArch64.
I have a Motorola Triumph I don't use anymore, but I wanted to build a custom system for. It uses a Snapdragon SoC and the only kernel I can use with it is a 2.6 series kernel from Motorola (or derivatives based on that code base) with lots of nasty deviations from the mainline kernel tree that will never make it into said mainline tree.
Probably lots of board specific details (the board support package) that have no relevance in the kernel. x86(-64) and other architectures have the advantage that once processor support is added, support for every motherboard that CPU gets plugged into is virtually guaranteed. x86 would have the same problem as ARM if not for the use of things like ACPI, PCI, and the various hardware reporting formats supplied by legacy bios/UEFI.
I have a WonderMedia WM8650-based netbook that originally came with an Android 2.3 port and I can't build anything but the WonderMedia GPL compliance kernel release if I want to use most of the hardware in the netbook, even though general WM8650 support exists in mainline.
You'll have to blame WonderMedia. Barnes and Noble, Amazon, etc. all do the same thing: baseline GPL compliance release. Chip vendors will do the same thing, releasing only what is necessary and not bothering to integrate upstream. This is no small part of why vendors abandon Android devices so rapidly.
Something needs to change to make it easier for vendors to bring their drivers and SoC specifics to mainline so that ARM devices aren't permanently stuck with the kernel version that they originally shipped with.
Something does need to change, however that something is not in the kernel.
I also have a Fujitsu P2110 with a Transmeta TM5800 CPU that makes my VIA look like an i7. I also own Phenom II servers, AMD A8 laptops, MIPS routers, a Raspberry Pi, and many Android devices I've collected over the years. What I've seen is that the mad rush to develop for every new thing and every new idea results in old hardware being tossed by the wayside and ignored, especially when that hardware isn't based on an x86 processor.
And virtually all of that is still supported, with the ARM caveat noted above. Even the Transmeta CPU is still supported. What ends up happening is that the world moves on, and older hardware passes into history and receives less attention.
Forcing signing to a Microsoft account when you restart until you fail signing in 3-5 times then it lets you do a local account
I hated that. At least you could easily skip it in the original Windows 8 setup. The other solution is to disable network connectivity, it then will let you skip creation of a Microsoft account.
It's probably the most underhanded way I've ever seen to try and herd people into your services.
It was only a bug when it appeared on systems with secure boot enabled, on systems without secure boot, and on Windows RT devices. It still appears on my system because I explicitly turned it off. Now I want to hide the notification.
And give me the ability to hide that stupid "Secure Boot isn't configured correctly" watermark sitting on my desktop! I have it turned off for a reason, I don't need to be harassed constantly about it.
Slashdot Mirror
Yes, because the moment we decide "we don't need any more OSes" is the moment we decide that "innovation" is done and nothing new is to be had unless it comes from Google, Microsoft, or Apple. And that's a bad, bad state to be in.
Consenting adults will absolutely be allowed to, once 23andMe complies with the regulations we have empowered the FDA to impose upon corporations acting in a medial scope.
This isn't an impingement on your rights to control you, it's a regulatory burden imposed upon a corporation to defend the validity of its product.
They were men of the late-18th century, there is a great deal they could never have imagined. That said, the current state of things has been 200+ years in the making- and it began almost immediately after the country was founded.
To put the FDA in the same ranks as the DEA is ridiculous. The FDA came into existence because corporations and quacks were pushing shit out that was tainted, dangerous, and exploited people's ignorance and penchant for magical thinking. The DEA exists because prudish people beset by an "us vs. them" atmosphere are easily manipulated.
With luck, times will change and the DEA will go away. The FDA needs maintenance, but will remain because it serves a useful purpose.
Maybe in a naive, simplistic view of government. Frankly I rather like not having to deal with corporations on the basis of caveat emptor.
Actually what they're really afraid of is the return of the ancient aliens that society was built upon. And there's equal evidence for both our conclusions.
https://addons.mozilla.org/en-US/firefox/addon/classicthemerestorer/
So long as the addon interface remains as powerful as it is, you can have any browser you want. Running FF28 with Australis now, and it's not far from FF27. I'm sure more changes could be done.
That's a very, very generous assumption. I would argue that IE and Safari have far more brand awareness than Firefox. What Firefox does have is a very loyal user base that promote it.
You make the assumption that the expenses aren't necessary to merely tread water and trade 1-2% with Chrome annually.
Because R&D is free, right? Or, rather, do you consider R&D to be pointless and not something Mozilla should do?
You know as well as I do that there is no way they would get enough donations. If they switched to that it's a virtual guarantee that Mozilla would be gone within a year.
Branding.
For the same reason they make Firefox - diversity and promotion of standards. They don't sell cellphones though.
Moron-ization? Between all the addons I've never had a more complex and capable browser. Perhaps you are annoyed at the defaults?
So purge it regularly? It's the second entry in the History menu. Of course, there are always addons that let you do just what you want.
Paranoid accusation made, now prove that Google has access to it. Go on, do it.
And in my experience, people look aggressively for things to be pissed off about. Mozilla can do no right to many on Slashdot, so I can only assume they all use Chrome, IE, and Safari.
Placing a wager on the security of Adobe are we?
Mozilla has only included one, I believe, and was not a significant overall size increase.
When IE and Chrome include it, it's a feature, when Firefox includes it, it's crap. I guess Mozilla can do no right by Slashdot.
I didn't say that Qt wouldn't have a Mir backend, I said they likely wouldn't accept it upstream. Fucking learn to read, drinkypoo. They're developing all of the Mir backends and will likely be stuck doing out-of-tree maintenance or all of it.
It just means that Gartner isn't thinking what they're thinking. They think they are, but it had something to do with porcupines and rubber nipples...
Right, and I suspect that Qt won't either. Thus the increased burden on Canonical to keep all of it going, and why I don't believe it's likely that Mir could be used as a point for lock-in.
They'd have to find a way to lock the toolkits to Mir, which is unlikely. Both GTK and Qt already have Wayland backends, which mean that anything using them should be able to function on Wayland or Mir seamlessly- assuming Mir doesn't require application-level awareness to operate. Hell anything using X11 as its graphical backend should still function.
Linux fully supports TRIM and failure to enable it will not damage the device in any way. What will happen is the device will slow down and spend more time freeing blocks as-needed if the drive is increasingly full.
Of course, if your SSD is your boot drive and you have /home elsewhere, chances are you aren't going to suffer and current drives are significantly faster than older ones (and at their worst, still significantly faster than rotating media.)
Thankfully I never made that claim. The AC below would do well to observe your straw man so he can recognize one in the future.
Linus was in his early 20s and in college when he created the first version of the kernel.
Actually, those opportunities exist for every kid with access to a PC.
If you want to talk about not extending opportunities, talk about devices like iPads that are displacing general purpose PCs. That is how you actively deny such opportunities.
Fire your management. It's the only way. That said, kernel developers are a distinctly different sort from the average "systems administrator." I did that in the late-90s, early 2000s as a summer job and quickly learned that it wasn't what I wanted to do.
How so? Getting drivers upstream isn't hard unless you're doing something really, really bonkers and or have to duplicate code for some reason. Spreading drivers to the winds would only make it harder to keep them up to date with the kernel, let alone finding them when you need them. Out of tree drivers are a huge pain to manage, something every Android vendor has to deal with because virtually none of the drivers for their support chips go upstream (nothing like a rotten, out of date sound driver.)
Yeah, right, IT'S A CONSPIRACY! Come back when you have a source more credible than Newsmax.
They're trolling.
So they're indirect patent trolls via Intellectual Ventures and Rockstar?
Not as long as Microsoft filesystems are the de-facto file systems for SD cards by virtue of their desktop monopoly.
Correction, that should be make localmodconfig. The build system will then prompt you for any missing/new options.
If you end up there then I doubt the "I know what I am doing" bit. If you're building your own kernel, the best ways to do it are either make oldconfig if you have a known good one or make modconfig if you're using a pre-built kernel and want to use only what's loaded. I'm not sure how you end up in "dependency hell" when building the kernel because it will autocorrect missing dependencies.
Nonsensical how?
Rather than just asking if they are necessary, the better question to ask is what are they using the cryptographic subsystem for? For example, BTRFS does checksumming and offers compression. EXT4 uses CRC32 as well. And that use isn't arbitrary, they use it to protect data integrity and, in the case of BTRFS, maximize use of disk space. The TCP/IP stack offers encryption. These requirements aren't arbitrary, they pull it in to accomplish a specific goal and avoid duplicating code.
And it will continue to be so long as every ARM device is its own unique thing. There might be forward progress with AArch64.
Probably lots of board specific details (the board support package) that have no relevance in the kernel. x86(-64) and other architectures have the advantage that once processor support is added, support for every motherboard that CPU gets plugged into is virtually guaranteed. x86 would have the same problem as ARM if not for the use of things like ACPI, PCI, and the various hardware reporting formats supplied by legacy bios/UEFI.
You'll have to blame WonderMedia. Barnes and Noble, Amazon, etc. all do the same thing: baseline GPL compliance release. Chip vendors will do the same thing, releasing only what is necessary and not bothering to integrate upstream. This is no small part of why vendors abandon Android devices so rapidly.
Something does need to change, however that something is not in the kernel.
And virtually all of that is still supported, with the ARM caveat noted above. Even the Transmeta CPU is still supported. What ends up happening is that the world moves on, and older hardware passes into history and receives less attention.
Mos
I hated that. At least you could easily skip it in the original Windows 8 setup. The other solution is to disable network connectivity, it then will let you skip creation of a Microsoft account.
It's probably the most underhanded way I've ever seen to try and herd people into your services.
THERE! Thank you. No more watermark. I wonder if this was their fix for the other systems afflicted with this message.
It was only a bug when it appeared on systems with secure boot enabled, on systems without secure boot, and on Windows RT devices. It still appears on my system because I explicitly turned it off. Now I want to hide the notification.
And give me the ability to hide that stupid "Secure Boot isn't configured correctly" watermark sitting on my desktop! I have it turned off for a reason, I don't need to be harassed constantly about it.