Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×

Comment Re:definitions (Score 4, Insightful) 197

>I agree Gimp sucks

It's the layers. They are what makes GIMP suck.

An average user, expects that when they select a rectangle, plant the mouse in the middle and drag it, the contents move. This happens in photoshop. It sometimes happens in GIMP, but usually not. This is something to do with layers, it is massively annoying and it is the barrier to entry that leaves most people saying GIMP sucks.

If I encounter this non functionality, I can usually drill through some menus and find something to 'merge layers' so they behave like the bitmap they are supposed to behave like. But most people don't manage to do that and give up.

It is inexcusable that when you import a jpeg picture it comes in as more than one layer and GIMPs tools then interact with a different invisible layer, frustrating the user trying to edit the image.

That is why GIMP sucks. If they fixed the layer interface, GIMP would not suck. I'd do it myself, but I'm too busy designing chips to fork GIMP and fix it.'
 

Comment Re:Not surprising (Score 1) 255

OrCAD never recovered from the transition from dos to windows.

The mouse thing got better with time, but the killer was that they broke keyboard macros. What replaced them (VB script) wasn't fit for purpose. A decade of carefully crafted tools to auto generate symbols from libraries got thrown in the toilet.

Comment Feedback. (Score 3, Insightful) 141

I want feedback.

I want to be able to stick a thermometer in my food, whether in the oven, microwave or on the hob and have the thing use feedback to follow a temperature vs. time profile.

Why waste $5k on immersion heaters and vacuum packers for sous vide setups when a simple thermometer input and a few lines of code could achieve the same thing on a conventional kitchen oven?

Comment Re:UPnP is a vulnerability (Score 1) 138

>My understanding was that UPnP was for punching a hole in the firewall/NAT for incoming requests

No, uPnP is primarily about AV devices finding each other so they can do stuff like sending video from the video source to the TV. It's network detection and selection, device discovery, service discovery and service negotiation. All run of the mill consumer electronic behaviors that the industry has managed to massively screw up for the past 30 years. P1394 tried and screwed it up (discovery and negotiation). uPnP tried and screwed it up (bad security, ineffective discovery). P802 tried and screwed it up - LLDP (too little), 802.21 (too late). I could go on. You still cannot string one wire, or wireless interface between standards compliant boxes, computer, dvd, tv, speakers, roku-esque box and have them find each other and present a user with the right options like "watch dvd" or "watch roku" or "watch TV".

The punching-a-hole thing is a router behavior to allow uPnP to work across the router (whether firewalled or not), because by default they block uPnP, as they should.

 

Slashdot Top Deals

To thine own self be true. (If not that, at least make some money.)

Working...