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.
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...
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.
> I am thankful that Apple does not allow to litter it with some JS scraps.
Oh, so much for being objective. References and all.
> All this cross-platform talk is just being cheap, being lazy or both.
Are you even serious? You really blame engineers/developers coming up with trade-offs for being cheap and/or lazy?
> And I would not be surprised that maintaining cross-platform monstrosity eats away any cost-savings pretty quickly.
No it doesn't. I'm a developer since much more than 10 years. I guess that's enough of a reference :)