Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
minitech
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
55 ms
·
631.
▲
by
minitech
9y ago
No, it’s not like that at all. Firefox’s performance, memory usage, and UI all far outstrip Chrome’s in my browsing now; I don’t see any reason to use Chrome apart from the usual cross-browser testing, and it’s been that way for a year (?)
632.
▲
by
minitech
9y ago
> Where desktop apps have exploit categories like “double free”, “stack smash”, “use after free” etc, web apps fix those but then re-introduce their own very similar mistakes: SQL injection, XSS, XSRF, header injection, MIME confusion, a
633.
▲
by
minitech
9y ago
With async (it’s just monads!): listOfPromises.reduce( async (m, n) => await m + await n, 0, )
634.
▲
by
minitech
9y ago
> just like HTML and CSS And yet if you browse this website with CSS also disabled, you get to enjoy the content without the pointless, distracting, time-consuming, and resource-wasting full-page second loading indicator (the browser alr
635.
▲
by
minitech
9y ago
Short version: Brad Wardell notices article about Brad Wardell shows up inexplicably in search results for “Brad Wardell”. Innocent enough on its own, right? Wrong. The author also links to a Daily Caller article about… the same search res
636.
▲
by
minitech
9y ago
If they were “point seekers”, they would have answered the questions (an action that gives points) instead of closing them (an action that gives no points). I somehow doubt the votes were incorrect, though.
637.
▲
by
minitech
9y ago
This is exactly the opposite of what I experience; Chrome eats up 6GB of memory with a couple dozen tabs open, but I can have as many and more active in Firefox on 2GB (and over 1000 tabs open but inactive – leftovers from when tab groups w
638.
▲
by
minitech
9y ago
Requesting a new certificate per user is another step that can go wrong, and contacting LE for limit increases is a barrier.
639.
▲
by
minitech
9y ago
> Then maybe the burden of proof is on you? I’m saying that the parent doesn’t prove its point, and I’m not attempting to prove its parent’s point. > If you started your career recently, it's easy to be caught up into this &quo
640.
▲
by
minitech
9y ago
> Dynamically typed languages for large code bases are terrible was the original argument. Success/failure of entire companies has somehow been brought into it.
641.
▲
by
minitech
9y ago
I’m saying that dynamically-typed programming languages are the best choice right now, but that it’s not because they’re dynamically-typed; existing fare for statically-typed languages is just worse. Probably should have clarified that ea
642.
▲
by
minitech
9y ago
It might say something that the creator of Python is working at Dropbox and currently on a project to add static typing to it… ( https://github.com/python/mypy/commits/master because I know the pain of linkles
643.
▲
by
minitech
9y ago
> You think the otherwise smart and successful founders of these projects all made the wrong choice when it came to selecting the right tool for the job? Not at all! I think dynamic typing hurts code, but there are: - not always alternat
644.
▲
by
minitech
9y ago
You mean sources for languages used in the implementation of various websites? - Wikipedia is mostly PHP https://github.com/wikimedia/mediawiki - Wordpress is PHP https://github.com/WordPress/WordP
645.
▲
by
minitech
9y ago
> seem to prove otherwise Prove how? They could have succeeded in spite of dynamic typing, not because of it. Facebook defined a new programming language to add static typing to HHVM. The process of plugging into WordPress is infamous in
646.
▲
by
minitech
9y ago
No. Does the parent comment imply that somehow? (Did the reply end up on the wrong comment?)
647.
▲
by
minitech
9y ago
What? If there’s a question there, could you ask it in a straightforward manner, please?
648.
▲
by
minitech
9y ago
Piling a bunch of redundant libraries on top of each other, becoming confused, and drawing the conclusion that functional programming was the problem? Okay.
649.
▲
by
minitech
9y ago
> Anybody can write crappy, bug-ridden and insecure code. In any language. Good news: with C, it's even easier! So familiarise yourself with common (and common-sense) pitfalls noted in the SEI CERT C coding standard and comp.lang.c
650.
▲
by
minitech
9y ago
The important part of Python 3 is the bytes/str/unicode rework, and there’s no way to make that not a breaking change. Everything else is minor stuff that’s allowed to be breaking because the str change already broke backwards com
651.
▲
by
minitech
9y ago
> for professional development, everything I do in Python is done in Python 2.x. That is not a theoretical argument, that is fact. And everything I do professionally in Python is done in 3.x as of this January. Also fact! Industry standa
652.
▲
by
minitech
9y ago
That’s a giant can of worms. One example problem: Python 2 has a type of class (old-style) that doesn’t exist in Python 3. What happens when you try to pass this type of class or one of its instances between the languages? There’s a bunch o
653.
▲
by
minitech
9y ago
There might be a workaround, but I think the common practice is to just avoid the problem with environment variables or by reading values from stdin.
654.
▲
by
minitech
9y ago
That’s unsafe even for scripts; unprivileged processes can, by default, read the argv of any other process. (Try `sudo -u nobody cat /proc/$(pgrep -n kbsecret)/cmdline`.)
655.
▲
by
minitech
9y ago
Mmm… no, I didn’t want to. Why do you say that?
656.
▲
by
minitech
9y ago
That’s not something that should be handled inside an async function (and therefore not in this example). If you don’t want to continue a promise chain, terminate it: .catch(error => { process.nextTick(() => { throw error; });
657.
▲
by
minitech
9y ago
Have you ever tried to run more than one operation at once and collect the results? (There are lots of other reasons to use the promise abstraction – having a type that can be transformed is extremely useful and natural – but that one’s pre
658.
▲
by
minitech
9y ago
One of the nice things is that you can just let async functions fail and they won’t throw asynchronously and kill the process. So no, error handling isn’t important to include in a small example.
659.
▲
by
minitech
9y ago
> Though couldn't you have it easier by making sure your top-level JSON structure is always an object? Yes, this works too. You’re correct about any keys causing a syntax error.
660.
▲
by
minitech
9y ago
> one crazy workaround because of the weirdness of modern jazz development Autocorrect of “JS”? If so: it’s not a modern weirdness; this is an old, long-fixed browser bug. FWIW, JavaScript continues executing after errors in cases where
More ›