Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Comment Re:Uh huh. (Score 1) 301

To sell cars in the US VW had to pass the test.
VW passed the test.
I actually wonder if they did break any laws or regulations. They without a doubt broke the spirit of the law but...
The simple truth is that the EPA probably has a regulation stating that the car can not have any special emissions testing modes that cause the care to perform in a way different than if driven under normal circumstances.
It is possible that the engineers did not know the law but simply knew the test.

Comment Re:16 nm vs 14 nm (Score 3, Insightful) 210

I'm not particularly familiar with either company's process, but it's been a couple of generations since you could actually make meaningful comparisons based on the quoted nm size, because everyone has different smallest features that they measure when deciding that they are Xnm. That said, we passed the end of Dennard scaling a long time ago. You'd expect the same chip to be consuming about as much power, be slightly more able to dissipate the heat. It may also have less leakage, though that depends on a number of other factors.

Comment Re:Yes and? (Score 1) 87

His point about ownership is spot on, however. Newer EFL is starting to use an IDL so that it can integrate with other languages. I talked to the designer of it at FOSDEM. The idea that your IDL couldn't just use char* for strings (without something to indicate that these ones were null-terminated strings and these other ones were data buffers whose length is represented in this other parameter) and needed to know who was responsible for freeing pointers had not occurred to him. My interest in Enlightenment ended shortly after that: it's not just FFIs that need to know these things, it's C programmers too, and if the underlying APIs are not designed with this in mind then code using them is going to be buggy.

Comment Re:I guess they realised... (Score 2) 87

It's not that supporting the old things slows things down, it's that it doesn't speed things up. It actually does cause some problems, because various things in the X11 protocol use 8-bit fields of which a significant space is used by legacy stuff that no one uses anymore, but that's largely worked around in newer extensions.

If you're in a world where most applications are sending commands like 'draw line from x,y to x1,y1' then X11 network transparency is really fast. At the protocol layer, anyway - if you use xlib then performance will suck unless network latency is very low because it adds a synchronous API on top of an asynchronous protocol (XCB fixes this). Modern applications don't do that, they typically render pixmaps and just have the X server composite them. X11 can still do a reasonable job here, with XDAMAGE, XFIXES, and XRENDER, allowing you to keep most of a pixmap (a Picture, in fact) on the server, update image data in selected parts, and do all of the compositing in the server. The problem is that none of the X11 toolkits actually do this very well. Wayland doesn't solve this at all - it simply says 'well, grab an OpenGL context and send drawing commands'. That works okay - the OpenGL protocol allows you to copy textures to the server (and the GPU) and composite them very fast. The problem is that this approach also works fine in X11, and with X11 you get network transparency when you do it (which works reasonably).

The main criticism I'd have of X11 is that it puts too much state on the server. There is no way, at the X protocol layer (or even in the low-level X libraries) of saying 'disconnect this window from this display, reconnect it here', or 'oh, my X server has crashed, recreate my state on this newly restarted version'. The latter worked fine in BeOS almost 20 years ago and works fine in Windows today. The former worked on NeWS 30 years ago. Both are use cases that I'd love to see addressed for modern devices. The Wayland solution to this is 'write a web app'.

Comment This is basic planetary physics.. (Score 5, Informative) 120

Mars has no Magnetic field because it's core cooled and is no longer a active moving iron mass. it cooled faster as it has very little radioactive isotopes and being further away from the sun it has less energy pounding it to slow the cooling.


Plus we had an event late after the formation of the planets in the solar system that also added a buttload of energy, when the moon was formed from a planetary sized impact.

Comment Why would I help Google with 'open source'? (Score 2) 88

Google which dominates the search/ad market can do this by itself, without my help.

Also, looking at the analysis here: Open source is simply part of its strategy for distributing software that will help it sell more advertising

This is part of a general trend that I call 'open season', basically big companies persuading naive people to do their work for nothing, under the banner 'open source'.

Comment Re:Give me a raise (Score 2) 308

If I had a manger in a software development team role, I'd want a structure where I'd look to him as my peer; there to do an important job of his own, where we evaluate each other; and where we can replace him if he's not working out...

This is how our company works and it's perfect. Their role is to handle client interaction, to set budgets (and hold us to budgets) as well as set schedules and work with us to accomplish the schedule. Ultimately their ass is on the line for staying within budget and schedule so anything within the purview of budget and schedule they are god. If something has to be cut because of budget, we cut it. So that naturally creates a healthy working dynamic. If they need to cut the schedule and/or budget then they come to an artist and ask them if we have any proposals. They then handle working with the client to let the client understand what the implications of moving up a deadline.

But just like an executive assistant isn't actually superior to an executive a producer or project manager isn't actually superior to the team they just are responsible for different aspects of the team's performance. And we understand that it's their ass on the line for schedule so if we deliver late, we need to let them know. If someone isn't delivering on time and making the producer look bad then we aren't going to team up on the project manager or producer like you would if they were your superior you are all in it together and if you are happy with your project manager's work then you can usually all pretty easily recognize the real problem source: the team member who isn't delivering on time. Conversely if the producer is setting impossible deadlines and not providing support to achieve those deadlines then everybody on the team will pretty easily be able to identify the source of the problem. It's not a position that is more highly paid, it's just another position on the team. You need goalies and you need forwards and you need coaches. Sometimes coaches get paid more, sometimes goalies get paid more, sometimes strikers get paid more. You need a chain of command, but mostly just to make arbitrary decisions.

A rock store eventually closed down; they were taking too much for granite.