thm76

I think the issue is that Google has too much power to push features via Chromium. This would allow them to create new de-facto standards, which is what we had with IE back in the day.

Sure, the forks could choose not to implement whatever Google might come up with, but that's unlikely, I think.

I took "identical" as in feature wise. The user should be able to accomplish the same things, no matter what platform they're using.

I do think that the way the features are implemented should be platform dependent, i.e. use common UX pattern on each platform, fit in with the UI, and be good platform citizens.

I would extend that to what if their views are an existential threat to anybody.

https://en.wikipedia.org/wiki/First_They_Came

When I look at job postings and see "React" I go "ugh" these days and find myself looking for Angular instead. That's the complete opposite of my thoughts from just two years ago.

I would still rather use something else (instead or React or Angular) but 1) most jobs in my area are asking for one of those, and 2) I'm actually starting to lean towards Angular even for personal projects.

Angular is great these days, and they're making really nice improvements.

How do I enable Zed AI?

I'm logged in, using Zed Preview, and selecting the model does nothing. In the configuration it says I "must accept the terms of service to use this provider" but I don't see where and how I can do that.

Having stuff included does have advantages, but, in my opinion, some of those included things in Angular are really badly designed (I'm looking at you, Forms)

I never use Angular for personal projects, and I have been using TypeScript exclusively for years. I.e. other libraries work really well with TypeScript as well (sometimes actually better than Angular, in my experience)

I find the dev experience of Angular very frustrating, and many things seem overly complicated or not very well designed, in my opinion. That's why I would choose something else (anything, really)

However, if it was noticeably faster than alternatives then I would just deal with those frustrations, personally. User experience (including speed) trumps developer experience.

After having worked on an Angular project for a little over a year I'm at the point where I'm very unlikely to accept another job where they use Angular. It's so frustrating to work with, and every week I find another corner in the framework that, in my opinion, is very poorly designed and/or implemented.

Angular, to me, feels like it was designed by Java developers - classes and bloat* everywhere. Most code, when compared to a React etc. version, just seems like a wall of text on my screen. But, this might make it more approachable to developers that come from a Java background - I see this at my current employer.

(*) By bloat I mean that I often feel like I should have been able to implement whatever feature I just implemented in half the amount of code.

I never really had an opinion about Jeff Bezos, but after seeing this video and how he's interrupting Shatner to spray some champagne - man, I can't say I like Jeff a single bit.

It's not about protecting one guy, but about stopping the spread as early as possible.

My father's former boss (in Germany) has fired women when they became pregnant and just paid the settlement when they sued. As soon as the employer becomes aware that somebody is pregnant they can't fire them and need to guarantee the position or a similar one for when they return from maternity leave.

I understand where you're coming from, but my guess would be that the situation is much more similar between the US, Europe and other countries than you think.

I guess they're talking about http://bohemiancoding.com/sketch/

My understanding was that they don't want to allow executing downloaded code that hasn't gone through the App Store review (such as JavaScript in web pages). I think they allow Lua for scripting in games, though.

So, basically, a 3rd party JavaScript engine is not allowed. I guess you could write your own browser engine that doesn't support JavaScript.

I guess Flash was not allowed for performance and security reasons (lots of vulnerabilities, right?)

You could read "half-blood" as only one half of the blood being of the "good" type. That is, you're only "half" as good as a person which has only the "good" type of blood.

Are they making money off Android?

From what I've read on some blogs they never give numbers showing their profit or loss from Android, and looking at the situation from the outside I'd think it's more likely they're losing money on it at the moment.

Season 2 is available up to episode 9 as a season pass for AUD28.99

The issue is that those companies agreed to licence those patents non-discriminatory and at reasonable terms to anybody that wants to implement those standards (that rely on those patented technologies).

I don't think it would be possible to have industry standards (H.264, Wifi, 3G etc) without such obligations.

Apple (and others) need to pay the patent holders licence fees, but those fees should be non-discriminatory (i.e. similar to the terms offered to other companies). It's not OK to try to use those patents to shut a competitor out.

As far as I know Apple hasn't sued anybody over FRAND patents - they're perfectly in their right to try use their patents the way they do. Samsung, Motorola etc are free to do the same with non-FRAND patents, but what they're doing at the moment is definitely not OK.

http://en.wikipedia.org/wiki/FRAND

No, it's a 200% speed increase. If the speed before was 1 unit, it's now 3 units. That's 200% more.

Hey, looks really cool.

If I were to scan stuff on the go (with JotNot, like in the article), would I be able to use PDFScanner just for OCR?

Or the Reader feature in Safari.

I think what Apple is doing usually, and I think that's one of the points Marco is making in the article, is that they only add features when they can get them working very well.

They didn't have a use for a front facing camera, or could make it easy enough to use, so they didn't include one. Now they have one because they were finally able to implement video chat in an easy to use way (Face Time).

They didn't have copy and paste until they figured out how to make it as elegant and easy to use as it is.

They didn't include 3G in the original iPhone because it would have affected battery life too much.

They only introduced the SDK once the API was in a usable state and they got the necessary documentation and infrastructure in place to support 3rd party developers.

Face Time currently only works on WiFi, but from what I read about it it actually works for Joe Average. On other phones you have to be a geek to figure out which software to install and how to set it up.

For some people it is certainly valuable to have barely working bleeding edge features on the phone, but for the 99% of users out there who're not interested in tinkering with their phone Apple's approach makes a lot more sense, IMO.

We're talking about passwords, though, not the user name.

It's also much more stable on Windows for me. In Chrome a lot of websites just crash the tab (and bring down a few other tabs as well usually - so much about separate processes).

I think the issue was with the limitation that the app can only be installed on up to five devices. The requirement to provide the source code could easily be satisfied by a download link on the app's homepage (which is accessible from iTunes).