Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re: Could have been a contender (Score 5, Interesting) 211

In 1995, a kid in my dorm showed me this new OS called Be. Running on a PowerMac 603 with a single cpu and 16mb of ram, he showed me how Be could play 6 video files simultaneously. Mapped to 6 faces of a cube. And you could spin the cube around via the mouse while all 6 videos were playing. Never any input lag, or dropped frames. It was a thing of beauty.

Comment This demands legal action (Score 1) 564

Microsoft have been wantonly abusing their customers with these non-consentual updates to Windows 10. This should not stand. There needs to be strong legal action against this sort of thing. Let's start by calling it what it is: #WindowsUpdateRape.

I didn't consent to the upgrade, I repeatedly said no, Microsoft repeatedly re-pushed the same upgrader and nagware to my machine. The best way to describe this behavior is "update rape".

Comment Re:The list of prefixed properties (Score 4, Insightful) 132

Long story short, WebKit did things exactly as they were supposed to. They implemented a proposed standard, prefixed it as they were supposed to, and then implemented the standard version later while maintaining support for the prefixed version. Really, the only ones who aren't following best practices are the developers too lazy to update their code to work with the current standards, but if we're going to blame WebKit for being too quick to support proposals, then we may as well blame the other rendering engines for being so slow that the lazy devs couldn't use their prefixed versions. Two sides of the same coin. It's no surprise that one side blames the other.

I think browser developers could all have gone a little bit further and not enabled their proprietary CSS prefixes in production releases by default. Maybe push those into a "developers only" mode, or an extension, but keep it out of production.

The prefixed CSS rules were supposed to be for not-yet finalized pre-standards versions of stuff the W3C hadn't yet finalized, to give web developers a chance to play with them, test them, and provide feedback so that when W3C finalized their recommendation, they were well tested in the real world and good.

By making them available to everyone early, it incentivized web developers who wanted their websites to look "cutting edge" to make use of the unofficial properties before they were ready. Also, the slowness with which W3C has historically acted to finalize their recommendations exacerbates this incentive. If a web developer waits for the W3C to finalize and only uses W3C recommendations, they're left hoplelessly behind the state of the art.

From that point, it was only a matter of time before a dominant browser emerged with its proprietary prefixes became de facto standards adopted by web developers before W3C was ready to finalize their own version of them. What else could they do?

So, blame W3C for not being faster, but mainly blame browser developers for tacitly allowing and encouraging developers to make use of the experimental CSS properties ahead of itme for production sites.

Submission + - Cox HSI ends unlimited internet, introduces cap system

Junior J. Junior III writes: Today, Cox High Speed Internet customers received the following communication:

Dear [Cox HSI Customer],

We spend more time online today than ever before, streaming movies and TV shows, downloading music, sharing photographs and staying connected to friends and family. As Internet and data consumption grows, Cox continues to improve our network to ensure a quality experience for all our customers.

To better support our customers' expanding online activity, we recently increased the amount of data included in all of our Cox High Speed Internet packages. About 95% of customers are now on a data plan that is well-suited for their household. In the event you use more data than is included in your plan, beginning with bill cycles that start on June 15th, we will automatically provide additional data for $10 per 50 Gigabyte (GB) block for that usage period. Based on your last 3 months of data usage and our increased data plans, it is unlikely you will need additional data blocks unless your usage increases.

What this means for you

To help our customers get accustomed to this change, we are providing a grace period for 3 consecutive billing cycles. During this period, customers will not pay for additional data blocks for data used above their data plan. Customers who exceed their data plan will see charges and a matching credit on their bill statement. Beginning with bills dated October 15th and later, grace period credits will no longer be applied, and customers will be charged for usage above their data plan.

Understanding and managing your data usage

You are currently subscribed to the Preferred package which includes a data plan of 350 GB (Gigabytes) per month. To help you stay informed about data usage, Cox will begin to notify you via email and browser alert if you use 85% of your monthly data plan and again if you use 100% of your monthly data plan. Additional blocks of data will only be provided if you exceed your data plan. This will not change your Internet package and there will be NO change to the speed or quality of your service for data usage above your plan. To better understand your household's historical and current data usage, you will find your household's data usage meter and other helpful tools and information here.

Thank you for choosing Cox.


Cox High Speed Internet Team

In the wake of FCC's ruling reaffirming Network Neutrality, is this what ISPs will be doing to squeeze more money out of its customers?

Slashdot Top Deals

Technological progress has merely provided us with more efficient means for going backwards. -- Aldous Huxley