Hard Light Productions Forums
Off-Topic Discussion => General Discussion => Topic started by: sigtau on June 29, 2012, 12:48:06 pm
-
http://semiaccurate.com/2012/06/29/hp-said-to-dump-microsoft-over-surface/ (thanks to Swantz/achtung for the link)
It may just be a rumor now, but I think this is a wonderful, wonderful thing. It appears that Microsoft is going to lose OEMs over forcing them to push new standards--in this case, the Windows RT/ARM tablet architecture.
I'm terribly glad for this.
-
Where else are they gonna go? Linux? Android lol. ;)
If this is only about ARM devices then frankly... storm in a teacup. If it's about Microsoft Windows in general.... then HP would saw off the branch that they are sitting on so... pfft. :p
Frankly, this comment seems more accurate than the actual article:
Joe Jun 29, 2012 at 12:36 pm #
Please! He doesn’t have any information. He’s just trying to get hits to his website.
-
HP dumping Windows as a desktop OS is a laughable proposition. It would basically be suicide for HP. Might as well close their offices and pack their stuff.
-
Updated news in the various pipelines seems to imply that HP is not dumping windows, but is instead dumping ARM as a tablet architecture for the next product cycle.
-
I got excited for a split moment when I first saw the article elsewhere, I thought it was implying HP was dropping Windows altogether. A glorious world without consumer HP, and a weaker Microsoft. Then I snapped back to reality. :(
-
does this not apply any more ?
http://www.bbc.co.uk/news/business-14584428
-
does this not apply any more ?
http://www.bbc.co.uk/news/business-14584428
No. There's a reason why Leo Apotheker is no longer CEO of HP. That silly idea being it.
-
Hp owns webos so they have some legit alternatives to windows tablets if they can tap some opensource awesomeness
-
i thought the whole point of open source was that it ISN'T commercialized and sold?
-
i thought the whole point of open source was that it ISN'T commercialized and sold?
Not sure if sarcasm, or wrong in so many levels. :lol:
-
i thought the whole point of open source was that it ISN'T commercialized and sold?
erm maybe you confuse open source and freeware? Sometimes open source is freeware, and sometimes it isn't. Sometimes freeware is open source, and sometimes it isn't. Open Source just means the source is released. The license to use that source is a whole different matter; some licenses let you use it, but only for noncommercial purposes, others let you use it for commercial purposes; but IIRC you have to include your modifications in the open source, so I guess nothing prevents someone from copying what you did..
However, that's just my brief, very stunted, possibly (probably?) incorrect summary.
Here:
http://en.wikipedia.org/wiki/Open_source
first couple of paragraphs:
In production and development, open source is a philosophy,[1][not in citation given][2][not in citation given] or pragmatic methodology[2][not in citation given] that promotes free redistribution and access to an end product's design and implementation details.[3] Before the phrase open source became widely adopted, developers and producers used a variety of phrases to describe the concept; open source gained hold with the rise of the Internet, and the attendant need for massive retooling of the computing source code.[citation needed] Opening the source code enabled a self-enhancing diversity of production models, communication paths, and interactive communities.[4] The open-source software movement was born to describe the environment that the new copyright, licensing, domain, and consumer issues created.[citation needed]
The open-source model includes the concept of concurrent yet different agendas and differing approaches in production, in contrast with more centralized models of development such as those typically used in commercial software companies.[5] A main principle and practice of open-source software development is peer production by bartering and collaboration, with the end-product, source-material, "blueprints", and documentation available at no cost to the public. This is increasingly being applied in other fields of endeavor, such as biotechnology.[6]
-
i thought the whole point of open source was that it ISN'T commercialized and sold?
not really. there are a lot of people making buttloads of money with open source hardware right now. not only do they sell you something but they also give away all the design information so you can build your own or make a derivative. in terms of software *nix is big buisness and *nix specialists are highly payed individuals. one advantage of using open source technology over proprietary technology, aside from the obvious fact that its cheaper and the people who support that technology dont need to be in bed with the ones that made it (for example when an apple product breaks you have to have it fixed at an apple store unless you want to void the warranty), so you dont have to rely on some other company's support cycle (like the way ms forces obsolescence in its old software by not supporting it so you have to buy the new version every few years).
the other good thing about it is you reduce wasted effort in the r&d department. if a company needs database server for example they have 3 options: higher a programmer and develop it in house. buy some software from a proprietary vendor like ms, or they could go with some piece of software off of sourceforge. it may look nice but it needs some additional features, so the company decides to allocate a programmer from another department to add said features to the software, and because its open source the company has to release their code, which my get merged into the codebase by its original development team. if another company decides to use that software they will also allocate personnel to maintaining it, by introducing performance improvements or new features, maybe a port to some other platform perhaps. they benefit from the previous companie's work on it, and add their own contributions benefit the other company. if both companies had developed it in house then they would have both had to hire a large development team and designed the same thing from the ground up, and if they had bought some software they would have gotten jacked.
so dont think that open source is communist or anti-corporate in any way. its really just about being more efficient. another point i like to make is that in the event of a catastrophic event like a nuclear war or some kinda megalithic natural disaster, a majority of the proprietary technologies will be lost. only the open technologies with wide distribution in the public domain will survive just on the grounds of being everywhere, while the blueprints for a proprietary machine aiding in the mass production of toilets is hidden in some vault in some city which got nuked. the result: you know have to **** in a bucket until somone re-invents the machine to do the job.
-
As someone once said, Open Source Software is only free if your time has no value. Which is an exaggeration and hyperbole, but carries a kernel of truth; after all, if you go down the OSS route, you will sooner or later find yourself in a position where the product you're using has some form of limitation that requires you to do a workaround (either in code or in your usage), thus costing time.
Now, I am not saying that closed source commercial products are all that different in that regard for private users, but in a commercial environment, where you are usually not just buying software but also support contracts for that software, you are in a different position to the developers. That is, you can go to them and say "We need this feature added to the product, please implement it or we switch to a different product and cancel our contracts with you", which when dealing with the open source community simply does not work.
-
As someone once said, Open Source Software is only free if your time has no value. Which is an exaggeration and hyperbole, but carries a kernel of truth; after all, if you go down the OSS route, you will sooner or later find yourself in a position where the product you're using has some form of limitation that requires you to do a workaround (either in code or in your usage), thus costing time.
Now, I am not saying that closed source commercial products are all that different in that regard for private users, but in a commercial environment, where you are usually not just buying software but also support contracts for that software, you are in a different position to the developers. That is, you can go to them and say "We need this feature added to the product, please implement it or we switch to a different product and cancel our contracts with you", which when dealing with the open source community simply does not work.
Unless you get a contract with an OSS support vendor like red hat.
-
OSS is not the same thing as FOSS.
-
I am sorry for having forgotten to make that distinction. Yes, OSS + Support contract is just as good, if not better, than closed source + support contract.
-
As someone once said, Open Source Software is only free if your time has no value.
and thats why i use windows. for now at least. i still use a lot of open source applications though, and id use an open source operating system if one existed that wasnt a bloated, overcomplicated piece of crap.
-
As someone once said, Open Source Software is only free if your time has no value.
and thats why i use windows. for now at least. i still use a lot of open source applications though, and id use an open source operating system if one existed that wasnt a bloated, overcomplicated piece of crap.
you mean haiku os(lol)? but yes it is disappointing that linux isn't the old hardware Resurrection OS that it used to be(and don't even get me started on gnome3 and unity). no one wants to risk thier main machine on a botched install so trying it out on an old machine is how most people learn learn to love it (once they work past the quirks).
-
If they work past the quirks.
Oh, you misconfigured your video? No problem, new Linux user, please lrn 2 navigate your ext4 partition using bash and edit the appropriate config file with vi.
:beamz: wtf, no safe mode / system restore???? Going back to the devil, I guess...
It's hard to Google the fix if it's your only computer that's down. Unless you had the foresight to dual-boot.
I managed to work through that particular nightmare on my first try, but it took a good day or so of fighting with it and researching on dual boot (when the dial-up was not being retarded, that is). Oh and ofc it was ext3 or ext2 back then IIRC. Same thing from the user's perspective though.
-
I'll never understand how people have show-stopping issues with desktop linux. The worst I've had to deal with has been video drivers years ago, flash, and broadcom wireless drivers before they opened up. This has been across 8 machines with varying hardware, and only one was built with Linux in mind. Unless I'm doing something unusual everything is pretty seamless and smooth.
-
Unless I'm doing something unusual everything is pretty seamless and smooth.
...nowadays. :nervous:
If they work past the quirks.
Oh, you misconfigured your video? No problem, new Linux user, please lrn 2 navigate your ext4 partition using bash and edit the appropriate config file with vi.
:beamz: wtf, no safe mode / system restore???? Going back to the devil, I guess...
It's hard to Google the fix if it's your only computer that's down. Unless you had the foresight to dual-boot.
I managed to work through that particular nightmare on my first try, but it took a good day or so of fighting with it and researching on dual boot (when the dial-up was not being retarded, that is). Oh and ofc it was ext3 or ext2 back then IIRC. Same thing from the user's perspective though.
At least Ubuntu has had a safe mode for years now.
And the console thing is something I will never understand. There ARE graphical tools in the main desktop enviroments to do almost everything, and yet walkthroughs are still written using console commands. :confused:
I don't like the console. When people tell me, for example, to add a repository, I launch Synaptic.
-
console commands are almost universal regardless of your setup, and can be easier to describe to a new user. my prob is that i have never had a dualboot install work right
-
console commands are almost universal regardless of your setup, and can be easier to describe to a new user. my prob is that i have never had a dualboot install work right
And yet still most walkthroughs are written targeting a particular distribution. And walkthroughs for Windows use images and notations like Start -> Control Panel so I see no reason why we can't do the same on KDE and Gnome.
-
universal for that distro would probably be better
its more of a forum thing no one helping a guy on a forum wants to make a powerpoint presentation on how to do something nor do they want to ask a thousand questions about thier desktop environment. so with console commands the guy using openbox can help the guy using gnome easily. how hard is it to open a terminal and copy and paste a command?
-
universal for that distro would probably be better
its more of a forum thing no one helping a guy on a forum wants to make a powerpoint presentation on how to do something nor do they want to ask a thousand questions about thier desktop environment. so with console commands the guy using openbox can help the guy using gnome easily. how hard is it to open a terminal and copy and paste a command?
It's not hard. It's just that most people are allergic to it.
And I'm talking about articles in the internet.
Take this guide (http://www.winehq.org/download/ubuntu) as an example. I haven't used it, but it looks right. That's the way I would do it. Well, actually, I usually do it in Cervantes' tongue :lol: , but anyway, you know what I mean.
-
@mormon_boy, EasyBCD (http://neosmart.net/EasyBCD/) is your friend (go under "Non-commercial" and click "Register", then just click the "Download" button -- you don't have to put your info in, it will download).
@el_magnifico, the GUI tools only work if the GUI is up and running. I seem to be particularly talented and poking around with system configurations in the GUI tools that cause the GUI to not load properly and get me in a bind. :ick:
-
@el_magnifico, the GUI tools only work if the GUI is up and running. I seem to be particularly talented and poking around with system configurations in the GUI tools that cause the GUI to not load properly and get me in a bind. :ick:
You should be doing something awfully wrong to get no GUI. Once I rebooted halfway through a distro upgrade and still got welcomed by a low-res login and session.
You guys realize you're looking into every possible "but" here, don't you? Like, what if I have to recompile my kernel and add modules to it? Well duh, of course you're going to use a CLI. But that's no reason for doing a console walkthrough when you're writting, say, "How to install Audacity on Ubuntu 12.04". And one just assumes if you're installing Audacity or adding Wine repos, that chances are high you've got a running graphical enviroment in the first place.
-
oh great, now its a linux user wank thread. stamp of wank applicated.
-
And yet still most walkthroughs are written targeting a particular distribution. And walkthroughs for Windows use images and notations like Start -> Control Panel so I see no reason why we can't do the same on KDE and Gnome.
Oh man it's so annoying when people do this. For example, when making a bootable thumb drive for Ubuntu (http://www.ubuntu.com/download/help/create-a-usb-stick-on-ubuntu), their tutorial assumes you already have ubuntu installed (it's windows OSX and ubunu, not windows OSX and Linux). I cannot post here what I would do to the person that wrote that tutorial. Contrast with Debian's tutorial (http://wiki.debian.org/InstallToUsbMemoryStick). Tutorials really aren't usually OS specific unless it's something that has to do exactly with that OS rather than a piece of software or something, or I suppose if they're crappy tutorials. Learn bash; once you know it you won't know how you managed without it.
-
I don't know where this is going, but I've been using Ubuntu for a long time, and while I wasn't too fond of Unity at first, it's beautiful and stable now. I also recognized that for the longest time, their driver support wasn't too great (not their fault, mind you), but it's only been getting better over the last few releases. Now, you can install Ubuntu without a problem.
Something to consider: The reason why I stick with Ubuntu and not other distros is because I consider myself to be a casual user. I know that I won't be able to fiddle with Arch Linux, and I'm quite happy with the Unity interface. I could switch to Fedora, but I haven't seen much of a reason to. Maybe when I decide to start gaming on a Fedora, I'll switch over. (The performance difference for gaming is notable, but if it's only because Unity is a performance hog, I might just switch to Gnome.)
There's nothing wrong with Linux. It can be as easy or as complicated as you want. You don't want bloatware and want it to be personal? Arch Linux is for you (maybe). You want to start somewhere? Try Ubuntu. You want proprietary by default? There's Mint.
With that said, I almost forgot about Ubuntu for Android. Depending on how well it works, I can imagine it being an alternative to Surface.
-
We're running in circles here.
And yet still most walkthroughs are written targeting a particular distribution. And walkthroughs for Windows use images and notations like Start -> Control Panel so I see no reason why we can't do the same on KDE and Gnome.
Oh man it's so annoying when people do this. For example, when making a bootable thumb drive for Ubuntu (http://www.ubuntu.com/download/help/create-a-usb-stick-on-ubuntu), their tutorial assumes you already have ubuntu installed (it's windows OSX and ubunu, not windows OSX and Linux). I cannot post here what I would do to the person that wrote that tutorial.
Oh, Canonical! You had the nerve of writing a howto for your own distro and posting it on your own servers, in your own enterprise's page, which you paid for with your own money. Now, have you thought about that poor guy running his customized Linux From Scratch? Did he even crossed your mind for a second? What's that unfortunate and defenseless newbie, who barely managed to compile his own kernel and a whole system on top of it, going to do now? You're so self-centered Canonical! *sigh*
Now, if you look at the example I posted, down at the bottom of the page you will see the alternative instructions right there, written in pure and pristine bash language for your enjoyment.
Come to think of it, your example is a clear demonstration of what I said: There's almost always an easier way to do it, but we expect people to do it the hard way. (And while I'm at it, at least the Ubuntu tutorial looks stylish and eye-catching. That's important for the user's experience too.)
Learn bash; once you know it you won't know how you managed without it.
Learning bash hasn't changed my life in any significant way. It didn't get me a better job, a warmer house or a luxury car. Learning web development in Java took me half the time. It gave me an official certification, friends, valuable contacts, and a small yet much appreciated scholarship. To be clear, I'm not a materialist person, but given experiences like that, do you really expect people to learn bash, something most of them will never actually have a use for in their whole life? Sure, it may be a nice tool to have in your arsenal, but I expect an OS to be usable without it.
And just for the record, I love Linux, I love Debian (my first full time distro), I've been a Linux user for the last seven years. It's just that I'm not blind, I know end users have requirements we're not meeting yet (except for Android, of course.)
With that said, I almost forgot about Ubuntu for Android. Depending on how well it works, I can imagine it being an alternative to Surface.
This.
Also, I imagine having Ubuntu or Android installed in one of those ARM Surface things would be pure glory. That's, if UEFI allows it... :nervous: