Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
STRML
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
241.
▲
by
STRML
11y ago
This will become easier with rollup, webpack@2, and so on, which can effectively reduce the penalty of including large modules like lodash by tree-shaking out all of the parts you don't use. I would expect many more utility libraries t
242.
▲
by
STRML
11y ago
Just to update you - looks like this has finally been released: https://github.com/npm/npm/releases/tag/v3.8.3
243.
▲
by
STRML
11y ago
That does help a lot and was a long time coming. TS is a little harder to get started with for a few reasons. For one, it simply does more, with features like interfaces (which "sort of" exist in Flow), and public/private acc
244.
▲
by
STRML
11y ago
Try Flow, if you haven't yet. It's not as complete as TS, but it gets out of your way and requires minimal investment. I find that the `(foo: string, bar: number)` annotation style is just far more readable than e.g. JSDoc. You do
245.
▲
by
STRML
11y ago
I completely agree with the sentiment that typed libraries are more stable and self-documenting. You can autogenerate documentation from typescript and it's guaranteed to be up to date, unlike JSDoc comments. I personally have converte
246.
▲
by
STRML
11y ago
Why not date-based version numbers, then, or as bryanlarsen stated, something obviously meaningless, like the Chrome/FF numbers? Edit: By the way, sorry to derail the conversation. You guys are doing great work! I'm always excited
247.
▲
by
STRML
11y ago
This is a nice release. I've always been confused about V8 versioning. Breaking changes appear to come all the time in minor versions. And there's this note from the release: > Note: The version number 5.0 does not carry semant
248.
▲
by
STRML
11y ago
ied is great, and getting better. Unfortunately, as detailed in a few npm3 threads, npm3 performance may forever be quite bad, due to a few ill-conceived features in npm's infancy. Due to shrinkwraps and bundleDependencies, it's i
249.
▲
by
STRML
11y ago
It has not been fixed: I did a series of PRs on this [1] and the most impactful of them was not merged, although a few smaller ones were. @iarna got to the root cause (instead of simply throttling it as I had been doing) but it has not yet
250.
▲
by
STRML
11y ago
It does give me hope. It's happening, and yeah, it's not perfect. But almost nothing in tech is. If we can build the right abstractions to paper over the mess that is the web as a platform, it might be possible for us to easily bu
251.
▲
How the Grinch Stole Array.length Access
(mrale.ph)
2 points
by
STRML
11y ago
|
0 comments
252.
▲
by
STRML
11y ago
Yeah, I had good fun building a Polymer frontend for my weekend project, Secureshare. I got around some of the data binding shortfalls with polymer-signals. It's been probably 2 years since I did it, so I'm sure there are better s
253.
▲
by
STRML
11y ago
This article echoes my experience this year and last, moving from a Backbone app into React + Fluxxor, and eventually into ES6 with Babel + Flow + Webpack. It's a huge pain to configure and understand all this tooling, but man is it ni
254.
▲
by
STRML
11y ago
We do this on securesha.re. Yes, you can't be sure the client hasn't changed the JS - I'm going to start putting md5s in the script tags but it's up to the client to check they haven't changed. However, the client i
255.
▲
by
STRML
11y ago
Nice project, I submitted the form for kicks. Just an FYI, uBlock is killing the chat form on the right. I had to disable it to get the form to show up. I assume this is because of the Olark integration. A nice way to avoid this would be to
256.
▲
by
STRML
11y ago
Just use ConEmu (or get off Windows) if you need a terminal. It's still far more fully-featured than the Console Host will ever be. The stagnation in cmd.exe (and even PowerShell) appears to be a casualty of Microsoft assuming that poi
257.
▲
by
STRML
11y ago
SSH's new AuthenticationMethods directive is extremely useful for pairing SSH keys with a password and/or 2FA. You should absolutely use keys everywhere, and encourage your users to encrypt their keys, but enforcing a password as
258.
▲
by
STRML
11y ago
It's very strange that the original image even shows signs of doctoring (note the two duplicated columns of water). It is so incredibly obvious to see - why were either of them manipulated in this way?
259.
▲
by
STRML
11y ago
See also react-list ( https://github.com/orgsync/react-list ), which does a surprisingly good and hassle-free job of rendering partial lists.
260.
▲
by
STRML
11y ago
I just went through a rather large profiling/optimization run on the my site, BitMEX (we're a Bitcoin derivatives exchange). Performance is paramount in trading, so our site has to be fast. Here's some additional tips: 0. sho
261.
▲
by
STRML
11y ago
After seeing this article, I just migrated from Dinghy to Dlite. I saved about 5GB of disk space, got much faster VM startup time and basically no hassle. It was a cinch to work my docker-compose startup into a LaunchAgent and now I finally
262.
▲
by
STRML
11y ago
> it keeps falling behind on their list because not many people are using it. How can that be true? try/catch is as common a JS idiom as a for loop. This causes significant trouble all over React and many other libraries, as many ho
263.
▲
by
STRML
11y ago
And it (and native modules) do this pretty well via nan ( https://github.com/nodejs/nan ).
264.
▲
by
STRML
11y ago
Thanks for that. I'll give you an example of where it hits hard - Event Emitters. Some of the largest EE libs in the NodeJS ecosystem still munge the arguments object to pass args to listeners. I've sent PRs to some of them, but t
265.
▲
by
STRML
11y ago
This actually happened well before IBM acquired StrongLoop - I first noticed it in February, but it was added in January 2015. The IBM acquisition was announced in September 2015. In their usual fashion they link to internal bug trackers wh
266.
▲
by
STRML
11y ago
Perhaps. I opened it a long time ago, but I've still been trying to keep it alive in the hope that somebody from Strongloop will actually comment on it. In the meantime, if you use a Strongloop package, fork it and remove the optionalD
267.
▲
by
STRML
11y ago
It depends on whether or not it actually delivers a payload. If it does, then it can use a `postinstall` hook to execute absolutely anything it wants, under the context of the user. This is why you should always shrinkwrap and run a private
268.
▲
by
STRML
11y ago
I've been frustrated with their code on a few occasions. We've seen breaking changes in patch versions on strong-remoting, PRs rebased out of patch releases with no explanation (and nobody could figure out why/how), and inten
269.
▲
by
STRML
11y ago
Well, there needs to be some proof of work, something that is hard to do at scale but easy for individuals. To that degree, Bitcoin has failed, because massive SHA256 crunching is now easy to do at scale and hard for individuals. More varie
270.
▲
by
STRML
11y ago
Hey, maybe you're the right person to ask - why does `arguments` so easily deoptimize in every major engine (well, V8 and SpiderMonkey, at least)? It seems that engines could easily detect the most common munging of `arguments` (such a
More ›