nichochar

10 ms·

61.
by nichochar 2y ago
They're both notebooks for TypeScript, but Observable is highly specialized in data visualizations (graphs, plots, etc...) and runs in the browser. Srcbook is built for different use cases: we focus on a backend runtime (node) and want
62.
by nichochar 2y ago
The plan is to have a cloud offering which runs Srcbooks as infrastructure. There are a couple of directions are considering, but essentially they boil down to helping you build an app quickly and iteratively, then serve it in production. T
63.
by nichochar 2y ago
This is on our roadmap, yes. We focused on node first because we thought that was missing (you can always spin up a devserver for component), but we'd like to introduce a browser cell which would allow you to add HTMl / JSX compon
64.
by nichochar 2y ago
Hey @mlejva, we have mostly been using this internally so far. Some of the coolest use cases are asking it to straight up teach us about something: "I want to learn about Y.js and CRDTs", or "What is a good implementation of
65.
Show HN: Srcbook – A TypeScript notebook for rapid prototyping(github.com)
267 points by nichochar 2y ago|50 comments
66.
by nichochar 2y ago
I like the 2 examples. Tailwind has multiple traits that make it a winner, and I think that "never naming anything" is a secret super-power it has. You don't realize it, but it just makes coding easier over time. Compare to s
67.
by nichochar 2y ago
I'm a little confused why you have to specify "strict: true" to get this behavior. It is obviously always desired, I would be surprised for people to ever specify "strict: false". That API design leaves to be desire
68.
by nichochar 2y ago
Totally. I wrote about this when they announced their dev-day stuff. In my opinion, they've found that intelligence with current architecture is actually an S-curve and not an exponential, so trying to make progress in other directions
69.
by nichochar 2y ago
We are building one right now. It's very early and we have only "soft launched", but you can check it out here. https://github.com/srcbookdev/srcbook
70.
Verifying Slack Requests with Phoenix(benreinhart.com)
2 points by nichochar 2y ago|0 comments
71.
by nichochar 3y ago
I predicted that if I made the front page of HN someone might be a little toxic about me!
72.
by nichochar 3y ago
Fixed, flex and z-index issue on my part, sorry
73.
by nichochar 3y ago
Hi, author here. This is a pretty hard problem. And I haven't found anyone that's too good at this, but here are some interesting players: - https://www.phind.com/ is a custom model fine-tuned on code, and pretty
74.
My 2024 AI Predictions(axflow.dev)
54 points by nichochar 3y ago|34 comments
75.
Show HN: Zero-dependency, TypeScript SDK for building robust NLP applications(docs.axflow.dev)
16 points by nichochar 3y ago|2 comments
76.
A guided, interactive tutorial of Retrieval Augmented Generation with LLMs(demo.axilla.io)
7 points by nichochar 3y ago|0 comments
77.
by nichochar 3y ago
Thanks for the feedback! The lesson that we learned at Cruise is that the tough thing when shipping AI software is closing the data loop and integrating all of the steps of the ML lifecycle together, so if you only look at the RAG workflow,
78.
by nichochar 3y ago
Glad to hear this, indeed we think there's opportunity for some more cutting edge tooling in the TS ecosystem. We absolutely want to add a caching layer. Actually, we think middleware is where a lot of the value of the framework will c
79.
by nichochar 3y ago
We're very open to contributions, I am interested in what the integration would look like. Do you want to email me at nicholas@axilla.io? we can get into the details.
80.
Show HN: Axilla – Open-source TypeScript framework for LLM apps(github.com)
161 points by nichochar 3y ago|40 comments
81.
by nichochar 3y ago
https://bytesizetheories.com My favorite article is around tech debt (I break it into 3 categories as a mental framework): https://bytesizetheories.com/posts/3-kinds-of-tech-debt/
82.
by nichochar 3y ago
Seems cool but i wish they had an auto-formatter. After years of coding, I have found that taking away the opinionated-ness and doing a format-on-save (ideally, that's supported by the language like Golang) is by far the most productiv
83.
Documentation Driven Development(gist.github.com)
1 points by nichochar 4y ago|1 comments
84.
Google Docs releases syntax highlighted code blocks(twitter.com)
22 points by nichochar 4y ago|2 comments
85.
by nichochar 4y ago
Hugo + nginx is ridiculously easy and good. I host https://bytesizetheories.com on there and it's been an absolute breeze.
86.
by nichochar 4y ago
Only solution is to regulate the companies. Musk is using his army of cultish followers to do QA with other people's lives. In my opinion this should be highly illegal, and prosecuted. Imagine your kid gets killed by a Tesla influencer
87.
by nichochar 4y ago
HN will hate this, but I was curious about web3/crypto and wanted to build something to understand how it all worked. This was inspired by moxie's post [1] (don't echo other people's opinion because you see them repeated
88.
by nichochar 4y ago
Moving to America from France, one of my biggest surprises was how poor the average engineer (person really, but engineers affect me directly at work) is at summarizing concepts clearly. I learned a little later that "summary" exe
89.
by nichochar 4y ago
[Disclaimer] I worked for Cruise for 4 years. I agree with everything you said, but chuckled at this particular part (which is very wrong): > Tesla is significantly ahead of everyone else. Everyone in the industry knows that Tesla is now
90.
by nichochar 4y ago
Check out graphite. Been LOVING it. Team is awesome and product is evolving fast.

More ›