Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jeremychone
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
21 ms
·
61.
▲
by
jeremychone
6y ago
I thought they rejected them because electron used private apis. Is that resolved?
62.
▲
by
jeremychone
6y ago
Looks interesting but difficult to get the details from just the slides. Also, not sure why Azure Arc still gets mentioned. I would have expected something more cloud independent. Our approach, for now, is to use Kubernetes Postgres for dev
63.
▲
by
jeremychone
6y ago
My guess, and I hope I am wrong, is that it might be a world of pain for backend/cloud developers. Virtualization gives us Linux ARM docker images, which is nice, but not the same as running the same Linux docker images that run on the
64.
▲
Show HN: Redis Stream API for TypeScript/Node.js (Ioredis Backed)
(github.com)
2 points
by
jeremychone
7y ago
|
0 comments
65.
▲
by
jeremychone
7y ago
First, the use of 'innerHTML' is just for the sake of examples and mvdom does not promote one way or another. Now on the broader discussion between innerHTML vs appendChild (with or without DocumentFragment). There is no real secu
66.
▲
Show HN: mvdom 0.9 – scalable HTML Native MVC library – 5kb – Real DOM is back
(github.com)
2 points
by
jeremychone
7y ago
|
2 comments
67.
▲
Understanding Kubernetes’ Value – From Virtual Hosts to Kubernetes
(blog.britesnow.com)
3 points
by
jeremychone
8y ago
|
0 comments
68.
▲
by
jeremychone
8y ago
First, no language is perfect, and building a real system with growing team(s) is always about making purity vs pragmatism tradeoffs with the main goal of keeping the complexity down as the system scale. The truth is that a system is much m
69.
▲
by
jeremychone
8y ago
Sure, there is always some difference in opinions even within the same organization. However, I do not think it is what killed Dart. It would have been a clear winner with clear traction, people will have changed their mind and adopted it (
70.
▲
by
jeremychone
8y ago
Good one. Developers really need to understand Structural vs Nominal typing before saying TypeScript is less type-safe than Java.
71.
▲
by
jeremychone
8y ago
Not sure one gives you safer typing than the other in absolute. They both have a different context/purpose. TypeScript is great for typing a code base for function calls type of APIs, whereas GraphQL is great to express types for inter
72.
▲
by
jeremychone
8y ago
Not sure TypeScript and GraphQL are mutually exclusive.
73.
▲
by
jeremychone
8y ago
Not really. TypeScript is just a JavaScript superset, and developer code JS with all its good and bad with some annotation types. TypeScript is not like Dart or reasonML for which your analogy would have been correct if someone said Dart co
74.
▲
by
jeremychone
8y ago
Pretty good resource categorization.
75.
▲
by
jeremychone
8y ago
TypeScript is a structural typing model vs nominal one, such as Java, which we are more used to. Not that one is more sound than the other, just different approaches. I actually like the structural system a lot, and found that combined type
76.
▲
by
jeremychone
8y ago
Wow, this is great. Yes, we need a “tensorflowjs” (with TypeScript types) for Torch, and this seems to be a great start to show the way.
77.
▲
by
jeremychone
8y ago
yes, there is a learning curve, but once you have your system in place (for local Kuberenetes Development as well as deployment), then, even of a web-sites, it is a breeze. But yes, still need to be organized.
78.
▲
by
jeremychone
8y ago
Thanks, appreciate the answer.
79.
▲
Ask HN: Anybody moved from ReactJS to VueJS, and why?
4 points
by
jeremychone
8y ago
|
0 comments
80.
▲
by
jeremychone
8y ago
> new coffeescript combined with the verbosity of J2EE - Saying that TypeScript is like CoffeeScript is almost equivalent than saying that CoffeeScript is like Babel. - The only part that CoffeeScript and TS (and Babel) have in common is
81.
▲
Ask HN: Who moved from Angular to React and why?
2 points
by
jeremychone
8y ago
|
4 comments
82.
▲
by
jeremychone
8y ago
I would say definitely yes, good one to learn, and smart bet (and we have avoided lot of hype languages like coffescript, dart, ...). 1. TypeScript is just a modern expressive strutural typing system on top of JavaScript, not a full new lan
83.
▲
by
jeremychone
8y ago
TypeScript is a structural typing system, vs the normal nominal one we are used to. Now, I agree that even with this difference, still not a strong typing as it could be, however, get pretty close to it (with all of the added expressiveness
84.
▲
by
jeremychone
8y ago
One solution would be to have your own service (bound to a public IP) and point a nginx pod doing the routing. You might be able to use an ingress type nginx, which might be a even better way to handle this. (not sure, because I always use
85.
▲
by
jeremychone
8y ago
Agree about the silliness of some npm modules, however, after 20 years of building enterprise application in Java, I find NodeJS / npm / TypeScript refreshing and a surprisingly robust platform to develop serious backend services.
86.
▲
Top 7 Node.js/TypeScript Tips for scalable back end development
1 points
by
jeremychone
8y ago
|
0 comments
87.
▲
Ported a Web back-end service from Java to NodeJS/Typescript: 40% less code,...
4 points
by
jeremychone
8y ago
|
0 comments
88.
▲
by
jeremychone
8y ago
Honestly, DI is really a thing of the OO-Obsessed world when everything has to be a class and instantiated. In the JS/TS world, we mostly use Interface/Type to describe constraints, and most of the module export function or group
89.
▲
by
jeremychone
8y ago
I just looked at flow briefly, but for what I can see, TS is a much more advanced typing system, the tool support is amazing (VSCode for example), and most libs today are TypeScript typed one way or another. The later is probably the one as
90.
▲
by
jeremychone
8y ago
I would add 1) Starts with `strict: true` 2) Favor interface over class 3) Functional first, OO as needed 4) Avoid Java way of coding, DI, Class for everything.
More ›