Don't be suprised, a company with the resources of Microsoft would be stupid not to pay shills to astroturf and FUD on discussion boards. Especially considering what's at stake.
In his Part 2 article, he recommends that you never update any package you don't understand.
I don't know what he does with microsoft update, the list can be pretty cryptic. I guess he doesn't patch because he thinks he's smarter than the vendor.
The ad-hoc random download method is the root of many security problems today. Users are trained to download mostly executable installers from random untrusted sites and run them. Aside from being more convenient, the repository method trains users to search trusted repositories for their software and actively confirm new repositories.
Ubuntu's partner repo is a good example of non-free distribution, although vendors seem to lull in and out of it. If commercial software is considered a necessary evil, what better way to distribute than directly through the distribution repositories? Users trust the software and repo are vetted by the distro, packaged builds are vetted for integration and security updates are automatically handled.
With comprehensive repos you can also train users to not trust plain packages. You effectively solve the human engineering problem of trojan distribution, avoiding junk like antivirus 360.
Ubuntu's goal is to provide a good free operating system for the desktop and server. Whereas their sponsor company, Canonical, is about providing value add support and services like the Landscape management tool which does all that stuff.
I see where you're coming from and the GNU extensions bring some extra ability in that area, but I'm all for using the right tool for the job. Perl is the swiss-army chainsaw, also hammers nails.:)
Python and Perl exist because some things are out of scope for a shell. What do you gain by giving a shell kitchen-sink functionality? Over complicated shell. Unix shell is successful because it is simple to understand and build command chains by checking the output before the next step.
You can by SSD now which consists purely of the same RAM sticks as on your motherboard. This is the idea that I'm getting at. So how do we handle it? Seems a bit wasteful to limit that massive bandwidth through legacy storage interfaces, so put it on the RAM bus. Also a bit redundant to double-handle it via antiquated filesystem IO, so map it directly.
There is no requirement for stream output to be ascii, that is up to the programmer to decide and preferable to having the architecture decision forced on you. But I think you're missing the point that you can actually use Perl or Python as your shell, you have a semantic roadblock from working too closely with monolithic solutions.
I never said that SSD would eliminate RAM either, which in turn will not eliminate on-die cache or registers in the forseeable future. When you've got a practically infinite address space you may as well use it.
Who said anything about flash-based SSD? I said SSD as in SOLID-STATE NON-VOLATILE STORAGE. Regardless, flash now is faster than CPU registers were not so long ago.
The demarcation of storage and RAM is a legacy constraint forced by hardware limitations. Ubiquitous 64-bit and SSD will blur and eventually totally eliminate this separation.
Yeah it was a great design in the day, but every PC component has had DMA for a long time now so there would be no real advantage. There were many advanced features in the AmigaOS such as drivers, plugins and mountpoints but some things may have ended up as security nightmares if they continued as legacy. Arexx ports and lack of memory management come to mind.
Slashdot Mirror
Don't be suprised, a company with the resources of Microsoft would be stupid not to pay shills to astroturf and FUD on discussion boards. Especially considering what's at stake.
That would be any FPS released last year. They're all the same.
TVTime.
In his Part 2 article, he recommends that you never update any package you don't understand.
I don't know what he does with microsoft update, the list can be pretty cryptic. I guess he doesn't patch because he thinks he's smarter than the vendor.
You can pay Ubuntu to give you phone support.
The ad-hoc random download method is the root of many security problems today. Users are trained to download mostly executable installers from random untrusted sites and run them. Aside from being more convenient, the repository method trains users to search trusted repositories for their software and actively confirm new repositories.
Ubuntu's partner repo is a good example of non-free distribution, although vendors seem to lull in and out of it. If commercial software is considered a necessary evil, what better way to distribute than directly through the distribution repositories? Users trust the software and repo are vetted by the distro, packaged builds are vetted for integration and security updates are automatically handled.
With comprehensive repos you can also train users to not trust plain packages. You effectively solve the human engineering problem of trojan distribution, avoiding junk like antivirus 360.
You fly to the moon 1KM at a time.
Ubuntu is not interested in those things
Ubuntu's goal is to provide a good free operating system for the desktop and server. Whereas their sponsor company, Canonical, is about providing value add support and services like the Landscape management tool which does all that stuff.
https://landscape.canonical.com/
Have you evaluated the canonical commercial tools?
I see where you're coming from and the GNU extensions bring some extra ability in that area, but I'm all for using the right tool for the job. Perl is the swiss-army chainsaw, also hammers nails. :)
Python and Perl exist because some things are out of scope for a shell. What do you gain by giving a shell kitchen-sink functionality? Over complicated shell. Unix shell is successful because it is simple to understand and build command chains by checking the output before the next step.
If you wanna get fancy, time to dump sh.
Look man, extrapolating SSD into an argument about flash vs SDRAM just shows a lack of imagination. I'll see you in ten years.
Back it up to floppy.
You can by SSD now which consists purely of the same RAM sticks as on your motherboard. This is the idea that I'm getting at. So how do we handle it? Seems a bit wasteful to limit that massive bandwidth through legacy storage interfaces, so put it on the RAM bus. Also a bit redundant to double-handle it via antiquated filesystem IO, so map it directly.
See where it's going...
There is no requirement for stream output to be ascii, that is up to the programmer to decide and preferable to having the architecture decision forced on you. But I think you're missing the point that you can actually use Perl or Python as your shell, you have a semantic roadblock from working too closely with monolithic solutions.
x86 is more than x64, so it's better right?
I would be brave enough to say that in the not-too-distant future, 1GB storage will be about as common as 1KB RAM chips are now.
Sure is lack of imagination in here...
I never said that SSD would eliminate RAM either, which in turn will not eliminate on-die cache or registers in the forseeable future. When you've got a practically infinite address space you may as well use it.
Who said anything about flash-based SSD? I said SSD as in SOLID-STATE NON-VOLATILE STORAGE. Regardless, flash now is faster than CPU registers were not so long ago.
The demarcation of storage and RAM is a legacy constraint forced by hardware limitations. Ubiquitous 64-bit and SSD will blur and eventually totally eliminate this separation.
Cygwin makes windows bearable.
Bands that sound good live don't translate well to the overdub recording precisely because they are good bands.
I guess some drummers practise with metronomes too.
Yeah it was a great design in the day, but every PC component has had DMA for a long time now so there would be no real advantage. There were many advanced features in the AmigaOS such as drivers, plugins and mountpoints but some things may have ended up as security nightmares if they continued as legacy. Arexx ports and lack of memory management come to mind.