Hacker News new | past | comments | ask | show | jobs | submit | johntran's comments login

Not sure why this is being downvoted. Deleting posts via scripts gave my Facebook a second life. I just use it for messenger and events. Highly recommended.


Exactly, and I put a cover picture explaining the situation (it is a closed account blabla), so I didn't receive any judgement from friends. Having removed friends, also means I can not go back in a smooth manner. It is a good way to cut yourself off of facebook's network effect without losing access to events, fb signin, messenger.


If I absolutely wanted to, I could createa second account for that with none of my friends read: um... family, that my first account had on it.


It's most likely easier to brute force a password than to break into someone's house. Would be easier to demand all credentials by gunpoint with that much effort.


That's a fair point, but that's not the only attack vector. I carry my token around on my keys which makes it vulnerable to being pick pocketed or just left behind somewhere. I think the original point was that you're just shifting your single authentication factor, not necessarily making it more secure. My key is only used for 2FA so even if someone were to get access to it, they'd have to know my password as well to get use out of it.


I took Calculus AB in high school and the teacher was notorious for giving students D's and F's because of his teaching style was poor and the exams were difficult. The only saving grace from that class was that you would be given a C if you scored a 4+ on the AP exam.

He still kept his job because majority of the class got 4+'s on those exams, despite at least 1/3 of his class getting D's and F's.

I wouldn't generalize editing letter grades as a way of "cheating the system". There's usually good intentions in every act.


You are a wonderful person. Keep doing you :).


The author misses the point where Facebook was only able to attract talent to their company because of open source. FB currently employs the creators of Babel, Redux, and Inferno; whom otherwise would not be there without OSS to show their talents.


I currently use ImgBot[1] to optimize all my assets in my GitHub repo. Works well.

[1] https://github.com/marketplace/imgbot


@jamesknelson

Also worth mentioning that TS npm download is greater than React consistently.

http://www.npmtrends.com/typescript-vs-react-vs-vue-vs-flow-...

I've used Flow in 2016 and getting it to work on code editors was a huge pain. Coworkers asked me weekly how to fix their environment to get it to work.

In 2017 I introduced TS to the codebase and never looked back. It just works™.


> I've used Flow in 2016 and getting it to work on code editors was a huge pain.

Typescript also has support for js-doc style type declarations, at a basic level, IMHO it's less painful to use than Flow. Does Flow even has a compiler that doesn't rely on OCaml?

https://github.com/Microsoft/TypeScript/wiki/JSDoc-support-i...


Indeed I have seen more and more people adopt TypeScript for all kinds of JS projects.

It is one of the things I have noted to look into next too.


Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems by Martin Kleppmann. Absolute best book on system design.


You're just adding an element to an array infinitely. Of course it'll crash because you'll run out of memory to support the array.

How is this a bug? What's the expected behavior?


I expect every page to have a memory limit similar to the jvm, after which trying to push to the array would result in Error("out of memory")

Perhaps a dialog asking if we want to let the page use more, like the long running script dialog in most browsers.

The sandbox is suppose to protect us from malicious pranks, like browsers these days protect us from an endless loop of alert boxes by asking us if we want to see more, and endless loops in general with the long running terminate dialog.


Personally I'd want something more graceful like halting JS execution on the page and some sort of message...

When I was a teen I rudely tricked a friend to load an infinite alert() page, forcing them to kill their browser and lose some state. These days browsers don't let alerts block switching tabs or closing the offending tab, and with too frequent alerts you can check a box to block any more. It's better.


Chrome doesn't crash, it gives you an error page with the message "Google chrome ran out of memory while trying to display this web page"

IE11 just gives an OOM error in the console.


Expected: Runtime (browser) tries to reallocate the array; requests heap memory from the OS. OS obliges until paging file is full, then warns; browser does something graceful like halting JS on the page. System is slow from disk churning, but nothing crashes.


I mean it probably should not blow up your browser altogether.


https://blog.acolyer.org/2017/09/19/to-type-or-not-to-type-q...

TL;DR: both Flow and TypeScript are pretty good, and conservatively either of them can prevent about 15% of the bugs that end up in committed code.


Thanks for finding the study! And it actually is sponsored by $M no wonder the conclusion is that using a $M product will help catch bugs.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: