Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
robpalmer
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
robpalmer
6y ago
There isn't much of a difference between regular enum and const enum when it comes to the usage of the enum keyword. The big difference is what they compile to - where const enum evaporates by inlining the values into the usage sites.
32.
▲
by
robpalmer
6y ago
Whilst TS does technically contain breaks, these are normally simple increases in the power of the type-checking. It's finding more errors in code that previous seemed fine. Think of it like adding more ESlint rules. It's rare f
33.
▲
by
robpalmer
6y ago
What about VS Code?
34.
▲
by
robpalmer
6y ago
That's an excellent suggestion! It's true you could just have every package publish the raw TypeScript source-code. So that when an app imports a library, it type-checks against the original source code of the library. No need f
35.
▲
by
robpalmer
6y ago
It's more about setting up the guard-rails ahead-of-time to avoid falling into a hole, rather than getting out of one. We know the way to do this is to stick to standards like ECMAScript. ES Modules are the glue that binds the whole J
36.
▲
by
robpalmer
6y ago
The TypeScript ecosystem is amazing - partly because of the large number of users also also because of the sense of community. It is run as a true OSS project. Roadmaps are release plans are all public on GitHub. Even as outsiders we
37.
▲
by
robpalmer
6y ago
Agreed. The article touches on this. When you have hundreds of projects that all target the same tightly-managed evergreen runtime, there's not much justification for having each project select and maintain a different toolchain. It
38.
▲
by
robpalmer
6y ago
Yes - you deduced correctly! There was a long period of parallel evolution. Over the last few years we've been able to get back on the standards track. The article describes this as one of the guiding principles. It's why we pa
39.
▲
Insights from Adopting TypeScript at Scale
(techatbloomberg.com)
180 points
by
robpalmer
6y ago
|
105 comments
40.
▲
by
robpalmer
6y ago
What other numeric types would you like to see? In addition to the existing doubles, ES2020 added support for signed integers.
41.
▲
by
robpalmer
7y ago
A new proposal for adding arbitrary-precision Decimal support to JavaScript is being presented at TC39 this week. Proposal: https://github.com/littledan/proposal-bigdecimal Slides: https://docs.google.com&#x
42.
▲
by
robpalmer
8y ago
Yeah, you see them all really easily here: https://anvaka.github.io/pm/#/galaxy/npm?cx=-1345&cy=-7006&c...
43.
▲
by
robpalmer
8y ago
That book is one of the most useful engineering books I have ever read. Top quality theory with practical application.
44.
▲
by
robpalmer
9y ago
Rollup's strength is its simplicity and focus. It splits a fine-grained module graph into coarse-grained vanilla ES modules with zero duplication across fragments and no artificial overheads, e.g. no wrapping internal modules inside fu
45.
▲
by
robpalmer
9y ago
I met Art, the Sencha CEO, back in 2013 after having some positive experiences using Sencha Touch on iOS to develop consumer-facing apps. He said that the company was going to solely focus on Enterprise because that's what the investor
46.
▲
by
robpalmer
9y ago
Agreed. ES6 class syntax is superior to constructor functions and prototype mutation, because it's declarative and statically analysable. I think the only legitimate reason left not to use ES6 class syntax is (for perf sensitive code)
47.
▲
by
robpalmer
9y ago
A codebase with no objects... I am guessing you mean no classes.
48.
▲
by
robpalmer
10y ago
So the argument is that the bad-effects of top-level await are viral. One bad apple in the app entry point's dependency graph stalls evaluation of the main entry point. And to mitigate this risk, you have to segregate out sub-graphs