Announcing: Slashdot Deals - Explore geek apps, games, gadgets and more. (what is this?)

Thank you!

We are sorry to see you leave - Beta is different and we value the time you took to try it out. Before you decide to go, please take a look at some value-adds for Beta and learn more about it. Thank you for reading Slashdot, and for making the site better!



Cisco Releases Open Source "Binary Module" For H.264 In WebRTC

Thinine Good luck with that... (95 comments)

A modern video codec that exceeds the performance of H.265 and VP9 without violating any of the patents held by contributors to either? And one that gains the support of hardware vendors to build it into systems? Good luck.

about a year ago

Things That Scare the Bejeezus Out of Programmers

Thinine Re:A faulty test suite (641 comments)

That "tiny discrepancy in the testing environment" being the fact that you can't simulate zero-g while on the ground, thereby missing out on the fact that loose solder may float around behind control panels while in free fall.

about a year and a half ago

Oracle Ships Java 7 Update 11 With Vulnerability Fixes

Thinine Re:Is this really a fix? (243 comments)

Why does your Mom need Java in the first place?

about 2 years ago

OS X 10.8 vs. Ubuntu On Apple Hardware, Benchmarked

Thinine Worthless... (130 comments)

Yet another worthless benchmarking from Phoronix (Moronix, amirite?). They switch between compilers, compiler versions, and even use Xcode itself for some of these comparisons, which make it essentially worthless. Add to that absolutely zero investigations of the reason for differences between the platforms (aside from the obvious mention of graphics drivers) and this is yet another piece of benchmark porn from a site dedicated to it.

more than 2 years ago

Google Killing Off Mini, Video, and iGoogle

Thinine Ahh, Crap (329 comments)

Now what will my Mom use for a homepage? It checks her gmail, stocks, weather, and offers a translator. What will she do now? TELL ME GOOGLE, WHAT WILL SHE DO NOW?!

more than 2 years ago

Objective-C Comes of Age

Thinine Re:ObjC sucks (437 comments)

Method signatures are often ridiculously long (see NSBitmapRep's initWithBitmapDataPlanes:pixelsWide:pixelsHigh:bitsPerSample:samplesPerPixel:hasAlpha:isPlanar:colorSpaceName:bitmapFormat:bytesPerRow:bitsPerPixel: method)

That's rather the point. It make code easier to read and understand when you can see, in the method invocation itself, what all of the parameters are for.

Parameter names in method calls are /always/ named. You can't just say obj.someMethod(x,y). It's always [obj someMethodForX:x y:y].

Again, rather the point. Otherwise your above example would endue as initWithBitmapData(p,w,h,b,s,a,p,c,f,r,b).

The above combine to make even the most basic operations tedious. Want to trim leading/trailing whitespace off a string? Enjoy [someString stringByTrimmingCharactersInSet:[NSCharacterSet whitespaceCharacterSet]]

Autocomplete makes this rather irrelevant, no? Especially the much improved autocomplete in Xcode4+.

Immutable arrays, dictionaries, sets, strings. I get it, it can be useful for performance to know something is immutable (maybe, I'm not that convinced). But the common use case is most certainly mutable, so /that/ should be the default, e.g. NSArray should be mutable and then if needed there can exist some NSImmutableArray or something. But no, they did it the other way around.

That you don't actually understand this point is pretty telling. Performance isn't the only reason to make arrays and such immutable by default. It also makes such structures safer to pass around, especially to outside code, without having to worry about the data getting modified unexpectedly.

Memory management (up until recently) was neither fully manual nor fully automatic and ownership was based on naming conventions

Ownership is always based on naming conventions, or else there would be no predictability and the language would be unusable.

Being a superset of C, they couldn't provide an object-oriented array class using the normal array syntax, so instead you have tedium like [myArray objectAtIndex:2]

"Fixed" in enhancements coming with Xcode 4.4.

Ditto for strings. Also, you have to prefix string constants with '@'.

Oh no, a single extra character!

Similarly, you can't put "plain" objects into arrays, e.g. [myArray addObject:5] won't work, but [myArray addObject:[NSNumber numberWithInt:5]] will.

Perhaps you one valid complaint, rendered nearly irrelevant by enhancements again coming in Xcode4.4.

And of course you can't just create an array with ['a', 'b', 'c'] but instead have to do [NSArray arrayWithObjects:@"a", @"b", @"c", nil].

Oh hey, same thing.

Backwards conventions like [NSDictionary dictionaryWithObjectsAndKeys:@"value0", @"key0", @"value1", @"key1", nil];

And again, a solved issue.

If I'm going to pay the dev cycle price of a compiled language, it should catch stuff like non-existent selectors at compile time instead of blowing up at runtime

It does. Unless you turned off those warnings. I always build with -Wall -Wextra -Wno-unused-parameter

Stack traces from delayed selector calls have zero contextual information

They have the same information as that selector normally does.

The single inheritance model and a strict class hierarchy discourages writing reusable code. For example, if I have an app that runs on iPad and iPhone and they share a common screen (from the user's perspective although the layout/design might be significantly different), it's a real task to write a common parent class holds the common code.

You're doing it wrong. Reusing code is trivial as long as you've cleanly separated it using the MVC paradigm most common in Objective-C.

Many violations of don't-repeat-yourself: if you want to have an object with properties like Foo.title, then the code is roughly:

@interface Foo { NSString *title; }

@property (nonatomic, retain) NSString *title; @end

@implementation Foo @synthesize title -(void)dealloc { [title release]; [super dealloc]; }

Oh hey, another solved issue. Some of it has been for a few years now. You don't need a backing ivar on iOS or 64-bit OS X and never have. With the enhancements coming in Xcode4.4, you don't even need synthesize. With ARC, you don't need dealloc.

Similarly, there's no way to have a truly dynamic object with a clean syntax, e.g. in Python/ruby/js/and a host of others you could have a quick little object you use to pass state around, kind of like a struct that has its members added on the fly, e.g.: x = new Object() ; x.name = 'dave' ; x.age = 3. There is literally no way to do that in ObjC - the best you can do is create mutable dictionary and use its verbose syntax.

These are a bad idea in those languages too. Hey, lets have an object that can store anything under any name at any time, with no restrictions. Brilliant!

We could have a whole extra thread about the toolchain (Interface Builder is an abomination, Xcode often pegs multiple CPUs when it's just sitting there, if you kill the simulator instead of stopping the app via Xcode then you often have to reboot your host machine before you can run the simulator again) but I digress.

We could indeed. IB is still leaps and bounds ahead of any other GUI tools and your last point is just completely wrong. Xcode does have its problems though.

more than 2 years ago

Doctors Transplant Same Kidney Twice In Two Weeks

Thinine Most Importantly (130 comments)

His sister is hot.

more than 2 years ago

NASA's Next Mission: Deep Space

Thinine SLS? No thanks... (182 comments)

SLS is a steaming pile of shit shoveled onto NASA by Congress. I hope it never flies. Frankly, the Ares V launcher was a pretty good idea, but was bogged down by having to involve all of the old shuttle contractors.

more than 3 years ago

Giant African Rat Kills With Poisonous Mohawk

Thinine Damn (97 comments)

Damn nature, you scary!

more than 3 years ago

Amazon, Google Cave To Apple, Drop In-App Buttons

Thinine Give in? (307 comments)

How does this give in to Apple's demands? By eliminating the in app subscription/purchase capability, they've actually denied Apple any income from their sales. Seems like they refused Apple's demands, not gave into them.

more than 3 years ago

iOS 4.3.4 Prevents Hacking and Jailbreaking

Thinine Terrible (281 comments)

What a shitty summary and article. Seems like both were written by retarded 4th graders.

more than 3 years ago

Open Source Software Hijacked To Push Malware

Thinine Dilemma? (147 comments)

What dilemma does this present for developers? It presents an obstacle to overcome, but where's the dilemma?

more than 3 years ago

UN Backs Action Against Colonel Gaddafi

Thinine Re:UN declares war on Libya (501 comments)

Illegitimate nations like Libya have no sovereignty beyond what the international community grants them. Just because a guy uses military force to control an area doesn't give him any sort of right to that area. Right now there is no Libya beyond Ghaddafi. Only once he is out of the way and the people of that area are able to determine their own fate can it be said that they truly have anything resembling sovereignty.

more than 3 years ago

The Car Faster Than a Speeding Bullet

Thinine Re:Why? (405 comments)

Massive computer-controlled Archimedes mirrors already exist in dozens of large reflector telescopes.

more than 3 years ago

Most IPv6-certified Home Network Gear Buggy

Thinine Re:The exceptions (174 comments)

Lion fully supports DHCPv6 and other IPv6 broadcast technologies.

more than 3 years ago

New Hampshire Bill Could Lead To Adoption of Approval Voting

Thinine Unequal? (416 comments)

Isn't this type of voting inherently unequal, from the voters perspective? I mean, if I only approve of a single candidate but the guy next to me marks several, isn't he in effect getting more votes than me? How am I wrong here? Instead of "one man, one vote" isn't this "one man, up to as many votes as there are candidates on the ballot"?

about 4 years ago

NASA Pitches Heavy Lift Vehicle To Congress

Thinine Re:Let's get this straight (275 comments)

Working with Boeing on a Delta 5 (call a special version for NASA the Ares 5 if you want, but I always thought Ares would be a better name for the program to land humans on Mars) sounds like a better idea anyway. That way we inherit as much of the commercial tech as possible, especially the RS-68. A new core with five 68s (could use the ET for that, but we probably want a redesign for structural support to handle upper stages) and the Delta 4 segments as boosters would be much more reliable than the SSME + SRB. The J2-X may be usable, but I'm not sure if a second stage wouldn't be better served by using another RS-68. Plus an all LOX+LH2 launcher would be much more environmentally friendly. The SRBs are dirty fuckers. Oh, and the external boosters could be upgraded to reusable flyback boosters in the future, if such a thing is actually worthwhile.

about 4 years ago

Chinese DNS Tampering a Real Threat To Outsiders

Thinine Re:I am safe... (181 comments)

Actually, OpenDNS is supporting a DNSSEC alternative, DNSCurve, which gives many of the same benefits, including the preventions of MitM attacks.

more than 4 years ago

Woz Says Android Will Dominate

Thinine Such insight! (416 comments)

Thank you for that startling revelation, Captain Wozvious!

more than 4 years ago


Thinine hasn't submitted any stories.


Thinine has no journal entries.

Slashdot Login

Need an Account?

Forgot your password?