gervwyk

48 ms·

241.
by gervwyk 5y ago
Why not have a look at QuickJs. I assume your reason is to run js in the browser in an isolated environment for security reasons? I’ve found this article from figma to be an excellent starting point [0] Also useful to consider this benchmar
242.
by gervwyk 6y ago
Agreed. Writing of this quality is very rare, such a talented author.
243.
by gervwyk 6y ago
Well said.
244.
by gervwyk 6y ago
> Someone else replied that if you have sufficiently advanced build tooling, you can statically extract the SQL/GraphQL from the client side code and replace them with IDs, and then move the SQL to the backend. We’ve taken this app
245.
by gervwyk 6y ago
There is a fascinating episode on Alzheimer treatment using some sort of frequency exposure [0], I don’t know much about this but radiolab made me really excited that there could be an end to Alzheimers one day soon. Studies like this and t
246.
by gervwyk 6y ago
Congrats on building this! Interesting concept. Just looked over the website for a few minutes. The screenshots looks nice, but would be cool to see a few examples. Maybe a longer video that goes through the details. Or a playground with a
247.
Research gives us the problem not the answer(world.hey.com)
1 points by gervwyk 6y ago|0 comments
248.
by gervwyk 6y ago
Same here. Although digging in a bit there is some really cool css tricks in here. Any idea who the developer is?
249.
by gervwyk 6y ago
It’s a great solution. Every class only maps to one css property setting, and they are very well named. Thus not much more difficult to read and remember than css key value pairs. Why would you typecheck component class names? If so, its al
250.
How to actually test web UIs(storybook.js.org)
2 points by gervwyk 6y ago|0 comments
251.
by gervwyk 6y ago
Some really basic apps are making mare than $1500 in Kin per week. Some larger ones more than $100k per week.
252.
Kin coin’s reward engine is paying some apps more than $100k per week(twitter.com)
2 points by gervwyk 6y ago|1 comments
253.
by gervwyk 6y ago
Would be great if the docs was mobile friendly.
254.
by gervwyk 6y ago
This is really scary but hardly surprising!
255.
by gervwyk 6y ago
webflow is great! I’ve implemented it for a non-tech company and will recommend, to the level where some non-tech people could even build parts of the site, and I just had to do the technical finishing. The cms is also super simple. Have al
256.
by gervwyk 6y ago
Well done! Really cool implementation and this first time I considered compiling wasm client side. Quite clever!
257.
by gervwyk 6y ago
Thanks! Glad you love it :) SQL support and inline JS is next on the roadmap, and actually mostly implemented, we're busy documenting and doing more testing. So we are really excited to ship it soon! We also implemented OpenID Connect
258.
by gervwyk 6y ago
Since you are creating all apps in readable YAML format, it is easy to version control or review changes which others has made. This is really helpful when you want less technical members of the team to contribute. Also it seamlessly integr
259.
by gervwyk 6y ago
Hi, We've built Lowdefy [0] for exactly this reason. It it is open-source, low-code and self hosted. On our team we have data analysts and implementation engineers (non-developers) creating apps in Lowdefy. For Lowdefy I would say that
260.
by gervwyk 6y ago
Querybook's journey to open-source. https://medium.com/pinterest-engineering/open-sourcing-query...
261.
Querybook: Big Data IDE from Pinterest now Apache-2.0(github.com)
24 points by gervwyk 6y ago|1 comments
262.
by gervwyk 6y ago
I really enjoyed this! Thanks for sharing!
263.
by gervwyk 6y ago
THIS! I cannot believe that these is still no auto hash validator thing between git and npm. Feels like npm should force a commit containing hash for the current version on every publish or something. How can we make this happen?
264.
by gervwyk 6y ago
I must chime in here. Yarn 2 is a fantastic experience!
265.
by gervwyk 6y ago
That's a funny story. Yes, we also check licenses, security, popularity and maintainers before introducing a dependency. Then of course again track changes for every future release so there is a significant overhead to for every depend
266.
by gervwyk 6y ago
Thanks. Yes, just meant keeping a local copy of the repo from a maintenance / future proof perspective, but obviously still curate next versions before including into build.
267.
by gervwyk 6y ago
Yes. Of course curating dependencies is super important. What I meant by automatically pull future commits is to keep the clone updated. I’m concerned about future maintainability should the main repo be removed from GitHub for whatever rea
268.
Ask HN: Should we clone all production dependancies?
3 points by gervwyk 6y ago|8 comments
269.
Design system component gallery: a repository of interface component examples(component.gallery)
2 points by gervwyk 6y ago|0 comments
270.
by gervwyk 6y ago
Love the concept! Well done!

More ›