Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
MatthewPhillips
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
DoneJS 3
(bitovi.com)
11 points
by
MatthewPhillips
8y ago
|
0 comments
62.
▲
by
MatthewPhillips
8y ago
Don't attempt to build a SPA if you are support browsers that old (even IE8 imo). Give them a traditional server-rendered app and they'll be happy. Since you've already built with React, the good news is that it's easy t
63.
▲
by
MatthewPhillips
8y ago
That depends on the provider and the database. For AWS Lambda with DynamoDB connection pooling is handled "behind the scenes", and you don't have to worry about it. AWS supports SQL databases as well, I would assume it also i
64.
▲
by
MatthewPhillips
8y ago
Without knowing the specifics of this project, more than likely they do not attempt to solve the problem you describe. Simply don't make changes to the real DOM, or use 2 workers on the same subset of actual DOM. Each worker owns its o
65.
▲
by
MatthewPhillips
8y ago
I worked on a similar project a few years ago: https://github.com/canjs/worker-render . It could render jQuery apps in a web worker, it was pretty neat. The problems I ran into, and I suspect this project will run into
66.
▲
by
MatthewPhillips
8y ago
Images and videos are less important though.
67.
▲
by
MatthewPhillips
8y ago
I'm not a React dev, but both approaches seem like they would make testing harder. Prop drilling must be the most testable approach. Am I wrong?
68.
▲
StealJS 2.0 Released
(bitovi.com)
7 points
by
MatthewPhillips
8y ago
|
0 comments
69.
▲
by
MatthewPhillips
8y ago
I don't know where you get that it can't be fast, that's certainly not true. Gambit Scheme is just one example of a fast lisp. People like lisps because they are written as ASTs. So you can manipulate programs (ASTs) to creat
70.
▲
by
MatthewPhillips
8y ago
That's great, but 1.3mb as a baseline is just too big for most common DOM manipulation type of use cases. You want your UI drawn within a couple of seconds or the experience becomes bad. Even if they were able to cut it in half I'
71.
▲
by
MatthewPhillips
8y ago
You know something has to perform low level DOM operations, right?
72.
▲
by
MatthewPhillips
8y ago
Criticizing a language that just got wasm support last week for not having mature high level solutions yet is a bit ridiculous.
73.
▲
by
MatthewPhillips
8y ago
Great article! I attempted something very similar and wrote about it here: https://matthewphillips.info/programming/wasm-golang-ce.html Like the author I'm pretty enthusiastic about using Go for web development. T
74.
▲
by
MatthewPhillips
8y ago
Yeah, this is a UI bug in devtools for a feature not a lot of people use. Plus web worker bugs always get pushed to the bottom of the queue for every browser. So I don't have any problem with how long my weird issues take to get fixed.
75.
▲
by
MatthewPhillips
8y ago
Like I said, my impression is that often the people replying are not engineers. Here's one with that problem: https://bugs.chromium.org/p/chromium/issues/detail?id=674096...
76.
▲
by
MatthewPhillips
8y ago
I can echo his experience reporting browser bugs and provide my own reviews: Firefox - By far the best. Quick response, usually from engineers. If it's important the fix will be quick. Edge - No reply for months / years. When I&#x
77.
▲
Creating Web Components in Go and Wasm
(matthewphillips.info)
1 points
by
MatthewPhillips
8y ago
|
0 comments
78.
▲
Improved Error Handling in DoneJS
(bitovi.com)
5 points
by
MatthewPhillips
9y ago
|
0 comments
79.
▲
Building Multi-Use Web Workers
(matthewphillips.info)
2 points
by
MatthewPhillips
9y ago
|
0 comments
80.
▲
DoneJS 2.0 Released
(bitovi.com)
4 points
by
MatthewPhillips
9y ago
|
0 comments
81.
▲
by
MatthewPhillips
9y ago
Hi Matt! First congratulations. This is a very interesting project, one that I look forward to trying out. I'm wondering if Promises are the right way to compile goroutines though. Promises don't run in parallel, and they actually
82.
▲
by
MatthewPhillips
9y ago
Of course, you can stream parts of your page that you don't use React. That should be obvious. :)
83.
▲
by
MatthewPhillips
9y ago
Note that React doesn't do streaming HTML in the traditional sense. You can't send out initial HTML while you wait on an API response, for example. Instead only the serializer is streaming. Your app renders to a VNode synchronousl
84.
▲
by
MatthewPhillips
9y ago
Note that you don't actually need the head or body tags in your page. The browser already knows what is allowed in the head. It looks weird at first, but you can write your html like so: <!doctype html> <html lang="
85.
▲
by
MatthewPhillips
9y ago
If rendering blocks the CPU to such a degree that this helps get bytes out faster, then you have a much bigger issue to deal with.
86.
▲
by
MatthewPhillips
9y ago
Just for clarification, React 16 does not support streaming, at least not in any way that is meaningful. React 16 has an API that gives you a Readable stream, but this stream doesn't provide HTML in chunks. It provides it all-at-once
87.
▲
Why you should Never EVER EVER copy paste and execute someone else's code
(github.com)
4 points
by
MatthewPhillips
9y ago
|
0 comments
88.
▲
by
MatthewPhillips
10y ago
Thanks, this explanation is very helpful. One last question, when you say: > Because this is just an integer comparison, it's very very fast on modern JavaScript VMs, even if you have lots of data on screen. I don't follow, wha
89.
▲
by
MatthewPhillips
10y ago
Thinking about it a bit more I think might know what is going on here. In a traditional KVO view layer (I've worked on a couple of these myself, so my thoughts here are biased) when a property changes it triggers an event. The view l
90.
▲
by
MatthewPhillips
10y ago
I love technical articles about how libraries are built. This is really great! I don't follow the last part of the article though. Specifically this part: > We accomplish this by (under the hood) allowing every bit of data that goes
More ›