Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New WebKit Features in Safari 13.1

webkit.org

Post reply on HN
Print view View original

21–30 of 60 posts

Re: New WebKit Features in Safari 13.1

#21

Post by tobr »

sunseb wrote: post #5

On a side note, I find crazy this obsessive-compulsive behavior to use `const` everywhere in modern JS codebase (even in Webkit now). It solves really no problem (I mean, Python, Ruby and almost all other programming languages are doing fine without preventing against variable reassignment, and we can still reassign function parameters and object properties in JS). So much brain power wasted on this useless thing. Al…

> So much brain power wasted on this useless thing.

I can see the argument that using `const` over `let` doesn’t bring any huge benefits, but I don’t see what the harm is either. I never found it a waste of brainpower. At this point it’s idiomatic, so I think using `let` everywhere is more likely to have people confused.

Re: New WebKit Features in Safari 13.1

#22

Post by maxwell »

forkLding wrote: post #17
maxwell wrote: post #10

Earlier quoted context omitted.

Apple has intentionally crippled WebRTC for years to stifle FaceTime competition and drive up dev costs by forcing native app development. The video chat startup I co-founded in 2015 was impacted. https://docs.house.gov/meetings/JU/JU05/20190716/109793/HHRG...

Hi maxwell, what would you recommend to another developer who might be entering the same space with a WebRTC-based product?

We settled on TokBox. We were one of their first customers making significant use of server-side recording (virtual estimates for home service providers), and worked closely with the TokBox QA/dev team to resolve bugs until things stabilized in 2016 around the time we hit real product-market fit (focusing on relocation moving estimates).

I've stepped away but AFAIK they're still using it. It was expensive but worked with our business model ($20 for a successfully completed self-service video call between service provider and end customer, $50 to have the virtual survey performed/recorded by our trained video surveyors around the world, $90 to also have priced).

I'd compare TokBox, Twilio Video, and Jitsi.

Re: New WebKit Features in Safari 13.1

#23

Post by holidaygoose »

forkLding wrote: post #4

At least I think WebRTC was mentioned, been dying for more fixes to issues.

With today's remote work and overuse of the internet, WebRTC is really critical. Same with WebP -- the bandwidth savings there could be immense in a time when we're using more internet than ever. I'm disappointed in Apple's lack of investment in these things, and it feels like they're out of touch.

Re: New WebKit Features in Safari 13.1

#24

Post by forkLding »

maxwell wrote: post #22
forkLding wrote: post #17

Earlier quoted context omitted.

Hi maxwell, what would you recommend to another developer who might be entering the same space with a WebRTC-based product?

We settled on TokBox. We were one of their first customers making significant use of server-side recording (virtual estimates for home service providers), and worked closely with the TokBox QA/dev team to resolve bugs until things stabilized in 2016 around the time we hit real product-market fit (focusing on relocation moving estimates). I've stepped away but AFAIK they're still using it. It was expensive but worked…

Thanks maxwell for the answer! Really appreciate it, apologies for asking more but how did you guys handle customer browsers not really up to date or compatible with webrtc back then?

Re: New WebKit Features in Safari 13.1

#25

Post by brandonhorst »

Austin_Conlon wrote: post #12
queezey wrote: post #9

> These improvements are available to users running watchOS 6.2 [...] I would like more information about Safari being available on Apple Watch. Normally I'd think it's inclusion was an accident or oversight, but it's mentioned at both the top and the bottom of the article.

Not a standalone browser app, but if I tap a link in say the watchOS Mail app, it'll display a web view. Developers can optimize their site for the watch display. It might sound crazy but it's useful for glancing at brief information on the web.

Siri can also show web results on watch. I believe the News app uses WebView as well.

Re: New WebKit Features in Safari 13.1

#26

Post by madeofpalk »

sunseb wrote: post #16
madeofpalk wrote: post #13

Earlier quoted context omitted.

What about const/let is poorly designed?

Have a look here: https://jamie.build/const https://twitter.com/dan_abramov/status/1208369896880558080 (React core team member) https://twitter.com/littlecalculist/status/91787524189167616... (Ember creator)

I don't think it's poorly designed, its just maybe perhaps not all that useful?

Re: New WebKit Features in Safari 13.1

#27

Post by karatestomp »

madeofpalk wrote: post #26
sunseb wrote: post #16

Earlier quoted context omitted.

Have a look here: https://jamie.build/const https://twitter.com/dan_abramov/status/1208369896880558080 (React core team member) https://twitter.com/littlecalculist/status/91787524189167616... (Ember creator)

I don't think it's poorly designed, its just maybe perhaps not all that useful?

Some people seem really unhappy that it might mean a reference is constant, rather than a value, if the value happens to be a reference. If that makes sense.

Re: New WebKit Features in Safari 13.1

#28

Post by gumby »

tmvnty wrote: post #20

I do love browse with Safari from time to time, but it would not take long for me to notice a site's behaviour being "different" because of it. Use hn.algolia.com as an example, on Safari 13.1, the site currently renders differently to Chrome (black background?) and the time range filter (Past Year/Month etc) text are missing...

Is this a bug in WebKit or in the algolia site?

Re: New WebKit Features in Safari 13.1

#29

Post by megous »

tobr wrote: post #21
sunseb wrote: post #5

On a side note, I find crazy this obsessive-compulsive behavior to use `const` everywhere in modern JS codebase (even in Webkit now). It solves really no problem (I mean, Python, Ruby and almost all other programming languages are doing fine without preventing against variable reassignment, and we can still reassign function parameters and object properties in JS). So much brain power wasted on this useless thing. Al…

> So much brain power wasted on this useless thing. I can see the argument that using `const` over `let` doesn’t bring any huge benefits, but I don’t see what the harm is either. I never found it a waste of brainpower. At this point it’s idiomatic, so I think using `let` everywhere is more likely to have people confused.

It's nice until you want to reassign some global variable externally for in-production debugging via a browser console.

Re: New WebKit Features in Safari 13.1

#30

Post by Austin_Conlon »

tmvnty wrote: post #20

I do love browse with Safari from time to time, but it would not take long for me to notice a site's behaviour being "different" because of it. Use hn.algolia.com as an example, on Safari 13.1, the site currently renders differently to Chrome (black background?) and the time range filter (Past Year/Month etc) text are missing...

The hn.algolia.com bug happens to me too when macOS is in Dark Mode.
Post reply on HN