Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Comment: meh (Score 1) 1191

by BagOBones (#45009131) Attached to: Come Try Out Slashdot's New Design (In Beta)

- News uses less than what 1/3 of the horizontal space not including the polls, everything is crammed in a narrow strip down the middle of the screen.
- bright blank white space on each side is great than the content section as a whole at 1920X1080
- contrast of new design makes reading harder some how.
- Comments are awful; due to the compressed layout and the fact they aren't boxed in as well as the old system
- loaded it on my iPhone, and waited... and waited... slow and the banner ad that loaded made the layout break. big step backward from the current mobile option

Bottom line I am hard pressed to find anything positive here...

Comment: Re:Why aren't people more hyped about the Wii U? (Score 1) 188

by BagOBones (#41778973) Attached to: Nintendo's Wii U Will Be Sold At a Loss

I don't know, when the Wii U controller was announced stuff like this http://www.macstories.net/news/ipad-games-on-apple-tv-firemint-announces-real-racing-2-hd-with-ios-5-airplay-mirroring/ had already landed.

If you already own a tablet that can stream to your TV why purchase a dedicated console with a limited tablet LIKE controller?

Comment: Re:Network gear features are still WAY behind v4 (Score 1) 244

by BagOBones (#40247753) Attached to: After Launch Day: Taking Stock of IPv6 Adoption

I can forgive Juniper when compared to Cisco on the topic of licensing and complexity.

Despite advancements for support at the device level the next major hurdle for large enterprise is the management tools and monitoring tools not fully supporting IPv6.

It is really hard to manage a modern network without flow monitoring, snmp and syslog data from all systems. This is another area where you end up with a setback or compromise if you try and roll out right now.

Comment: Network gear features are still WAY behind v4 (Score 4, Informative) 244

by BagOBones (#40247523) Attached to: After Launch Day: Taking Stock of IPv6 Adoption

On the consumer front only just recently did home WiFi routers start shipping or start getting IPv6 support, even then finding an ISP that will provision you is next to impossible.

On the enterprise front gear has been labeled as IPv6 ready or compatible or even listed it as a feature for a long time. However if you work in security and have to implement policy control over content, you quickly see that the functionality is years behind when applied to IPv6 flows... At an enterprise level switching isn't easy without swamping out a lot of gear, or reducing expectations... IPv6 enabled deep inspection, and application layer inspection tools are only now becoming available, or only now becoming mature enough to roll out.

Comment: Re:Yes, blame the developers! (Score 1) 156

by BagOBones (#40187429) Attached to: The Cost of Crappy Security In Software Infrastructure

Developers are not end users... they are some level of engineer, as they are BUILDING things for end users to use... They should be reading some kind of docs before choosing tool / function they use for the job... the more powerful the language the more you need to know.

In your example the developers should be the ones that build the BAD CAR with the exploit in it that was sold, they where not the poor end users that purchased it.

Disclaimer: "These opinions are my own, though for a small fee they be yours too." -- Dave Haynie