Yes, the keyword is proprietary, another keyword is 'optional', and the time of proprietary UNIX GUIs is only of historical interest, probably even predates the free software movement as we know it now.
So i really don't see your point here. Also, you completely ignored the 'walled garden' argument.
What? If something crashes, I sure as hell inspect the core dump(*), which usually leads me right into the source code you think nobody every looks at.
(*)unless it's, say, the damn flash plugin, by far the most crashing program here. Those times, while bending over to take it up the ass from adobe, i'm reminded of how your proprietary world feels.
OS X, despite having some unix anchestry, and using some NetBSD code here and some FreeBSD code there, can nowadays hardly be called 'unix', for it shields nearly everything behind the apple-proprietary GUI, and the whole ecosystem is tuned to "walled-garden". that contradicts unix philosophy in so many ways, therefore, no.
I wasn't talking about what 'the tools do, under the hood' (dammit, typical windows speak), my point was that your operating system is a black box. dammit there isn't even source code available.
IOW, windows experts know how to use windows, unix experts know how unix work (and therefore, due to the openness and clarity, a lot more about how their computers work).
They are stuck in the way TFA points it out -- it's in their minds.
Lets try an analogy:
Say you have a hammer - yet nobody ever taught you how to use it, so you have to figure it out yourself. You mistake the head for a grip, and start bashing nails into the wall by holding the hammer's head in your hand, and hitting them with the/actual/ grip. It sort of works, and more importantly, you aren't aware of a better way, so it's "the best way" (you know).
Now imagine being told that you've been doing it wrong all the time, that the hammer is to be held at the other end. Skeptically, you give it a try. Holding the hammer correctly for the first time in your life, you realize it's a bit harder to handle than the way you're used to. Then you violently, like most people on their first attempts to hammer something, smash it onto your thumb, OUCH, WTF, this is fucking dangerous. Clearly, your original way to hammer was superior, and way less painful/dangerous. Right? No -- all it would have taken is to actually see someone working the hammer properly, before you realize how wrong you've been.
It's pretty much the same when it comes to CLI vs GUI
Because by coding against a black box, you can only become more and more proficient in knowing how the black box behaves for given inputs - the underlying concepts are pretty much invisible so the computer mostly remains 'magic' It's the price you pay for being "ready for granny";).
Another reason would be the WINAPI. It's a horrible, horrible mess.
Yes, but then again, there are people who/want/ to become developers, yet are hopelessly stuck in the proprietary shiny-UI apple-windows world, and often don't realize they/need/ to get out of there in order to become decent programmers.
Seriously? Not by any chance "predominantly"? Being this much of an arrogant asshole and then mess it up yourself? I suggest you go learn what sadly appears to be your fucking native language to a proper degree, before trying to correct others.
Oh and FWIW, English isn't my native language, I hope that hurts.
And how is that related to a higher pixel density? How exactly, given same font sizes, does it ease reading for people with bad vision? More crystal-clear lines which aren't crystal clear for someone with bad vision to start with? Hm.
Ohh, ``perhaps i should do some sports''. Hilarious, my other brainwashed little friend. FWIW, at work I look at damn new high-end displays, at home i look at 2005-ish 4:3 TFTs. I have good vision, maintain a distance of about 80cm from the screen, and it does not make any difference at all to me. Plus, there's literally no reason why it should make a difference for the eyes. Whatever, keep believing what your TV ads tell you.
Slashdot Mirror
Yes. Especially when compiled with debugging symbols, and a call stack points you right at the line where it crashed.
That being said, this isn't at all only about the Linux kernel.
IOW, they predate not only X, but also W.
Yes, the keyword is proprietary, another keyword is 'optional', and the time of proprietary UNIX GUIs is only of historical interest, probably even predates the free software movement as we know it now.
So i really don't see your point here.
Also, you completely ignored the 'walled garden' argument.
Yes. So? I'm not even a Linux user.
What? If something crashes, I sure as hell inspect the core dump(*), which usually leads me right into the source code you think nobody every looks at.
(*)unless it's, say, the damn flash plugin, by far the most crashing program here. Those times, while bending over to take it up the ass from adobe, i'm reminded of how your proprietary world feels.
OS X, despite having some unix anchestry, and using some NetBSD code here and some FreeBSD code there, can nowadays hardly be called 'unix', for it shields nearly everything behind the apple-proprietary GUI, and the whole ecosystem is tuned to "walled-garden". that contradicts unix philosophy in so many ways, therefore, no.
The first statement is not true for the share of developers among the Linux or unix users, which is substantial.
Your second statement, meh. I am a sysadmin, and quite frequently we fix bugs in open source software ourselves.
I wasn't talking about what 'the tools do, under the hood' (dammit, typical windows speak), my point was that your operating system is a black box. dammit there isn't even source code available.
IOW, windows experts know how to use windows, unix experts know how unix work (and therefore, due to the openness and clarity, a lot more about how their computers work).
That isn't what i was talking about.
/actual/ grip.
They are stuck in the way TFA points it out -- it's in their minds.
Lets try an analogy:
Say you have a hammer - yet nobody ever taught you how to use it, so you have to figure it out yourself. You mistake the head for a grip, and start bashing nails into the wall by holding the hammer's head in your hand, and hitting them with the
It sort of works, and more importantly, you aren't aware of a better way, so it's "the best way" (you know).
Now imagine being told that you've been doing it wrong all the time, that the hammer is to be held at the other end.
Skeptically, you give it a try. Holding the hammer correctly for the first time in your life, you realize it's a bit harder to handle than the way you're used to.
Then you violently, like most people on their first attempts to hammer something, smash it onto your thumb, OUCH, WTF, this is fucking dangerous.
Clearly, your original way to hammer was superior, and way less painful/dangerous. Right?
No -- all it would have taken is to actually see someone working the hammer properly, before you realize how wrong you've been.
It's pretty much the same when it comes to CLI vs GUI
Because by coding against a black box, you can only become more and more proficient in knowing how the black box behaves for given inputs - the underlying concepts are pretty much invisible so the computer mostly remains 'magic' ;).
It's the price you pay for being "ready for granny"
Another reason would be the WINAPI. It's a horrible, horrible mess.
Yes, but then again, there are people who /want/ to become developers, yet are hopelessly stuck in the proprietary shiny-UI apple-windows world, and often don't realize they /need/ to get out of there in order to become decent programmers.
predominately
Seriously? Not by any chance "predominantly"? Being this much of an arrogant asshole and then mess it up yourself? I suggest you go learn what sadly appears to be your fucking native language to a proper degree, before trying to correct others.
Oh and FWIW, English isn't my native language, I hope that hurts.
Cool it got upmodded, but why 'Funny'? I was dead serious. (And I am, now. (And now. (And now. (And now. -- Oh dammit.
Actually we peaked with NetHack. It's been a while, admittedly, but then again, you guys never had a peak anywhere near that high
Bbut netcraft confirmed it! I go tell!
Yours,
Armchair engineer
part
I'm not sure if your eyes work the same way that mine do, but mine aren't designed to be limited by pixels.
Mine aren't, either, but then this is but a straw man, or you didn't understand what I was trying to say.
Or do you suggest that the proportional near-letter-quality Serif font from a Star 9-pin dot matrix printer is good enough for any document, ever?
No, I am not suggesting this. It's just another straw man.
Except your current little problem of your own government not giving a fuck about the law
not sure if i could discern differences in kerning when the widths in question are fractions of a (normal-sized) pixel
Well it's a UDP summary.
And how is that related to a higher pixel density? How exactly, given same font sizes, does it ease reading for people with bad vision? More crystal-clear lines which aren't crystal clear for someone with bad vision to start with? Hm.
Ohh, ``perhaps i should do some sports''. Hilarious, my other brainwashed little friend.
FWIW, at work I look at damn new high-end displays, at home i look at 2005-ish 4:3 TFTs. I have good vision, maintain a distance of about 80cm from the screen, and it does not make any difference at all to me. Plus, there's literally no reason why it should make a difference for the eyes. Whatever, keep believing what your TV ads tell you.
Oh and FWIW, I go free climbing twice a week.
Right. I seem to be stuck in the desktop world.
protip: rotate it. 9:16 is great for coding
I know that the Retina display is better for my eyes over many hours.
How do you know that, my brainwashed little friend?