hasanhaja

6 ms·

1.
by hasanhaja 2mo ago
In a similar vein, I've been really enjoying the Go + Datastar combo with Templ.
2.
by hasanhaja 6mo ago
> even more secure Based on what? Happy to be wrong, but the quote in my reply was Apple's stance on the WebKit vs native iOS apps
3.
The Tyranny of What If It Changes(chriskiehl.com)
1 points by hasanhaja 6mo ago|0 comments
4.
by hasanhaja 6mo ago
How did you determine the weighting for your scores?
5.
by hasanhaja 6mo ago
If it's about security and privacy, why push more people away from the Web to native apps that they know is less secure [1][2]? > WebKit’s sandbox profile on iOS is orders of magnitude more stringent than the sandbox for native iOS
6.
by hasanhaja 6mo ago
The problem is that it has to use the WebKit rendering engine, and not that it happens to. I think it's more insulting to browser vendors that they have to throw away their browser engines to appease the monopolistic tendencies of on
7.
by hasanhaja 6mo ago
They don't need to implement it though. They just need to unban browser vendors from shipping their own engines.
8.
by hasanhaja 6mo ago
I don't think it does benefit the open web. If consumers can't get value from the web, they'll go where they can find it. That is currently native apps, which is a closed and proprietary ecosystem. This causes the market itse
9.
by hasanhaja 6mo ago
I think malicious compliance is a fair interpretation of the situation: https://open-web-advocacy.org/blog/apples-browser-engine-ban...
10.
by hasanhaja 9mo ago
It's hard to understand the privilege bubble you're in unless you actively try to live like your users. My read of the current trend [1] is that building for your marginal users isn't prioritized culturally in orgs or within
11.
Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025(chrisebert.net)
127 points by hasanhaja 10mo ago|56 comments
12.
by hasanhaja 10mo ago
Thank you so much for the write up! I've been avoiding processes for some reason while I've been learning Elixir and this post pushed me to play with it today. And I started in Erlang and then managed to translate it to Elixir suc
13.
by hasanhaja 11mo ago
Maybe the versioning should be powers of 2
14.
by hasanhaja 11mo ago
Why have a call-to-action to something they don't want you to do? It's only there for Pro users and people who want to support the project [1] and not normal use. [1] https://data-star.dev/essays/greedy_develo
15.
by hasanhaja 11mo ago
Use the Navigator API directly then? Why do _need_ a declarative version of it?
16.
by hasanhaja 11mo ago
I'm confused. Datastar is a free open source framework that you can choose to use or not. It's weird to call them out as indecent and deceitful for not actively marketing features that they really don't think you need. Even w
17.
by hasanhaja 11mo ago
If an enterprise won't want to pay for the product, what makes you think they're more likely pay for support? If you're implying they'll only pay when they've seen the value of the product, then the non-pro part of
18.
by hasanhaja 11mo ago
This feels incredibly unfair and harsh and is completely unfounded. What's the scam here?
19.
by hasanhaja 11mo ago
Fair enough! That's up to you If the core of the framework fits what you need, you could write those additional plugins yourself, rather than relying on the official "pro" ones. My understanding so far is the plugin architect
20.
by hasanhaja 11mo ago
> They aren't. This is not good API design Why isn't it a good API design? > Snide vaguely dismissive remarks don't make such remarks true. Agreed! I don't believe I was doing anything of the sort. > Who's
21.
by hasanhaja 11mo ago
Which feature are you referring to?
22.
by hasanhaja 11mo ago
I can see what you're saying. But again, the API design woes are subjective and I think it's perfectly fine to iterate on getting this to a nicer state. "Wrong" to me suggests a gap in the understanding of fundamentals o
23.
by hasanhaja 11mo ago
Simple features? Making those imperative APIs declarative is not very simple for me, but you're welcome to not use those features and write them yourself. A couple of things on the Phoenix point: - Requires the adoption of Elixir and D
24.
by hasanhaja 11mo ago
I don't think that's a fair read of their intentions given how they talk about it everywhere [1]. Pro isn't there to paywall great features, but there to support the development of complex and annoying ones. The example of `d
25.
by hasanhaja 11mo ago
Isn't that the whole point of hypermedia frameworks like Datastar and HTMX? It's to extend the declarativeness of HTML. If you don't like the syntax, that's your preference. But I'm curious to hear why this is &quot
26.
by hasanhaja 11mo ago
The type-safety concern would be to do with your templating tool, right? It doesn't have anything to do with Datastar
27.
by hasanhaja 11mo ago
What's your concern with the paid features? https://news.ycombinator.com/item?id=45537335
28.
by hasanhaja 11mo ago
Wanted to include that this is so the development and maintenance of Datastar as a project is sustainable. And that they are a registered 501(c)(3) nonprofit organization. https://data-star.dev/star_federation#nonprofit-orga
29.
by hasanhaja 1y ago
I've been having fun exploring this actually: https://news.ycombinator.com/item?id=45333494 I've found it to be a fun way to build apps.
30.
by hasanhaja 1y ago
I've only started playing with local first recently to learn the Service Worker API and IndexedDB, and I'm looking forward to learning about CRDTs more. Here's a little todo app that I built: [1] GitHub: https://gi

More ›