Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
nathankleyn
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
31.
▲
by
nathankleyn
11y ago
Edited, that's a mistake - I meant to write "HTTP2 + Web Assembly" (which will take the place of file concatenation and minification).
32.
▲
by
nathankleyn
11y ago
Sorry, that's a mistake - I meant to write "HTTP2 + Web Assembly" (which will take the place of file concatenation and minification).
33.
▲
by
nathankleyn
11y ago
Almost certainly not, if only because it's another layer of indirection when debugging and for this use you're not limited by distribution size. There is a potential benefit if the minifier can apply some performance optimisations
34.
▲
by
nathankleyn
11y ago
You're absolutely right, as indeed pcwalton says above - but it's a step in the right direction from "let anybody have access to anything they feel like".
35.
▲
by
nathankleyn
11y ago
Said add-ons can also access your entire browsing history, listen to you type in your passwords to your online banking account, get access to your emails and hence online identities, and generally know everything there is to know about you
36.
▲
by
nathankleyn
11y ago
Wow, this is a great list. It would be fantastic to take this set visualise their causes. It would be really interesting to see whether the causes are that different for large corporations vs smaller startups. I suspect, as in the article,
37.
▲
by
nathankleyn
11y ago
Really great article, spending your weekend making the animated step-by-step diagrams was worth it! The fact that browsers don't get this stuff right by now is pretty worrying. Makes it difficult to imagine the web being the platform o
38.
▲
by
nathankleyn
11y ago
If anybody ever asks me what Hacker News is, I'm going to screenshot this thread and send it to them.
39.
▲
by
nathankleyn
11y ago
Amusingly, Bitbucket has since removed a lot of their useful fork information after a redesign that took place between now and this article's publish date (2011) [1]. One approach to this problem, as the article mentions, is to list by
40.
▲
by
nathankleyn
11y ago
First thing I do when I get a new laptop is wipe it completely and do a fresh install. You can selectively restore the drivers/software you actually need. Of course it goes without saying that this isn't something most of the mi
41.
▲
by
nathankleyn
11y ago
He probably obfuscated that fact so people wouldn't judge him just by his age; it would seem based on some of the comments in this thread that he was right to do so. Some of the best lessons in life can come from those who haven't
42.
▲
by
nathankleyn
11y ago
I can't overstate how useful it would be to at least restrict write access to certain branches. Bitbucket has had it for a while now [1], so I'm surprised GitHub haven't followed suit. [1]: https://blog.bitbucket.o
43.
▲
by
nathankleyn
11y ago
Yep - that's totally possible. Actually, now you phrase it like that, I see what you mean about using it that way for a CMS, and it's an awesome idea.
44.
▲
by
nathankleyn
11y ago
That's all fine until Googlebot-Image comes along, collects up all your unwatermarked images, and displays them in search results for the world to use. I can see this being useful for running as a batch process in Node/IO.js and u
45.
▲
by
nathankleyn
11y ago
The Haskell wiki has a page called "Haskell in industry" [0] which lists all the people using Haskell in the real-world. Some notable ones include: * Facebook Haxl, an abstraction around remote data access [1] * Microsoft Bond, a
46.
▲
by
nathankleyn
12y ago
Op here! One of the primary reasons for using Redis here is not so we can use Lua (even if it is great!) - it's so that we can generate IDs using a service we already have. This idea could be extended to anything that allows user scrip
47.
▲
Show HN: Distributed ID Generation with Redis and Lua
(engineering.intenthq.com)
12 points
by
nathankleyn
12y ago
|
2 comments
48.
▲
by
nathankleyn
12y ago
I really enjoyed reading what you've written so far, and I'm hoping you continue to write more. It was really refreshing to see somebody write about the struggle to pick up Haskell - indeed, I had a lot of the same issues. I often
49.
▲
by
nathankleyn
12y ago
I cannot upvote this more than once, so I feel obligated to let you know how much I agree with this. "Readability" may be a personal thing, but you'll reach convergence pretty quickly by following the approach you outlined. I
50.
▲
by
nathankleyn
12y ago
I've always felt that it's a fools errand to define things like that. Certainly things like "readability" are completely community/language centric, it would seem. I wonder if this post presents enough focus for res
51.
▲
by
nathankleyn
12y ago
I would have expected better to mean, in this circumstance, less likelihood of there being issues that impact the user - something that almost certainly has a correlation! No amount of "good practice" will protect again an idea be
52.
▲
by
nathankleyn
12y ago
It's on this list as "does well what is intended to do". In fact the article specifically discusses the fact that people, when surveyed, did not mention "it works" as a priority: Works: writing code should always h
53.
▲
by
nathankleyn
12y ago
Good code is written so that is readable, understandable, covered by automated tests, not over complicated and does well what is intended to do. Couldn't agree more.
54.
▲
by
nathankleyn
12y ago
You guys are doing a fantastic job, anything that can give you a bit more of a breather between releases and increase quality is something I'm certain the community will embrace.
55.
▲
by
nathankleyn
12y ago
Looks like the site is getting trampled; here's a Google Cached version for those who want it: http://webcache.googleusercontent.com/search?q=cache:xXcsxR3...
56.
▲
by
nathankleyn
12y ago
Congratulations Mr Nystrom! I've been reading through each chapter as you posted them, and I've found your writing style throughly enjoyable and your ability to describe complex code patterns with ease. It's really hard to ge
57.
▲
by
nathankleyn
13y ago
You'd need to take care of this anyway, since almost any asynchronous action otherwise carries the danger of being dispatched twice if the UI is left active. Most frequently, this is done by disabling submit buttons or debouncing async