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

Comparative unsafety

flak.tedunangst.com

Post reply on HN
Print view View original

11–20 of 99 posts

Re: Comparative unsafety

#11

Post by tyingq »

AndrewDucker wrote: post #5

This has the most toxic UI I've seen in my life. Switching away from my browser and back again causes the page to re-render, losing my place as it did so. Just awful!

Extra maddening, as it works fine with Javascript disabled. Those loading and rendering progress bars are a terrible idea.

Re: Comparative unsafety

#12

Post by howeyc »

Wait, what? I don't know rust, at all, but why is path freed? I thought rust didn't have GC?

> let path = CString::new(filename.as_str()).unwrap().as_ptr();

Is one of those functions calling free behind the scenes?

Re: Comparative unsafety

#13

Post by chriszhang »

AndrewDucker wrote: post #5

This has the most toxic UI I've seen in my life. Switching away from my browser and back again causes the page to re-render, losing my place as it did so. Just awful!

If I try to search something within the page with Ctrl + F that also causes the whole page to re-render and display "loading ..." and "rendering ..." progress bar.

Re: Comparative unsafety

#14

Post by stefan_ »

tyingq wrote: post #11
AndrewDucker wrote: post #5

This has the most toxic UI I've seen in my life. Switching away from my browser and back again causes the page to re-render, losing my place as it did so. Just awful!

Extra maddening, as it works fine with Javascript disabled. Those loading and rendering progress bars are a terrible idea.

Haha, it's true! Disabling JavaScript leaves a perfectly working article. Is this one big troll?

Re: Comparative unsafety

#15

Post by caslon »

tyingq wrote: post #11
AndrewDucker wrote: post #5

This has the most toxic UI I've seen in my life. Switching away from my browser and back again causes the page to re-render, losing my place as it did so. Just awful!

Extra maddening, as it works fine with Javascript disabled. Those loading and rendering progress bars are a terrible idea.

It's a joke. It's not a terrible idea. It's a great idea! A great joke!

Re: Comparative unsafety

#16

Post by tyingq »

nicoburns wrote: post #10
AndrewDucker wrote: post #5

This has the most toxic UI I've seen in my life. Switching away from my browser and back again causes the page to re-render, losing my place as it did so. Just awful!

I'm pretty sure it's an artificial loading screen too. There's no way it actually takes that long to render. It's quite an interesting artistic statement.

Yep.

  window.setTimeout(makeprogress, delay)
With various repeated hard-coded delays of 50, 250, and 500ms.

Re: Comparative unsafety

#17

Post by liminal »

AndrewDucker wrote: post #5

This has the most toxic UI I've seen in my life. Switching away from my browser and back again causes the page to re-render, losing my place as it did so. Just awful!

You can't even search within the page. Ctrl-F hides the content and shows the progress bars.

Re: Comparative unsafety

#18

Post by [deleted] »

howeyc wrote: post #12

Wait, what? I don't know rust, at all, but why is path freed? I thought rust didn't have GC? > let path = CString::new(filename.as_str()).unwrap().as_ptr(); Is one of those functions calling free behind the scenes?

[deleted]

Re: Comparative unsafety

#19

Post by ptomato »

AndrewDucker wrote: post #5

This has the most toxic UI I've seen in my life. Switching away from my browser and back again causes the page to re-render, losing my place as it did so. Just awful!

I'm pretty sure it's explicitly intended solely as punishment for people who have javascript enabled.

Re: Comparative unsafety

#20

Post by brundolf »

> I used it for a while, but generally found it too tiresome.

Worth noting that you can disable individual Clippy warnings instead of the whole thing (per line or for the whole project). I almost always turn off the dead_code warning, especially when I'm iterating

Post reply on HN