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


Forgot your password?

Comment Re:Moor? (Score 1) 151 151

That depends on whether you are using it as storage, or a main memory.

As a main memory, that is nowhere near enough writes.

And yes, this is being suggested as a solution for main memories in certain applications. However, these applications will not change state as often - in-memory caches, databases, etc.

Comment Re:Not the right tool (Score 1) 143 143

Why not? This extends the spreadsheet as a tool to include complex real time processing, and allow people who are spreadsheet savvy but otherwise not programming savvy, to calculate and visualise large complex datasets in however way they want to.

Indeed, given the complexity of parallel programming, for many problems that could be expressed on a spreadsheet, but were before not viable because of the speed, these can now use the spreadsheet, and get results better than what many programmers could achieve without using OpenCL/CUDA/OpenMP themselves.

Comment Read the article, it's full of great quotes (Score 5, Funny) 133 133

“People who made early implementations of Perl 6 came back to me, cap in hand, and said “We really need a language designer.””

“I was almost explicitly told: “Stay out of the implementation! We saw what you did made out of Perl 5”

“With Perl 6, we found some ways to make the computer more sure about what the user is talking about.” ...

Comment Re:Is this unique to Java? (Score 1) 130 130

It was viable in 1998! That was when I last wrote an applet (a tetris game to run on a 40MHz ARM-based Set Top Box from Acorn that never saw the light of day).

No, no, wait, I did write a rotating 3D globe applet in 2006 for a laugh.

Applets were a bad idea, are a bad idea, and should be dead. Luckily browser security policies are making maintaining in-house applets non-viable so they can move to better installation mechanisms now.

Comment Re:The root cause : poor unit testing (Score 1) 130 130

Just maintain a visible Risk document with all the issues. Document the estimated fix time. Let it have visibility.

Then when the shit hits the fan, you have your arse covered. Not that this will protect you against particularly nasty management scum...

Using Apache libraries, or ${largeCompany} libraries is one thing. But random crap found on Github?

All you can do is overestimate work, and use the time to kill off the libraries one by one.

Comment Re:The root cause : poor unit testing (Score 1) 130 130

My previous employer was of this mindset. Even with in-house dependencies. Nothing was other updated, out of fear.

A horrible environment to work in, of course. Every few months a component upgrade would be required, and because it was 100 releases out of date the upgrade was a horrible horrible experience.

And they had generally reasonable test suites too. It was pure fear of downtime because of the monolithic architecture of the application.

Comment Re:Debunking the debunker (Score 1) 172 172

Yet rechargeable AAs work at 1.2V and most products don't have problems with them...

It makes more sense for this tech to be installed in the devices that require that 1.4V+ supply rather than be external.

And in that case, the tech needs to be cheap, and we talking cents for a device cheap here.

And just stop buying non-rechargeables already!

Comment Re:One port to rule them all... (Score 5, Interesting) 179 179

And for most users, that one cable is going to be a bog-standard USB 3.1 passive cable, that can still be used for 20Gbps Thunderbolt, as well as USB 3.1 and DisplayPort. This is going to be massive news for consumer docks.

If you absolutely need more than 2GB/s for your attached RAID/GPU then you will need an active Thunderbolt cable to reach 40Gbps.

I'm sure this use case was part of the USB Type C plan.

Comment Fun little project, of course ... (Score 4, Insightful) 41 41

Ah, but this will not be able to implement the ability to swing around corners that traditional pacman has, which lets you get away from chasing ghosts, just a little bit.

Otherwise, it's a great project if you want to work with microcontrollers and embedded programming. Beats the obvious tetris clone at least. Sokoban might be another good game to implement. And Bejeweled.

Comment Re:You can do Open right (Score 1) 156 156

Yes, given the need to maximise headcount per square foot, open plan offices are here to stay. I agree with your points (I get most of them), they will keep morale higher.

Hot desking for tech people has to be the singular most stupid idea ever. In fact it is stupid for everyone, I think most people would prefer to have an assigned 'callcentre' style desk than to hotdesk. I have not heard a single good thing about the concept from people forced to endure it. As an aside, I worked on 'smart office' stuff for BT back in 2000, the idea was to personalise hot desks - clever stuff to keep the area personal with shared facilities (a person's photos would travel to the digital picture frame on the hot desk they were logged into, etc). It sucked back then.

I just wish the flexible working hours aspect was more of a thing here. Early in, early home would be nice for some, late in late home for others.

And yes, given a choice, I bet people would stick with open plan offices rather than a pay cut (to get a bigger work space) or commuting to some out of town office park full of empty Disaster Recovery offices, no food outlets, no pubs, no nothing.

Comment Re:because it's cheap, and you're expendable (Score 1) 156 156

You got a divider! Lucky sod.

Open plan offices suck, but they're here to stay because to work in a decent area, you have to pay more for the offices, and for many companies that is an undesirable situation. Most people can cope with background noise and hubbub, or use headphones to become totally unapproachable, you get distracted by the hot QA girl that walks by every so often which is a nice perk, etc.

It's a shame that most places don't use curved desks, so that the person behind you isn't directly behind you. Also the new thing seems to be about removing cabinets from desks, or moving to lockers. That's saving like fifty dollars, on a potentially $100k member of headcount.

They do work for overhearing things in your team that you can contribute to. But that would still work in a Team Lab space type office layout, with six to twelve people in a large room.

The days of individual offices, 10ft by 10ft or more, are over for most employees. At best you can hope for a 6ft by 8ft area. And that works partially because monitors are thin; you need 1/10th the paperwork and books and manuals you needed even ten years ago, never mind 20; no one ever prints so 2 printers can service an entire floor; and people are generally used to timewasting .... sorry, internet time, that they don't care if you do it as you would have done it in your cube.

Time-sharing is the junk-mail part of the computer business. -- H.R.J. Grosch (attributed)