The US continues to use some idiot system of measurement based on some dead dude's foot.
It's always cute when people try to justify a massive change to the metric system (Yes, I am an engineer and agree that the metric system is superior in scientific purposes), but the US is highly entrenched in the English system. I for one, live in a metropolitan area divided into perfect mile by mile grids, and I would rather see "15 miles to Mesa" than "24.14km to Mesa".
What MAJOR benefit is there to the American people if we were to switch unit systems?
Re:Spatial Tree file view and huge directories
on
GNOME 2.12 Previewed
·
· Score: 1
The tree expander only loads the subdirectory when expanded. So it takes roughly the same amount of CPU power/RAM as viewing the folder and double-clicking the subdirectory. More because of the extended architecture, and less because you won't be creating a new window each time.
I think what was meant was that the crufty libraries can't be purged without breaking API/ABI. While this won't be possible 'til 3.0, what I've gathered from the topic was that gnome programs are going to be migrated away from libgnome and libgnomeui until it's no longer neccessary, at which point it will be marked as depreciated. The library won't die, but will fall into disuse.
Well, they are percieved errors. The GNOME developers had a good reason for puting the primary button on the right, and don't see it as an error, thus it is perceived by Ali Akcaagac.
Come now. What if I were to write a service called "delete:///" for the sole purpose of deleting files? The standard for Windows applications, IE and Moz included, is to say "Can I open this? I can't? Okay, who here can?... Okay, go for it!" So, if someone notices that there's a population of machines with "delete:///" on them and uses it to slate a bunch of computers, whose fault is it, mine or Mozilla's?
Of course, they could whitelist, say "Okay, only telnet:, ssh:, and aim: can go through." But this really isn't viable because it breaks the principle of things just working because future additions won't work.
The simple truth of it is, without adding layers to the system, like a shell: blocker, is to be accountable when programming a protocol.
The Article's title is: Microsoft products also vulnerable to Mozilla flaw
That is gross misinfomation, it should be something along the lines of "Microsoft products allow exploit of OS flaw, similar to Mozilla."
The flaw itself is in the Windows operating system. It exposes access to shell functions that applications need to blacklist. Application developers shouldn't need to be concerned with "Oh, I need to stop that protocol for security." It should be the protocol developer's responsibility to say "Is this safe?"
I really don't see it as that big a threat. How many Windows users are going to use WMP9? Most people with 95/98/NT/2000 probably won't update unless forced, so really, a small portion of existing PCs and all new PCs will have it. After that, many people will still use iTunes, WinAMP, etc. I really can't see very many people using this new software, unless things like Kazah and Gnutella can integrate like Napster can. Of course, if that's the case, WinAMP and the like will probably follow suit and that advantage will be moot.
A lot of people mention the rarity of ironing shirts, but while the Slashdot crowd may not, I know engineers, accountants, and businessmen who wear freshly washed and ironed shirts each and every day. If they make $50000 a year working 2000 hours (40 hours, 50 weeks), that's $25/hr. Say they spend 5 minutes ironing a shirt every busines day (~250), that's $520 of life they waste every year ironing. While still not enough to justify having something iron for them, especially as no one measures their life relative to how much they'd make on the job, there is enough savings to warrant consideration by people who iron in bulk, like Dry Cleaners. It may even be useful in a Laundramat (Probably not, but who knows?).
Not all innovations toward laziness or progress are one way. Something that is designed for the consumer market may easily be applied in other more useful fields, and vice versa, like the material in excersize pants being used for cooling systems, the material in shuttle windows being used for fogless ski goggles, computers being used by people other than scientists...
Who is to say that this innovation won't be useful in other fields down the road, it uses quite a few pieces of technology which could easily be applied to industry and NASA.
The artical aside, I love neck ties, I have 17, ranging from Star Trek to the molecular structure of Scotch to a maroon one with a flower embroidered to a portrait of Einstein. Unlike starched shirts and ironed pants, a tie is a chance for self expression in the otherwise bland world of corprate attire. They're especillay cool if they're stolen, as you're then you're flaunting your rebellion through conformity.
This is far different from the stem cell research sung about. This is taking healthy Schwann cells from peripheral nerves which regrow which can be taken from the same animal. I don't see how there is really any ethical problem here.
The easy way out is probably just to grab the first 10 bytes from HTTP and use your own stripped down library to read the header. These precious 10 bytes tell you a) that is is an id3 tag, and b) how much more has to be downloaded. If you take the size data you can easily see how much of the remaining file you need and dump it into a temp file for parsing.
Slashdot Mirror
This has nothing to do with high Mach number flight.
http://en.wikipedia.org/wiki/Fluorescent_Multilaye r_Disc
I'm pretty sure the company went bankrupt.
The tree expander only loads the subdirectory when expanded. So it takes roughly the same amount of CPU power/RAM as viewing the folder and double-clicking the subdirectory. More because of the extended architecture, and less because you won't be creating a new window each time.
I think what was meant was that the crufty libraries can't be purged without breaking API/ABI. While this won't be possible 'til 3.0, what I've gathered from the topic was that gnome programs are going to be migrated away from libgnome and libgnomeui until it's no longer neccessary, at which point it will be marked as depreciated. The library won't die, but will fall into disuse.
The Sims came out 2 weeks before finals one semester and a few of my friends destroyed their GPA's that way.
Pretty much the same thing as every other release. More stability.
I think, in 2.2 at the latest, key events in the docks are passed back to the active image.
Yeah, expert mode is hidden in this power tool: gconf-editor
Could you provide an example of a UI problem that they've said "Well, that's how they do it in Windows"?
Well, they are percieved errors. The GNOME developers had a good reason for puting the primary button on the right, and don't see it as an error, thus it is perceived by Ali Akcaagac.
Originally the plan was to call it "Return of the Sith", but it was too non-violent so they changed it to Revenge.
Come now. What if I were to write a service called "delete:///" for the sole purpose of deleting files? The standard for Windows applications, IE and Moz included, is to say "Can I open this? I can't? Okay, who here can? ... Okay, go for it!" So, if someone notices that there's a population of machines with "delete:///" on them and uses it to slate a bunch of computers, whose fault is it, mine or Mozilla's?
Of course, they could whitelist, say "Okay, only telnet:, ssh:, and aim: can go through." But this really isn't viable because it breaks the principle of things just working because future additions won't work.
The simple truth of it is, without adding layers to the system, like a shell: blocker, is to be accountable when programming a protocol.
The Article's title is: Microsoft products also vulnerable to Mozilla flaw That is gross misinfomation, it should be something along the lines of "Microsoft products allow exploit of OS flaw, similar to Mozilla." The flaw itself is in the Windows operating system. It exposes access to shell functions that applications need to blacklist. Application developers shouldn't need to be concerned with "Oh, I need to stop that protocol for security." It should be the protocol developer's responsibility to say "Is this safe?"
I really don't see it as that big a threat. How many Windows users are going to use WMP9? Most people with 95/98/NT/2000 probably won't update unless forced, so really, a small portion of existing PCs and all new PCs will have it. After that, many people will still use iTunes, WinAMP, etc. I really can't see very many people using this new software, unless things like Kazah and Gnutella can integrate like Napster can. Of course, if that's the case, WinAMP and the like will probably follow suit and that advantage will be moot.
A lot of people mention the rarity of ironing shirts, but while the Slashdot crowd may not, I know engineers, accountants, and businessmen who wear freshly washed and ironed shirts each and every day. If they make $50000 a year working 2000 hours (40 hours, 50 weeks), that's $25/hr. Say they spend 5 minutes ironing a shirt every busines day (~250), that's $520 of life they waste every year ironing. While still not enough to justify having something iron for them, especially as no one measures their life relative to how much they'd make on the job, there is enough savings to warrant consideration by people who iron in bulk, like Dry Cleaners. It may even be useful in a Laundramat (Probably not, but who knows?).
Not all innovations toward laziness or progress are one way. Something that is designed for the consumer market may easily be applied in other more useful fields, and vice versa, like the material in excersize pants being used for cooling systems, the material in shuttle windows being used for fogless ski goggles, computers being used by people other than scientists... Who is to say that this innovation won't be useful in other fields down the road, it uses quite a few pieces of technology which could easily be applied to industry and NASA.
Lest we forget: 2.65630387 × 10^23 leagues 3.22800182 × 10^27 cubits
The artical aside, I love neck ties, I have 17, ranging from Star Trek to the molecular structure of Scotch to a maroon one with a flower embroidered to a portrait of Einstein. Unlike starched shirts and ironed pants, a tie is a chance for self expression in the otherwise bland world of corprate attire. They're especillay cool if they're stolen, as you're then you're flaunting your rebellion through conformity.
This is far different from the stem cell research sung about. This is taking healthy Schwann cells from peripheral nerves which regrow which can be taken from the same animal. I don't see how there is really any ethical problem here.
Or jump a humpback with a Bird of Prey.
The easy way out is probably just to grab the first 10 bytes from HTTP and use your own stripped down library to read the header. These precious 10 bytes tell you a) that is is an id3 tag, and b) how much more has to be downloaded. If you take the size data you can easily see how much of the remaining file you need and dump it into a temp file for parsing.
ID3v2, to which he was refering, has been out for years and is at the beginning of the file.
Science fans may be excited to learn that "Mutant X" has been cancelled.
Actually, if you make a file called /usr/portage/packages.unmask, you can keep the ebuilds unmasked perminently:09:49:10 /etc/portage $ cat package.unmask
>=gnome-base/gnome-2.5
>=gnome-base/gconf-2.5
>=gnome-base/ORBit2-2.10
>=gnome-base/control-center-2.5
>=gnome-base/eel-2.5
>=gnome-base/nautilus-2.5
>=gnome-base/gnome-applets-2.5
>=gnome-base/gnome-desktop-2.5
>=gnome-base/libbonobo-2.5
>=gnome-base/libbonoboui-2.5
>=gnome-base/libglade-2.3
>=gnome-base/libgnome-2.5
>=gnome-base/libgnomecanvas-2.5
>=gnome-base/libgnomeui-2.5
>=gnome-base/libgnomeprint-2.5
>=gnome-base/libgnomeprintui-2.5
=gnome-extra/libgtkhtml-2.6*
=gnome-extra/libgtkhtml-2.5*
>=gnome-base/libgtop-2.5
>=gnome-base/librsvg-2.6
>=gnome-base/gnome-vfs-2.5
gnome-base/gnome-keyring
>=gnome-base/gnome-panel-2.5
>=gnome-base/gnome-session-2.5
>=gnome-extra/gconf-editor-2.5
>=gnome-extra/bug-buddy-2.5
>=gnome-extra/nautilus-cd-burner-0.6.5
>=gnome-extra/nautilus-media-0.7
>=gnome-extra/yelp-2.5
>=gnome-extra/zenity-2.5
>=gnome-extra/gnome-utils-2.5
>=gnome-extra/gnome2-user-docs-2.5
>=gnome-extra/gnome-games-2.5
>=gnome-extra/gnome-media-2.5
>=gnome-extra/gnome-system-monitor-2.5
>=gnome-extra/gucharmap-1.3
>=gnome-extra/gcalctool-4.3.50
>=media-gfx/eog-2.5
>=net-www/epiphany-1.2
net-analyzer/gnome-netstatus
>=net-print/gnome-cups-manager-0.17-r03202004
>=app-arch/file-roller-2.5
>=app-editors/gedit-2.5
>=app-text/ggv-2.5
>=app-text/gpdf-0.125
>=x11-terms/gnome-terminal-2.5
>=x11-themes/gnome-themes-2.5
>=x11-themes/gnome-icon-theme-1.1
>=x11-libs/gtksourceview-0.9
>=x11-libs/libwnck-2.5
>=x11-wm/metacity-2.7
>=media-libs/gstreamer-0.8
>=media-libs/gst-plugins-0.8
>=media-plugins/gst-plugins-oss-0.8
>=media-plugins/gst-plugins-gnomevfs-0.8
>=media-plugins/gst-plugins-mad-0.8
>=media-plugins/gst-plugins-ogg-0.8
>=media-plugins/gst-plugins-vorbis-0.8
>=media-plugins/gst-plugins-esd-0.8
>=media-plugins/gst-plugins-alsa-0.8
>=media-plugins/gst-plugins-ffmpeg-0.8
>=media-plugins/gst-plugins-mpeg2dec-0.8
>=media-plugins/gst-plugins-flac-0.8
>=media-plugins/gst-plugins-png-0.8
>=media-plugins/gst-plugins-xvideo-0.8
>=media-plugins/gst-plugins-a52dec-0.8
>=media-plugins/gst-plugins-cdparanoia-0.8
>=gnome-base/gail-1.5
>=app-accessibility/gnopernicus-0.8.1
>=app-accessibility/gok-0.9.5
>=gnome-extra/at-spi-1.4
>=app-accessibility/gnome-mag-0.10.10