@MiffTheFox said:
Although don't think I've ever seen crapware based on open-source software (probably with "enhancements" added by the distributor) before.
@MiffTheFox said:
Although don't think I've ever seen crapware based on open-source software (probably with "enhancements" added by the distributor) before.
@Weng said:
(Is GIMP still Gnu Image Manipulation Program, or has the obvious and inevitable rename to GIMP Image Manipulation Program happened?)
It's the GNU Image Manipulation Program. Which isn't really the worst name of a GTK+ project.
I kind of figured this thread would turn into the "Bash Linux Thread" of the week...
@blakeyrat said:
@RHuckster said:@blakeyrat said:Like the specification for determining which mouse button was pressed during an event.The event object has a button property. Granted it should use constants, but besides that it's no different than C# or Java.It's quite different from C# and (I presume) Java:
@W3C said:
During mouse events caused by the depression or release of a mouse button, button is used to indicate which mouse button changed state. The values for button range from zero to indicate the left button of the mouse, one to indicate the middle button if present, and two to indicate the right button. For mice configured for left handed use in which the button actions are reversed the values are instead read from right to left.So here's how the W3C defines the button property:
@W3C said:
Left = 0
Middle = 1
Right = 2Here's how Microsoft ad-hoc-ed the same property:
@Microsoft said:
None = 0
Left = 1
Right = 2
Left & Right = 3
Middle = 4
Left & Middle = 5
Right & Middle = 6
Left & Right & Middle = 7Tell me: which standard looks like the result of a well-thought-out standards process, and which standard looks like the result of a 3-day cocaine and hot rocks bender?
They both seem like poorly though out solutions that require looked back at the documentation every time you want to change something. IMHO a better design would be to use bitmasks with constants for each button.
function recieveButtonEvent (event) {
if (event.buttons == (LEFT | RIGHT)) alert ('The left and right buttons were both clicked.');
else if (event.buttons
== (MIDDLE | RIGHT)) alert ('The middle and right buttons were both clicked.');
else if (event.buttons == LEFT) alert ('Only the left button was clicked.')
else if (event.buttons & MIDDLE) alert ('The middle button was clicked, and possibly some other buttons');
}
@the license said:
Given the above, this work may not be put towards any uses other than
those that would help the establishment and/or continuation of a Kingdom
of Little Monsters.
This license looks familiar. Wasn't this line from Apple's EULA?
@blakeyrat said:
I have no idea if it's legal for me to host it, you read the license terms and let me know!
It would be hilarious if you got sued and a court ordered Lady Gaga to determine "what a Kingdom of Little Monsters is and whether its establishment and/or continuation has not been helped in any way."
@Sutherlands said:
I also find underscores extremely slow to type, because of all the stopping and shifting.
I agree that can be true at first, but they're easier to read since it's not all jumbled together.
I believe there's a made up statistic often cited on this forum about how many times code is written compared to how many times it's read.
TheBestWayToArgueAgainstACodingStyleIsToComposeASarcasticReplyUsingSaidStyleAsIfItWereMeantForNaturalLanguage.
By the way, I have yet to hear a real argument supporting camel case. Perhaps that can be this thread's mandatory offtopic flamewar?
The solution is simple - don't use camel-case. Using capitalization to separate words is silly, since capitalization isn't exclusively used at the beginning of words. Sure, you could have a special exception for acronyms, but it's not always clear to everybody what's an acronym and what isn't without looking up the documentation. Also, you could just treat acronyms like normal words, but good luck enforcing that.
void fire () { fireMahLASER (getLASERXMLDocument ()); // Or was it... fireMahLaser (getLaserXmlDocument ()); // Or was it... fireMahLaser (getLaserXMLDocument ()); } // Versus void fire () { fire_mah_laser (get_laser_xml_document ()); // It certainly wasn't... fire_mah_l_a_s_e_r (get_l_a_s_e_r_x_m_l_document ()); // Nor was it... fire_mah_laser (get_laser_x_m_l_document (); }
This is why I prefer using all lowercase with underscores to separate words. "document.get_element_by_id" can't be confused with "document.get_element_by_i_d".
Also, this is in my ~/.bashrc:
alias maek=make
@boomzilla said:
@TheChewanater said:Almost everybody I know uses a Debian or Ubuntu based distroFTFY
http://counter.li.org/reports/machines.php
Scroll down to "Distrobution".
@boomzilla said:
@TheChewanater said:Almost everybody uses a Debian or Ubuntu based distro, and APT also works with RPMs anyway.Ironic, since APT is pretty much omnipresent in modern GNU/Linux distros, while every Windows program has its own installer.Only in Debian derived distros. RedHat, Suse, Arch, Slack all have their own. No doubt so do others.
@Weng said:
@DaveK said:
This would be easier if the Linux "community" could get together and agree on a fucking package management system, instead of everybody inventing their own, each with its own unique set of shortcomings.
The moral of the story, BTW, is that the time taken to learn how to properly use the package management system is always worth it, no matter what your OS.
Ironic, since APT is pretty much omnipresent in modern GNU/Linux distros, while every Windows program has its own installer.
And what sort of "shortcomings" does APT have, anyway?
@AndyCanfield said:
I'll give blakeyrat another point. IMHO the software developers of Linux are excellent; the best around. But the QA is terrible.This thread started with a bug in an uninstall script (or was it an install script?). Wasn't the final version tested before being shipped? If it had been tested at all it would have been noticed and set off alarms everywhere.
The bug occured in version 1.4.31, which, having an odd microversion, is traditionally not a final release.
This is an excellent example of Linus's Law.