Apple’s refusal to support Progressive Web Apps is a detriment to the web

Re:Apple’s refusal to support Progressive Web Apps is a detr... by SquareWheel on Thursday July 27, 2017 @09:15AM (#14864907)

I'd also add SQL to your language list, and often SASS, gulp/grunt configuration, JSON, ASP.NET, and so on.

And come on, JS is a C-style language. If you know one you know them all.

It's also not a difficult jump to OOP languages; especially now that Java 8 supported lambdas and C# supports async/await. It's hard to learn concepts, not syntax.

[ Parent | on HN ]

Re:Apple’s refusal to support Progressive Web Apps is a detr... by egeozcan on Thursday July 27, 2017 @09:23AM (#14864973)

Don't you agree, though, thinking that web developers don't write iOS apps because they don't want to learn Swift, is a bit ridiculous at this point? Yet another language isn't even significant for a typical web developer. For me, tooling (XCode) took more time to learn than being able to write acceptable Swift...

[ Parent | on HN ]

Re:Apple’s refusal to support Progressive Web Apps is a detr... by SquareWheel on Thursday July 27, 2017 @09:41AM (#14865120)

Yes, I agree. I was agreeing with you before as well. Setting up a Mac, learning a new IDE, and getting your tooling/builds set up is a far bigger pain point than actually learning the new language.

At least that's the case if it's logically similar. C, Java, JS, etc are mostly transferable. I might not say the same about something like Haskell.

[ Parent | on HN ]

Re:Apple’s refusal to support Progressive Web Apps is a detr... by s73ver on Thursday July 27, 2017 @07:39PM (#14870749)

If that's the case, then we shouldn't hear any complaining about having to learn Java, ObjC or Swift.

[ Parent | on HN ]