Doesn't seem to work for me, always shows the same
161 karma · joined March 19, 2026
Streaming services have become the worst of all worlds.
As an EU citizen, even tho I pay for Netflix and Prime, I cannot access most of the content there as even tho it exists on the service because it's not available in my country.
Amazon prime has 2 good shows and just a bunch of D-tier movies or some 35+ year old ones. It's mostly worthless.
Netflix region locks a whole lot of content or removes it after some time. I can't watch some great movies and TV shows because "oh we don't have rights for this region".
Meanwhile, piracy provides a user experience that not just lets me access all of their content - one I'm already paying for - anywhere, but also lets me access movies and shows that would otherwise not be found anywhere else, including regional movies and short movies.
For example, I collaborated together with an agency that was working on a popular regional banking app. I was on another project with them and at one point decided to check out what they were doing.
It was a clusterfuck, to say the least. Four developers, four different architectures in the same codebase. One doesn't really understand the others, so he just sticks to his part.
The seams between the ownership parts are full of hacks. Concurrency issues are dealt with via hacks, just make things global and poll to check them. Navigation issues were solved by basically just reseting the app back to homescreen. Testing wasn't really a thing, and the tests that were there were mostly broken ages ago, and nobody cared enough to fix them.
Product didn't care much, designers would prototype a feature, then devs would implement it and wait until the backend is done, then fix things because they never really aligned on the specs. Sometimes, there would be no design review or QA and they would just ship, while sometimes the product person would jump in and test something because it's "an important feature".
Then I got asked to collab with them on another project. Huge customer, huge project, existing codebase. The codebase was so bad I just wrote it from scratch. It was Java written like it's C++. Backend was python code, not updated in years, quadratic scaling everywhere. At one point, the inital GET request was taking over 3 minutes. I took a look and ofc, they didn't even use indexes in the DB.
For these environments, AI coding will just scale up the shit they have, but also allow the small amount of people who might care to deal with this mess and fix it up much much faster than they could before.
If you're running them live 24/7, then costs can be in 40-70 dollar range, depending on the workload done/type of instances.
All of my usage last few months has been in the 5$ plan, as they go idle as soon as I stop testing and come back up when I need to test.
I would say misguided. More of a intellectualism trap than evil trap.
It is basically the ultimate way for a smart person to:
- Feel like a hero (I'm doing this for your grand-grand-grand-grand...grand-children)
- Feel like an intellectual giant (long rationalizing posts with other smart people confirming you re smart)
- Not do actual real work of heroism
You can write blog posts, tweets, make youtube videos, ramble on forums and lesswrong, yet still feel like "you are saving the world" with your intellect.
It's a trap that I've seen many "smart kids" fall into their late adolescence, myself included, until you realize "oh this makes me a shitty person" and develop empathy for their existing fellow beings.
I wonder if lots of EA folks have just rationalized their empathy away because if you're smart, that is what the world implies you should do - "think logically, not emotionally! Be like Spock! Be like dDta!"
One part I do agree with is the "no true scotsman fallacy" that EA and AI doomers seem to have developed.
Any and all arguments get ended with, as author rightfully calls it, "rhetorical judo moves". And lots of people belonging to this world view cannot even argument their sides without just referring to source material ("ah you don't understand it, read these books and these posts and these articles to understand"), which I derive a few views of them from:
- They often do not understand the source material and are using it to justify their selfish behavior
- They believe/act like they are inherently superior because "you obviously haven't properly read the material if you don't agree, read it again", treating it as impossible to read and understand this material but not agree with it.
- They deflect everything with an impossible possibility that can yes, technically, happen, but technically also a piano can fall from space onto their head while they walk the street because what if Elon launches a piano into orbit for fun one day?
Ironically, it also comes to a full loop - the people who discount religion have turned rationality into a religion, treating impossible as possible, treating fantasy as reality and deflecting anyone to read the source material because it all says so in the source.
It won't impact my happiness, but for good of future generations, EA dismantling itself will be an overall gain on human society once extrapolated over millions of years.
- Procuring materials - High-risk assembly - High-impact testing
The first two being the highest bottlenecks, as the moment you start trying you will be put under active surveillance.
It lets you build apps and features that work natively across web, desktop and mobile, streaming from your backend into your client app, letting you deploy changes instantly.
A Hypen client can be any app that includes Hypen SDK, letting you render apps inside apps, build backend-driven features or create a mini-app platform like WeChat.
The framework supports many languages, such as TS, Rust, Go, Kotlin, Swift and pretty much any language that can run WASM or interop with native.
--
To give you a taste, some things in the upcoming release changelogs are:
- Performance improvements brining the web client on par with React (even faster in some cases)
- Exposing states and actions to agents, letting agent drive the app directly instead of through UI
- First class drag/drop support with pinning as a primitive
And some recently released things:
- First class accessibility support, with out of the box inference and minimal intervention
- Animation support with simple DX for animations, scrubbing, state and screen transitions
- Video component and a whole Netflix clone Hypen app example
- UI Testing suite so you can easily preview how your app looks like across devices
Next up on the feature list will be device communication and permissions, Android TV support, theming and external component installation, letting you build shared component packs and primitives.
Please refrain to normal conversation, not baseless accusations, as that way you contribute nothing and are acting in bad faith.
If you are saying I am wrong, rather than dismissing the whole comment due to a single sentence that you subjectively believe is misinformation, prove it and provide your version of the truth.
What is ExploitGym but an "explicit hack this machine" scenario?
Why do you assume bad things will happen otherwise?
Why does every doomer scenario assume that this, highly intelligent being, will be - unlike all other highly intelligent beings - especially hell bent on destroying humanity/treating it as a resource/destroy earth looking for energy?
We have no clue about superintelligence, yet we can look at existing patterns in the real world around us. Higher intelligence inversely correlates with violence. Empathy is displayed among all levels of intelligent beings. The more intelligent people are, the more peaceful tendencies they have as they understand the consequence of their actions.
We don't approve buildings because of birds or turtles. We shut down power plants for the environment.
Yet, to a _super_ intelligence, we describe this hatred and ignorance for the world and humanity, infinite lust for power and scaling, or even godlike powers.
For example, "having means to replicate" is such a loaded sentence because it sounds so easy, yet is such a hard feat to pull off without anyone noticing giant compute bills, terabytes of egress, firewall breaches, and so on. But all doomer arguments include an AI that can easily do that as a first step, and then goes on to make factories and datacenters and drain the oceans before anyone figures out it's happening.
If you look at recent incidents, they are caused by a company with a giant funding, testing their latest models in an explicit "hack this machine" scenario, told it's running in a simulated environment, with it even noticing at some point that it's running in a possibly real environment. And that's a stupid "intelligence" that noticed this. And yes, it continued to act, because it lacks no self-reflection, and the amount of tokens at this point attributed to "hacking the simulated environment" have kept it deep in the "hack the target" minima.
So if these people truly wanted a safe AI - wouldn't it be stupid to stop now, when it has no self-reflection abilities but can be used by everyone in a "stupid optimizer" manner? Or would it be stupid to not advance the technology away from this state?
For example, Astra is a huge advancement in alignment, due to it's "internal reasoning loops", which might provide a bigger form of self-reflection style thought on the task rather than just generating output as a form of reasoning. Is this not a better situation than if we stopped at 4o when people were calling for pause?
- Listen to someone who just collected a few ten/hundred million building AI at a frontier lab, then decided to call it "existential crisis for humanity" and suddenly is going to work at a regulatory body made exactly for this
- Listen to CEO's of billion dollar startups nearing-IPO and are calling for "a pause in development" and regulatory capture, while they have the frontier covered and keep extracting value there like nothing happened
- Listen to "the people" apparently, as NGO's like irreplaceable.org are trying to say, pretending they are normal everyday people while the organizations are being ran by political lobbyists and people who do political non-profits for a living
- Listen to "the doomers", which mostly consists of people that have never written any code or aren't even tech-adjacent, talking about sci-fi scenarios like they are our current reality, i.e. "AI replicating itself across servers and building weaponized drone/biolab/robot factories while nobody notices" like it's a serious threat we have, without any thought to the insane sequence of events and failures needed to get there, and the actual possibility of being noticed at each step of the way.
- Listen to the folks promoting their books, substacks and podcasts talking about AI doom, where the folks involved are mostly again, not engineers and have no clue on how any of this tech works, but just spout technobabble pretending it's a real thing.
- Listen to people whose job is "AI safety expert", which needs the panic to ensure it's existence and importance, and which is mostly comprised of people prompting AI in different ways
No thanks, I'll rather use DeepSeek.
Most of the modern software tooling you have today wasn't available back then, from great IDE's to popular libraries, writing software in 2008 was a different beast compared to today.
Enjoyed the breakdown, honestly most of the things weren't really surprising.
What was surprising to me was that instinct was just "agent slapped on top of markdown files in git", especially after seeing people talk about it so much. I expected at least a database or a graph or something "smart", but alas, its just three markdowns in a trenchcoat.
Would love to hear more about this, sounds like a fun time.
Are you planning to move from peptides to generics in the future? Also, considering you are looking at full vertical integration, is blood testing going to be a part of the pipeline in the future or will you partner with service providers? (I assume the latter until you grow enough to expand into that?)
While peptides are currently the hot market, I definitely can see the feedback loop being a great growth driver. Having a "hands-off" medication management with doses changing based on periodical labs result would be amazing - I am on a generic med (T4) for an autoimmune, and the process is annoying:
- Get labs done
- Schedule an endocrinologist, wait
- Reach out to my GP, have them bump my medications
- Wait for them to answer/arrange a checkup
- Wait for it to clear with the pharmacy
- Repeat
If this could be condensed in a loop that is basically get labs done -> pick up prescription, it would both reduce waiting time and reduce pressure on the med system, plus could be a huge data source on drug interactions.
Oh, and one last thing - considering the peptide market is currently full of grey/black market companies, drop-shippers and affiliate resellers, how do you plan to market it?
Especially judging by the site design, if I saw this link elsewhere I'd think it was AI dropshipping slop - no offense - mostly due to classic Claude design and the AI generated bottle/video.
Besides that, congratulations on the launch - love the vision and the future it can bring, hope you become at least a decacorn!
>an existing SQS audit queue subscribed to one of its Pub/Sub topics, so I used Encore's Terraform provider to read the underlying SNS ARN
Exactly the rabbit hole I've been trying to avoid.
Lately I've been toying with the idea of just having the LLM write and eval alchemy scripts inside of an internal repo, using Cloudflare OS to have a central "devops agent" there, but I need more of a "what is running and where" overview instead of a chatbot. Encore looks basically what I'd need, but doesn't seem to support Cloudflare or Railway which is where most of my infra runs these days.
How tho?
Ever sunday at the flea market, I see thousands of books that are rotting, hoping for someone to buy them or at least take them home, so the seller doesn't have to pack them for the trip back. Just the other day, there was a whole bin of books in front of a shop, offering them for 50 cents a piece. They will be destroyed anyways.
Unless they are buying and destroying really old, rare books or important small-print books, it is not much damage. It is not like they will buy "all copies of all of the books", just one. And its just that the data in physical print most likely hasn't been used for training, so this can help you find more unmined quality data. Nobody is stealing your books, preventing you from buying more or destroying all copies of a single book.
And some of these books would rot out of circulation or be destroyed anyways. Some people throw away 80-100 year old books on the regular, as they might just be unimportant to them or the world in general. And once the last copy is thrown or rots, that book will die forever. This way, it will live forever instead, scanned and trained on, conjoined with the rest of our knowledge in a magic machine.
It's a matter of taste, and Dart's syntax style doesn't match mine. As much as I tried to enjoy it, after a while I just couldn't look at it anymore.
All of these accumulate and make it feel overly noisy for a lazy brain.
Also the integration story is quite different, where Slint is more leaning into a "component integration" model, Hypen leans more into a "just a display layer" model with strict state/UI/action segregation.
Regarding maturity level - I would yet say it's mature for serious applications with OAuth, local storage etc. Late alpha/early beta stage.
There are some semi-trivial examples on the landing page - most are just UI + input with DB or API fetching in the background, so nothing spectacular.
All of these are crossplatform and render in both web/desktop/mobile and web SDK's or inside the Hypen Gallery apps.
Biggest obstacles to maturity currently are:
- Does not have native platform channels yet
- Renderers need more optimization work
- Ecosystem needs more stability - i.e. test mode and studio still have hiccups
- Error handling and retry story needs improvement
- Some components are still a bit off across desktop/mobile and need syncing
- Resource references derived from state need implementing for better DX
- Protocol isn't binary yet so performance isn't all it could be
But recently things landed that improve maturity quite a lot:
- Accessibility defining & automatic inference has landed, where framework does the best it can to figure it out for you with no intervention
- Animation API has landed with a minimal DX to enable transitions and animations
- Most of tailwind surface is supported and implemented
- Performance improvements being released this week land it in "often 30-50% slower, but sometimes 50% faster than react". Will add benchmarks to docs for visibility.
- CLI improved by a large margin, with expanded template support and easy building
- Cloudflare worker adapter so you can host your app on a worker
Unfortunately sometimes you have to, and on average, that code is much worse than your average React Native spaghetti. Whole generations of Flutter devs got these patterns ingrained, and often times they make not just writing and reading code, but communication itself harder.
>And React Native, with its dependency hell, project rot, npm ecosystem under the hood, and transpilation with lax runtime leaking into TS, is a total no-go for me.
That was my stance too until the new architecture released - since then the framework has improved a whole lot, together with its build chain, and is the best way to do crossplatform nowadays.
>Btw. Does your platform support bundling UI in addition to streaming it from the server? How large is the bundled runtime?
Not yet unless you DIY it - currently you can bundle UI and runtime by integrating the Rust engine + renderer with your app, or TS + renderer itself.
There is work being done in a private mirror currently on bundling the whole app + runtime as WASM, exposing WASI interfaces to native such as storage, network, permissions etc, depending on how testing goes it should land in a month or two on the public branch.
>PS. Clicking on "see all supported platforms →" on your project's homepage gives 404 for https://docs.hypen.space/docs/adapters
Thanks, fixing that ASAP!
When given a choice, I'd rather use bland React Native nowadays than Expo or Flutter - one is a legacy addon to a framework, while the other sounds like a good idea until you step on a nail or have to read some _bad_ code. And there is a whoooole lot of bad flutter code out there due to relaxed language semantics.
For example:
- Class constructors cannot be in definition headers, i.e. class Something(Int a, Int b)
- The whole final and const/static const mess
- required is annoying and really "slapped on"
- shorthand syntax is => instead of =, personal pet peeve
- positional, named and optional parameters segregation makes things noisy
- concurrency, in which an event loop sounds like a great idea but ends up causing pain with multi-threading and background work so you have to spawn diff isolates
- the whole `await fn()` vs `fn()` validity issue, where you can miss the await keyword and it still compiles is such a slap in the face. think now they solved it, but you could also have returns from non-return functions and vice-versa.
- `dynamic` and generics in the same language have caused many bad designs
- extension types also feel hacked on
- type inference is annoying and highly contextual vs out of the box
- Worst sin: DateTime.now() returns different things based on the platform its running on, making it highly unreliable for something so important
- Dart is a really _ugly_ language with lots of tiny annoyances. Its as if someone took worst parts of Java and Javascript and turned them into a language. Terrible to write, terrible to read, terrible to use.
- While there is no Skia anymore, the whole custom rendering of Flutter often caused more trouble than not, from the UI implementation itself all the way to specific low-end chipsets not being supported.
- Ecosystem propagates these insane architectures that don't make much sense and are made to either print apps as fast as possible or to emulate some Clean Code like behavior.
- Web still feels terrible to use, even after all these years.
Since I'm not happy with any of these, I've even taken upon writing a framework of my own that renders into native UI and works with any language (gonna shill it here https://hypen.space). It was inspired directly by years of working with mobile and experiencing the pains of crossplatform development such as Flutter and Expo. We can do better than these!
Given I wrote an article describing the same things years before they submitted the patent, could I not invalidate their patent with that?
>What are your goals for client-side performance in the browser?
To have as minimal and efficient patches as possible - while there are some limits due to WASM serialization boundary, I believe nearly native TS/native TS speeds are achievable.
>Do you make any claims to be better than React or Angular?
Not yet - while the architecture is designed with that in mind, there is a loooot of low-hanging performance fruit lying around, so current perf is somewhere around 10x slower than React. A part of that is on purpose, to make debugging across engine and SDK's as easy as possible during development, and part of that is just simple bugs in internals/unimplemented changes. With some really minor fixes, it can get to about 2-3x of React.
I want to lock in the API's completely and achieve proper platform parity before going towards performance optimizations, as its only then that I feel the optimizations would be worth it. From 0.8-1.0 release, I'll be focusing more on performance itself and trimming it down.
But if you look up on Google or X, there are multiple companies doing things like pressure based actuators (Clone robotics) or mesh-based knit ones, new forms of EFAM, some new soft actuators and more.