migueloller

8 ms·

31.
by migueloller 6y ago
It will give us the opportunity to let developers build their own components, allow us to use frameworks like Next.js to power our users' sites, and let us leverage the ecosystem to build cool components and integrations. So as far as
32.
by migueloller 6y ago
I mistakenly replied to the incorrect thread hah. Sorry for the confusion!
33.
by migueloller 6y ago
Improving performance is something we're actively working on!
34.
by migueloller 6y ago
The promise (and I understand it's something we have to prove) is that extensibility won't lock you down. The most succinct way I can put it is: component composition. We're making a bet on the idea of components as a composa
35.
by migueloller 6y ago
Thanks!
36.
by migueloller 6y ago
Hah, all good. We give them _visual_ control of everything. But say you wanted to make a component that pull the last 10 tweets from an account or a Stripe Checkout button or some other custom component, then you can. Any React component is
37.
by migueloller 6y ago
I'm not sure I understand what you mean. Why would developers have to maintain a website that's not hosted by them? If the issue is maintainability once the website has been extended (i.e., with custom code and integrations), then
38.
by migueloller 6y ago
We're in the early days of Makeswift but extensibility is a big part of our vision. The way we've built the core technology of our product is such that every component used in the builder is just a React component (and could be a
39.
by migueloller 6y ago
Of course! You can find my contact info in my HN profile. Feel free to reach out and I'll get you one :)
40.
by migueloller 6y ago
Internationalization is definitely a big one. It's a hard thing to do right for a website builder designed for non-technical people, though. That being said, I'm proud to currently have customers that have built sites in over 5 di
41.
by migueloller 6y ago
> -Output accessibility (eg for blind users) This is something that's in our roadmap. Makeswift components are just React components and as only developers of those components at the moment we plan to follow accessibility best pract
42.
by migueloller 6y ago
I agree that there's a clear difference between the two. Makeswift sites aren't just a "presentation", though. They're hybrid (server-side rendered on first load and client-side rendered after) React apps. And becau
43.
by migueloller 6y ago
Hah! Nice catch there :) This is actually not part of the core Makeswift code, but a custom snippet we added to this blog post to tweak the navigation. It sets a class on scroll, which is why you saw so many errors in the console. I just fi
44.
by migueloller 6y ago
You could say Webflow is a direct competitor, yes. The way we see it, though, Webflow is a tad too complex for non-technical users and you end up just shifting the bottleneck from developers to the "Webflow expert". Heck, they hav
45.
by migueloller 6y ago
Yeah, you can't do that right now. But we do have plans to support self-hosting. We believe it will be table stakes for various customers. We're a small team of 5 right now, though, and decided to focus on the core experience righ
46.
by migueloller 6y ago
Heh ;)
47.
by migueloller 6y ago
You're totally right, this is critical. If you want to check out how we do responsive design, you can do so here [1]. We're constantly iterating on the product so some of the UX and visuals in the videos might be outdated, but the
48.
by migueloller 6y ago
We do all hosting ourselves at the moment. As for trying it out, we're currently in early access and you'll need an invite code to use it but if you apply [1], you'll get one in your inbox pretty quickly. And thanks! [1] htt
49.
by migueloller 6y ago
I don't think you're being absolutist or cranky at all. I think there's valid reasons why you would want to export your site. I guess the reason we call ourselves a "website builder" is because Makeswift lets you bu
50.
by migueloller 6y ago
Hey guys, I'm super excited about early access so that we can gather as much feedback as possible. We made a nifty handbook [1] a while back to show the basics of building a page in Makeswift. Would love to hear what you think! [1] ht
51.
by migueloller 6y ago
It's very interesting to see how their benchmarks [1] progress over time. I would love to see a comparison with the alternatives. Perhaps that could show some of the benefits of writing this in Rust. For another JavaScript parser, but
52.
So you want to live-reload Rust(fasterthanli.me)
4 points by migueloller 6y ago|1 comments
53.
by migueloller 6y ago
I like doing `Math.max(min, Math.min(num, max))` since it puts them in sort order.
54.
by migueloller 6y ago
Thanks for the response!
55.
by migueloller 6y ago
Would you be willing to expand on why using strings for file paths turns out to be unworkable? Very curious what the obscure reasons are!
56.
by migueloller 6y ago
I recently shared a thread [1] on Twitter with CRDT resources I found useful if you’re interested in that kind of thing. [1] https://twitter.com/ollermi/status/1279067350269124609?s=21
57.
by migueloller 6y ago
I've found this [1] screencast on the low-level principles of async in Python an amazing resource to understand async at a deep level. [1] https://www.youtube.com/watch?v=Y4Gt3Xjd7G8&list=PLKLmIMXskJ...
58.
by migueloller 6y ago
Building an 8-bit computer from scratch [1]. Planning on building a quadruped [2] after. [1] https://eater.net/8bit [2] https://spotmicroai.readthedocs.io/en/latest/
59.
by migueloller 6y ago
Is there so little to report that taking the average growth of his wealth for the last 5 years and extrapolating for the next 5 is worthy news? This is an absolutely worthless prediction. How can this be journalism?
60.
Visualizing quaternions – An explorable video series(eater.net)
1 points by migueloller 6y ago|0 comments

More ›