hypendev

Can't really name them off the top of my head, sorry!

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.

I'm working on https://hypen.space/

It's a cross-platform UI framework for developing native mobile, desktop and web apps using Typescript, Rust, Go, Kotlin and Swift.

Currently it's aimed at "server-driven UI" where your app lives in the cloud but renders on the client, with full compilation to WASM packages coming soon. Of course, you can just embed the server/use it as a library.

Some cool things the framework does/has/lets you do:

- Renders real native components that look the same across platforms

- Out of the box routing system, tailwind support, accessibility and animations

- On the web, switch between DOM and canvas rendering with one boolean

- Embedding apps - you can embed Hypen in any app, but also embed any Hypen app into another Hypen app, letting you nest apps (i.e. the homescreen example)

- Deploy the whole app to CloudFlare just by using the adapter. Then you can have a whole desktop/mobile/web app running as a CF worker.

- You can build a mobile app feature in Hypen and update it by deploying to your backend, skipping app store reviews for bug fixes

- Build apps that share state across devices without building a whole sync layer

- Use DB as a data source - the current state can be persisted anywhere, so if you add a persistence plugin, you can use DB as a direct state source (i.e. have @db.messagess come directly from your DB)

- Make the app a normal part of your backend, use your stack, and just have a small Hypen part that emits the UI

- Let LLM's use your app - not via accessibility and screen reading, but purely exposing state and actions as tools. This is in progress as it's being built with the WASM target, but support will be soon included into the non-WASM builds too.

---

I started working on this about 6 years ago out of disappointment with the "mobile stack".

I've build a similar thing for internal use in companies multiple times over the last 10+ years, so I decided to build a public version too. And even tho it took me some time, and native/RN/Flutter got better in the meantime, I am still disappointed by all of them so I kept on building.

The original versions of it - parsers, engine, renderer - were written by hand in Kotlin, then got slowly migrated to Rust, but once LLM's got good enough the rest of it got built with AI based on my handwritten code and guidance. So it's not "vibecoded" into existence, but definitely AI re/written.

Exactly, the last year or two has been insanely innovative for actuators, with some new material combinations, approaches and multiple startups that are starting to scale up their innovations in this space. Give them a few years to sort out the vaporwares and the robotics revolution will begin.

>1. The PRs are across different related repos, so they literally can't be combined into one PR.

This would be such a insanely useful features for a small subset of power users that they will never deliver.

Why isnt refactor in its separate PR? Every developer with an ounce of thought would tell youn to:

>Do PR refactoring module A >Do PR with feature X + cleanup >Maybe PR with additional work if bigger

But couldnt you just create a PR2 that targets your PR1 branch? What does stack contribute that multiple PRs targeting each other dont?

i.e. like this where each one targets prior PR1 db_migrations PR2 backend_base PR3 adds_frontend_scoobydoodle PR4 adds_some_landing_page_thingy PR5 probably_have_to_fix_something

Or is stacks just a feature built to make this type of PR stacking easier to review?

It really hit a specific vibe. RIP to a legend.

This is so cool!

Would love a writeup on how you went at it and how the layers work, think the real juice is hidden there as Java ME is basically archeology at this point so it would definitely have some learning value. Even if your agent was the one dealing with it, still a dump of "weird things saw while dealing with JavaME" would be fun to read.

What a throwback, last time I played this was I believe on my Motorola v3 Razr, where I spent days playing Gang Starr game and Splinter Cell. And spent a few hundred on internet traffic and downloads, which were super costly at the time so my parents banned me from using internet/WAP on my phone for a while.

Also, if it could fit into 275kb, wonder if it could also be made to fit on the 128k SIM cards that run Java

You might have misread me - I meant in a time when LLM's are speeding up development in general, as now you can write giant interfaces and implementations without having to manually deal with glue code.

> If WASM would've worked as advertised, allowing fully fledged apps to run easily and natively in the browser with no fuss and 90% native perf, then basically all app stores would've been dead.

Working on that! I'm building hypen.space which is platform agnostic language & SDK for building native crossplatform apps.

It's a WASM engine at it's core, and while currently it doesn't have "package this app as wasm" capability but supports streaming/local apps only, that capability is currently being developed - together with WASI layers for all of the platforms.

That way your app can run either as a browser (DOM) app, browser canvas app, native desktop or native mobile app.

It's still early, but moving fast - I just added accessibility support, and the animation framework will be out this week.

Regarding the WASM disappointed, when I started building this about 6 years ago, WASM was in a terrible (barely usable without wasting a ton of time) state. Now that WASI 0.3 is out and LLMs have sped up development by a large margin, it's in a quite usable state to ship things to production without fear.

Android had a tradeoff - less vertical integration and more annoyances, a bit worse software quality, for a more open, customisable and utility-like experience. I loved that.

Now, the tradeoff is - less vertical integration, double the integration layer trash (Google & OEM) and a much more locked down experience. But the quality of it hasn't improved, it just got worse.

Doesn't make sense anymore. They can now do 99% of the same things, but iOS has a better quality OS, better apps and better vertical integration.

Not even vertical integration, actually just any kind. FFS it's 2026 and the recommended android way to send a photo to your mac/PC is "upload to google photos and hope it decides to sync".

Might be that German law covers for such cases, but at that point, I'd expect then the regulations and annoyances about starting a company be more high trust.

In our EU member country, one can do this without penalty, for years - and people have been abusing it consistently with only rare persecutions.

That system is silly.

I can open a company, work for a year, acrue debt, acrue tax debt, close it.

Nothing will happen. Company "estate" will be sold to cover the debt, which can also be nothing.

Because reasoning is an emergent byproduct of training it on all knowledge. It still doesn't "know" things in this form and just generates tokens, no matter how weird we spin it.

So if you don't train it on a large dataset of a lot of words with a lot of sensible connections, it won't be able to reason, as it won't be able to make proper connections between words and sentences.

You can try training a really small model and seeing the gibberish outputs when you train it on only a small dataset.

Minmaxing the dataset to extract maximum generation with minimal data does sound like fun, but if you want to build SoTA models as a company, the economic tradeoff of doing that vs slapping a few more GPU's together is terrible.

This is kind of a loaded question.

"Google" doesn't understand anything, as it isn't one being. Google has also as many average employees as any other company, and they will also come up with bad, corporate, ideas.

Honestly the worst part about the LLM age is that everyone is suddenly an "expert", and that is why we get shitty things like A2A or MCP or whatever the next "shiny" overengineered thing is.

Just like with any new technology, people will crawl out the woodwork to establish "standards" just so they can claim fame, money and attention that comes with it.

Similar problems here in Croatia, few reasons for it:

- Boom of AirBNB's and apartment rentals with tourism, with real low tax rates

- Limited liability abuse - company opens up, sells 30 apartments in a new building, build out the building, don't get any permits, just close the company down and open a new one. Legally, they are untouchable, and getting the permits is now on the apartment owners. Multiple friends live in such buildings, and maintenance is a PITA, trying to legalize it is a PITA, getting water/power is a matter of making shady deals with the neighbours, basically even living in it is technically illegal but not much they can do.

- Large influx of illegal money into the housing market (we have no law to investigate source of income), so money could be laundered easily.

- "Legalization procedures" where if you built a house before a certain year, or just started construction, it could be legalised. This caused people to build "fake roofs" and then claim it as a real building later on.

- Recently, immigration joined too - workers from non-EU countries are now allowed to get work visa's, and a lot of landlords are renting out a small 50m2 apartment to 10 people at the same time for ridiculous prices. The poor workers have to share bedroom with 10 other people, which is a terrible living condition, causing accidents like a whole floor collapsing due to 50+ people living in the building. While it's not legal, inspections are rare and the grey market is thriving.

- And my favorite - as a large number of apartments are bought as investments and uninhabited - around 22% in the capital, according to official estimates, with about 500k free total, in a country of 3.5 million people - the government got a great idea:

They will free up more housing, by offering the landlords of the empty apartments to rent thenm out with government guarantees. This means the government will pay them out 60% of the future rent money immediately, so the landlord can buy another apartment as an investment immediately using that money, and just get richer.

Now, we're in an interesting situation:

- Prices have risen quite a lot, like 3x over the last 5-6 years

- Existing landlords will get funding from the government to buy more apartments

- Meanwhile, new loan rules came out, prevent people from getting a loan that is more than 45% of their salary (after subtracting the costs, including your current RENT). 10% of the value has to be provided immediately by the buyer, and after loan payment and living expenses, you need to have at least 900 euros remaining each month from your salary.

In a country with a median salary of 1300 euros, with median rent being about 500-700 euros, this puts a lot of people in a locked position - you can't get a loan to buy, because you are renting. So from the 1300 euros of your salary, the bank subtracts 500 euros of rent as your "living expense", leaving you with 800 euros monthly total, which is under the legal limit for getting a loan, even tho once you buy the apartment you would not pay rent anymore.

So to get a 30 year loan to buy a 50m2 apartment, you need to have about double the median salary.

Now, they are talking about property taxes, which will force people barely making ends meet to sell the inherited land/houses/apartments for cheap to people that can afford it.

> but the mold in the bathroom and roaches in the kitchen definitely are.

I would not agree.

Having lived in low budget apartments for quite a while as a student, a lot of these things are "a norm" and not really the renters fault, but the owners.

Examples:

I moved into an apartment that was "subterranean" level, meaning not fully basement but also not ground floor. When we were looking at it, it seemed fine, everything great, but bathroom had the tiniest vent window ever. I asked about the mold, and the owner was like "oh no, no need to worry about that, the ventilation is quite good actually even tho the window is tiny, we made sure of that" - and at the moment, it seemed so, the air was dry and there was no "humid" feeling about the room.

Well, well - the bathroom was humid as hell and would stay that way after the first shower, even with all the vents open and ventilation turned on. Even worse, the humidity in the rooms was so high that the paint on the wall stayed fresh for quite a long time, painting a few of my shirts that touched the wall. When summer came, the rooms became a hotspot for mosquitoes, and the owner would be like "ah just close the windows" - but that kept the humidity and heat in, making life unbearable and causing mold to erupt (also, because a lot of it was just painted over!! just painted over mold, like what the fuck?)

Another one had homeless people which started living around the building, leaving food and booze all over the place. To make it worse, large trash bins were outside our building, which lead to roaches coming in from the bins and from the balconies, under which the aforementioned people "lived". We couldn't do nothing about it, except ensure that there is minimal reason for them to come to us, lay traps around and ensure we have anti-bug powders around the perimeter. I talked to some of the neighbors that lived there for years and they said it happens nearly every summer.

The bed in the apartment started falling apart at some point, and going to fix it I noticed the bed _was fixed_ already, even tho it was said to be new - and it was fixed badly. The same owner charged me 2k for a "designer couch" that "we ruined", even tho before us moving in the couch was welded and nailed together, as it was obviously broken before, and the owner did not want to admit it even when shown the photo evidence.

Once I moved out, I saw what happened to the apartment on the next listing - the owner just painted over the kitchen cabinets, painted the bed, put a new mattress on it and said "all furniture is new".

So a lot of things might sound like they're the authors fault, but having met one too many "bad actors" in the renting game, I'm quite sure that some of these things might be the owners responsibility.

Thanks!

Honestly, in one iteration of Hypen I actually added a `Script` component, but after trying it, it already felt both dirty and confusing, so it's a definitive no for the near future :)

Regarding accessibility - I've also burned myself quite a few times on that bridge and that is why there won't be 1.0 without it being fully solved - I don't want devs to have to retroactively think about it or for it to have a second class implementation.

I believe there is a solution out of the box that should cover at least 80% of the most common needs, and provide primitives for more custom cases. Hopefully this time I can nail it... fingers crossed!

I also have a horse in this race, would love to have it included!

I'm building Hypen (https://hypen.space), a UI framework with a DSL that works in in Rust, TS, Go, Kotlin, Swift, and all over the place, as long as you can use WASM or binaries.

Some cool things about it:

- Renders natively on Desktop, Web (DOM and Canvas), Android and iOS.

- Streaming-first (SSR), so you can stream native apps from the server

- Custom tailwind parser so it supports your favorite shorthands

- Support for streaming apps from CF workers with 5 lines of JS/TS

- You can embed any Hypen app into another Hypen app like its an iframe, with just 1 line of code

- Has a custom "browser" for Hypen apps, both on desktop and on mobile, so you can easily check how your app looks anywhere

- Coming soon - stdlib and WASI interface to enable full WASM portability across platforms

Note: Desktop support is still a bit early and needs more crossplatform testing

I started building this years ago, first manually, now accelerating it with LLM's which are incredible for mindnumbing tasks like writing frameworks like these requires. Its still in an "early alpha" but it's getting closer to maturity and a "stable beta" by the day, hopefully fully stable 1.0 by end of the year.

Sorry, my bad, might be 97 running on windows 98 - but yes, this is a giant corporation serving hundreds of corporate customers and a few hundred thousand private ones, using nearly 30 years old software because the management does not see reasons to upgrade and spend the extra cost associated with it. New machines and Windows XP are only used by upper management.

Worst part?

Their whole software stack is running on some version of Visual Basic, written by a dude that did not trust "others code" so he wrote everything from scratch, and retired about 5 years ago.

Nobody knows how any of it works, or has any clue. The company will continue to run it and pay him for consultations as long as he is able to do it.

It is still "in distribution", that is why when its "distributed" properly, it will surely add much, much more value to the economy.

But it is a generational opportunity - we can remove a lot of barriers that come with knowledge, lack of it, access to it and more. Someone can easily get pretty on point medical advice without access to doctors. Get specific engineering advice without engaging with those engineers. We can apply common sense or specific knowledge on scale - in a world where about 50% of people have IQ under 100 and access to knowledge is gated behind lines and payments, this has a huge chance ot improve their lives.

And there is the whole shadow inference economy - just for example, a few corporations I have worked with in insurance and telecommunications have been slowly introducing it inside their workflows and their data tooling, being able to clean data, tag it, analyse it in a way that before would probably cost them billons in human costs.

One of them has a database going back to the 80's, with data being formatted and reformatted in all shapes and sizes, coming back all the way from paper records for some of their oldest clients. Cleaning this up was unimaginable before as a "something we can do in a day" project, but was more of a "possible with insane costs". This lead to all further activity being shaped by decisions someone made 40+ years ago, details being lost, data being thrown away or saved in random notes.

And there's millions of companies like that all around the world, which can now do "impossible" and become much more efficient and productive for a much cheaper price and in way less time than ever.

I wouldn't argue the same.

My parents love using ChatGPT, asking it all kinds of questions. My mom discovered Claude and helps her immensely with her job - where she would have to take it home and work a few hours to be able to finish the tasks on her computer, as her company that still uses Office 98, now Claude does it in 5 minutes.

They fixed so many random issues using it, it is insane. My dad had a bike issue which would otherwise be solved by either trying to find obscure manuals from 20 years ago on random forums with me translating it from english to our language, or by taking it to a mechanic which could take months. This way, he just snapped a few photos, said what the problem is, and in a few minutes he had the fix.

I've built software that uses LLM's for a specific usecase - besides general adoption, professionals in the field contacted me and thanked me for making their lives easier, as the tasks would often take a lot of manual work. These people are earning way more from using my software, than I am from their subscriptions, which is still about 20x more than my API costs are.

While most non-dev people are behind the curve, the impact it has on their lives is becoming bigger and bigger by the day.

Back in the times of GPT3 text completion, right before the API came out, a contemporary art museum asked me to collaborate on a project. The project was supposed to include a chatbot, and I was like okay I can probably hook something up.

Then I remembered the "text completion LLM thingy" I saw on HN, and tried it out in the playground. Once I gave it an IRC style example of a conversation to complete, I was like hm, this could work. Then I figured out I could "sort" people into different groups based on personality using the same text completion engine and some answers they provided. Then I noticed I could have it provide me with JSON directly.

That's when I realized how big this could be for code and data analysis - even tried to convince an at the time cofounder to pivot into AI coding, but to no avail.

Once the API was released and the art project chatbot got launched (and the theater show associated with it, which even won some awards), people who used it loved the chatbot, got into heated arguments with it, tried to teach it things, talked about their lives and were sad when it didnt remember something.

That was when I understood the social impact this could have on people - they really behave like its a person on the other side. They show interest, think it displays emotion, try to entertain it, be polite, ask about its thoughts and hopes and dreams. And even when they knew they were talking to a machine, they were still trying to be friends and make it happy, which was quite beautiful to see.

Later on, I had a third oh shit moment - once the 3.5 API was out and about, I prototyped a Rust code generation harness for a client, akin to a primitive claude code. That was the "I'm getting a bit worried" oh shit moment, and it caused a lot of reflection and thinking about the future. And I happily welcome it.

What is a larger scaler for you? What is "outside harness an LLM"?

What is _the proof_ if all the proofs are not _proofs_?

I don't babysit my LLM based services which are used by coaches and clients around the world. One of my LLM based solution get 30-4k daily hits and I have users coming back on the regular to use it. without babysitting, doing things that would take them hours of manual work and research.

I don't babysit the developers I work with and our clients, which both use LLM's themselves and at scale with their clients, serving all kinds of LLM powered services to millions of users worldwide.

You are not "seeing" the large adoption because:

- The technology is "a few years old" in its usable state - The corporate adoption cycle is slow - You have to understand the technology to use it in a good way, which most corporate devs and PM's do not

So it will take a bit for the "obvious" adaptation on large scale.

But you won't "know" when the large adoption happens.

Silent inference is growing every day, and that is what real adoption looks like - not an LLM being in your face chatbox, but running in the background, sorting, finding, fixing things, aligning data, figuring out analytics, tuning the ads, cleaning the datasets.

Perry definitely looks interesting, was just looking at getting one of these to include into my framework.

Would love to see more about it, or see more about the actual compiler docs.

While the UI framework part is neat, I prefer not to force everything into TS. Combining it means UI definitions and semantics get mixed into AST, making the unbundling of them a humongous task in itself.

Exactly the reason I built my own with pretty similar native UI semantics which supports Rust, Go, Kotlin and more (https://hypen.space) - would love to integrate Perry with it to compile TS apps directly into the runtime - but while the idea itself is great, looking at the documentation makes it hard to implement, and a lot of parts seem confusing.

Can I just use the compiler without the rest of the framework? What is the architecture? What are the limits?

After digging through the documentation, I'm unfortunately just more confused honestly. There are dozens of packages and slop markdown files such as `BUG_STRING_COMPARISON.md` and or `PERRY_UI_IMPLEMENTATION.md` which is an instruction file left for the LLM that just makes me trust the project less.

So while the idea is cool and the performance seems cool, the AI slop presentation would definitely need improvement. Adding a human touch would make it much, much better, as one could actually understand what they are dealing with.

Motorola's history is so unfortunate.

They were a great brand, cool phones, one of early Android players.

After being bought out by Google, Motorola had some of the best devices out there with stock android, especially in the budget segment (and loved among android devs).They had one of the best smartwatches in the game at the time - Moto 360 (2014!!).

Then, after dropping the Nexus 6, Google stripped the patents and sold them to Lenovo. For a while it was ok, even dropping the relatively innovative Moto Z which had all the cool "modular" addons, played with it for a bit and seemed cool.

And then, things seemed to start taking a turn for the worse as Lenovo kept enshitiffying it more and more, using the brand name as a wedge in the market in which they are basically forgotten. They have the Razr brand which is cool, but the segment that was their best (budget phones) is now ruined with adware so they can extract every bit of value from it.

Such a sad ending for a company that was so early in the space.

Interesting, agents seem to always fall in a spectrum between overengineering and underengineering, where they will either go wild and overengineer a simple solution, or do the minimal effective thing to pass with "//TODO fix for prod".

It's the same patterns we see with human devs, just applied on codebases at scale.

The conclusion has an interesting tibid tho - maybe the frameworks and their developers should start including more abstract focused primitives instead of just the low level ones, similar to what Encore did, as that way the behavior is encoded at the framework level.

Thank you so much! If you ever have any feedback or wishes for the Go side, feel free to reach out!

I'm actually working on that - it's called Hypen - (hypen.space).

You can build your core in Go or any other supported language, and write the UI in the Hypen DSL.

While desktop is still in the works and should be out in the next week or two, currently the alpha supports Native iOS, Android, Web and Web Canvas, and just like mobile, the Desktop will be _real_ native.

I mostly agree with the article - I believe the differentiation should be between documents and applications.

While HTML serves its purpose, especially for documents, the modern web is a giant mess of that legacy, combined with unfriendly ergonomics and glue/hacks built on top just so we as developers can have better DX for creating complex software on top of it.

Building a browser means having to deal with all that legacy, wether we like it or not, so most of the browser market got captured by the big players who have enough manpower to cover all those edge cases. That also means we have to deal with whatever technical choices or bloat they make, causing an infinite stream of issues, from memory usage, to size, to limitations that don't make sense in 2026 but are still there because someone 20 years ago decided to write them like that. As I deal with mobile webviews a lot in my daily work, I unfortunately had to get familiar with quite many gotcha's and edge cases, and some are just... absurd in this day and age.

I believe we need a separation between an application layer and the document layer, and especially between the UI language and the actual application code - script tags serve their purpose, but again, they are a hacky solution with its own bag of tricks, and those tricks impact all of the software built upon it.

Now, a bit of a shameless plug I've been working on something to fill that gap, at least for myself and hopefully for others who encounter the same issue - it's called Hypen (https://hypen.space) and it's a DSL for building apps that work natively on all platforms, with strict separation of code/UI/state, and support for as many languages and platforms as I can maintain, not "just javascript". While currently it's focused on streaming UI, it's built with Rust and WASM at it's core and will soon allow fully "compileable" apps.

While it may not be the future of software, once you get into building something like that, it becomes obvious that the way we are building now is at least wrong, and at best kafkaesque.