Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Comments

top

Microsoft Announces Windows 10

Bogtha Re:Microsoft skips 'too good' Windows 9, jumps to (640 comments)

Fuck everything, we're doing Windows 10.

Would someone tell me how this happened? We were the fucking vanguard of operating systems in this country. Windows XP was the operating system to run. Then Apple came out with OS X. Were we scared? Hell, no. Because we hit back with a little thing called Windows Vista. That's Aero UI and a sidebar. For widgets. But you know what happened next? Shut up, I'm telling you what happened - the bastards went to mobile. Now we're standing around with our cocks in our hands, selling a desktop operating system with a sidebar. Aero or no, suddenly we're the chumps. Well, fuck it. We're going to Windows 10.

Sure, we could go to Windows 9 next, like the competition. That seems like the logical thing to do. After all, 8 worked out pretty well, and 9 is the next number after 8. So let's play it safe. Let's make a better UI and call it the Start Screen. Why innovate when we can follow? Oh, I know why: Because we're a business, that's why!

2 days ago
top

Ask Slashdot: Swift Or Objective-C As New iOS Developer's 1st Language?

Bogtha Re:Does Swift work on older iOS versions? (314 comments)

it would have been much easier and more polite to point that out instead of ranting nonsense for two posts minimum now

Not reading the sources I provided is impolite. I haven't been "ranting nonsense", I've been pointing out how and why you are wrong.

As I said: I'm full ear ... but not for rants. For information and facts.

I linked to these. You didn't read them.

2 days ago
top

Building Apps In Swift With Storyboards

Bogtha Re:NOT like Microsoft's Visual Studio GUI layout a (69 comments)

Interface Builder has not changed in any fundamental ways since it debuted in 1988 with NeXTstep.

I'd say storyboards and auto layout are pretty big changes. Before storyboards, nibs were basically just view hierarchies and whichever other objects you threw in there. With storyboards, they can contain an entire application's user interface, including the transitions between different screens.

it is NOT a screen drawing tool. It is an object instantiation and configuration tool.

It's both. It's a screen drawing tool that uses object instantiation and configuration to accomplish that.

2 days ago
top

Ask Slashdot: Swift Or Objective-C As New iOS Developer's 1st Language?

Bogtha Re:Does Swift work on older iOS versions? (314 comments)

I simply doubt that companies other than Apple have any means to collect reliable data at all.

Yes, but your doubts are based on incorrect guesses you have made about collection methods and personal experience, both of which are worthless.

Furthermore, the statistics coming out of these companies are roughly the same as the statistics published by Apple, and you don't believe them either! So basically, your attitude is "if I don't like the stats, they are wrong". Well sorry, but you not liking the stats is not a reason to disbelieve them.

Otherwise we had not that company releasing every year a statistics claiming that Microsofts web server (IIS) where the most widely used one, ah well second most widely used :)

Huh? None of the companies we are talking about publish statistics like those.

However if you have ideas how they measure iOS versions share them, I'm full ear.

No you aren't. If you were paying attention, you'd already know how they measure iOS versions. The information is right there waiting for you to read it, but you ignored it already in favour of your own incorrect guesswork.

you gave me two links, I checked one and the 'usage distribution' of iOSes made no sense at all

No, what you mean is that you didn't like the statistics. They make perfect sense.

there was no information how they gathered that statistic

All you are showing here is that you didn't bother looking. That information is available on their websites, in one case at the bottom of the page I linked to.

I get that you don't like the fact that iOS adoption of new versions is high, but can you try to understand the difference between what you would like to be the case and what actually is the case?

If three different companies all independently measuring iOS adoption all come up with roughly the same figures, the fact that you know people who haven't upgraded does not outweigh those statistics.

Now, if you aren't willing to pay attention to reliable sources and think your personal experience is more relevant than statistics sourced from millions of people, don't bother responding, as it's impossible to have a sensible discussion with you.

2 days ago
top

Ask Slashdot: Swift Or Objective-C As New iOS Developer's 1st Language?

Bogtha Re:Very outdated info (314 comments)

Staying close to the cutting edge is easy when it's an incremental change. It's a very different thing when it means throwing out all of your your code.

Adopting Swift doesn't mean throwing out all of your code. You can have Swift classes in a mostly Objective-C codebase and Objective-C classes in a mostly Swift codebase as you wish.

I could be wrong, but I really, truly don't see anything about the new language that makes me want to start rewriting those billions of lines of existing code in a new language.

Who is talking about doing that? The conversation is about Swift being the dominant language for iOS development. If most new code is written in Swift, then it's dominant regardless of the fact that there's lots of legacy Objective-C code out there.

Apple is positioning this not as a replacement for Objective-C, but as a replacement for the Ruby/Python/Perl bridges

That's not even close to accurate. Read the Apple material, watch the WWDC videos, talk to the Apple engineers. This is not a replacement for a scripting bridge, it's intended to be the first choice for typical developers.

tell me why in the world you think that Apple won't take even longer to replace a non-temporary language

Once more, the conversation is about whether or not Swift will be the dominant language, not whether it will be the only supported language. Nobody is arguing that Apple are going to remove Objective-C support tomorrow.

Preliminary third-party analysis of Swift shows that for many simple operations, it is more than an order of magnitude slower than Objective-C. Assuming their testing methodology does not prove to be invalid for some reason

It already has for the most part, where have you been? Most of the benchmarks out there were run with beta tools, had different compiler switches, or other beginner level mistakes. Yes, there are some areas where Swift is slower, but most application developers aren't going to be significantly affected by that. Letting vague aspersions about performance dictate your language choice is nuts. Most of the time it doesn't matter and when it does, which language is faster depends on the exact thing you are doing.

if you're thinking about writing a major app in Swift, you should probably think twice

This is just FUD. Most languages are fast enough for typical use cases, and if you think you are going to be in the minority affected by performance issues, you really should consider Swift rather than dismiss it because depending on your use case, it could be faster for your situation.

start with Objective-C. That will let you get started working with real-world code now

Ah yes, my running streak of conversations involving the phrase "real-world" meaning "things I don't irrationally dislike" remains unbroken.

There is absolutely nothing that is not "real-world" about Swift.

The vast majority of what you learnâ"the frameworks themselvesâ"won't change if you later decide to switch to Swift. Only the syntax changes.

If you think that the only difference between Objective-C and Swift is syntax, then you really haven't given Swift more than a passing glance. It's a very different language.

3 days ago
top

Ask Slashdot: Swift Or Objective-C As New iOS Developer's 1st Language?

Bogtha Re:Does Swift work on older iOS versions? (314 comments)

Just stop. You have no idea what you are talking about. You are just guessing incorrectly at how these companies collect their data and you think your personal anecdotes trump real statistics. You're ignoring the information right in front of you because you only see what you want to see.

3 days ago
top

Ask Slashdot: Swift Or Objective-C As New iOS Developer's 1st Language?

Bogtha Re:Does Swift work on older iOS versions? (314 comments)

My source is the author of NovoCard.

Yes, but where did he say this? I want to be sure you aren't misinterpreting him or that there isn't another factor involved.

Mixpanel and Fisku have no means to figure who is running what version of iOS on what device

Of course they do. Do you really think they are just making the numbers up?

The only company who could is Apple, but they only track sold devices versus downloads of new OS versions.

No, that's not how they track it. Where did you get that idea from?

It seems to me you are denying the numbers based upon your feelings towards the update. It doesn't matter what you feel, the numbers are what they are. Almost everybody is using iOS 7+.

3 days ago
top

Ask Slashdot: Swift Or Objective-C As New iOS Developer's 1st Language?

Bogtha Re:Does Swift work on older iOS versions? (314 comments)

The programmer of "NovoCard" released that for iOS 5 or iOS6, he is now prevented from putting bug fixes for the old release into the AppStore because Apple requires him to release the "new release" for iOs7 and above.

Are you sure you aren't mistaking that for the fact that he's required to support iOS 7? Where's your source?

Your claim that 95% of the users are now on iOS7 and newer is simply wrong, regardless what Apple claims.

Nearly everyone I know (and has the knowledge how to do it) switched back from iOS7 to iOS6.

Your anecdotes about people you know do not outweigh the statistics gathered across all active users.

It's not just Apple that say that 95% of people are on iOS 7+. Mixpanel do as well. Fiksu put it at 90%. You get the picture. Multiple independent sources all say that the vast majority of people are using iOS 7+ regardless of your personal gripes with it. Just because you don't like it and you know other people that don't like it, it doesn't mean Apple are "simply wrong" when they say that almost everybody is using iOS 7+.

3 days ago
top

Ask Slashdot: Swift Or Objective-C As New iOS Developer's 1st Language?

Bogtha Re:Does Swift work on older iOS versions? (314 comments)

this is one good reason to use Obj-C instead of Swift: to support older iOS devices that cannot upgrade to iOS 7.

Not all that good a reason. 95% of active iOS users are already on iOS 7+ and that number is growing every day. The only devices that can't upgrade to it are the iPhone 3GS and below, the equivalent iPod touch, and the first generation iPad. There aren't many people using these devices any more.

I have an iPad 1 that is stuck at iOS 5.1.

I appreciate that it's frustrating being left behind, but when only 0.66% of active iOS users are on version 5, it's very difficult to justify the extra work involved in supporting them.

By the time the OP learns to develop for iOS and actually builds his application, the number of people using older versions of iOS will be even lower. Unless you're willing to chase diminishing returns, it's not worth supporting anything beyond the previous major version, and even that's debatable.

5 days ago
top

Ask Slashdot: Swift Or Objective-C As New iOS Developer's 1st Language?

Bogtha Re:Very outdated info (314 comments)

Remember how long it took to lay Carbon to rest.

Very different situation. I work with a lot of companies that develop iOS applications, and it's extremely rare for them to be more than a couple of years behind the cutting edge.

Then take a look back at all the new programming languages and frameworks Apple has introduced over the years and then shot in the head.

Modern Apple does it very infrequently, and usually, when they do, it's because they've got something newer to replace it. In this case, Swift is the newer thing.

5 days ago
top

Ask Slashdot: Swift Or Objective-C As New iOS Developer's 1st Language?

Bogtha Re:Does Swift work on older iOS versions? (314 comments)

No, you're right, there's no rule against supporting older versions. Xcode 6, which is the version released just the other day to support iOS 8 development, supports building applications targeting iOS 6 and up.

Apple have never explicitly required developers to support a minimum version of iOS, they just drop support for targeting older versions in Xcode a few years after release. Xcode 5, which was the most recent version until the other day, still supported iOS 4.3, which is over three years old and has virtually nobody using it.

5 days ago
top

Ask Slashdot: Swift Or Objective-C As New iOS Developer's 1st Language?

Bogtha Re:If you 'speak' C (314 comments)

It's technically possible to write an iOS application in nothing but C, but it's deeply unpleasant compared with using the right tool for the job. Just learn Objective-C. There's very little more to the language than plain C, but it makes things so much easier. Then, when you're familiar with the platform, pick up Swift. It's by far the better language, but it's a bigger change than C to Objective-C and it's still pretty immature.

5 days ago
top

Ask Slashdot: Swift Or Objective-C As New iOS Developer's 1st Language?

Bogtha Re:Stay away from Objective-C (314 comments)

One of the worst parts is all the retain and release calls.

OP says he's familiar with C, so he's already used to manual memory management.

Regardless, modern Objective-C uses ARC, which means all the retain and release calls are automatically generated by the compiler. You actually get a compiler error if you try to write the calls yourself these days.

god help you if you forget because there's no obvious way to see the problem.

Aside from the fact that Apple provides excellent tools like Instruments and a static analyser which lets you track down problems like this easily, so long as you understand one single principle, it's very difficult to go wrong with manual memory management on Apple platforms.

NARC. If a method begins with new, alloc, retain, or copy, then you own it and it's your responsibility to release it. Otherwise, you don't need to.

The only people who struggle with memory management are the ones that don't understand this very simple rule. Learn that, and it's effortless.

My boss, who wrote all the Objective-C stuff, says that Objective-C has become a mess over the past 5-10 years as Apple is promoting Objective-C for both iOS (iPhone, iPad) and OSX (desktop) applications, which has caused all kinds of problems and bloat. I've had all kinds of problems with Objective-C, so I don't doubt his characterization of it.

To be frank, it sounds like none of you have more than a beginner understanding of the language. How can you not be aware of NARC or ARC? It's the kind of thing you learn on day one.

5 days ago
top

Ask Slashdot: Is iOS 8 a Pig?

Bogtha Re:Alright smart guy (504 comments)

I'm going to try putting it in airplane mode when I go to bed tonight to see if that stops whatever is eating it.

Go to Settings > General > Usage > Battery Usage and it will tell you what's been using energy.

about two weeks ago
top

Science Has a Sexual Assault Problem

Bogtha Re:HOw to tell a ridiculous sexual claim. (460 comments)

If the men have a significant response rate, then just maybe that means the problem is YOUR QUESTION IS TOO VAGUE, rather than both genders experiencing sexual issues.

Wow, how unscientific can you get? You've decided on what you want the result to be and you're discarding data that doesn't fit.

Sexual assault is really, really common. It's not just another word for rape, it covers any unwanted sexual touching. I had a woman I didn't know grope me as I was leaving a club last week. That's sexual assault. You may think that it's harmless - I wasn't particularly bothered by it - but regardless of severity, it's still sexual assault.

about two weeks ago
top

Apple's "Warrant Canary" Has Died

Bogtha Re:Coincidence? (236 comments)

Apple has so many sweetheart deals with the US gov that it's not funny, mostly in the area of non-compliance with tax code or outright tax evasion.

Can you substantiate this? Every time somebody has said this to me and they've gone into specifics, it's been bullshit.

Just the fact that Apple is allowed to flaunt the anti-trust laws is a good example of why Apple (and shareholders) benefit from spying.

Same here. Which anti-trust laws? Be specific.

about two weeks ago
top

Apple's "Warrant Canary" Has Died

Bogtha Re:Coincidence? (236 comments)

I don't believe a fucking word. They'd throw a baby off a bridge for a $2 bump in their stock price.

How would providing data to the USA government raise their stock prices? If anything, it would lower them.

You don't really have to trust Apple to do the right thing here. If - as you say - they are only motivated by profit, then look at what is more profitable for them. Their business model doesn't depend on access to their customers' personal data and habits. Google, on the other hand, makes use of their users' personal data and habits, however benignly you choose to judge that.

Basically, privacy is a competitive advantage Apple have against their biggest rival in the mobile market. If you think they are only motivated by profit, then the reasonable conclusion is that they will act to preserve their customers' privacy rather than disclose it.

about two weeks ago
top

Apple Locks iPhone 6/6+ NFC To Apple Pay Only

Bogtha Re:WTF (335 comments)

You're massively overreacting to a biased headline. What is meant by "Apple locks NFC to Apple Pay" is simply "Apple have only provided APIs for Apple Pay so far".

This is pretty standard practice with new Apple hardware features.

Bluetooth? Originally developers couldn't access that at all, only the higher-level gaming APIs used it.

Touch ID? Again, developers couldn't access that at all to begin with, but iOS was released yesterday and that introduced an API for developers to use it.

The camera? Originally developers could only tell the system that they wanted a photo. Now we've got fine-grained control over shutter speed, etc.

Apple have a habit of introducing hardware features then providing a third-party API after they've had a chance to see it deployed at a large scale. If you are a long-time iPhone user, you've seen them do this time and time again. The fact that there isn't an API for it on day one doesn't mean that they are trying to lock it away.

about two weeks ago
top

Why Apple Should Open-Source Swift -- But Won't

Bogtha Re:interesting, except... (183 comments)

Apple haven't said that they will open-source Swift. The only thing they've said so far is that they've been concentrating on getting it to 1.0 first and haven't made a decision about open-sourcing it yet.

about two weeks ago

Submissions

top

BBC creates 'Perl on Rails'

Bogtha Bogtha writes  |  more than 6 years ago

Bogtha (906264) writes "Long-time users of Perl for their public websites, and having successfully used Ruby on Rails for internal websites, the BBC have fused the two by creating a 'Perl on Rails' that has the advantages of rapid development that Rails brings, while performing well enough to be used for the Beeb's high-traffic public websites. This is already powering one of their websites, and is set to be used in the controversial iPlayer project as well."

Journals

Bogtha has no journal entries.

Slashdot Login

Need an Account?

Forgot your password?