Major Linux Problems on the Desktop, 2018 edition
-
@helix
I dont see how this will happen at all.Windows 10 is far more powerful than windows 7, and runs twice as fast. It is also much harder to pirate, and this point more than anything else has the Linux crowd in a panic.
It wont be long until Windows 7 is no longer supported, and when that happens, what is Linux going to do ?
Linux will have to find a way to work under Windows 10 from here on, since it wont be able to rely on 7 being readily available anymore.
Linux may seem like a good alternative to Office, but all that is happening in linux is that the windows interface is cleverly hidden away. It still needs the drivers and software services in order to run, and in most cases - that happens WITHOUT a valid windows licence.
This is just plain piracy.
Windows 10 will finally put an end to this blatant abuse of intellectual property, and linux should decline, taking the pirates with it.
Anyone that supports the continuation of Windows 7 in place of 10 surely has a hidden agenda .. and you will surely be caught out.
-
Stop it!
I should have changed my post to:
I particularly hateLinuxANY fanboyz.
-
@onyx said in Major Linux Problems on the Desktop, 2018 edition:
Filed under: Best example of Poe's law ever
-
@jaloopa said in Major Linux Problems on the Desktop, 2018 edition:
@helix
I dont see how this will happen at all.Windows 10 is far more powerful than windows 7, and runs twice as fast. It is also much harder to pirate, and this point more than anything else has the Linux crowd in a panic.
It wont be long until Windows 7 is no longer supported, and when that happens, what is Linux going to do ?
Linux will have to find a way to work under Windows 10 from here on, since it wont be able to rely on 7 being readily available anymore.
Linux may seem like a good alternative to Office, but all that is happening in linux is that the windows interface is cleverly hidden away. It still needs the drivers and software services in order to run, and in most cases - that happens WITHOUT a valid windows licence.
This is just plain piracy.
Windows 10 will finally put an end to this blatant abuse of intellectual property, and linux should decline, taking the pirates with it.
Anyone that supports the continuation of Windows 7 in place of 10 surely has a hidden agenda .. and you will surely be caught out.
At least some distributions like Ubuntu will still continue to work
-
@jaloopa said in Major Linux Problems on the Desktop, 2018 edition:
It wont be long until Windows 7 is no longer supported,
Mainstream support ended 1/13/2015 -- Over 3 years ago.
-
@thecpuwizard said in Major Linux Problems on the Desktop, 2018 edition:
1/13/2015
The first of undecember?
-
@jaloopa said in Major Linux Problems on the Desktop, 2018 edition:
@thecpuwizard said in Major Linux Problems on the Desktop, 2018 edition:
1/13/2015
The first of undecember?
Yup! or the 2015th day of the 13th month of the first year --- I am a fany of Y-M-D (with padding) so you get a proper sort order easily.
-
@lorne-kates said in Major Linux Problems on the Desktop, 2018 edition:
What kind of development is even going on with Linux anyways? By now you'd think they'd have a fairly stable, solid core product. Sure, there needs to be code for new drivers / hardware, and I suppose every now and then modding it to support a new platform-- but other than that, what are they actually doing? I can't see there being any need to develop code for
cat
.So with all this supposed manpower going into the world-wide development of TEH LINUX, how the hell aren't the devoting some of that to UI?
Heck, I bet they could raise $1M overnight, and hire 2-3 expert level UI designers to work for a couple years making one.
GUI toolkits have mayor changes every time a mayor feature is needed, like HiDPI, forcing every GUI program to be rewritten (and with Wayland it will be even worse due to the fundamentally different design). Also, new volunteers can't understand the old legacy code left behind, so it usually gets rewritten. There are lots of projects written in C or Python 2 that are completely dead.
-
Problem #1 - windows is too easy to pirate
-
@magnusmaster said in Major Linux Problems on the Desktop, 2018 edition:
Wayland
At they seem to have removed a stick from their ass there and have made a bridge to X11 a key component. There's a lot apps out there for which this will be entirely adequate for years to come. (The weyland client library docs are better than they were, but are still really confusing.)
-
@sockpuppet7 said in Major Linux Problems on the Desktop, 2018 edition:
too easy to pirate
Oh yeah, speaking of which, I'm wondering what's supposed to happen.
I installed this VM months upon months ago, and all it's done is put a watermark on the screen, which screen I never look at because it's a build slave.
-
@e4tmyl33t said in Major Linux Problems on the Desktop, 2018 edition:
@izzion said in Major Linux Problems on the Desktop, 2018 edition:
The hardest part about editing linux text files is figuring out how to actually exit vi
Not as much of a problem when you use nano :D
-
@gurth Try setting the
EDITOR
environment variable to your preferred editor first…
-
@dkf said in Major Linux Problems on the Desktop, 2018 edition:
@gurth Try setting the
EDITOR
environment variable to your preferred editor first…Setting environment variables is probably covered in chapter 12 XD
-
@akko said in Major Linux Problems on the Desktop, 2018 edition:
@dkf said in Major Linux Problems on the Desktop, 2018 edition:
@gurth Try setting the
EDITOR
environment variable to your preferred editor first…Setting environment variables is probably covered in chapter 12 XD
But it's easy, just open a text editor and... oh, wait...
-
@remi said in Major Linux Problems on the Desktop, 2018 edition:
@akko said in Major Linux Problems on the Desktop, 2018 edition:
@dkf said in Major Linux Problems on the Desktop, 2018 edition:
@gurth Try setting the
EDITOR
environment variable to your preferred editor first…Setting environment variables is probably covered in chapter 12 XD
But it's easy, just open a text editor and... oh, wait...
Short story time:
I was reading a DOS manual and came across the
prompt
command. Nifty! Previously they also taught aboutautoexec.bat
, and how to add to text files usingecho
and>
. Guess what happened?If you guessed "@Tsaukpaetra was a dumbass and wiped away autoexec.bat , which included code on how to boot from the two floppy drives!" a winner is you!
This of course was during a time when computers didn't have a BIOS so the boot device was controlled by jumpers inside the box.
-
@tsaukpaetra said in Major Linux Problems on the Desktop, 2018 edition:
@remi said in Major Linux Problems on the Desktop, 2018 edition:
@akko said in Major Linux Problems on the Desktop, 2018 edition:
@dkf said in Major Linux Problems on the Desktop, 2018 edition:
@gurth Try setting the
EDITOR
environment variable to your preferred editor first…Setting environment variables is probably covered in chapter 12 XD
But it's easy, just open a text editor and... oh, wait...
Short story time:
I was reading a DOS manual and came across the
prompt
command. Nifty! Previously they also taught aboutautoexec.bat
, and how to add to text files usingecho
and>
. Guess what happened?If you guessed "@Tsaukpaetra was a dumbass and wiped away autoexec.bat , which included code on how to boot from the two floppy drives!" a winner is you!
This of course was during a time when computers didn't have a BIOS so the boot device was controlled by jumpers inside the box.
Citation needed for a machine running MS-DOS (or equiv.) where there was no BIOS....
-
@tsaukpaetra said in Major Linux Problems on the Desktop, 2018 edition:
This of course was during a time when computers didn't have a BIOS so the boot device was controlled by jumpers inside the box.
That time was around 1970 ?
Hint: the first IBM PC (released August 12, 1981) contained a BIOS
-
@timebandit said in Major Linux Problems on the Desktop, 2018 edition:
@tsaukpaetra said in Major Linux Problems on the Desktop, 2018 edition:
This of course was during a time when computers didn't have a BIOS so the boot device was controlled by jumpers inside the box.
That time was around 1970 ?
Hint: the first IBM PC (released August 12, 1981) contained a BIOS
Maybe he means there was no BIOS config menu.
-
@mikehurley said in Major Linux Problems on the Desktop, 2018 edition:
Maybe he means there was no BIOS config menu.
<blakeyrant>I can't read his mind </blakeyrant>
-
@thecpuwizard said in Major Linux Problems on the Desktop, 2018 edition:
@tsaukpaetra said in Major Linux Problems on the Desktop, 2018 edition:
@remi said in Major Linux Problems on the Desktop, 2018 edition:
@akko said in Major Linux Problems on the Desktop, 2018 edition:
@dkf said in Major Linux Problems on the Desktop, 2018 edition:
@gurth Try setting the
EDITOR
environment variable to your preferred editor first…Setting environment variables is probably covered in chapter 12 XD
But it's easy, just open a text editor and... oh, wait...
Short story time:
I was reading a DOS manual and came across the
prompt
command. Nifty! Previously they also taught aboutautoexec.bat
, and how to add to text files usingecho
and>
. Guess what happened?If you guessed "@Tsaukpaetra was a dumbass and wiped away autoexec.bat , which included code on how to boot from the two floppy drives!" a winner is you!
This of course was during a time when computers didn't have a BIOS so the boot device was controlled by jumpers inside the box.
Citation needed for a machine running MS-DOS (or equiv.) where there was no BIOS....
Ok, technically yes it has a BIOS, but not with a pre-boot setup program you can get into by mashing Del or F1.
It was a Tandy 1000 (SX?).
Edit: Y'all are quick on the draw sometimes...
-
@dkf said in Major Linux Problems on the Desktop, 2018 edition:
@gurth Try setting the EDITOR environment variable to your preferred editor first…
Because that's so intuitive.
The fact that Linux distros set their least user friend editor as the out-of-the-box default really says something, doesn't it. It says: "fuck you!"
-
@blakeyrat said in Major Linux Problems on the Desktop, 2018 edition:
@dkf said in Major Linux Problems on the Desktop, 2018 edition:
@gurth Try setting the EDITOR environment variable to your preferred editor first…
Because that's so intuitive.
The fact that Linux distros set their least user friend editor as the out-of-the-box default really says something, doesn't it. It says: "fuck you!"
I don't know. I think nano is fairly decent for a lightweight CLI editor. :D
-
@blakeyrat it has the instructions right there at the bottom
-
@blakeyrat said in Major Linux Problems on the Desktop, 2018 edition:
Right; but why should the network interface matter to this protocol?
Can you explain how that works in Windows? Like, how the different layers of the stack interact with each other?
-
@gordonjcp said in Major Linux Problems on the Desktop, 2018 edition:
Can you explain how that works in Windows? Like, how the different layers of the stack interact with each other?
Through the font installer
-
@bb36e said in Major Linux Problems on the Desktop, 2018 edition:
@blakeyrat it has the instructions right there at the bottom
Nano does, yes. (Although it's still a really shitty UI. How are users supposed to know that an caret == control key?)
It used to be the default was always Vi though. Have linux distros finally fixed that bullshit?
-
@gordonjcp said in Major Linux Problems on the Desktop, 2018 edition:
Can you explain how that works in Windows? Like, how the different layers of the stack interact with each other?
-
@blakeyrat So no, then, you can't. Okay.
I'm guessing you've never attempted to implement a network driver in Windows.
-
@gordonjcp Nope. But I know Linux had a really embarrassing bug that Windows never had for the entire existence of wifi, so Microsoft must have fucking done something right.
-
@blakeyrat Using the OSI model is tr
-
@blakeyrat said in Major Linux Problems on the Desktop, 2018 edition:
But I know Linux had a really embarrassing bug that Windows never had for the entire existence of wifi
Which one?
-
@timebandit said in Major Linux Problems on the Desktop, 2018 edition:
Which one?
Why don't you fucking scroll up instead of steering the whole thread in circles?
-
@blakeyrat Can Windows do PPPoE over Wifi?
If it can, why? What possible use would anyone have for that?
-
@blakeyrat said in Major Linux Problems on the Desktop, 2018 edition:
Common Linux defender refrain: "if we don't have it, it's because you don't need it"
-
@blakeyrat Just admit you have no idea what use there is for PPPoE over WiFi
-
@blakeyrat In Windows can you do UPnP over AX.25?
-
Oh fuck off. Christ.
-
@dkf said in Major Linux Problems on the Desktop, 2018 edition:
@gurth Try setting the
EDITOR
environment variable to your preferred editor first…Which does what in this case? Use that instead of vi(m) when the command
visudo
is given?
-
@blakeyrat Common Windows defender refrain, "If we don't have it, it's because you don't need it."
Now - can you tell me if Windows actually allows you to do PPPoE over Wifi?
Bonus prize if you can show me a device that might make some use of that.
-
@carnage said in Major Linux Problems on the Desktop, 2018 edition:
@blakeyrat said in Major Linux Problems on the Desktop, 2018 edition:
@dkf said in Major Linux Problems on the Desktop, 2018 edition:
@gurth Try setting the EDITOR environment variable to your preferred editor first…
Because that's so intuitive.
The fact that Linux distros set their least user friend editor as the out-of-the-box default really says something, doesn't it. It says: "fuck you!"
I don't know. I think nano is fairly decent for a lightweight CLI editor. :D
I actually think nano is a worse editor than vim because it uses shortcuts that are the same pattern but different than the standard CTRL+O=open, CTRL+S=save, etc. CTRL+O for output (save) is really messed up. I get my hotkeys really messed up in my head. Vim is at least different enough that you won't be tempted to think it works the same or vice versa when you're back in a regular GUI editor.
-
@mikehurley said in Major Linux Problems on the Desktop, 2018 edition:
@carnage said in Major Linux Problems on the Desktop, 2018 edition:
@blakeyrat said in Major Linux Problems on the Desktop, 2018 edition:
@dkf said in Major Linux Problems on the Desktop, 2018 edition:
@gurth Try setting the EDITOR environment variable to your preferred editor first…
Because that's so intuitive.
The fact that Linux distros set their least user friend editor as the out-of-the-box default really says something, doesn't it. It says: "fuck you!"
I don't know. I think nano is fairly decent for a lightweight CLI editor. :D
I actually think nano is a worse editor than vim because it uses shortcuts that are the same pattern but different than the standard CTRL+O=open, CTRL+S=save, etc. CTRL+O for output (save) is really messed up. I get my hotkeys really messed up in my head. Vim is at least different enough that you won't be tempted to think it works the same or vice versa when you're back in a regular GUI editor.
This.
-
@blakeyrat said in Major Linux Problems on the Desktop, 2018 edition:
I'm saying that if you go to the distro's official support channel, and say "hey my Firefox is too old", do they come back with "well here at this third-party repository" or do they come back with "upgrade to a new release of distro, do not add third-party repositories"?
Why would you go to the distro support channel to ask questions about Firefox? Why wouldn't you go to Firefox? If you have trouble with an application do you go to support for that application or do you ring up the boys in Redmond?
-
@polygeekery you should always file bugs against your distro's system so that the maintainer can triage and determine if the bug was caused by distro-specific patches, if it was already fixed upstream etc. JWZ got understandably annoyed because people kept emailing him to report xscreensaver bugs that he fixed ages ago, but many people's distros either didn't backport his changes or simply didn't upgrade the version in their repos. I believe this is the reason why xscreensaver displays a 'please upgrade' message on older versions:
-
@polygeekery said in Major Linux Problems on the Desktop, 2018 edition:
If you have trouble with an application do you go to support for that application or do you ring up the boys in Redmond?
Obviously Redmond. Because Windoze sucks and it's all Micro$loths fault. Obviously.
-
@gordonjcp said in Major Linux Problems on the Desktop, 2018 edition:
@blakeyrat Can Windows do PPPoE over Wifi?
Yes.
-
@polygeekery said in Major Linux Problems on the Desktop, 2018 edition:
If you have trouble with an application do you go to support for that application or do you ring up the boys in Redmond?
No, I just wait for Windows to call me about the viruses and ask them.
-
@blakeyrat said in Major Linux Problems on the Desktop, 2018 edition:
@dkf said in Major Linux Problems on the Desktop, 2018 edition:
@gurth Try setting the EDITOR environment variable to your preferred editor first…
Because that's so intuitive.
The fact that Linux distros set their least user friend editor as the out-of-the-box default really says something, doesn't it. It says: "fuck you!"
I love people like that. Rocket likes using a lot of colors in its output, and when I talked to the owner I learnt that he doesn't give a tin shit whether PowerShell's defaults make it so that a lot of important text is either impossible or virtually impossible to read, and his solution was to install a different color scheme.
-
@blakeyrat said in Major Linux Problems on the Desktop, 2018 edition:
@gordonjcp said in Major Linux Problems on the Desktop, 2018 edition:
Can you explain how that works in Windows? Like, how the different layers of the stack interact with each other?
-
@blakeyrat said in Major Linux Problems on the Desktop, 2018 edition:
It used to be the default was always Vi though. Have linux distros finally fixed that bullshit?
Well, I used one a while back where it was emacs, which objectively even worse.
Filed under: Editor flame war in 3... 2... 1...